I'm seeing weird and buggy power behavior on krillin ever since rc-proposed 196 (and thus also in rc 38, the OTA8.5 release candidate). The root cause isn't determined yet, but there's a high probability it's related to the landing for bug 1480877.
This issue only occurs on krillin (not arale), and only when wifi is connected. Arale might be a red herring though, since it never really "sleeps" properly with wifi connected and has always had highly erratic results for this case.
Something appears to be waking up the phone and keeping it awake about half the time, causing the power graph to look like a square wave instead of a flat line. I don't see additional forks or crashes in the logs, which suggests a long-running process (like dbus) is responsible.
I'm seeing weird and buggy power behavior on krillin ever since rc-proposed 196 (and thus also in rc 38, the OTA8.5 release candidate). The root cause isn't determined yet, but there's a high probability it's related to the landing for bug 1480877.
This issue only occurs on krillin (not arale), and only when wifi is connected. Arale might be a red herring though, since it never really "sleeps" properly with wifi connected and has always had highly erratic results for this case.
Before: ~9 mA people. canonical. com/~platform- qa/power- results/ 2015-12- 08_03:19: 30-krillin- 195-power_ usage_idle/ graph.png
http://
After: ~35 mA people. canonical. com/~platform- qa/power- results/ 2015-12- 08_07:36: 16-krillin- 196-power_ usage_idle/ graph.png
http://
Here's the commit log for 196:
http:// people. canonical. com/~lzemczak/ landing- team/ubuntu- touch/rc- proposed/ 196.commitlog
Something appears to be waking up the phone and keeping it awake about half the time, causing the power graph to look like a square wave instead of a flat line. I don't see additional forks or crashes in the logs, which suggests a long-running process (like dbus) is responsible.