iPod 5.5 80G: Rockbox reverting to default cfg after power off

[StsIkel]

I am a bit hesitant about reporting this as no-one else seems to be suffering this. I first noticed it after cabbie v2 became the new default theme, but I have not yet retested with an earlier build yet. I was wondering if anyone else had actually had this problem before.

Here's what happens: I turn my ipod off, and if I leave it more than a minute or so before I turn it back on, all settings are set to defaults. This isn't as ugly as it used to be, but it means that dircache, lastfm, shuffle, playlist warnings, follow playlist, my theme, crossfade, pause on headphone unplug etc. etc. are all off, and for a device used as a broadcast input on a radio station, booting up in repeat mode is absolutely unacceptable. I can set the right settings and then reboot and the ipod will remember them.

Some quirks that make me think it's not a hardware problem: I'm not losing any data. Rockbox is remembering database builds and backdrops between these reverts.

Any ideas?

[zajacattack]

Have you tried saving your own settings in a .cfg file that you can load?

As well, if that fails, you can save your own settings to the "default.cfg" file.

[AlexP]

Just to make sure, you are not turning hold on during boot are you?  This would reset the settings as you describe.

[XavierGr]

I remember I had that strange problem once on my H115.

Here's what I did:
1. Delete the config.cfg file in the .rockbox folder. (that file holds the current settings).
2. Turn off and while turning the device on make sure to reset the settings with hold.
3. Start setting your preferred settings, then save them just in case.
4. Reboot and see if it got fixed.

[StsIkel]

I remember I had that strange problem once on my H115.

Here's what I did:
1. Delete the config.cfg file in the .rockbox folder. (that file holds the current settings).
2. Turn off and while turning the device on make sure to reset the settings with hold.
3. Start setting your preferred settings, then save them just in case.
4. Reboot and see if it got fixed.

Seems to have done the trick, thanks XavierGr!

I will post again if I start experiencing this again but hopefully this has worked fully.