@Pat: Does it print out something like: Suspend blocking wakelocks: None
Resume wakeup causes: None Suspend failure causes: None Suspends: 0 suspends aborted (0.00%). 0 suspends succeeded (0.00%). total time: 0.000000 seconds (0.00%). minimum: 0.000000 seconds. maximum: 0.000000 seconds. mean: 0.000000 seconds. mode: 0.000000 seconds. median: 0.000000 seconds. Time between successful suspends: total time: 0.000000 seconds (0.00%). minimum: 0.000000 seconds. maximum: 0.000000 seconds. mean: 0.000000 seconds. mode: 0.000000 seconds. median: 0.000000 seconds. If yes, that is right. The log file does not contain any suspend attempt (from the kernel side) and your phone will never try to suspend as long as a usb cable is plugged in. -- 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
