Sansa Fuze+

[oh_fuck_im_a_ghost]

What are the start up times like on a rockboxed Fuze+ compared to the original firmware?  I went with a Clip Zip ONLY because I read about long boot up times with the OF.

[pamaury]

The Fuze+ OF starts in about 9/10 seconds whereas rockbox boots in about 4/5 seconds. It is hard to beat the Sansa AMSv2 (clipv2, clip+, clip zip) with respect to start up time.

[monoid]

I haven't used OF for a year or so, so I do not remember exactly. But it seems to me that OF with full 16 GB memory and 32 GB uSD card have booted many tens of seconds. Maybe a minute. Ill driver of touchpad and extremely long boot time were the main reason I switched to RB.

EDIT:
Just to avoid confusion...
The startup with RB is fast, but of course not instant. Few seconds.

[buckminster]

Yes, without a microSD card inserted, the OF is reasonable in start time; with one, however, it's an insanely long. My guess is it rebuilds the database on the microSD card every time. That alone would convert anyone that knows of Rockbox. I also found that removing album thumbnails that Windows creates improves start time for the OF (since it's building a DB for it's photo viewer).

[Roboturner913]

Getting some hangups with the past few updates. Extreme slowdowns while playing files - happens completely at random. Any button press would take a 5-6 second delay before executing the action, buffer would take up to 30 seconds to build up, screen fade-in/fade-out was noticeably slow.

Went back to an earlier build of Jan. 15 which solved the problem. Doesn't bother me at all, just making it a known issue.

[pamaury]

Can you bisect the problem to find which commit caused this ? Or at least get a smaller window of when such a breakage could have happened.

[Roboturner913]

Honestly, I don't know. somewhere between Jan. 15 and the first build with the 10-band EQ. I went a couple weeks without updating. I'll experiment with it a little and see what happens. I was inclined to call it a hardware failure until rolling back erased the problem.

[pamaury]

I cannot reproduce the problem with the latest version, can you try to remove the .rockbox dir, do a clean install with the HEAD version and if it still fails, post a bug report describing exactly what you do.

[Roboturner913]

I'm not sure what you mean by HEAD version. But when I first noticed the bug I did format the player and installed RB from scratch with the daily build from Jan.31 and it still happened. Same with the Feb. 2 build.

As to what triggers it, not sure. Seems to be completely random. Sometimes happens when I'm playing a file and then go into the database and pick another album. Sometimes happens when a file is already playing with the backlight off and I press the button to go into the menu (the slow "fade in" I mentioned earlier). Seems to be no rhyme or reason to it at all.

It reminds me of an old laptop I have that just decides to take a dump every once in a while. That I know is a hardware problem, which is why I assumed the same for the player. But rolling back to earlier builds with no issues pretty much rules that out, I guess.

EDIT: Now that I go back and look at it, its either f2dfc84-130126 from Jan. 27 or 1789b71-130122 from Jan. 23. One of those was the first time I noticed the problem. Not sure which, but I'll try them both when I can.

[[Saint]]

I'm not sure what you mean by HEAD version

This link will always point to a Fuze+  binary compiled from git HEAD. Backup your .rockbox directory (if desired) and remove it from the device, then extract the linked binary to the root of the device and see if you can still replicate the issue.
If you can replicate the issue, please report it on Flyspray, our Bug Tracker, making a note of the specific firmware version listed in:

System -> Rockbox Info -> Version: xxxxxxx-13****

(xxxxxx is a unique 7 digit alphanumeric version string, 13**** is the build date formatted as YYMMDD)


[Saint]

[fsclavo]

Getting some hangups with the past few updates. Extreme slowdowns while playing files - happens completely at random. Any button press would take a 5-6 second delay before executing the action, buffer would take up to 30 seconds to build up, screen fade-in/fade-out was noticeably slow.

Went back to an earlier build of Jan. 15 which solved the problem. Doesn't bother me at all, just making it a known issue.

Same here. The player keeps playing (with some minor audio gaps) but the response times are so slow that becomes unusable. It's like the processor doesn't scale up frequency when load is increased. I'm using 42a725f.

[pamaury]

Please post bug reports for those issues, remember that this thread is about development only and we try to keep it reasonably readable.

[fsclavo]

Opened task http://www.rockbox.org/tracker/task/12821
Regards

[sdf5]

Hi,

My Fuze+ with Rockbox was working fine for a while but now it's behaving strangely and I'm not sure if it's related to Rockbox firmware or something else.

The problem now is that when my Fuze+ is disconnected from PC it stays dead and doesn't respond to on/off button at all. When I connect it to PC it connects to PC in USB mode and I can access the player and transfer files between the Fuze+ and PC. The following messages are shown on Fuze+'s screen when it's connected to PC:
  Boot version: 1.0
  org=CAFEBABE addr=4000000
  USB: Connecting
  Boot Loader USB mode

When I press and hold the on/off button while Fuze+ is connected to PC, Fuze+ seems to reboot itself going blank and then showing the above message again.

I tried to reinstall Rockbox using the installation utility and it seems to work fine (with exception that the player went dead instead of rebooting itself) but but it did not resolve the problem.

Any ideas? Thanks

[pamaury]

The battery might simply be flat and our bootloader doesn't charge currently. Try booting to the OF in usb (hold volume down when plugging the device).