This is the bug/patch tracker for Rockbox. Click here for more information.
Quick links: Bugs · Patches · Rockbox frontpage
FS#10926 - Backlight off causes track info to freeze
Attached to Project:
Rockbox
Opened by Mike Holden (mikeholden) - Thursday, 21 January 2010, 12:01 GMT+2
Last edited by Jonathan Gordon (jdgordon) - Tuesday, 03 August 2010, 09:28 GMT+2
Opened by Mike Holden (mikeholden) - Thursday, 21 January 2010, 12:01 GMT+2
Last edited by Jonathan Gordon (jdgordon) - Tuesday, 03 August 2010, 09:28 GMT+2
|
DetailsOn my H340, once the backlight fades to off, the now/next track names in the WPS freeze. They remain frozen once the backlight comes on again (due to button press), even though playback has now progressed onto subsequent tracks the track 1 & 2 info remain on screen. Other info (track progress, time remaining etc are still correct, just the track title, track number etc are stuck.
This is tested with current CVS r24271, and a "clean" set of settings (i.e a fresh .rockbox tree from the build, all default settings). To reproduce: 1. Play a playlist or directory with multiple tracks (at least 2). 2. Let backlight fade to off during 1st track. 3. Wait until track transition occurs to track 2. 4. Press Vol Up to activate backlight 5. Note the track names displayed are still track 1 & 2, not track 2 & 3. |
This task depends upon
Could it be that the WPS isn't updatedwhile the backlight is off - even on targets where the display can be read without backlight.
But they aren't refreshed when the backlight goes on after a track change and don't change unless you launch & exit the file browser.
If the refresh is time driven, then it's longer than the backlight fade off timer (30s maybe?).
Main LCD: not readable when backlight off => no update when backlight off, to power consumption.
Remote LCD: readable when backlight off => update every time.
The problem seems to be that when you turn backlight on, the screen isn't automatically refreshed (maybe it's trying to fast and the screen still says that it's off?).
It's the same build that the last time I checked and from wich I wrote that it dind'nt work. Quite strange.
I don't know what's happening, maybe to much work ^^
I'll continue to check to see if it's really ok everytime.
Sometime the infos are refreshed, sometime they aren't.
Can't find a way to easily reproduce though...
in 27666. let me know how it goes
FS#11514) and uses the default.Lines 5,7 and 8 need updating due to skin syntax changes. Here are the updated lines:
%s%ac%?ia<%ia|%?d(2)<%d(2)|%(root%)>>
%s%ac%?id<%id|%?d(1)<%d(1)|%(root%)>>
%ac%?iy<%(%iy%)|>
I did notice that the progress bar got broken? Did progress bar wps syntax changed recently?
FS#11514) and uses the default.