Yeah it seems likely that some driver is probably being slow in its late_resume handler. There may be something in dmesg which shows how long individual late_resume calls are making, I can't remember (there may also be some debug option which has to be enabled).
Iirc the reason we have to wait for the fb state to change was because you can hit deadlocks with some of the phone kernels if you write state changes to /sys/power/state without waiting. Android also waits for the framebuffer state to change, so that's the only arrangement that's probably tested by the phone makers as well. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to powerd in Ubuntu. https://bugs.launchpad.net/bugs/1421455 Title: Slow wake up time on physical power button pressed Status in powerd package in Ubuntu: New Status in unity8 package in Ubuntu: Incomplete Bug description: Device: bq Aquaris E4.5 running: Stable #17 When pressing on physical power button on device to wake it up sometime it even takes up to 2-3 secs before anything appears on the screen. This time wary but its hard to tell then its shorter and when is longer. This is not so bad on nexus4. Should you need more info, I'm happy to help. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/powerd/+bug/1421455/+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