This is the bug/patch tracker for Rockbox. Click here for more information.
Quick links: Bugs · Patches · Rockbox frontpage
FS#10508 - Player gets stuck because of incorrect battery status
Attached to Project:
Rockbox
Opened by Heinrich Münz (HMuenz) - Tuesday, 11 August 2009, 11:10 GMT+2
Last edited by Andree Buschmann (Buschel) - Wednesday, 27 July 2011, 21:38 GMT+2
Opened by Heinrich Münz (HMuenz) - Tuesday, 11 August 2009, 11:10 GMT+2
Last edited by Andree Buschmann (Buschel) - Wednesday, 27 July 2011, 21:38 GMT+2
|
DetailsSometimes, when I boot my Sansa e260 (v1) into rockbox with a fully charged battery, it suddenly gets stuck after about 30 minutes, and the display tells me, that the battery is low. When I switch off the player and boot into rockbox again, the battery symbol indicates again, that the battery is fully (or nearly fully) charged. Now it's a game of chance: Will it play on correctly now, or will it get stucked again. Both can happen.
I have never had that problem before rb 3.3. |
This task depends upon
Closed by Andree Buschmann (Buschel)
Wednesday, 27 July 2011, 21:38 GMT+2
Reason for closing: Out of Date
Additional comments about closing: No further details since nearly 1 year.
Wednesday, 27 July 2011, 21:38 GMT+2
Reason for closing: Out of Date
Additional comments about closing: No further details since nearly 1 year.
As that page is a disambiguition page, the correct meaning in this context is http://en.wikipedia.org/wiki/Analog-to-digital_converter (all other technology meanings obviously won't match here anyway). It's a standard abbreviation in the electronics area.
As for your report: you never had that problem before release 3.3. But does the problem disappear when downgrading to an older version? If it's a hardware failure it unsurprisingly isn't related to the Rockbox version.
I have been running rockbox 3.2 for a couple of days now - and everything works fine. Until now, the problem hasn't occurred anymore. I even played the same playlist where playback got stuck last time, but everything worked just fine. So it doesn't seem to be a hardware issue.
I also noticed that the scrollwheel didn't work correctly in rb 3.3, sometimes it seemed to be kinda locked. In rb 3.2 it works correctly again (unless the database is updating in the background). But that's possibly another bug.
Please tell me if you need any more information.