ok, turns out this was actually caused by my current unity8 branch I'm
testing on the phone. I've fixed it in there now.
** Changed in: canonical-devices-system-image
Status: New => Invalid
** Changed in: qtmir (Ubuntu)
Status: New => Invalid
** Changed in: unity8 (Ubuntu)
S
** Description changed:
My rc-proposed phone doesn't go to deep sleep in many cases. We're still
investigating what exactly is going on but this should probably be
- looked into before releasing OTA-13 with new repowerd.
+ looked into before releasing OTA-13.
--
You received this bug notific
reading through the logs, it seems unity8 requested the wakelock and
never released it again.
https://paste.ubuntu.com/23111236/
I have now closed all the apps and it did release it
2016-08-30T12:20:19.466945+02:00 ubuntu-phablet repowerd[2431]:
UnityScreenService: dbus_clearSysState(:1.76,486)
Ok, seems when an app has a lifecycle exception, qtmir requests a
wakelock and doesn't release it again.
** Also affects: qtmir (Ubuntu)
Importance: Undecided
Status: New
** Changed in: qtmir (Ubuntu)
Importance: Undecided => Critical
--
You received this bug notification because y