| 2016-07-14 04:21:41 |
Selene ToyKeeper |
bug |
|
|
added bug |
| 2016-07-14 04:23:50 |
Selene ToyKeeper |
attachment added |
|
k-idle.png https://bugs.launchpad.net/repowerd/+bug/1602933/+attachment/4700590/+files/k-idle.png |
|
| 2016-07-14 04:25:44 |
Selene ToyKeeper |
attachment added |
|
a-display.png https://bugs.launchpad.net/repowerd/+bug/1602933/+attachment/4700591/+files/a-display.png |
|
| 2016-07-14 04:26:48 |
Selene ToyKeeper |
description |
As of yesterday's phone images (2016-07-12, krillin rc-p 383, arale rc-p 376, when repowerd landed), I'm getting unusual behavior during automated tests. This is easiest to see, manually, with video playback.
Steps to trigger this issue:
* Flash the affected image.
* Put a video on the device, at least 2 minutes long.
* Start video playback. Symptoms seem most severe when played via "adb shell" with "ubuntu-app-launch mediaplayer-app file:///media/phablet/3562-3231/Videos/long-video.avi".
* Wait at least 60 seconds.
* Unplug USB.
Expected result: Phone stays active until video playback completes.
Actual result: Phone suspends after a few seconds. Depending on how the video was started, sound may or may not continue playing.
Playing a video from inside the video scope (without launching mediaplayer-app) results in sound but no visuals. Playing it with mediaplayer-app at a command line (like the automated tests do) results in a full suspend with no sound.
I'm getting similar behavior during other automated tests too. What happens is, roughly:
* USB connect.
* Reboot.
* Adt runs to set up the device. This takes a few minutes.
* USB disconnect.
At this point, what should happen is:
* If the current app has no "keep screen on" state, the screen should dim after 50 seconds then shut off after another 10 seconds. Otherwise, the screen should stay on until the "keep screen on" state is cleared. (adt sets this state sometimes to allow testing power with the display on, or it should also stay on until the video finishes)
* Measurements start after a while, and continue for a pre-determined length of time.
What actually happens instead:
* A few seconds after USB gets unplugged, the screen turns off. If music isn't playing, the phone also goes into suspend mode. The "keep screen on" state appears to be ignored, and the user's screen-off delay setting appears to be ignored too. No 50-seconds-then-dim-then-10-seconds-then-off happens.
* Measurements happen at the expected times, but the phone isn't in the expected state so the results are wrong.
Will attach comparison measurements below. |
As of yesterday's phone images (2016-07-12, krillin rc-p 383, arale rc-p 376, when repowerd landed), I'm getting unusual behavior during automated tests. This is easiest to see, manually, with video playback.
Steps to trigger this issue:
* Flash the affected image.
* Put a video on the device, at least 2 minutes long.
* Start video playback. Symptoms seem most severe when played via "adb shell" with "ubuntu-app-launch mediaplayer-app file:///media/phablet/3562-3231/Videos/long-video.avi".
* Wait at least 60 seconds.
* Unplug USB.
Expected result: Phone stays active until video playback completes.
Actual result: Phone suspends after a few seconds. Depending on how the video was started, sound may or may not continue playing.
Playing a video from inside the video scope (without launching mediaplayer-app) results in sound but no visuals. Playing it with mediaplayer-app at a command line (like the automated tests do) results in a full suspend with no sound.
I'm getting similar behavior during other automated tests too. What happens is, roughly:
* USB connect.
* Reboot.
* Adt runs to set up the device. This takes a few minutes.
* USB disconnect.
At this point, what should happen is:
* If the current app has no "keep screen on" state, the screen should dim after 50 seconds then shut off after another 10 seconds. Otherwise, the screen should stay on until the "keep screen on" state is cleared. (adt sets this state sometimes to allow testing power with the display on, or it should also stay on until the video finishes)
* Measurements start after a while, and continue for a pre-determined length of time.
What actually happens instead:
* A few seconds after USB gets unplugged, the screen turns off. If music isn't playing, the phone also goes into suspend mode. The "keep screen on" state appears to be ignored, and the user's screen-off delay setting appears to be ignored too. No 50-seconds-then-dim-then-10-seconds-then-off happens.
* Measurements happen at the expected times, but the phone isn't in the expected state so the results are wrong.
Will attach comparison measurements below. In the graphs, the red areas indicate when USB was connected. Non-red areas mean USB was unplugged. Green areas are the part of the measurement which "counts" for test purposes. |
|
| 2016-07-14 04:28:14 |
Selene ToyKeeper |
attachment added |
|
a-video.png https://bugs.launchpad.net/repowerd/+bug/1602933/+attachment/4700592/+files/a-video.png |
|
| 2016-07-14 04:29:07 |
Selene ToyKeeper |
bug task added |
|
canonical-devices-system-image |
|
| 2016-07-14 04:34:53 |
Selene ToyKeeper |
description |
As of yesterday's phone images (2016-07-12, krillin rc-p 383, arale rc-p 376, when repowerd landed), I'm getting unusual behavior during automated tests. This is easiest to see, manually, with video playback.
Steps to trigger this issue:
* Flash the affected image.
* Put a video on the device, at least 2 minutes long.
* Start video playback. Symptoms seem most severe when played via "adb shell" with "ubuntu-app-launch mediaplayer-app file:///media/phablet/3562-3231/Videos/long-video.avi".
* Wait at least 60 seconds.
* Unplug USB.
Expected result: Phone stays active until video playback completes.
Actual result: Phone suspends after a few seconds. Depending on how the video was started, sound may or may not continue playing.
Playing a video from inside the video scope (without launching mediaplayer-app) results in sound but no visuals. Playing it with mediaplayer-app at a command line (like the automated tests do) results in a full suspend with no sound.
I'm getting similar behavior during other automated tests too. What happens is, roughly:
* USB connect.
* Reboot.
* Adt runs to set up the device. This takes a few minutes.
* USB disconnect.
At this point, what should happen is:
* If the current app has no "keep screen on" state, the screen should dim after 50 seconds then shut off after another 10 seconds. Otherwise, the screen should stay on until the "keep screen on" state is cleared. (adt sets this state sometimes to allow testing power with the display on, or it should also stay on until the video finishes)
* Measurements start after a while, and continue for a pre-determined length of time.
What actually happens instead:
* A few seconds after USB gets unplugged, the screen turns off. If music isn't playing, the phone also goes into suspend mode. The "keep screen on" state appears to be ignored, and the user's screen-off delay setting appears to be ignored too. No 50-seconds-then-dim-then-10-seconds-then-off happens.
* Measurements happen at the expected times, but the phone isn't in the expected state so the results are wrong.
Will attach comparison measurements below. In the graphs, the red areas indicate when USB was connected. Non-red areas mean USB was unplugged. Green areas are the part of the measurement which "counts" for test purposes. |
As of yesterday's phone images (2016-07-12, krillin rc-p 383, arale rc-p 376, when repowerd landed), I'm getting unusual behavior during automated tests. This is easiest to see, manually, with video playback.
Steps to trigger this issue:
* Flash the affected image.
* Put a video on the device, at least 2 minutes long.
* Start video playback. Symptoms seem most severe when played via "adb shell" with "ubuntu-app-launch mediaplayer-app file:///media/phablet/3562-3231/Videos/long-video.avi".
* Wait at least 60 seconds.
* Unplug USB.
Expected result: Phone stays active until video playback completes.
Actual result: Phone suspends after a few seconds. Depending on how the video was started, sound may or may not continue playing.
Playing a video from inside the video scope (without launching mediaplayer-app) results in sound but no visuals. Playing it with mediaplayer-app at a command line (like the automated tests do) results in a full suspend with no sound.
I'm getting similar behavior during other automated tests too. What happens is, roughly:
* USB connect.
* Reboot.
* Adt runs to set up the device. This takes a few minutes.
* USB disconnect.
At this point, what should happen is:
* If the current app has no "keep screen on" state, the screen should dim after 50 seconds then shut off after another 10 seconds. Otherwise, the screen should stay on until the "keep screen on" state is cleared. (adt sets this state sometimes to allow testing power with the display on, or it should also stay on until the video finishes)
* Measurements start after a while, and continue for a pre-determined length of time.
What actually happens instead:
* A few seconds after USB gets unplugged, the screen turns off. If music isn't playing, the phone also goes into suspend mode. The "keep screen on" state appears to be ignored, and the user's screen-off delay setting appears to be ignored too. No 50-seconds-then-dim-then-10-seconds-then-off happens.
* Measurements happen at the expected times, but the phone isn't in the expected state so the results are wrong.
An additional oddity: If I start a video with USB unplugged, it will continue playing indefinitely. However, if I plug in USB during playback the video stops after a few seconds. Or if I simply plug/unplug USB while the phone is idle, the screen comes on but turns off again after a few seconds instead of the configured delay time. Pretty much any USB event seems to cause screen-off after a few seconds.
Will attach comparison measurements below. In the graphs, the red areas indicate when USB was connected. Non-red areas mean USB was unplugged. Green areas are the part of the measurement which "counts" for test purposes. |
|
| 2016-08-09 10:29:09 |
Jean-Baptiste Lallement |
canonical-devices-system-image: milestone |
|
13 |
|
| 2016-08-09 10:29:13 |
Jean-Baptiste Lallement |
canonical-devices-system-image: importance |
Undecided |
High |
|
| 2016-08-09 10:29:18 |
Jean-Baptiste Lallement |
canonical-devices-system-image: status |
New |
Confirmed |
|
| 2016-08-09 10:29:27 |
Jean-Baptiste Lallement |
canonical-devices-system-image: assignee |
|
kevin gunn (kgunn72) |
|
| 2016-08-09 15:30:39 |
Alexandros Frantzis |
repowerd: status |
New |
Confirmed |
|
| 2016-08-09 15:30:43 |
Alexandros Frantzis |
repowerd: status |
Confirmed |
In Progress |
|
| 2016-08-09 15:30:45 |
Alexandros Frantzis |
repowerd: importance |
Undecided |
High |
|
| 2016-08-09 15:30:48 |
Alexandros Frantzis |
repowerd: assignee |
|
Alexandros Frantzis (afrantzis) |
|
| 2016-08-11 14:17:29 |
Launchpad Janitor |
branch linked |
|
lp:~ci-train-bot/repowerd/repowerd-ubuntu-yakkety-landing-000 |
|
| 2016-08-12 05:01:39 |
Selene ToyKeeper |
repowerd: status |
In Progress |
Fix Committed |
|
| 2016-08-12 06:50:31 |
Jean-Baptiste Lallement |
canonical-devices-system-image: status |
Confirmed |
Fix Committed |
|
| 2016-09-20 21:10:59 |
Pat McGowan |
canonical-devices-system-image: status |
Fix Committed |
Fix Released |
|
| 2016-10-05 07:44:50 |
Alexandros Frantzis |
repowerd: status |
Fix Committed |
Fix Released |
|
