touch-packages team mailing list archive

[Michael Terry <michael.terry@xxxxxxxxxxxxx>]

So looking at the powerd code, the only thing that does anything *real*
between "exiting suspend" and "Emitting signal for transition to state
ACTIVE" is a call to libsuspend_exit_suspend().

Which -- depending on the backend -- either makes one syscall and
returns, or makes one syscall and waits for the fb state to be awake.
Since the latter is the default backend and we're seeing delays, I'm
guessing that's the code path we're hitting.

Why do we need to block on fb state there?  (honest question, I don't
understand the libsuspend code very 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