upower gives incorrect data/misleading data
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
upower (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: upower
I am using lucid. I have a dell inspiron 6000
upower gives data that is inconsistent with acpi.
> acpi
Battery 0: Charging, 27%, 01:25:50 until charged
this agrees with the bios, so I believe it to be correct.
> upower --dump
Device: /org/freedeskto
native-path: /sys/devices/
power supply: yes
updated: Tue Jun 15 22:34:20 2010 (754 seconds ago)
has history: no
has statistics: no
line-power
online: yes
Device: /org/freedeskto
native-path: /sys/devices/
vendor: Sanyo
model: DELL F51267
serial: 1410
power supply: yes
updated: Tue Jun 15 22:46:25 2010 (29 seconds ago)
has history: yes
has statistics: yes
battery
present: yes
rechargeable: yes
state: charging
energy: 14.8962 Wh
energy-empty: 0 Wh
energy-full: 79.92 Wh
energy-
energy-rate: 26.3514 W
voltage: 11.64 V
time to full: 2.5 hours
percentage: 18.6389%
capacity: 67.375%
technology: lithium-ion
History (charge):
1276638385 18.639 charging
1276638355 18.347 charging
1276638325 18.042 charging
History (rate):
1276638385 26.351 charging
1276638355 29.393 charging
1276638325 27.728 charging
Daemon:
daemon-version: 0.9.1
can-suspend: yes
can-hibernate yes
on-battery: no
on-low-battery: no
lid-is-closed: no
lid-is-present: yes
the incorrect stat is percentage. Note that it is 18%, i.e. different from what acpi reports. this battery is an older battery and only holds about 65% of the design capacity when full. So, energy-full seems to be wrong as well. I don't know what capacity is, but as I said the last full capacity is about 2/3 of the design capacity, so it could be that. In fact, 18%/67%= 27% agrees with acpi, so that is probably what capacity means.
Anyways, this is causing my gnome-power-manager to report the wrong charge as well.
Something similar is happening to my computer. Not only is the charge information inconsistent, the reporting technology of the battery also changes inexplicably from Li-ion to Nimh. I believe, in my case, these issues may be related. I have been looking into writing a udev rule to force the correct battery type, but I don't know if this will correct the charge information.
System: HP Pavilion dv5-1125nr
OS: Ubuntu Lucid Lynx 10.04, all updates applied (6-16-10)
Dave