SanDisk Sansa c200v2, m200v4, clipv1, clipv2, clip+, and fuzev2

[smartboyathome]

You probably know about this, but I thought I would mention it anyway. I was playing around with a build I checked out last night on my Fuze v2 and found that with some of the applications (especially some games and demos) you get flickering and some of the colors get distorted. In addition, it seems that you can't exit the chess game unless you completely reboot the device. I'll try to build a new build today and see if I can find any more bugs in it, so far great job guys!

EDIT: After more testing, doom doesn't work giving error "Undefined instruction at 30134348" (I wasn't expecting it to work, just testing), and the text editor completely crashes the player with a black screen.

[wildmetal]

Greetings!
I have tried the build from 10/04 and it gives me a white screen when entering in rockbox.
I'm using the from 09/04 and the playback works well, i have tried the game doom but it doesn't work.
I can play bubbles while listening to music but the screen flickers at the botton and this game exit fine with out any problem.

[funman]

Some plugins leave me with a black screen when I exit them (Tested on the Clipv2/Clip+/Fuzev2), but keys still work (I can power off fine).

For example: chopper, demistify

I commented out backlight_use_settings() in chopper.c and now it works fine.

backlight_use_settings just reset the timeout to the global_settings value, so it seems to load the value 0 for global_settings.backlight_timeout (0 = never enable the backlight).

Shouldn't global_settings.backlight_timeout be filled with the default value (index=3, timeout = 10sec), or whatever is in the config.cfg file I have ?

I couldn't see where global settings are set to the default values (if they are at all), also I thought it's weird that firmware/backlight.c::lcd_sleep_timeout_value[] is not static (perhaps it was previously used by other files ?).

Can someone put some light over this ?

[Xanikseo]

Using the current build on the Fuzev2, I notice the screen only flickers and shows distortions when a larger than small amount of what's on the screen changes, for example when you scroll quickly, or view the fire demo. When only small sections of the screen change and slowly, like when you scroll slowly within one page of a playlist, this doesn't occur.

EDIT: Flickering is unlikely when no music is playing. Can scroll very quickly with no flickering. When playing music, using the scroll wheel at the bottom of a playlist, where there is no movement, does cause flickering. Well I suppose it's just down to how much the chip is working, more work = more flickering.

Also, I think you may already be aware of this, but you can't reduce the volume very much. Anything lower than -39db has no effect on the volume.

[tofmin]

Sansa c240 v2.

Every build above 25508 crashing. Can't access to database, setings. Can't skip next/prev song. Don't works cuesheets support... Something wrong happend

BTW. Where I can download old b25508?

Sorry 4 bad english

[ssorgatem]

EDIT: backlight brightness fixed, bootloader updated
EDIT2: this means you shouldn't follow these directions

Looking for fuzev2 testers, the LCD started working today

There seems to be 2 different LCD types, at least me and kugel have the same type, so I would like to know if other people have the (hypothetical) other type of LCD on their fuzev2.

To test:

• download this patched OF version 2.3.31 and a current build
• unzip both archives on the root of the fuzev2
• unmount/eject and disconnect: firmware update starts, player powers down itself
• Keep pressing Left and power on : OF start (it'll work as before, you can shut it down at this point)
• Power on without touching left : you should see the rockbox bootloader and then the rockbox menu
• Since buttons do not work yet, you must force a power off by keeping power button pressed for ~20 seconds

If your fuzev2 doesn't display anything when booting rockbox code, power it off by keeping power pressed for ~20 seconds, then power it with left key pressed to boot the OF and update with an unmodified OF.

Then come to us on the forum or irc so we can try custom code on your player

this is not working for me. I must have done something wrong, but when I install the patched OF, everything goes as if it were an unmodified OF. And this happens to me not only with that file, but with every other firmware version i've tried to patch with mkamsboot. I've double-checked i'm using the correct (patched) firmware file and not the original, but my v2 fuze just seems to ignore the RB bootloader.

What amb I missing/doing wrong? I even tried patching with bootloader compiled with arm-elf and arm-elf-eabi chainloads, just in case it made any difference, but without results.

May the problem be that i have the other (hypothetical) LCD type?

[saratoga]

Are you booting with the USB plugged in?

[ssorgatem]

Are you booting with the USB plugged in?

No, I disconnect it from the usb, then upgrade begins, finishes and it powers off. Then I power it on, it shows the splash screen, then database refresh, then language &region selection. Rebooting doesn't show up anything different from OF.

[wildmetal]

The builds from 12/04 and 11/04 after some time of playback crashes.
I'm using the build from 09/04 because the palyback in this one works fine.
I can search especific bugs if you tell me witch ones to look for.

cumps

[ssorgatem]

I've tried patching latest OF with  both mkamsboot and bootloader compiled from subversion, without succes.


My v2 fuze won't even try to boot rockbox, just as if the firmware weren't patched.

Any ideas?

[funman]

May the problem be that i have the other (hypothetical) LCD type?

No, else your player would boot and show an empty screen (only backlight).

This could be the same problem we had on c200v2 : USB detection is unreliable and dualboot code always boot to OF.

Are you ready to test modified dualboot code and risk bricking your Fuzev2 ?

Do you feel confident working with patches (we can give you clear instructions, but if you mess up your Fuze is dead)

[ssorgatem]

Yes and yes

Of course I would prefer not to brick my fuze, but it has the screen badly scratched and since I got a nokia 5800 xpressmusic in november, I don't use it anymore... but rockbox could change that.

[funman]

If you can come on irc that would be simpler (look on the left : Support -> IRC)

[ranma]

Sansa c240 v2.

Every build above 25508 crashing. Can't access to database, setings. Can't skip next/prev song. Don't works cuesheets support... Something wrong happend

Can you be a bit more precise on 'crashing'?
Does it boot fine, but you can't navigate the menu?
You can start a song, but skipping to next/previous doesn't work?

Really exactly after 25508?
Because that looks unrelated: http://svn.rockbox.org/viewvc.cgi?view=rev&revision=25508

Gigabeat S: Extend the upper temperature range for battery charging to 50C: OK and 45C: Resume. Currently extended disk activity can cause it to detect overtemp which doesn't quite seem correct. Add macros for the range so that they may be target-specific.

[notlistening]

Clip+ observations:

1. When loading a new build of rockbox,  a couple of time I find that the very first time i play a song I just get white noise from the player. After that first play it is fine and great every time after. Even after a reboot. Just testing this appear to be a reproducible by koading the OF playing a sound switching it off and then back to rockbox the first song you play or even speech kill the player and give this white noise effect.

2. If the database is not refreshed in the OF and i force it to shutdown then rockbox takes an age to boot. After a full refresh we have normal boot times for rockbox.

3. Rockbox seems to run for much longer than the OF is that because the low battery level has not been set and is there the potential to damage the battery but draining it too much? Might it be good to warn users of this?

Great job everyone so far.

NL