ACPI battery information not correctly updating on Acer Aspire ZG5

Bug #931821 reported by Adam Portier
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
upower (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

My battery status indicator is reporting incorrect times for both charge and discharge. The time will fluxuate greatly across values much to large to be believed (5 hours to charge, 6 hours to discharge). The battery will also not indicate a correct charge percentage. Upon reboot, the information appears correct for a few minutes, then starts drifting to incorrect values. Attached are the hal-device outputs from similar bug report already on Launchpad.

Charging
acpitool -b
  Battery #1 : charging, 38.05%, 04:51:32

Discharging
acpitool -b
  Battery #1 : charged, 38.17%, 02:14:36

hal-find-by-capability --capability "ac_adapter" | xargs -n 1 hal-device
udi = '/org/freedesktop/Hal/devices/computer_power_supply_ac_adapter_ACAD'
  linux.hotplug_type = 2 (0x2) (int)
  linux.subsystem = 'power_supply' (string)
  ac_adapter.present = false (bool)
  info.subsystem = 'power_supply' (string)
  info.product = 'Generic AC Adapter Device' (string)
  linux.sysfs_path = '/sys/devices/LNXSYSTM:00/device:00/ACPI0003:00/power_supply/ACAD' (string)
  info.parent = '/org/freedesktop/Hal/devices/computer' (string)
  info.udi = '/org/freedesktop/Hal/devices/computer_power_supply_ac_adapter_ACAD' (string)
  info.category = 'ac_adapter' (string)
  info.capabilities = { 'ac_adapter' } (string list)

hal-find-by-capability --capability "battery" | xargs -n 1 hal-device
udi = '/org/freedesktop/Hal/devices/computer_power_supply_battery_BAT1'
  linux.hotplug_type = 2 (0x2) (int)
  linux.subsystem = 'power_supply' (string)
  battery.type = 'primary' (string)
  battery.reporting.technology = 'Li-ion' (string)
  battery.technology = 'lithium-ion' (string)
  battery.model = 'UM08B74' (string)
  battery.vendor = 'SIMPLO' (string)
  battery.voltage.design = 11100 (0x2b5c) (int)
  battery.voltage.unit = 'mV' (string)
  info.product = 'UM08B74' (string)
  battery.reporting.design = 5200 (0x1450) (int)
  battery.serial = '013B' (string)
  battery.present = true (bool)
  battery.reporting.unit = 'mAh' (string)
  battery.reporting.rate = 658 (0x292) (int)
  battery.is_rechargeable = true (bool)
  battery.rechargeable.is_charging = true (bool)
  battery.rechargeable.is_discharging = false (bool)
  battery.reporting.current = 1847 (0x737) (int)
  battery.reporting.last_full = 4949 (0x1355) (int)
  battery.charge_level.current = 20501 (0x5015) (int)
  battery.charge_level.last_full = 54933 (0xd695) (int)
  battery.charge_level.design = 57720 (0xe178) (int)
  battery.charge_level.rate = 7303 (0x1c87) (int)
  battery.charge_level.percentage = 37 (0x25) (int)
  battery.remaining_time = 16973 (0x424d) (int)
  info.subsystem = 'power_supply' (string)
  battery.voltage.current = 11472 (0x2cd0) (int)
  info.udi = '/org/freedesktop/Hal/devices/computer_power_supply_battery_BAT1' (string)
  linux.sysfs_path = '/sys/devices/LNXSYSTM:00/device:00/PNP0C0A:00/power_supply/BAT1' (string)
  info.parent = '/org/freedesktop/Hal/devices/computer' (string)
  info.category = 'battery' (string)
  info.capabilities = { 'battery' } (string list)

Revision history for this message
Adam Portier (aportier) wrote :
Revision history for this message
Adam Portier (aportier) wrote :
Revision history for this message
Steve Langasek (vorlon) wrote :

Acpi-support is not related to reports of charge/discharge time. Reassigning to upower.

affects: acpi-support (Ubuntu) → upower (Ubuntu)
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Thank you for reporting this bug to Ubuntu.
Ubuntu 17.04 (zesty) reached end-of-life on January 13, 2018.
Ubuntu 16.10 (yakkety) reached end-of-life on July 20, 2017.
Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016.
Ubuntu 15.04 (vivid) reached end-of-life on February 4, 2016.
Ubuntu 14.10 (utopic) reached end-of-life on July 23, 2015.
Ubuntu 13.10 (saucy) reached end-of-life on July 17, 2014.
Ubuntu 13.04 (raring) reached end-of-life on January 27, 2014.
Ubuntu 12.10 (quantal) reached end-of-life on May 16, 2014.
Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017.
Ubuntu 11.10 (oneiric) reached end-of-life on May 9, 2013.
Ubuntu 11.04 (natty) reached end-of-life on October 28, 2012.
Ubuntu 10.10 (maverick) reached end-of-life on April 10, 2012.
Ubuntu 10.04 (lucid) reached end-of-life on May 9, 2013.
Ubuntu 9.10 (karmic) reached end-of-life on April 30, 2011.
Ubuntu 9.04 (jaunty) reached end-of-life on October 23, 2010.
Ubuntu 8.10 (intrepid) reached end-of-life on April 30, 2010.
Ubuntu 8.04 (hardy) reached end-of-life on May 12, 2011.
Ubuntu 7.10 (gutsy) reached end-of-life on April 18th, 2009.
Ubuntu 7.04 (feisty) reached end-of-life on October 19, 2008.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed.

Changed in upower (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.