Rockbox

(Confirmed this in 4c6c8cd-130926, discovered in build from several weeks earlier)

If ‘Voice Menus’ are enabled, entering the Recording menu will freeze the player…usually before the entire screen is redrawn. Although I can still hear the sound the mic is picking up, the player is locked up, and removing the battery or super-long-pressing of Power is required.

During my testing, I was able to randomly get it to -not- lock up, but it was like a 1 in 50 occurance…tried all formats/sample rates/etc. When ‘Voice Menus’ is -disabled-, all formats/rates/etc work fine.

Thinking it was a problem with my config that I’ve been using for years, I tried with a clean config.cfg (well, deleted and let it regenerate), and narrowed the cause down to the spoken ‘Voice Menus’ being enabled.

The setting works similar to the autoresume dirs: Directories are seperated
by colon, e.g. "/Music:/Podcasts". Default is "/sdcard" on android, "/" on
all other targets.

A maximum of 8 dirs can be selected, the setting cannot be longer than 80 chars.

Note: There's one problem. If you specifiy "/Music:/" (or any folder and one if its parents afterwards), then /Music is scanned twice. It's tricky to fix, and I'm not sure if it's worth it. This does not happen for "/:/Music" as it can be detected more easily in this order (and this is already implemented).

This tracker task will be used to house my Summer of Code work. For information about the goals of the project please see http://www.rockbox.org/twiki/bin/view/Main/PluginLocalization . Please read the comments and the descriptions of each patch.

Latest patch:
July 22

I’m using the latest Dev build for the Fuze+. SanDisk Sansa Fuze+ 5ef1e2d. Same issues experienced in v3.12 stable.

The screen, for lack of a better term, jumps when navigating in upside-down mode.

http://youtu.be/dRfiBtMx2to

According to the manual, to exit the EQ settings page you press the back button on the fuze+. This doesn’t work. I tried all key combos and none work.

Alarm wakeup doesn’t work reliably. It is unclear whether the setup is wrong or the wake up is. It might be that the player wakes up before time because of a small press on the power button and thus somehow forgets about alarm.

Hi, thanks a lot for all of your coding efforts, support, etc. I noticed that the WPS layout changed slightly after installing the latest dev build.

===

Problem: An unexpected indent appears in the WPS after installing the latest dev build on a Sansa Clip+. Please see attachment for an example.

Steps to Reproduce:
1. Install 3.13 with Blind theme
2. Play some tracks to see WPS
3. Upgrade to latest dev build
4. Play some tracks to see WPS
5. Problem occurs here: there’s an extra indentation after the “{current track number} / {number of tracks in playlist}” text, at the bottom-left of the screen.

Player: Sansa Clip+
Rockbox version: 1879de7-140525
Binary: rockbox.sansa
Size: 582384

Additional: Possibly related to #12953

2. Installation
Installing Rockbox is generally a quick and easy procedure. However before beginning
there are a few important things to know.
2.1. Before Starting
Supported hardware versions. The Clip v2 is available in multiple versions…

this should read :”The Clip is available in multiple versions…”

This patch adds more touchpad functionality to the game. It is possible to play by selecting the pieces directly instead of using the simulated buttons.
The changes are:
1. Added touchpad_get_mode to the plugin API.
2. Added menu entry for touchpad devices the switch between button mode and direct mode.
3. The user’s default touchpad mode is save during start-up of the plugin and restored after quitting.
4. The direct input mode is set only during the game (not in menu or view).
5. Extended play loop to handle BUTTON_TOUCHPAD event.
6. A piece is selected by clicking twice on it, moving is also done by clicking the target field twice.

The patch has been tested on the COWON D2 and also seems to compile fine for devices w/o touchpad. The patch has been created with

svn diff -x -w apps > touch_chess.diff

in the root directory. It would be nice if someone could test this (also on non-touchpad devices) and give me some feedback (bugs and improvements).

This is a rockbox version of the simple word game called “Target”.
Rules: (stolen from The Age newspaper website)
“See how many words of four letters or more can you make from the letters shown in the grids.
In making a word, each letter must be used once only.
The word must contain the centre letter and there must be at least one nine-letter word in the list.
No plurals or verb forms ending with “s”; no words with initial capitals and no words with a hyphen or apostrophe are permitted. The first word of a phrase is permitted (eg inkjet in inkjet printer).”

Currently it only works on H300, iPod Photo and iPod 5g DAPs, but I plan to expand this to all bitmap targets soon enough.
The games are either user selected or loaded from the file target_wordlist.dat, I’ve included 10 puzzles, but there are heaps more on The Age newpaper’s site (www.theage.com.au).

HI, is there a way that you could add a “Single”
playmode, so it stops after playing one song, instead of
repeating all, or repeating single? That way, it could also
be used as an “auto-off”, where it shuts off after one
song. Also, and maybe this isnt possible, but you could
have an option to play X number of songs and then stop,
where the X is configurable.

All settings should be listed there (even more so settings which cannot be set through the UI), but root menu order is only described in advanced_topic/main.tex as of now.

I have a Sansa e260 player and currently Rockbox 3.11.2 running on it.
I got a shuffled playlist with all of my music in it (added to the playlist using the insert function and reshuffled afterwards). When I want to listen to one or more specific songs, I enqueue them with the queue function (in play mode select song, album etc. from database → context menu → Current playlist → Queue).
This works fine in most cases but when there had already been a queue that ended the song before, the song that I want to enqueue is placed before the currently playing song (which is the first song not any more part of the former queue) instead of after it.
If I use the feature "Queue next" the song, album or whatever is correctly placed after the currently playing song. After having used "Queue next" once, other songs enqueued with the "Queue" command may be also placed correctly at the end of the new queue. I believe to remember some strange behavior though when in that case the song was also incorrectly placed as described above.
I tried mp3 and ogg files and the behavior was the same regardless of which file format was used. It also doesn't matter if the song is played from the player's memory or from micro SD card.
As soon as the second song after the queue is playing, enqueued content is correctly placed after the currently playing song again.
I have experienced this behavior for a long time now and with different Rockbox builds on my player.

To reproduce the behavior:
1. Have a reshuffled playlist (created using "Insert" command, then selecting "Playlist" → "Reshuffle" from the wps context menu) with some songs in it
2. Listen to one of these songs which is not the first or last one in the playlist
3. Enqueue a song from your database via the context menu (This song should be placed directly after the currently playing one)
4. Play the enqueued song (or a part of it)
5. Play the next song in playlist
6. Now enqueue another song (This song should now be placed directly before the currently playing song in the playlist)

I have hardly any programming experience at all but it seems to me that somehow there exists some sort of marker that indicates the end of a queue and that this marker is not erased immediately after a queue ends but "one song too late"?

“First Keypress Enables Backlight Only” doesn’t work on the 5G iPod. For example, if that’s enabled, the backlight is off and I press next track while at the WPS, Rockbox will go to the next track.

It seems like clickwheel event(s) generated when I touch the wheel turn on the backlight. When the button is pressed, the backlight is already considered to be on and the button press performs its usual action. If I carefully hold my finger still on the clickwheel, let the backlight fade, and then carefully press a button without moving my finger on the clickwheel, I am able to turn on the backlight without causing anything else to happen.

I don’t know what to do about this. Requiring a physical button press might be annoying. Removing this option on affected targets might be okay, because it’s easy to turn on the backlight by touching the clickwheel (and that doesn’t seem to cause anything else to happen). Another possibility is to require more or specific wheel events.

I set player type to iPod 5G because that’s all I have, but I expect this problem also exists on other clickwheel iPods. This problem exists on r20079 and r20033.

After upgrading from 3.0 to 3.1, the “Beep” sound (enabled in Settings / Playback Settings / Beep Volume) now sounds very distorted and fuzzy.

It sounds this way on any setting. Strong, Moderate or Weak and with the player’s volume on any setting. It definitely sounded like a normal clean beep with 3.0

This is on an 80gb Ipod 5.5 with Rockbox r19569-081223

I’m not sure if this should be under “Music Playback”, as I don’t seem to hear the distortion and fuzziness when playing mp3’s.

Mike

as3525
Version: 91b52a1-120122

Running on Sansa clip zip, unable to play the following .ogg file (I can't try it on other Rockbox versions, maybe someone can?). Works fine played any other way.

www.quik.clara.co.uk/Wontplay_inrockbox.ogg

(too large to attach directly)

Build 21245

I have ''Start Screen' set to 'Resume Playback'.

When connecting the Ipod (from OFF) to the PC the Ipod boots and USB mode starts but also playback (the play > sign is display on the title bar).

The Ipod is not shows and not mounted on the PC.

On disconnecting USB I get 'data abort' and have to hard reset.

In the "Scroll bar width" screen, the value used to show the width selected is the previous one, not the current one. The first value change has no effect.
Anyway it seems that the right value is stored: if you select a value and exit by the screen, when you re-enter in it, the width is correct.

Priority low.

Referred to r22406.

The OF ide_power_enable routine sets some GPIO _ENABLE bits to zero when enabling power and sets them to 1 when disabling power. This makes a difference of about 1 in 4066_ISTAT ( FS#9728 ) on my 30 gig iPod, which probably means saving about 0.75 mA. But if 1 is enable, why does enabling pins save power?