My recommendation is that we should bring up the SIM PIN unlock screen if user 
tries to launch the DIALER and MESSAGING apps. This can be done additionally to 
the indicator access. This way a user will know instantly that there is no 
access to this apps without unlocking the SIM.
For the browser it might be a little different though. If the device is on WIFI 
the browser still can be used, if not it will require to unlock the SIM again 
in order to user mobile data...

-- 
You received this bug notification because you are a member of Unity API
bugs, which is subscribed to Network Menu.
https://bugs.launchpad.net/bugs/1362150

Title:
  SIM PIN unlock usability needs improving

Status in Network Menu:
  New
Status in Ubuntu UX bugs:
  Confirmed
Status in The Unity 8 shell:
  New

Bug description:
  Several bugs have been reported related to using the PIN unlock
  Grouping here for review

  Add feedback on failed attempts
   - The dialog tells you how many attempts you have remaining before a PUK 
code will be required
   - Entering the wrong PIN will result in a clear message to user of the 
failure and an update of the attempts remaining count

  After cancelling SIM unlock, how to unlock is not obvious:
  1.Insert this SIM card
  2.Power on device
  3. Popup SIM PIN unlock interface after power on device
  4. cancel this dialog
  5. Go to phone app to make a call
  It is not obvious that the next step should be to drag down the indicator and 
use the unlock button.

  the phone and messaging apps should have a shorthand button clearly
  visible to unlock the relevant SIM so that the user does not have to
  "know" to go to the indicator-network first to be able to make
  phonecalls or send SMS

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

-- 
Mailing list: https://launchpad.net/~unity-api-bugs
Post to     : unity-api-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~unity-api-bugs
More help   : https://help.launchpad.net/ListHelp

Reply via email to