Have a MX4 being active now for more than 3 days and not getting this problem with rc-proposed (which has BlueZ 5 merged) again
simon@nirvana ...-bluez5-upgrade/suspend-problem-arale % ~/Work/ubuntu2/suspend-blocker/suspend-blocker syslog syslog: Suspends: 421 suspends aborted (13.66%). 2661 suspends succeeded (86.34%). total time: 14336.580655 seconds (24.56%). minimum: 0.273411 seconds. maximum: 29.424044 seconds. mean: 5.387667 seconds. mode: 2.000000 seconds. median: 4.020927 seconds. Time between successful suspends: total time: 44043.299598 seconds (75.44%). minimum: 0.907498 seconds. maximum: 38991.833792 seconds. mean: 16.557631 seconds. mode: 1.000000 seconds. median: 1.220935 seconds. simon@nirvana ...-bluez5-upgrade/suspend-problem-arale % adb shell uphablet@ubuntu-phablet:~$ uptime 08:33:51 up 3 days, 13:00, 1 user, load average: 0.00, 0.01, 0.02 -- You received this bug notification because you are a member of Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
