Rockbox General > Rockbox General Discussion

Gigabeat F20(Mar 20th & 24th Builds) -- Long Rockbox Startup

<< < (5/7) > >>

bluesbeat:
Hi,
I started using Rockbox on my Gigabeat x30 early March, i have noticed the above mentioned startup delay for the last week or so.
I am using the build from 28 Mar (today). And I'm also using the March 12 bootloader.
After the rockbox splash screen there is a delay of around 1 minute (hdd is active and screen is white) then everything is ok. I only have less than 150 mp3 files on it at the moment.
It doesn't happen on every start. It did just happen after I connected the usb to update to the latest build, otherwise i can't see a pattern to it.

Edamame:
Hi, I've installed the march 12th Bootloader. I did a complete defrag. I tried many thing, but it was getting worse at every attempt. for example, I got several total freeze while browsing my files in my X30 forcing me to switch the battery off to switch of my X30.

I'm back on an older version of the bootloader and rockbox (22 feb) for now. It's working quite well. Unfortunately, I don't have the latest improvement such as in the mpeg player...

If someone find any solution, I might try it out. But for the moment, I think I'll stick with the older version... :'(

Nate!:
Wow this is weird.  I have an official build r12936 with March 12th bootloader.  I don't get the freezes or the lengthy load screen at start-up.  I only get the "loading" screen when booting for the first time into a newer build.

I do get a one to two second pause when going into the file browser.  But I suspected that was because I don't have dircache enabled.  I don't find it to be a hinderance, but I'll mention it here for added information to Edamame's issues.  (btw, I love edamame: lol)

fyi, Gigabeat F60; official build r12936, eq off, dircache off, dithering off, replaygain (on shuffle) enabled/ prevent clipping enabled.  Can't think of any other cpu intensive options that I would have enabled.

Llorean:
Yes, with dircache off, a 1-2 second pause upon entry of the filebrowser (or any time you don't change folders for whatever period your disk spindown time is set to) is entirely expected. It's just the wait for the disk spinup.

Job Van Dam:
Just wanted to say I'm using the March 30th build and startup is back to normal. It almost seems faster or maybe I'm used to waiting a minute for it to start. :P

Thanks for all your help guys, really appreciate it.

Navigation

[0] Message Index

[#] Next page

[*] Previous page