Attached is the log from Pat which shows the actual problem together with some verbose logging.
>From the log the reason for the continous hold wakelock MT662x are therm events we're receiving from the WiFi/BT/.. combo chip. They start to flood at one point which will keep the device awake. One krillin interestingly we don't have support for this enabled at all and those events just never come in. What triggers the flood of therm events isn't clear yet but a first attempt to just disable them gave very good results as Pat showed above. I've uploaded a fix for this to get some more eyes on this. ** Attachment added: "syslog-pat-with-therm-events.txt" https://bugs.launchpad.net/canonical-devices-system-image/+bug/1505241/+attachment/4539341/+files/syslog-pat-with-therm-events.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1505241 Title: Phone does not suspend Status in Canonical System Image: In Progress Status in bluez package in Ubuntu: In Progress Bug description: I am seeing both the MX4 on proposed and the E4.5 on stable exhibit similar behavior According to the logs they are not able to suspend due to active wakeup sources. (I am running a BT test kernel on the MX4 3.10.35+) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1505241/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
