Rockbox Development > New Ports
SanDisk Sansa c200v2, m200v4, clipv1, clipv2, clip+, and fuzev2
Jennifur:
--- Quote from: Xanikseo on June 01, 2010, 04:01:56 PM ---This is gonna sound trivial compared to bricked fuzes and bootloader-patched-fws not working, but the backlight doesn't fade in smoothly anymore on the fuzev2 :P. It kinda switches on, off and on again, without really fading in nicely. This has been going on for a few days I reckon... Sorry I didn't report this earlier
--- End quote ---
Make sure Backlight Fade In and Backlight Fade out are on. Its under Settings -> General Settings -> Display -> LCD Settings
Xanikseo:
Backlight fade in and out are both set as yes in settings as always.
I've noticed that backlight fade in and out are fine just after you switch on. But as soon as you play a file, fade in is not smooth, even if playback is paused, and no matter what screen you are on.
Ah! I stopped playback altogether by holding down home, and fade in and out are smooth again.
Rob2222:
Xanikseo:
Its more probable that the new units check a flag/byte/mark in the new firmware at a specific location, that the old firmware and the RB firmware doesnt have.
Even more player has a reserved (hidden) storage area where the first half is the firmware-file-data and the second half has data, too.
In the data in the second half of the reserved space can be a difference, too.
But to see this data you have to open the unit and connect it in the "recovery" mode like found out and described by funman in the SansaAMSUnbrick wiki article.
BR Robert
Xanikseo:
--- Quote from: Rob2222 ---Its more propable that the new units check a flag/byte/mark in the new firmware at a specific location, that the old firmware and the RB firmware doesnt have.
Even more player has a reserved (hidden) storage area where the first half is the firmware-file-data and the second half has data, too.
In the data in the second half of the reserved space can be a difference, too.
But to see this data you have to open the unit and connect it in the "recovery" mode like found out and described by funman in the SansaAMSUnbrick wiki article.
--- End quote ---
Ah ok, so the rockbox bootloader modifies the part of the fw file which the new fuzes check, or at least inserts code above the flag/byte/mark which is checked.
There was some talk a few weeks ago about some byte being different in the new 02.03.* fws. I take it this is related...
Rob2222:
But the "bad" fuzes accept 02.03.31 AND 02.03.33.
BR Rob
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version