FS#11755 - Battery reports 0% charge even after fully charged in Rockbox 3.7 - iRiver H300

Attached to Project: Rockbox
Opened by Andy Smith (ufo) - Saturday, 13 November 2010, 13:27 GMT
Last edited by Bertrik Sikken (bertrik) - Saturday, 13 November 2010, 15:14 GMT
Task Type Bugs
Category Battery/Charging
Status Unconfirmed
Assigned To No-one
Operating System Iriver H300 series
Severity Low
Priority Normal
Reported Version Daily build (which?)
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No


URGENT/HIGH PRIORITY: Rockbox Firmware 3.7 installed with iRiver H300 1.29J.

Charging when in Rockbox mode (player switched on):

When Rockbox is running and the charger is plugged in, Rockbox can be seen charging the battery in the top left hand corner. When it is fully charged, it shows a full battery.

Charging when iRiver is powered off (player switched off):

When the charger is plugged in, the iRiver begins charging in Original Firmware mode. This is okay as the player charges correctly until Complete.

Booting into OF mode, shows a full battery charge so I can be sure it is fully charged.

However, boot back into Rockbox mode and Rockbox seems to be misreporting the battery charge as depleted - I say misreporting because at this point I know it is actually full/complete. (Booting back into OF mode would also confirm again at this point that there is indeed a full battery charge).

But run Rockbox 3.7 and after a few minutes, a false message - "Low Battery - Shutting Down" appears, after which Rockbox powers off.

I know this is inccorect, because if the battery was so low in OF, the iRiver OF would not even allow you to attempt to power back on (instead it would display a "Low Battery" picture on the display), but I can boot back into OF mode easily with no problems even after this message from Rockbox, again the OF shows a full battery and I can run it for hours with no problem so I know somewhere here there must be a miscommunication/misreading from the battery charge to the Rockbox 3.7 firmware.

Have tested this a number of times to ensure it is a fault and yes it presents itself everytime.
This task depends upon