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

[saratoga]

Even if we have USB working, we still need to do a new bootloader/mkamsboot release to make it boot rockbox on USB insert right?

In that case I would prefer to wait until either USB is working, or until it looks like its going to be a while before USB works.  Updating the bootloader isn't that risky, but its kind of a mess.  Maybe we could just disable rebooting on USB insert?

[Jennifur]

Even if we have USB working, we still need to do a new bootloader/mkamsboot release to make it boot rockbox on USB insert right?

In that case I would prefer to wait until either USB is working, or until it looks like its going to be a while before USB works.  Updating the bootloader isn't that risky, but its kind of a mess.  Maybe we could just disable rebooting on USB insert?

I agree with saratoga on this. Also, it is nice having it charge and be able to play at the same time instead of booting into the OF which doesn't allow this.

[saratoga]

Also, it is nice having it charge and be able to play at the same time instead of booting into the OF which doesn't allow this.

As funman said, you can already do this by holding a button while plugging in USB.

[csavery]

funman: I'm testing a version of button-fuzev2.c adapted to HZ timer. It seems to be working and I'm just waiting about 30 minutes to see how it behaves. If it works then I'll make a patch. Keep in mind that I've only been coding in Rockbox for a couple days so I'm not sure it wouldn't have other side effects.

edit: Seems to work. I have posted patch in Flyspray. I hit save too quickly and forgot to set correct patch info. Maybe someone with edit rights can fix that? 

[bor_ka]

I see you're using some odd compiler version as well as EABI.  Does this still occur if you use the normal compiler (4.0.3)?

Well, I thought that eabi is the preferred way (looking at the speed comparison on the fuze). And the 4.4.3 is the recommended for eabi. Will try 4.0.3 though.

P.S. The database update does not freeze if there is no playback, and if I "play" with the scrollweel (turn it back and forth every 30 secs or so).

[funman]

I have posted patch in Flyspray. I hit save too quickly and forgot to set correct patch info. Maybe someone with edit rights can fix that? 

I edited FS#11288

[mitk]

Funman: I'm charging clip+ under Rockbox. Started from 62%, now have 74% and still going up.
Firmware, bootloader and mkamsboot from r26125

Edit:
Charging stalled at 99%, 4.210 V. Status is charging, it didn't stop..

[bor_ka]

Update on FS#11267. Fuzev1 hangs if playback is on, and database is updated in the background. It hangs even on the "official" 3.5.1.

[csavery]

Updated patch FS#11288 for fixing scroll wheel lockup after 20 minutes.
Should work, please test when you have time. 

[max242]

I strongly believe that the issues i'm having getting pictureflow correctly building the cache of  thumnails on my sansa fuze v1, is related to the issue bor_ka is reporting on him building the tag cache/database correctly.

The pictureflow thread can be found here: http://forums.rockbox.org/index.php?topic=24496.0, and also started at r25299.

So when i today saw r26116 is fixing an issue introduced in r25299, i tried again building at first the database, then the pictureflow cache.  But still no success in building the pictureflow cache.

I have seen a message from funman stating he has issues building the tag cache/database properly, which i think might be related to what bor_ka is saying.

Bor_ka did you ever try to use pictureflow, and also see your sansa freeze/lockup somewhere during the thumbnail generation process?  It fails on me nearly every time!

But unfortunately i have absolutely no clue on what is causing these issues, and i guess wild guessing is not really permitted in this thread (interrupts, maybe?).

The only thing i know for sure is that the picture flow freeze issue didn't occur in r25298, and does occur ever since r25299

We really should try to find the root cause of these issues, so we can nail them down, and squash them forever.  Can some of you guys give some hints on what we can do to locate the troublesome code?

Also, since i'm pretty sure the pictureflow freeze issue, and the database building freeze issue are related, i think it would be better to rephrase FS#11267 http://www.rockbox.org/tracker/task/11267 to something like 'Freeze on sansa fuze v1 during tag cache/pictureflow cach building', or something more reasonable.  Is this possible?

I'm sorry for this (very) long post, but i just wanted to make sure you all are aware of this.  And if this post is not in the proper place, move it to a position which does make sense, i just didn't want this info to get lost.

Keep on rockboxing!

Marc

[funman]

the fuzev1 freeze issues should be fixed in current svn (for me they are)

[Ahcsas]

Rockbox runs very well on my Clip+  ,

but I have a lot of artefacts (clicking and whirring sound) during navigation (browsing database, open&close plugins/games, at each memory access [when the memory access-symbol is on the display).

When I hear music (on low volume) I can hear the artefacts also. With OF I have this problem not.

------------------------------------------------
Firmware, bootloader and mkamsboot from r26150.

[funman]

I think I hear that one in the OF too, perhaps it's less noticeable since the OF has no plugins/games


I have a put a patch for set_cpu_frequency() : FS#11297

Please report on the flyspray task if it works or not for you

[bor_ka]

the fuzev1 freeze issues should be fixed in current svn (for me they are)

Unfortunately for me - not r26185, the bug as described in my FS#11267 is still there. I noticed, though, very big speedup in database scanning, and overall menu responsiveness.

And who can edit FS#11267, especially the title and description? Me not.

By the way, fuze hangs only if there is simultaneous playback and database population. If And the card is 16GB Class 2 Kingston - may be it depends on the card speed?

max242

Pictureflow scanning for me works Ok. No hangs. Some jpegs are not displayed though...

[athatai]

funman, I own a Clip+ and am using 26179 and it looks like the USB charging is broken. I tried it on my PC and the screen blacked out with no music. The wall charger does not seem to work either (same problem).