Sansa Fuze+

[pamaury]

There is an important change in the way the volume is managed before 0dB and after. Before, only the DAC volume is used and volume changes are handled by hardware by waiting zero cross to minimize noise. After 0dB, I begin to use the headphone amplifier which also has a zero cross mechanism. At the switch, it is possible that something weird happen, I will investigate this.
I think I also heard the noise when loading but it's not really "beepy".

[metaphys]

@Pamaury did you see the post from beezeer38 on the previous page? This is quite a problem, though it's still only two user so far, there seems to be a problem with internal memory.
It might be interresting to investigate further on this/to have a bootloader that can boot from sdcard

[pamaury]

This must be a hardware problem. The mmc flash reports success on every operation, I can't possibly do anything. Jean Louis told me that the problem also arised with the OF, several users reported it on the Sansa forums.

[alienkid10]

no beeping that I've noticed, yet I'll keep and ear out for it. No flash problems either. Radio is freezing the whole player when I try to go into it. (like when it wasn't implemented right.)

[megal0maniac]

A few issues which I found while bug-hunting yesterday.

Noise while scrolling through menus, immediately after power-on. Goes away when you start playing audio.

CRT-effect when playing music. Only occurs when you start a song from the database or file manager, not when you skip to the next track.
Screen flickers for about 5 seconds when a track begins, seems to be related to disk access.

Radio seems to be working alright, but I always go back to the menu after starting it, and I don't autoscan.

[halonachos117]

Has anyone noticed that Rockbox's clock is always one hour behind the OF clock, or is it just me?

[alienkid10]

Haven't noticed but will check tonight.

confirmed OF is +1hour compared to RB.

[halonachos117]

Perhaps it has something to do with Daylight Savings Time? Perhaps the OF sets the clock/chip back one hour, then adds an hour while in operation? If Rockbox doesn't do that, Perhaps the mistery is solved.

[alienkid10]

I don't think so. It needed to be reset manually for me. I don't know a good way to test this though.

[megal0maniac]

The daylight saving theory would make sense, if it were possible to turn DST (daylight saving) on or off.
There isn't even a timezone setting. Closest thing to it is regional settings, to which mine is set to "rest of world"
In South Africa, we don't have DST. In fact many countries don't.

Most likely just a quirk of the OF. Shouldn't be too difficult to advance the the Rockbox clock by an hour as well...

Meanwhile, my Fuze is doing other stupid things.
When it boots, sometimes it takes a while before booting, (stays on "power up source" for about 4 seconds,) sometimes it boots fine and sometimes it says "File not found"

I've re-installed Rockbox to the device to rule out a sketchy rockbox.sansa file and I've run chkdisk on the internal memory and it came out fine.

Is the bootloader on a different partition on the main memory, or on a seperate eeprom?
Has anyone else had this issue?

[pamaury]

Hi,
having reverse engineered the OF on this point, I'm sure that the calculation are right. This one hour offset must come from daylight saving or different time zone.
The bootloader is stored on the internal storage (in a hidden partition) and it should be fast to boot. I don't think I've heared of someone getting random errors at boot time. Sometimes the device goes crazy if you didn't power it off properly. In doubt you can boot and immediately power off so that it properly turns off. Or perhaps there is a problem with the internal flash, you wouldn't be the first then but reports are always about write failures, not read.

[Raiden175]

Sorry if I am a little late to the party. I had the same problem as you Breezer I could not Add/Delete Files either. I couldn't even access the OF. It inevitably sucked. I ended up getting an RMA for it. And I reinstalled Rockbox and it did not happen again, but in the time I did have it I could not find a solution to fix it. So I feel your pain.

[halonachos117]

I've always noticed a three or four second delay when booting into Rockbox. This extra delay only occurs when the player was previously booted in the OF. If the last time you used the player, you booted into rockbox, there is no delay. If the last time you used the player, you booted into the OF, there is a delay.

Very strange. I assume there's some good reason behind this. I wouldn't worry about it.

As for the false "File not found" error, I've had that once. A simple reboot fixed it.

[megal0maniac]

So I decided to boot into the OF and go back to Rockbox to see whether I had the same delay.
I did.
Then I restarted it, and now all it does is say "File not found."
Consistently. Every time I start it up.

arg=CAFEBABE addr=40000000
Are these parameters correct?
Not that I could change them, but it might point to what's causing this issue.

Running ee6e88f-120315.
Can't remember which bootloader, but it was the first one to introduce the power button delay.

Will update shortly when I get it working.

UPDATE: Booting into OF and back into Rockbox fixed it the first time. But then I restarted and same issue. Went back into OF, restarted, and "File not found"
Any suggestions on checking the integrity of the internal memory?

UPDATE AGAIN: Installed (updated?) bootloader and Rockbox through the utility. Delay after booting OF is minimal now and the other issue is gone.

[luetzel]

@Pamaury did you see the post from beezeer38 on the previous page? This is quite a problem, though it's still only two user so far, there seems to be a problem with internal memory.
It might be interresting to investigate further on this/to have a bootloader that can boot from sdcard

Well, one more to count - I've got the same problem as well, and no solution. Tried re-formatting the device and the recovery procedure - nothing helps. When looking at the partition table, fdisk or cfdisk do not recognize/complain about an unsupported table. Any options to restore it somehow?