Battery level stuck overnight

Bug #1429784 reported by Víctor R. Ruiz on 2015-03-09
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
upower (Ubuntu)
Undecided
Unassigned

Bug Description

Test case.
- Leave the device locked overnight.
- On the next morning, go to System Settings > Battery.

Expected result.
- Battery should report a lower level.

Actual result.
- A plain graph is shown.

current build number: 135
device name: krillin
channel: ubuntu-touch/devel-proposed

Víctor R. Ruiz (vrruiz) wrote :
description: updated
Sebastien Bacher (seb128) wrote :

settings only displays the recording done by upower, that's an upower or kernel issue, not a settings one

affects: ubuntu-system-settings (Ubuntu) → upower (Ubuntu)
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in upower (Ubuntu):
status: New → Confirmed
Sturm Flut (sturmflut) wrote :

I noticed this bug when the system settings screen showed a battery level of 94% after 59 hours of idling. But I am not sure it is an userspace bug:

phablet@ubuntu-phablet:~$ cat /sys/devices/platform/battery/power_supply/battery/uevent
POWER_SUPPLY_NAME=battery
POWER_SUPPLY_STATUS=Charging
POWER_SUPPLY_HEALTH=Good
POWER_SUPPLY_PRESENT=1
POWER_SUPPLY_TECHNOLOGY=Li-ion
POWER_SUPPLY_CAPACITY=93
POWER_SUPPLY_BATT_VOL=4186
POWER_SUPPLY_BATT_TEMP=260
POWER_SUPPLY_TEMPERATURER=6644
POWER_SUPPLY_TEMPBATTVOLTAGE=508
POWER_SUPPLY_INSTATVOLT=4186
POWER_SUPPLY_BATTERYAVERAGECURRENT=462
POWER_SUPPLY_BATTERYSENSEVOLTAGE=4186
POWER_SUPPLY_ISENSEVOLTAGE=4275
POWER_SUPPLY_CHARGERVOLTAGE=4702
POWER_SUPPLY_STATUS_2ND=Discharging
POWER_SUPPLY_CAPACITY_2ND=50
POWER_SUPPLY_PRESENT_2ND=0
POWER_SUPPLY_VOLTAGE_MAX_DESIGN=4200000
POWER_SUPPLY_VOLTAGE_NOW=4186000
POWER_SUPPLY_TEMP=260

It shows POWER_SUPPLY_STATUS=Charging because I had to connect the USB cable for phablet-shell. POWER_SUPPLY_CAPACITY=93 must be wrong, it is an impossible value after two and a half days of idling with radios enabled. I rebooted the device and nothing changed.

So it might be a kernel and/or hardware issue.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers