Battery incorrectly reported as critcally low at when almost full
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
DeviceKit-Power |
Invalid
|
Undecided
|
Unassigned | ||
devicekit-power (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: gnome-power-manager
Release: 9.10
gnome-power-manager 2.28.1
Pop up message appears stating battery critically low and action set in power management is triggered although the power manager applet still reports good charge. This happened at 80% and then again at 30% in one discharge. After reboot the machine continues to run on battery as normal. This has only happened since upgrade to 9.10 on my Acer Aspire one A110.
Output of /usr/share/
Distro version: squeeze/sid
Kernel version: 2.6.31-14-generic
g-p-m version: 2.28.1
HAL version: 0.5.13
System manufacturer: missing
System version: missing
System product: missing
AC adapter present: yes
Battery present: yes
Laptop panel present: no
CPU scaling present: yes
Battery Information:
battery.
battery.
battery.
battery.
battery.
battery.
battery.model = 'UM08A72' (string)
battery.present = true (bool)
battery.
battery.
battery.
battery.
battery.
battery.
battery.
battery.
battery.serial = '0544' (string)
battery.
battery.type = 'primary' (string)
battery.vendor = 'SIMPLO' (string)
battery.
battery.
battery.
DeviceKit data:
Device: /org/freedeskto
native-path: /sys/devices/
vendor: SIMPLO
model: UM08A72
serial: 0544
power supply: yes
updated: Tue Nov 3 22:12:14 2009 (5137 seconds ago)
has history: yes
has statistics: yes
battery
present: yes
rechargeable: yes
state: fully-charged
energy: 22.7883 Wh
energy-empty: 0 Wh
energy-full: 22.7883 Wh
energy-
energy-rate: 716.228 W
voltage: 12.147 V
percentage: 100%
capacity: 85.5417%
technology: lithium-ion
Device: /org/freedeskto
native-path: /sys/devices/
power supply: yes
updated: Tue Nov 3 21:12:15 2009 (8736 seconds ago)
has history: no
has statistics: no
line-power
online: yes
Daemon:
daemon-version: 011
can-suspend: yes
can-hibernate yes
on-battery: no
on-low-battery: no
lid-is-closed: no
lid-is-present: yes
GNOME Power Manager Process Information:
1000 1494 0.0 0.7 35072 11968 ? S 21:12 0:02 \_ gnome-power-manager
HAL Process Information:
107 801 0.0 0.2 6260 4040 ? Ss 21:12 0:01 hald --daemon=yes
root 915 0.0 0.0 3336 1200 ? S 21:12 0:00 \_ hald-runner
root 1153 0.0 0.0 3412 1140 ? S 21:12 0:00 \_ hald-addon-input: Listening on /dev/input/event8 /dev/input/event5 /dev/input/event3 /dev/input/event2 /dev/input/event1 /dev/input/event6 /dev/input/event0
root 1154 0.0 0.0 3420 1124 ? S 21:12 0:00 \_ /usr/lib/
107 1155 0.0 0.0 3256 1124 ? S 21:12 0:00 \_ hald-addon-acpi: listening on acpid socket /var/run/
This bug seems to be related to other simalar issues such as Bug #393008
I notice that the power manager applet doesnt recognise the AC has been unplugged. After running like that for an hour or so shut the machine down. Restarted later in the day and the indicator now correctly reported battery power and correct battery level however this soon changed to telling me the battery was almost empty (7% or so) but still with more than 30 min run time remaining.
On closer inspection running $ devkit-power --monitor-detail
The battery was incorrectly reported as
energy-full: 88.7883 Wh (or there abouts)
energy-full-design: 26.64 Wh
I didn't get chance to copy this as my machine shut down seconds after I noticed this. The machine is now on charge and looking at this again I notice the charge rate is extremely high which cannot be correct
History (charge):
1258072896 50.999 charging
1258072865 50.609 charging
1258072834 50.268 charging
1258072803 49.683 charging
History (rate):
1258072896 715.928 charging
1258072865 715.950 charging
1258072834 715.850 charging
1258072803 716.771 charging
The charge graphs are also all over the place. see screen shot at http:// www.flickr. com/photos/ bshephard/ 4098866663/
Bugs in Devicekit-power seem not to be handled by launchpad but I don't see any way to record the bug upstream either. Documentation also seems to be incomplete