touch-packages team mailing list archive

[Michael Zanetti <michael.zanetti@xxxxxxxxxxxxx>]

Well, currently, as long as the application process is running, the
request for keeping the display list is respected. When the app is
closed (or killed by OOM) the request is deleted.

I agree the long term solution should be to drop it when the app is
unfocused (although we should consider how that works with convergence
and windowed mode before we make a decision).

On a side note, I would also argue that most applications should even
keep the display list all the time. For example, BigMovingText should
not request the display to be kept lit while being in the settings menu,
but only when it actually is displaying the big moving text. In order to
create good quality apps, be clever and set screensaverEnabled to
something meaningful instead of just "false". For example:

screenSaverEnabled: !(Qt.application.active &&
doingStuffThatReallyRequiresIt)

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

Title:
  Allow apps to keep the screen on

Status in Canonical System Image:
  Fix Committed
Status in Canonical Click Reviewers tools:
  Fix Released
Status in Ubuntu Developer Portal:
  New
Status in apparmor-easyprof-ubuntu package in Ubuntu:
  Fix Released
Status in qtsystems-opensource-src package in Ubuntu:
  Fix Released
Status in qtubuntu package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed
Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed
Status in unity-system-compositor package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed
Status in qtsystems-opensource-src package in Ubuntu RTM:
  Fix Released

Bug description:
  Support an interface in QML and HTML to allow an app to keep the
  screen on while the app is active. This has come up in several
  scenarios, such as an ebook reader, a clock in night mode.

  First step is to hook up QtSystemInfo screenSaverEnabled

  One solution to inhibit the screen blanking:

  Add a new dbus rule to the default template
  Provide a mediator (unity8) to control this, so it can restore the screen blanking when the app is not active or has been closed
  Prompt the user for confirmation the first time the app accesses it
  use the trust store to avoid prompts each time
  add to the System settings Other app access panel an entry for Screen or Display so the setting could be revoked

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