... and of course, 2 reboots later, and it looks like the screen reset code
is still there. I have my display back after boot!
... for a few minutes, anyway. I just plugged in USB to add some juice then let it sleep. Pressing the button later to wake it up has it
again in the low-contrast, too bright mode. Hmm ...
Hi, All.
Hope this is the right place to post.
I just upgraded to RockBox 3.3 and I'm now getting a problem with the screen. It has long been the case with my unit (though I think I heard other describe the same problem) that the screen will get stuck in a too-bright/no-contrast mode, sometimes after booting, sometimes after going to sleep. The iRiver firmware also suffered from this same problem.
If I tilt the screen top waaay forward towards me I can juuust about read what is on the screen. But it is well short of awesome. Playing the System settings for the display does not appear to have an effect (though the LCD output power does respond, but the screen stays looking like someones slammed the gamma value up to 11).
The thing is, RockBox 3.0 appeared to do something to fix the problem. When version (-r18607-3.0) booted, the screen would start bright, then just before showing the menu, would 'reset' into normal mode. It would
occasionally go into this bad mode after a sleep, but now it looks like it is
always in this too-bright mode with 3.3.
This is totally guess work (and you can tell me to RTFS -- I'm a programmer!) but .... Has there been some sort of LCD driver initialisation removed for the iRiver screen? Can it be put back?
In fact, the 'kick LCD in pants' code only appeared to function in 3.0 at start-up. ie. It was only at that point when I would see a too-bright screen become normal, whereas I think perhaps it would need to function for
every wake up.
Cheers!
[Attached is a cruddy picture of the screen in this bad, too-bright mode, tilted at the very slight angle that makes is possible to view the screen content].