Rockbox Technical Forums

Support and General Use => Hardware => Topic started by: kpapr1 on June 14, 2010, 07:50:00 AM

Title: Release 3.6 didn't solve FS#10926 on my iriver H300
Post by: kpapr1 on June 14, 2010, 07:50:00 AM
The FS#10926  - backlight turning off stops track info being updated doesn't seem to be solved on my iriver H300. Back to V3.3 again.

Has anyone else mentioned this?

Thanks

Costas
Title: Re: Release 3.6 didn't solve FS#10926 on my iriver H300
Post by: Llorean on June 14, 2010, 08:06:02 AM
You'll notice the task is currently opened. There's no need to bring it up here as long as there's an open bug report - that means it's a known issue.
Title: Re: Release 3.6 didn't solve FS#10926 on my iriver H300
Post by: kpapr1 on June 15, 2010, 08:49:30 AM
Yes, I know it's an open issue, but release 3.6 states that the bug has been fixed. This is why I'm bringing it back.

Fixed bugs

Since the release of Rockbox 3.5, the following bugs have been fixed.

Core

    * FS#9072 - iPod color/photo battery voltage invalid
    * FS#10591 - iPod nano reboots on idle poweroff when plugged in
    * FS#10913 - File Browser not updated properly upon microSD insert/removal with dircache enabled
    * FS#10926 - backlight turning off stops track info being updated
Title: Re: Release 3.6 didn't solve FS#10926 on my iriver H300
Post by: AlexP on June 15, 2010, 09:51:24 AM
Right, that's my fault (mainly) - when writing the release notes I saw that since 3.5 a fix had been committed for it and the bug was closed, I just then didn't notice that it had been re-opened.
Title: Re: Release 3.6 didn't solve FS#10926 on my iriver H300
Post by: kpapr1 on June 15, 2010, 04:00:42 PM
No problem my friend  :)

Has anyone else this issue? I made a clean install this time but the problem is still there.

Title: Re: Release 3.6 didn't solve FS#10926 on my iriver H300
Post by: Serenity on June 15, 2010, 09:55:01 PM
Confirmed--my iRiver H330 ;) has the same symptom; when I press a button after the backlight turns off, the screen comes back but the play info seems to have frozen.

It's odd, but it seems like with conditional tags (same line displays current track and alternates with next track every three seconds), some information behaves correctly (next track displays and scrolls fine for three seconds) until it switches (current track does not display; next track simply freezes for three seconds, then resumes scrolling as usual).

I haven't tried it on a wide variety of WPSs, though.

I imagine they're working on it as best they can; as long as my music keeps playing, I'm fine with it.