| 2016-01-31 11:27:52 |
Jean-Baptiste Lallement |
bug |
|
|
added bug |
| 2016-01-31 11:27:52 |
Jean-Baptiste Lallement |
attachment added |
|
upower-history-charge-krillin-20160131.png https://bugs.launchpad.net/bugs/1540062/+attachment/4560486/+files/upower-history-charge-krillin-20160131.png |
|
| 2016-01-31 11:31:27 |
Jean-Baptiste Lallement |
attachment added |
|
syslog.1454238636 https://bugs.launchpad.net/canonical-devices-system-image/+bug/1540062/+attachment/4560487/+files/syslog.1454238636 |
|
| 2016-01-31 11:43:55 |
Jean-Baptiste Lallement |
description |
current build number: 248
device name: krillin
channel: ubuntu-touch/rc-proposed/bq-aquaris.en
[This report is used to gather data about the main issue reported in bug 1471913]
Test Case:
1. Charge the device to a reasonable capacity (between 30% and 50%)
2. Reboot it
3. Let it drain
Actual result
After some time (in this experiment it was 24h) the capacity suddenly drops to 0 (from 10% in this case) |
current build number: 248
device name: krillin
channel: ubuntu-touch/rc-proposed/bq-aquaris.en
[This report is used to gather data about the main issue reported in bug 1471913]
Test Case:
1. Charge the device to a reasonable capacity (between 30% and 50%)
2. Reboot it
3. Let it drain
Actual result
After some time (in this experiment it was 24h) the capacity suddenly drops to 0 (from 10% in this case)
The graph attached shows upower charges history over time.
From syslog the battery is the wakeup source so the battery is really empty:
Jan 31 10:31:24 ubuntu-phablet kernel: [ 3696.984325]active wakeup source: battery
The test is rerunning and captures the value of the capacity from the battery to check if the difference between the capacity reported by upower comes from upower itself or the driver or lower. |
|
| 2016-01-31 12:56:15 |
Jean-Baptiste Lallement |
description |
current build number: 248
device name: krillin
channel: ubuntu-touch/rc-proposed/bq-aquaris.en
[This report is used to gather data about the main issue reported in bug 1471913]
Test Case:
1. Charge the device to a reasonable capacity (between 30% and 50%)
2. Reboot it
3. Let it drain
Actual result
After some time (in this experiment it was 24h) the capacity suddenly drops to 0 (from 10% in this case)
The graph attached shows upower charges history over time.
From syslog the battery is the wakeup source so the battery is really empty:
Jan 31 10:31:24 ubuntu-phablet kernel: [ 3696.984325]active wakeup source: battery
The test is rerunning and captures the value of the capacity from the battery to check if the difference between the capacity reported by upower comes from upower itself or the driver or lower. |
current build number: 248
device name: krillin
channel: ubuntu-touch/rc-proposed/bq-aquaris.en
[This report is used to gather data about the main issue reported in bug 1471913]
Test Case:
1. Charge the device to a reasonable capacity (between 30% and 50%)
2. Reboot it
3. Let it drain
Actual result
After some time (in this experiment it was 24h) the capacity suddenly drops to 0 (from 10% in this case)
The graph attached shows upower charges history over time.
From syslog the battery is the wakeup source so it suggests that the battery is really empty:
⟫ grep battery syslog.1454238636
Jan 31 10:31:24 ubuntu-phablet kernel: [ 3696.984325]active wakeup source: battery
Jan 31 10:47:41 ubuntu-phablet powerd[935]: Turning screen on, battery state changes
Jan 31 10:53:09 ubuntu-phablet kernel: [ 4215.152283]active wakeup source: battery suspend wakelock
Although on the upower graph, upower reports 28% left at exactly the same time (there is a +1h offset due to timezone)
09:38:36 29 discharging
11:31:56 28 discharging
11:32:28 27 discharging
Then starting from 10:31 UTC it goes down to zero in about 15 minutes. The powerd events correspond to the low battery notification.
The test is rerunning and captures the value of the capacity from the battery to check if the difference between the capacity reported by upower comes from upower itself or the driver or lower. |
|
| 2016-01-31 12:56:52 |
Jean-Baptiste Lallement |
description |
current build number: 248
device name: krillin
channel: ubuntu-touch/rc-proposed/bq-aquaris.en
[This report is used to gather data about the main issue reported in bug 1471913]
Test Case:
1. Charge the device to a reasonable capacity (between 30% and 50%)
2. Reboot it
3. Let it drain
Actual result
After some time (in this experiment it was 24h) the capacity suddenly drops to 0 (from 10% in this case)
The graph attached shows upower charges history over time.
From syslog the battery is the wakeup source so it suggests that the battery is really empty:
⟫ grep battery syslog.1454238636
Jan 31 10:31:24 ubuntu-phablet kernel: [ 3696.984325]active wakeup source: battery
Jan 31 10:47:41 ubuntu-phablet powerd[935]: Turning screen on, battery state changes
Jan 31 10:53:09 ubuntu-phablet kernel: [ 4215.152283]active wakeup source: battery suspend wakelock
Although on the upower graph, upower reports 28% left at exactly the same time (there is a +1h offset due to timezone)
09:38:36 29 discharging
11:31:56 28 discharging
11:32:28 27 discharging
Then starting from 10:31 UTC it goes down to zero in about 15 minutes. The powerd events correspond to the low battery notification.
The test is rerunning and captures the value of the capacity from the battery to check if the difference between the capacity reported by upower comes from upower itself or the driver or lower. |
current build number: 248
device name: krillin
channel: ubuntu-touch/rc-proposed/bq-aquaris.en
[This report is used to gather data about the main issue reported in bug 1471913]
Test Case:
1. Charge the device to a reasonable capacity (between 30% and 50%)
2. Reboot it
3. Let it drain
Actual result
After some time (in this experiment it was 24h) the capacity suddenly drops to 0 (from 10% in this case)
The graph attached shows upower charges history over time.
From syslog the battery is the wakeup source so it suggests that the battery is really empty:
⟫ grep battery syslog.1454238636
Jan 31 10:31:24 ubuntu-phablet kernel: [ 3696.984325]active wakeup source: battery
Jan 31 10:47:41 ubuntu-phablet powerd[935]: Turning screen on, battery state changes
Jan 31 10:53:09 ubuntu-phablet kernel: [ 4215.152283]active wakeup source: battery suspend wakelock
Although on the upower graph, upower reports 28% left at exactly the same time (there is a +1h offset due to timezone)
09:38:36 29 discharging
11:31:56 28 discharging
11:32:28 27 discharging
[...]
11:46:41 1 discharging
11:47:11 0 discharging
Then starting from 10:31 UTC it goes down to zero in about 15 minutes. The powerd events correspond to the low battery notification.
The test is rerunning and captures the value of the capacity from the battery to check if the difference between the capacity reported by upower comes from upower itself or the driver or lower. |
|
| 2016-02-01 10:42:55 |
Jean-Baptiste Lallement |
description |
current build number: 248
device name: krillin
channel: ubuntu-touch/rc-proposed/bq-aquaris.en
[This report is used to gather data about the main issue reported in bug 1471913]
Test Case:
1. Charge the device to a reasonable capacity (between 30% and 50%)
2. Reboot it
3. Let it drain
Actual result
After some time (in this experiment it was 24h) the capacity suddenly drops to 0 (from 10% in this case)
The graph attached shows upower charges history over time.
From syslog the battery is the wakeup source so it suggests that the battery is really empty:
⟫ grep battery syslog.1454238636
Jan 31 10:31:24 ubuntu-phablet kernel: [ 3696.984325]active wakeup source: battery
Jan 31 10:47:41 ubuntu-phablet powerd[935]: Turning screen on, battery state changes
Jan 31 10:53:09 ubuntu-phablet kernel: [ 4215.152283]active wakeup source: battery suspend wakelock
Although on the upower graph, upower reports 28% left at exactly the same time (there is a +1h offset due to timezone)
09:38:36 29 discharging
11:31:56 28 discharging
11:32:28 27 discharging
[...]
11:46:41 1 discharging
11:47:11 0 discharging
Then starting from 10:31 UTC it goes down to zero in about 15 minutes. The powerd events correspond to the low battery notification.
The test is rerunning and captures the value of the capacity from the battery to check if the difference between the capacity reported by upower comes from upower itself or the driver or lower. |
current build number: 248
device name: krillin
channel: ubuntu-touch/rc-proposed/bq-aquaris.en
[This report is used to gather data about the main issue reported in bug 1471913]
Test Case:
1. Charge the device to a reasonable capacity (between 30% and 50%)
2. Reboot it
3. Let it drain
Actual result
After some time (in this experiment it was 24h) the capacity suddenly drops to 0 (from 10% in this case)
The graph attached shows upower charges history over time.
From syslog the battery is the wakeup source so it suggests that the battery is really empty:
⟫ grep battery syslog.1454238636
Jan 31 10:31:24 ubuntu-phablet kernel: [ 3696.984325]active wakeup source: battery
Jan 31 10:47:41 ubuntu-phablet powerd[935]: Turning screen on, battery state changes
Jan 31 10:53:09 ubuntu-phablet kernel: [ 4215.152283]active wakeup source: battery suspend wakelock
Although on the upower graph, upower reports 28% left at exactly the same time (there is a +1h offset due to timezone)
09:38:36 29 discharging
11:31:56 28 discharging
11:32:28 27 discharging
[...]
11:46:41 1 discharging
11:47:11 0 discharging
Then starting from 10:31 UTC it goes down to zero in about 15 minutes. The powerd events correspond to the low battery notification.
The driver uses 2 counters:
- SOC: Read from battery meter
- UI_SOC: State of charge internal to the driver
The capacity attributes exposed by sysfs in /sys/class/power_supply/battery corresponds to UI_SOC.
The driver linearly decreases (or increases) the UI_SOC each time the battery status is updated i.e either called from pmic when a charger is plugged or unplugged, or from the battery kthread.
If UI SOC drifts too much, the driver triggers an adjustment algorithm until
UI SOC is back within bounds. There is a calibration mechanism to calculate the periodicity and the step to use for the adjustment.
The driver syncs the RTC SOC with the UI SOC if:
- UI_SOC - SOC >MAX_DIFF_UI_AND_SOC (2)
- SOC > MIN_SOC_FOR_ADJUST (20)
The battery graph suddenly decreasing to 0, then oscillating between 0 and 1 until the battery is completely empty (<3.4V) is the symptom of this adjustment function.
For some reason this adjustment function is not triggered when it should, the difference between the SOC in the driver and the real SOC becomes significant (> 20%) and the adjustment only starts when the battery is already below a critical level. |
|
| 2016-02-02 10:58:22 |
Jean-Baptiste Lallement |
attachment added |
|
upower-history-charge_20160201.png https://bugs.launchpad.net/canonical-devices-system-image/+bug/1540062/+attachment/4562036/+files/upower-history-charge_20160201.png |
|
| 2016-02-02 10:59:36 |
Jean-Baptiste Lallement |
attachment added |
|
power.20160131-112359.ods https://bugs.launchpad.net/canonical-devices-system-image/+bug/1540062/+attachment/4562037/+files/power.20160131-112359.ods |
|
| 2016-02-03 23:43:55 |
Pat McGowan |
canonical-devices-system-image: importance |
Undecided |
High |
|
| 2016-02-03 23:43:55 |
Pat McGowan |
canonical-devices-system-image: status |
New |
Confirmed |
|
| 2016-02-03 23:43:55 |
Pat McGowan |
canonical-devices-system-image: milestone |
|
backlog |
|
| 2016-02-03 23:43:55 |
Pat McGowan |
canonical-devices-system-image: assignee |
|
Jean-Baptiste Lallement (jibel) |
|
| 2016-02-04 13:07:27 |
Jean-Baptiste Lallement |
attachment added |
|
arale_20160204_battery.png https://bugs.launchpad.net/canonical-devices-system-image/+bug/1540062/+attachment/4563738/+files/arale_20160204_battery.png |
|
| 2016-02-04 13:08:31 |
Jean-Baptiste Lallement |
attachment added |
|
fg.20160203-122551.ods https://bugs.launchpad.net/canonical-devices-system-image/+bug/1540062/+attachment/4563741/+files/fg.20160203-122551.ods |
|
| 2016-02-23 15:57:52 |
Pat McGowan |
tags |
|
power-bugs |
|
| 2016-03-15 13:46:14 |
advocatux |
bug |
|
|
added subscriber advocatux |
| 2016-03-15 17:45:08 |
Marek Greško |
bug |
|
|
added subscriber Marek Greško |
| 2016-11-11 20:14:19 |
Alexey Balmashnov |
bug |
|
|
added subscriber Alexey Balmashnov |
| 2016-11-24 00:28:55 |
Cousteau |
attachment added |
|
screenshot20161124_013328616.png https://bugs.launchpad.net/canonical-devices-system-image/+bug/1540062/+attachment/4782246/+files/screenshot20161124_013328616.png |
|
| 2016-12-08 20:30:06 |
Pablo180 |
bug |
|
|
added subscriber Pablo180 |
| 2016-12-30 15:00:01 |
Henrik Norrman |
bug |
|
|
added subscriber Henrik Norrman |
| 2017-01-17 09:00:35 |
Dirk-Jan van Leeuwen |
bug |
|
|
added subscriber Dirk-Jan van Leeuwen |
