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

[Finixlives]

(Fuze V2)
Well i got home from school today to be delightfully surprised that memory is no longer read only
I've done very very little testing (only the rockboy plugin) and i can save games on the game, but not with the save state. Another thing to note is that when i shut down rockbox and then turn it back on the save is erased. Ill be testing more things out and give more feed back later.

PS: Thanks for the great work you Developers are doing!

[bilditup1]

So I tried the official build of 25799, as well as a few of my own changing the udelay params in sd-as3525v2.c.

The official build (which I'm assuming has udelay at 1000) hangs forever at boot with an 8gb uSDHC. The same behavior occurs with every build I've made, including sleep(1), udelay (5000), and udelay(3750) which all worked with the earlier revision 25791. These builds also failed to recognize the card on insertion after startup, except for (3750). However, this support was very glitchy - flashing click wheel, slow loading of next folder (like a .5-1.0 sec delay), freezes on trying to access, etc. This only happened once - when I tried to put this build back on (25799/3750), I could not replicate results (other than the hang at startup). So I reverted back to 25791/5000 for now, which seems the most stable.

What is there to be done...?

[Jennifur]

Using a FuzeV2 with an 8GB Kingston Class 4 uSD card. It freezes with the build r25799-100503 when the uSD card is inserted. It will not detect the uSD after it is inserted while Rockbox is running. The builds with read only support will not see the uSD card either. The OF can read/write to both the internal memory and uSD. The previous version that I used was r25758-100429 from SVN.

[bilditup1]

Yeah jennifur - the last ready-made build this works with is 25733. If you modify the file I wrote about above (funman/kugel's suggestion) and make your own build, you could work with 25791. (I'm also using an 8gb Kingston Class-4). Read the thread in the middle of the last page for more info.

Devs- one more thing. My builds show up with an "M" after the build number. Should this be cause for concern?

-e

[saratoga]

Devs- one more thing. My builds show up with an "M" after the build number. Should this be cause for concern?

'M' = 'modified'

Just means you edited the source code.

[Jennifur]

Checking it out now and will try udelay (5000). I will let you know how it turns out.

Yeah jennifur - the last ready-made build this works with is 25733. If you modify the file I wrote about above (funman/kugel's suggestion) and make your own build, you could work with 25791. (I'm also using an 8gb Kingston Class-4). Read the thread in the middle of the last page for more info.

Devs- one more thing. My builds show up with an "M" after the build number. Should this be cause for concern?

-e

[Vague Rant]

So far write support on Clip+ seems to be working perfectly, no crashes yet and I've been messing with settings, writing a scrobbler log, creating a database, etc. My microSD is working perfectly, but has never given me any trouble while others had issues, so that's not really useful information. If it is an access speed issue that would make sense, as the mSD I'm using is a 2GB Kingston (produced in Japan); these are noted for their access speeds and my original use for it was somewhere this was important--so now that it's been commandeered for my Clip+ it makes sense that it's worked well here also.

I'm currently running audio through a speaker, so I'm not sure of the mechanics re: power usage, as the speaker is itself powered. For that reason (and also because it's not fully charged yet) I haven't run a battery bench but I will do so shortly using headphones.

EDIT: Does Rockbox on these devices currently write anything in RAM to disk upon shutdown? I played a single album with logging enabled, switched off the player, and opened the log in QTScrobbler (and also Notepad++ to verify) and only the first five tracks (of a 13-track album) appeared in the .scrobbler.log. It is reproduced below.

Code: [Select]

#AUDIOSCROBBLER/1.1
#TZ/UNKNOWN
#CLIENT/Rockbox sansaclipplus $Revision: 23447 $
Patrick Wolf	The Magic Position	Overture	1	280	L	1274541921	
Patrick Wolf	The Magic Position	The Magic Position	2	233	L	1274542220	
Patrick Wolf	The Magic Position	Accident & Emergency	3	196	L	1274542457	
Patrick Wolf	The Magic Position	The Bluebell	4	74	L	1274542655	
Patrick Wolf	The Magic Position	Bluebells	5	314	S	1274542730	

[7o9]

As I reported on IRC, my initial testing of the write support on my Clip+ seems very successful.

I haven't tried extended tests but I saved settings and made bookmarks on both internal and uSD.

Great job guys, even if it's not all perfect, this update makes my Clip+ so much more awesome!

[bYOndo]

Wow! thanks funman and flyndice, as usual, you're great!
on my clipv2, r25799-100503, everything works fine, unless "pitch" function; if modified frequently, it leads to great unstability.
here is the error:

Code: [Select]

Data abort
at 30030688
FSR 0x8
(domain 0, fault 8)
address 0xE59FF024

it can be reproduced by keeping "-2%" or "+2%" button pressed for a certain period.
and with "clipline" theme, the "pitch" screen glitches.

Massimo

edit: after some test, I realized that it's not so reproducible. Some time there's the "abort" message, other time it simply freezes, other time it scrambled the file duration on WPS, but playback keeps working. 

[Jennifur]

Tried what bilditup1 said. It works, it can read the uSD card. Though, I can't get the database to build. I will try it with the latest SVN build and see if that will work.

[bilditup1]

jennifur - write support was only enabled by 25779, the same release that hangs on startup.
Looks like flyndice modified the file though in the very latest build, 25811, so we should probably try that. I'm having trouble checking out SVN right now, however.

-e

[Jennifur]

I had no problem checking out to 25811. I'm going to test it now.

[Xanikseo]

Can confirm writing to my 8gb kingston class 4 µSD works! Dayam , I can finally use the database properly! Great work!

Still got this problem with scrolling (you suddenly jump straight to the bottom/top if you are scrolling any faster than slowly), probably caused by r25736 link to post. kugel please fix this!

Button light now flashes like crazy while switching tracks :O! Still takes a while to switch tracks as well, as soon as you press skip twice in a row, you have to wait like 5 seconds for anything to happen. I suppose these delays still need to optimised, but we know that already right ? It's great that we've got write support now though, I reckon a lot of crashing was caused by some vital files being read-only.

EDIT: OK, some more helpful info about switching tracks: you can only switch tracks after the first five seconds of the current song have played. As soon as you have passed around 5~6 seconds of the current track, switching tracks happens quickly. If you skip a track before the first 5~6 seconds of the current track have played, the next track will only start playing as soon as you reach ~5 seconds.

Another (totally unrelated) thing I have discovered. After you exit the pitch detector plugin, the sounds being picked up by the microphone are still recorded, and you can still hear them quietly in your earphones.

[Timar]

Thanks to all the developers for the rapid improvements! Write support works flawlessy so far. One exeption: I can't get the recorder to work.

I've tried to run a battery bench but I've given up. I hardly get more than one or two hours of playback before the Clip crashes. Maybe I'll try again without crossfeed/EQ...

[marc2003]

just to echo the above post, thanks for all the recent updates.

i'm currently 10 hours into a battery bench on my clip v2/r25799/database enabled/ogg q5. i'll post full results when complete. still 40% battery left so i'm aiming for around 16 hours i think.

playback is running fine although cpu frequency has to be boosted. i can barely last 20 minutes without it.

edit: i haven't tested this build unboosted but all recent builds have been problematic for me and i have no reason to think the new addition of write support is going to fix that?? absolutely no problems boosted though.