touch-packages team mailing list archive

[Gerry Boland <1309915@xxxxxxxxxxxxxxxxxx>]

Still trying to get my head around this. If I manually create a wakelock:
    sudo bash -c "echo mylock > /sys/power/wake_lock"
then I can't reproduce the bug (tried 20 times anyway). If I remove that wakelock:
    sudo bash -c "echo mylock > /sys/power/wake_unlock"
then yes, I get the bug again. Sadly there's no /proc/wakelocks to get the wakelock state.

Seeing the Greeter have a black background makes me suspicious too. Is
phone going to deep sleep before unity8 is ready - as Greeter should be
drawn on screen after display is turned off, not before display is
turned on.

I need to learn how powerd is interacting with wakelocks

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1309915

Title:
  foreground app should keep wakelock open until actual suspend happens

Status in the base for Ubuntu mobile products:
  Confirmed
Status in qtmir package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Confirmed
Status in qtmir package in Ubuntu RTM:
  In Progress
Status in unity8 package in Ubuntu RTM:
  New

Bug description:
  while apps that you put in the background are properly SIGSTOPed 
  (this is easy to verify with a music streaming website atm (while the browser does not use media-hub it will/should stop playback)).
   An app that is in the foreground will try to play on when the system is suspended (easy to verify with the same method, music plays on but becomes stuttery if the browser was in the foreground. This indicates the system tries to suspend but the running app tries to keep it alive. 

  Unity should send s SIGSTOP/SIGCONT sequence on suspend/resume to the
  app in foreground when the system goes into suspend and resumes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1309915/+subscriptions