• Status Closed
  • Percent Complete
  • Task Type Patches
  • Category Battery/Charging
  • Assigned To No-one
  • Operating System Sansa e200
  • Severity Low
  • Priority Very Low
  • Reported Version
  • Due in Version Undecided
  • Due Date Undecided
  • Votes 3
  • Private
Attached to Project: Rockbox
Opened by mattzz - 2007-03-19
Last edited by Marc_Guay - 2008-03-31

FS#6860 - prepared correct sansa e200 battery status handling

- prepared a first version of correct battery status handling
- improved battery status accuracy
- this is a first shot, more measurements have to be done

Closed by  Marc_Guay
2008-03-31 19:23
Reason for closing:  Out of Date
Additional comments about closing:   Warning: Undefined array key "typography" in /home/rockbox/flyspray/plugins/dokuwiki/inc/parserutils.php on line 371 Warning: Undefined array key "camelcase" in /home/rockbox/flyspray/plugins/dokuwiki/inc/parserutils.php on line 407

Power consumption improvements have made this obsolete.

- corrected shutdown voltage to 3,3V
- warning level 3,4V
- discharging curve linear between 3,3V and 4,2V

sansa-battery_2.diff committed to SVN. I’ll leave the task open for now as mattz wanted to improve on the linear discharge curve between 3.3V and 4.2V.

Added first complete discharge curve (had to patch batter_bench) on

my battery_bench file

Here is my battery_bench file. It ran from just about full charge to low battery shutdown.

Please make sure that you use a patched battery_bench plugin - otherwise the battery_bench.txt will not be completely written.
(Refer to for the information about the one line that has to be patched)

Recalibrate the voltage based on the latest batter_bench on the wiki page.

maybe a new idea to this:
instead of patching rockbox with new battery “profiles”, wouldnt it be better to patch rockbox to use a profile which we can put into a normal textfile?
as far as i understand the textfile only needs to hold a conversion table from Voltage to % and runtime left. The rockbox battery indication then needs to look into this file to get the correct readings.
this way everyone could use a battery profile which fits his/her needs.

if we could then update the battery-benchmark plugin to write exactly this textfile for the individual sansa we use, every user can use the plugin to create a battery profile matching his/her exact use of the sansa (as i believe the differen usages, graphics, games, settings influence the possible runtime of a battery).

MikeS commented on 2007-06-20 10:40

In general that might be helpful with the use of custom, non-OEM replacement batteries as well without having to have a custom build. Other profile information besides a conversion table should probably be included for charging purposes.

Does battery_bench still require to be patched? I can’t see a bug report or patch sitting in Flyspray and without it working properly, there is much less chance of an average user running it and adding to the base of knowledge…

EDIT - yes it does need to be patched.

I’ve raised a proper Flyspray bug report for this specific battery_bench plugin error here:

My battery_bench.txt from a full charge to an automatic shutdown.


Available keyboard shortcuts


Task Details

Task Editing