touch-packages team mailing list archive

[Alexandros Frantzis <alexandros.frantzis@xxxxxxxxxxxxx>]

> Krillin and Arale seem to behave fine, but I'm not sure if it's by accident - do we actually have code that waits for something
> (a new frame? feedback from shell?) before powering the screen on?

Before turning the screen on/enabling the compositor, after the power
button is pressed, USC currently waits for powerd to notify us that we
have come out of suspend. On some devices, this notification takes some
time to arrive (about ~0.5 second on Krillin). I haven't tried myself
recently but Alberto mentioned that N4 wakes up faster.

The different delays (depending on HW) introduced by this mechanism
offer a plausible explanation of why we see the frame on some devices
and not on others.

Also see my previous explanation in comment 5 [1]. It's important to
note that although we can eventually get a "good enough" solution (e.g.
unity8 signals USC that it has rendered the greeter), a 100% perfect
solution is difficult to achieve since we can't really know when the
frame with the greeter has actually been displayed on screen (vs only
rendered and swapped).

[1] https://bugs.launchpad.net/unity-system-
compositor/+bug/1340510/comments/5

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

Title:
  [Mako] Session screen seen upon quick power key strike only when
  roaming

Status in Mir:
  Opinion
Status in Mir 0.4 series:
  Won't Fix
Status in Mir 0.5 series:
  Won't Fix
Status in Mir 0.6 series:
  Won't Fix
Status in Unity System Compositor:
  New
Status in mir package in Ubuntu:
  Opinion
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  this is not seen on krillin

  Image #125 on N4

  1) boot phone and unlock phone to display dash
  2) strike power key to blank & unblank screen quickly
  3) the dash is seen instead of lockscreen for a brief moment

  logging against u-s-c as this was fixed, but power policy changes may
  have effected this

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1340510/+subscriptions