Support and General Use > Audio Playback, Database and Playlists

Sansa Fuze v1 Playback problems above build 27996

<< < (2/6) > >>

orbidia:
Okay. Thanks darlredfish and BigPapi for confirming the latest builds work on your end.

Now, I don't know what to do. I must have messed up somewhere.
I'm just trying to get everything back to normal.

I still can't get anything to work past 27996...

Here's what I did:

First, I booted into the official firmware and connected the fuze v1 to the computer.
I slow formatted the internal contents (way too long).
Then I loaded up the latest Official Sansa Firmware 1.02.31 into the root.
I unplugged the Fuze and let the Official firmware update.

After I turned it back on, everything seems like its back to original Sandisk spec.

I connected the fuze to the computer and I loaded up the latest Rockbox Utility 1.2.8.

I did a "Complete Installation" to install the last stable version 3.6.
Everything installed fine.

Now, last time I tried using the Rockbox Utility (before r27996) it did not install the latest Rockbox Boot Rom ver. 2.0. That's why I used mkasmboot last time to make the firmware. I wanted the full USB support. This time, I notice the Rockbox Utility is now loading up the Boot Version 2.0 during the complete installation.

I unplug the fuze and the Official firmware says the firmware is being updated. The fuze turns off. I turn it back on to Rockbox Boot ver 2.0 and Rockbox 3.6.

It all works nice and stable - EXCEPT:

The problems start now.
When I go to plug it back into the computer from either an "Off" state OR from the Rockboxed "On" state, the fuze keeps trying to connect to the computer and then it reboots and then tries to connect again... and again in a infinite loop.

This is why I didn't want to use 3.6. Because the full USB support doesn't work...
Without Full USB Support, I need to go into the official firmware whenever I want to change any music and deal with the "Database updates" and all those useless folders the official firmware creates.

*****
QUESTION:
Using stable Rockbox v3.6 and Fuze v1 Boot ver 2.0, does anyone else have properly working Full USB Support?
Or, with Rockbox v3.6, Boot ver 2.0, does the Fuze v1 endlessly reboot when trying to connect?
*****

When I then go to a build AFTER official version 3.6, the USB connection works perfectly - right up to the present build. This makes me think Boot Version 2.0 Firmware was not really meant to work with Rockbox v3.6 -OR- something is really wrong with my Fuzes (I have the exact same problem with 3 tested Fuze v1s).

I then used the Rockbox Utility to update to the latest build and I still get all the same problems from my original post. I went back to r27996 and its all working again.

I get this bad feeling I'm just gonna be stuck on r27996 forever because the firmware got messed up permanently somehow... I guess that's still a heck of lot better than the official firmware.

In summary: I tried completely flushing the system and just used the Rockbox Utility to reload everything. But all the latest builds for the last few weeks are unsusable.

----------------------------

Does anyone know what would have broken in my fuze to make it non-functional with builds after 27996 and boot ver 2.0? And what else could I try to fix it?

I guess I could just wait until the next stable release but I don't know why it would just start working at that point...

Any ideas?

saratoga:
3.6 does not have USB support on the Fuze:

http://www.rockbox.org/wiki/MajorChanges

manequin:
You can try my build with reverted r28000 changes. On my fuze I had a problem playing ogg vorbis files using official build. Remember to make a copy of ".rockbox" folder before extracting archive to your player. If something goes wrong, just remove .rockbox folder and revert your backup. However, it works great on my device. Here is the link: http://dl.dropbox.com/u/554609/Rockbox%20archive/rockbox-full-fuze-28177-manequin.zip

darlredfish:
I tested your build manequin and it works for me fixing the cross fade crackling. I also tested the newest svn to see if it was maybe something I might have done but it was still there.

orbidia:
Manequin,

You the Man!

I loaded your .rockbox folder onto my problem fuze and...

IT WORKS PERFECTLY!!!

When I load Manequin's build, it starts with:
r28177M-100927

I can't believe it - it is just as stable and perfect running as r27996.
I compared it with the current daily build which shows up with:
r28177-100926

In direct comparison, the official r28177 build for me is UNUSABLE!
As I fast forward through songs or rewind, the status bars keep flashing ridiculously high numbers.
The battery indicator used to flash absurd numbers too but that seems to depend on the theme.
The audio works intermitantly if at all.
Also, I've been getting straight out crashes with a White Screen of Death:

3 or 4 of these:
Data abort
at 30065388
FSR 0x8
(domain 0, fault 8 )
address 0xB7D094A0

and 1 of these:
Data abort
at 30057D78
FSR 0x8
(domain 0, fault 8 )
address 0xA5D90320

But with Manequin's version of the same r28177 build - r28177M - it all works again.

Me and my family have 7 Sansa Fuzes in total - two of them are Fuze v2s and five of them are Fuze v1s.
And I tried a number of builds after r27996 on a few of the Fuze v1s.

**************
Last night I tried r28177 official build on another Fuze. It turns out that whatever the problem is - It affects some Fuze v1s more than others!
One of them I have is more or less stable and seems to be okay. But I managed to get it to freeze up after some fast forwarding and rewinding and moving between menus and tracks. I also noticed the status time flashed a 0:00 once when fast forwarding. When I rebooted it seemed more stable and I couldn't get it to crash again. Another fuze v1 I have is somewhere between unstable and stable. And then the first one I was using is totally unstable.

But Manequin's build fixes the worst Fuze v1 until it is just as stable as the best one. Rock solid. Can't make it crash.

So, whatever code you reverted Manequin was precisely the culprit code!

Lear - the developer responded earlier -
"The change that looks most likely is r28000 (FS #11597 : decrease FCLK frequency when unboosted)."
Was that the main change Manequin or was there more?

Even though I don't code, I really appreciate this community effort in making Rockbox...

Now, what do we do to get that reverted fix back into the official builds so I can use my Fuze v1s with the latest builds again??

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version