Ipod startup issue

[squidkidd]

This is an issue that causes me minor annoyance.  Sometimes when I push select to turn my unit on (80gb 5.5g), instead of the apple logo, my screen displays some sort of battery logo (an apple firmware logo, not rockbox) and then disappears.  The unit then does not proceed to turn.  In fact, when this occurs, I cannot then press select again to turn the Ipod on, I must hit menu and select to reset the player.  Anyone else had this or know what's causing it?

Before anyone asks, the battery is fully charged.

Regards,
Brian

[DefineByte]

Happens to quite a few people. As of yet the cause is unknown.

It occurs on my 30GB 5G too so isn't limited to the 80GB models.

[Llorean]

And the Nano. As I've said, it's currently believed to be a bug in the Apple bootloader (since it only happens in that, and it has happened to people who've never installed Rockbox).

[bluebrother]

Also, this isn't a Rockbox issue -- when turning on the Ipod there is Apple's startup code running (which itself loads the bootloader). So unfortunately there is nothing we can simply do about. Btw, I sometimes experience that on my mini too.

[robin0800]

Yes its definately an apple problem.
On a side issue does any one know, if using the latest Itunes to restore the ipod is the apple bootloader overwritten/upgraded?

[itihatigoroku]

I'm sorry, because I am not good at English, it is a machine translation.

http://www.rockbox.org/tracker/task/6175
Though it writes here because the above-mentioned bug was close about another ploblem...
I think that there is a problem also in Rockbox. seems this is not a problem when booting.
Though the firmware of Apple might also have the problem,
However, it is happend frequently.
It seems that Rockbox can't shut down normally. When this occurs, screen and sound when Rockbox is shutting down are obviously different from it the usual.
If this is a problem when booting,
How do explain that the battery level decreases when this occurs?
For about one year in the previous build,
I think that this bug had not happened...