Rockbox.org home
Downloads
Release release
Dev builds dev builds
Extras extras
themes themes
Documentation
Manual manual
Wiki wiki
Device Status device status
Support
Forums forums
Mailing lists mailing lists
IRC IRC
Development
Bugs bugs
Patches patches
Dev Guide dev guide
Search



Donate

Rockbox Technical Forums


Login with username, password and session length
Home Help Search Staff List Login Register
News:

Welcome to the Rockbox Technical Forums!

+  Rockbox Technical Forums
|-+  Rockbox General
| |-+  Rockbox General Discussion
| | |-+  Gigabeat x30 - HDD busy for 2-3 minutes on start up
« previous next »
  • Print
Pages: [1]

Author Topic: Gigabeat x30 - HDD busy for 2-3 minutes on start up  (Read 1177 times)

Offline bluesbeat

  • Member
  • *
  • Posts: 21
Gigabeat x30 - HDD busy for 2-3 minutes on start up
« on: March 09, 2007, 10:34:13 PM »
Hi,
New to Rockbox I have build 070307 installed and it seems lately that the hdd is busy for a few minutes on startup and therefore the player is not responsive.
Could I have caused this by one or more of the settings etc?
Any clues appreciated. I'll re read the manual, just thought someone may know the answer.
thanks.
Logged

Offline bluesbeat

  • Member
  • *
  • Posts: 21
Re: Gigabeat x30 - HDD busy for 2-3 minutes on start up
« Reply #1 on: March 09, 2007, 11:03:19 PM »
I think I have found the problem.
When Rockbox is set to "Resume Playback" for the start screen option, this seems to happen....goes to the wps but takes ages to resolve the track that was playing, displays track name but can't determine the id3 values for a few minutes then starts to play.
I just set the start screen to main menu and it's fine from there.

 Is this a known problem?
Logged

  • Print
Pages: [1]
« previous next »
+  Rockbox Technical Forums
|-+  Rockbox General
| |-+  Rockbox General Discussion
| | |-+  Gigabeat x30 - HDD busy for 2-3 minutes on start up
 

  • SMF 2.0.17 | SMF © 2019, Simple Machines
  • Rockbox Privacy Policy
  • XHTML
  • RSS
  • WAP2

Page created in 0.046 seconds with 15 queries.