| 2016-01-25 08:56:52 |
Jean-Baptiste Lallement |
bug |
|
|
added bug |
| 2016-01-25 08:56:52 |
Jean-Baptiste Lallement |
attachment added |
|
history-charge-generic_id.dat https://bugs.launchpad.net/bugs/1537668/+attachment/4556124/+files/history-charge-generic_id.dat |
|
| 2016-01-25 08:57:12 |
Jean-Baptiste Lallement |
attachment added |
|
power.20160124-103548.csv https://bugs.launchpad.net/canonical-devices-system-image/+bug/1537668/+attachment/4556125/+files/power.20160124-103548.csv |
|
| 2016-01-25 08:57:25 |
Jean-Baptiste Lallement |
attachment added |
|
screenshot20160124_225415263.png https://bugs.launchpad.net/canonical-devices-system-image/+bug/1537668/+attachment/4556126/+files/screenshot20160124_225415263.png |
|
| 2016-01-25 08:57:38 |
Jean-Baptiste Lallement |
attachment added |
|
history-from-sysfs.png https://bugs.launchpad.net/canonical-devices-system-image/+bug/1537668/+attachment/4556127/+files/history-from-sysfs.png |
|
| 2016-01-25 09:00:58 |
Jean-Baptiste Lallement |
description |
mako rc-proposed/ubunut 348
In some cases, apparently when the state of the device changes and the device is immediately suspended, upower history stops being updated and results in graphs like the one attached (ignore the sudden drop then jump between 5:00AM and 10:00AM, investigation is still ongoing)
In the history file attached, the history stops on Sun, 24 Jan 2016 09:36:50 GMT (1453628210) It corresponds to the state change of the device (charging -> discharging) around the same time (1453628284 - Sun, 24 Jan 2016 09:38:04 GMT in power.20160124-103548.csv)
Then if you plug the device to a charger and unplug it but don't suspend it the update of the history resumes normally (around 10:00PM). The graph shows the charge decreasing linearly (which is wrong, it should look like the graph history-from-sysfs.png which is based on battery/capacity sysfs entry) |
mako rc-proposed/ubunut 348
In some cases, apparently when the state of the device changes and the device is immediately suspended, upower history stops being updated and results in graphs like the one attached (ignore the sudden drop then jump between 5:00AM and 10:00AM, investigation is still ongoing)
In the history file attached, the history stops on Sun, 24 Jan 2016 09:36:50 GMT (1453628210) It corresponds to the state change of the device (charging -> discharging) around the same time (1453628284 - Sun, 24 Jan 2016 09:38:04 GMT in power.20160124-103548.csv)
Then if you plug the device to a charger and unplug it but don't suspend it the update of the history resumes normally (around 10:00PM). The graph shows the charge decreasing linearly (which is wrong, it should look like the graph history-from-sysfs.png which is based on battery/capacity sysfs entry)
The attached screenshot shows the network 4G data is available but doesn't connect as shown in the indicator.
Possible Test Case:
1. Disable main sources of wakeup (bt, wifi, location, set airplane mode on)
2. plug it to a charger for a short time (15min or so), but don't fully charge it
3. unplug the DUT and press the power button to suspend it
4. wait several hours without waking up the device.
Actual Result
The history is not updating anymore. |
|
| 2016-01-25 09:01:53 |
Jean-Baptiste Lallement |
description |
mako rc-proposed/ubunut 348
In some cases, apparently when the state of the device changes and the device is immediately suspended, upower history stops being updated and results in graphs like the one attached (ignore the sudden drop then jump between 5:00AM and 10:00AM, investigation is still ongoing)
In the history file attached, the history stops on Sun, 24 Jan 2016 09:36:50 GMT (1453628210) It corresponds to the state change of the device (charging -> discharging) around the same time (1453628284 - Sun, 24 Jan 2016 09:38:04 GMT in power.20160124-103548.csv)
Then if you plug the device to a charger and unplug it but don't suspend it the update of the history resumes normally (around 10:00PM). The graph shows the charge decreasing linearly (which is wrong, it should look like the graph history-from-sysfs.png which is based on battery/capacity sysfs entry)
The attached screenshot shows the network 4G data is available but doesn't connect as shown in the indicator.
Possible Test Case:
1. Disable main sources of wakeup (bt, wifi, location, set airplane mode on)
2. plug it to a charger for a short time (15min or so), but don't fully charge it
3. unplug the DUT and press the power button to suspend it
4. wait several hours without waking up the device.
Actual Result
The history is not updating anymore. |
mako rc-proposed/ubunut 348
Possible one reason of the symptoms observed in bug 1471913
In some cases, apparently when the state of the device changes and the device is immediately suspended, upower history stops being updated and results in graphs like the one attached (ignore the sudden drop then jump between 5:00AM and 10:00AM, investigation is still ongoing)
In the history file attached, the history stops on Sun, 24 Jan 2016 09:36:50 GMT (1453628210) It corresponds to the state change of the device (charging -> discharging) around the same time (1453628284 - Sun, 24 Jan 2016 09:38:04 GMT in power.20160124-103548.csv)
Then if you plug the device to a charger and unplug it but don't suspend it the update of the history resumes normally (around 10:00PM). The graph shows the charge decreasing linearly (which is wrong, it should look like the graph history-from-sysfs.png which is based on battery/capacity sysfs entry)
The attached screenshot shows the network 4G data is available but doesn't connect as shown in the indicator.
Possible Test Case:
1. Disable main sources of wakeup (bt, wifi, location, set airplane mode on)
2. plug it to a charger for a short time (15min or so), but don't fully charge it
3. unplug the DUT and press the power button to suspend it
4. wait several hours without waking up the device.
Actual Result
The history is not updating anymore. |
|
| 2016-01-25 09:01:57 |
Jean-Baptiste Lallement |
canonical-devices-system-image: importance |
Undecided |
High |
|
| 2016-01-25 09:02:08 |
Jean-Baptiste Lallement |
bug task added |
|
upower (Ubuntu) |
|
| 2016-01-26 17:10:18 |
Pat McGowan |
canonical-devices-system-image: status |
New |
Confirmed |
|
| 2016-01-26 17:10:18 |
Pat McGowan |
canonical-devices-system-image: milestone |
|
backlog |
|
| 2016-01-26 17:10:18 |
Pat McGowan |
canonical-devices-system-image: assignee |
|
Pat McGowan (pat-mcgowan) |
|
| 2016-01-26 18:25:49 |
Pat McGowan |
upower (Ubuntu): assignee |
|
Martin Pitt (pitti) |
|
| 2016-01-27 13:32:33 |
Jean-Baptiste Lallement |
attachment added |
|
battery.1453894138.log https://bugs.launchpad.net/canonical-devices-system-image/+bug/1537668/+attachment/4557542/+files/battery.1453894138.log |
|
| 2016-02-23 15:53:25 |
Pat McGowan |
tags |
|
power-bugs |
|
| 2016-06-06 06:41:58 |
Martin Pitt |
upower (Ubuntu): assignee |
Martin Pitt (pitti) |
|
|
| 2016-06-29 06:52:40 |
Launchpad Janitor |
upower (Ubuntu): status |
New |
Confirmed |
|
| 2016-06-29 06:52:44 |
Richard Somlói |
bug |
|
|
added subscriber Richard Somlói |
