Your log is actually fine from powerd's perspective (powerd is indeed trying to
suspend and releasing everything it can), but in your case it seems the usb
device is blocking suspend:
Feb 19 16:01:04 ubuntu-phablet kernel: [ 5926.373385] usb 1-1: abort suspend
Feb 19 16:01:04 ubuntu-phablet kerne
Sorry forgot to upload the syslog, this is just the time after the incoming call
I do have powerd debug enabled
** Attachment added: "incoming2"
https://bugs.launchpad.net/ubuntu/+source/android/+bug/1420387/+attachment/4323252/+files/incoming2
** Changed in: android (Ubuntu)
Status: N
Is this last comment produced from a new syslog file? If so, mind
attaching it here as well?
Would you mind enabling debug on powerd as well when trying to reproduce
this issue? I pushed that by default on vivid, and should have it
enabled by default on RTM as well once the gates are opened for ne
On mako
After an incoming call
Suspend blocking wakelocks:
None
Resume wakeup causes:
None
Suspend failure causes:
devices failed to suspend 1 100.00%
Time between successful suspends:
Interval (seconds) FrequencyCumulative Time (Seconds)
1024.000 - 2047.999
So far I have not been able to reproduce on a krillin.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1420387
Title:
Phone does not deep suspend after incoming call
To manage notifications about thi
