Current Build=no microsd detected Fuze v2

[Julian67]

Actually some good news.....it was apparently just unresponsive, no sound, no USB, no display, nada. It should have powered down having not been used for a few minutes but instead had hung(?).  Realised it was still powered up when hearing some noise removing and inserting the phones and was able to power it off......back to life! Whew!  Anyway I'm conscious that bricking it is always a possibility and am prepared to risk it because it's infinitely more useful with RB on it than otherwise.  Time to try out latest svn......

[SheepCake]

fully died or what?  any chance of recovery?

It seems to be dead as in deceased, expired, kaput.  So back to my iRiver H140 and H340, players that refuse to quit. The Fuze lasted one year, the iRivers are still going strong - both > 5 years old, one battery replaced so far.  I just wish they were smaller.

good news, but i gotta say, i would take that iriver h300 over the fuze, despite size, I been trying to get a buddy to trade me his for 2years!!!

[Julian67]

And keep away from my iRivers too! They are mine mine all mine!  I'm normally happy to share and help but nobody gets to use those except me and I'm not selling either 

Actually the H340 feels terribly slow after a modern flash storage player so I guess a lot of people wouldn't like it, and the monochrome screen of the H140 looks like a piece of history these days.  Both now look huge compared to modern players.  But I do see both these selling for big prices when they turn up on ebay or similar.

edit: built and installed r26979 and seems all OK.

[SheepCake]

yeah, i would still love a h300, a friend of mine managed to replace his 320's drive with one thats 120gb and a good bit faster then the orignal, not sure where he got it, he also put a better batt in it.

they are a beastly little player for their day, im so sad i missed out on the referb sale of them a few years back 85bucks for the h320!!!!

now im gonna try and figuar out how to use saratoga's volume patch, should be a fun lesson in fighting with cygwin

[bertrik]

SheepCake, sorry to hear I didn't work for you. Please keep in mind that the fuze v2 is still in development, so specific things may break sometimes when trying to move the port as a whole forward.

The idea of the commit that was reverted was 1/ to use the same clock frequencies as we do on the ams v1 sansas and 2/ fix playback rate error (it is now 1.1% too slow again).

Personally, I'm not convinced yet that the change to 248 MHz was the root cause of the uSD problem on the fuzev2. uSD worked fine for me on my clip+ and you said it worked on your fuzev2 when you reloaded ("rolo"-ed) the .sansa file. The fuzev2 is a bit of a special case because of its larger display (so we need to increase the display clock to make sure we have sufficient frames-per-second, for example).

[SheepCake]

that build fixed it(the one that changed clock)

if you can figuar out how to boost the clock without the sd card issue that will rock.