touch-packages team mailing list archive

[Michael Terry <michael.terry@xxxxxxxxxxxxx>]

Also, I just looked up how long phone rings last, and it's much longer
than 15s (reports vary from 30s to a minute).  So it makes sense to have
the longer screen wakeup.

re: Telegram, those other bugs seem to be about the notification showing
at all or the sound not triggering.  And both mention BQ phones.  I'm
using a mako and both the sound and notification appear.  The screen
just doesn't turn on.  I didn't know if we treated push notifications
differently.  Maybe ubuntu-push should have a USC::setScreenPowerMode
call?

-- 
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/1426115

Title:
  Screen timeout for system event (e.g. notification) needs to be a
  shorter duration than the standard inactivity timeout

Status in Canonical System Image:
  In Progress
Status in Unity System Compositor:
  Fix Released
Status in powerd package in Ubuntu:
  New
Status in telephony-service package in Ubuntu:
  New
Status in unity-system-compositor package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  New

Bug description:
  When receiving an SMS notification or a calendar event the screen is
  left on for the full min or more as set by the user. This is not
  necessary and not how other phones behave.

  I would suggest 15 secs and go direct to suspend.

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