← Back to team overview

touch-packages team mailing list archive

[Bug 1295762] Re: snap decision timeout needs to be determined by the requesting app

 

** Changed in: telephony-service
       Status: New => Triaged

** Changed in: telephony-service
   Importance: Undecided => Medium

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

Title:
  snap decision timeout needs to be determined by the requesting app

Status in Network Menu:
  Fix Released
Status in Telephony Service:
  Triaged
Status in Ubuntu UX bugs:
  Fix Committed
Status in Unity:
  Invalid
Status in Server and client library for desktop notifications in Unity:
  Confirmed
Status in “indicator-network” package in Ubuntu:
  Fix Released
Status in “telephony-service” package in Ubuntu:
  New
Status in “unity” package in Ubuntu:
  Invalid
Status in “unity-notifications” package in Ubuntu:
  Fix Released

Bug description:
  Problem:
  If user receives an SMS/call, snap decision for incoming SMS/call stays on screen for always only 60sec. and then disappears from screen (by default). There was no interaction from user. 

  Possible solution:
  The snap decision should stay on screen for the amount of time the app asks it to, being always app dependant. 
  A 60sec. time-out is too short due to use cases where an action from user is mandatory. 

  Use case example: A class 1/2 SMS arrives after user triggered a USSD
  command from dialer. These type of SMS always requires a response from
  user (CANCEL or a further COMMAND). Thus a timeout of only 60 sec is
  too short because it can be missed and these type of SMS is NOT saved
  into the usual messages thread.

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-network/+bug/1295762/+subscriptions