Openmoko Bug #1158: Charging stops even while connected
Openmoko Public Trac
bugs at docs.openmoko.org
Mon Jun 15 03:45:32 CEST 2009
#1158: Charging stops even while connected
---------------------------------+------------------------------------------
Reporter: plr@… | Owner: openmoko-devel
Type: defect | Status: closed
Priority: high | Milestone: Om2008.10
Component: System Software | Version: unspecified
Severity: blocker | Resolution: fixed
Keywords: power management | Haspatch: 0
Blockedby: | Estimated:
Patchreview: | Blocking:
Reproducible: sometimes |
---------------------------------+------------------------------------------
Comment(by joerg):
http://www.batteryuniversity.com/partone-12.htm
According to this it isn't desirable to hold bat at 4.20V, no matter
whether charging or cyclic recharging.
My tests seem to show the PMU restarts charging properly at
>>autores = 1 from the dump => supposed to restart charging at 96% of
vbatmax
which according to CC is ~75%..80%.
Obviously the above mentioned restart by kernel is broken and so we don't
need to worry (fixed by bug ;-), just sysfs reports "charging" after
kernel tried to restart, when evidentally it isn't charging.
Common sense is LiIon batteries suffer much less from frequent small
90%..75%..90% cycles than from deep discharge or being kept at max charge
(4.2V) all the time.
So I think we should completely remove the (anyway useless, esp in
suspend) kernel resume scheme, and live with the fact that our bat reaches
~80% ~10..20h after charging stopped, then gets recharged by PMU
automatically.
Anybody who needs to make sure he has 100% capacity when leaving the house
should hook up the device to charger 3h prior to that, so it reaches 100%
capacity just in time and doesn't lose too much after stop of charging.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1158#comment:63>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
More information about the buglog
mailing list