touch-packages team mailing list archive

[Ricardo Salveti <rsalveti@xxxxxxxxxxxx>]

Public bug reported:

current build number: 51
device name: mako
channel: ubuntu-touch/vivid-proposed
last update: 2014-12-11 15:02:13
version version: 51
version ubuntu: 20141211
version device: 20141209
version custom: 20141211

Currently it takes around 3 seconds for the app to get the SIGSTOP
signal when the app moves to background (when changing apps, moving to
the home scopes, suspending the phone, etc), which is specially annoying
if the app has an active audio stream (you can still hear the sound for
a few seconds before it stops completely).

I know we export signals for the apps to react when they are moved out
of focus, but I also believe the platform could react a bit sooner than
the current 3 seconds timeouts (in order to improve the user experience
for webapps, for example).

** Affects: qtmir
     Importance: Undecided
         Status: New

** Affects: platform-api (Ubuntu)
     Importance: Undecided
         Status: New

** Affects: qtmir (Ubuntu)
     Importance: Undecided
         Status: New

** Also affects: qtmir (Ubuntu)
   Importance: Undecided
       Status: New

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

Title:
  3 seconds delay before sending SIGSTOP (changing apps, suspending
  phone) seems too much

Status in Qt integration with the Mir display server:
  New
Status in platform-api package in Ubuntu:
  New
Status in qtmir package in Ubuntu:
  New

Bug description:
  current build number: 51
  device name: mako
  channel: ubuntu-touch/vivid-proposed
  last update: 2014-12-11 15:02:13
  version version: 51
  version ubuntu: 20141211
  version device: 20141209
  version custom: 20141211

  Currently it takes around 3 seconds for the app to get the SIGSTOP
  signal when the app moves to background (when changing apps, moving to
  the home scopes, suspending the phone, etc), which is specially
  annoying if the app has an active audio stream (you can still hear the
  sound for a few seconds before it stops completely).

  I know we export signals for the apps to react when they are moved out
  of focus, but I also believe the platform could react a bit sooner
  than the current 3 seconds timeouts (in order to improve the user
  experience for webapps, for example).

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