Closed Bug 956829 Opened 10 years ago Closed 10 years ago

[B2G][Gaia] Apps become unresponsive after user's enter their SIM pin.

Categories

(Firefox OS Graveyard :: Gaia::System, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(blocking-b2g:1.3+, b2g-v1.3 fixed)

RESOLVED FIXED
blocking-b2g 1.3+
Tracking Status
b2g-v1.3 --- fixed

People

(Reporter: rkunkel, Assigned: etienne)

References

Details

(Keywords: regression, Whiteboard: dogfood1.3)

Attachments

(2 files)

Attached file logcat
The user can cause apps to become unresponsive by skipping to enter their SIM pin upon starting the phone and later entering their pin when an app ask for it.

Setup Steps:
Enable SIM security, Settings > SIM security.

Repro Steps:
1) Update Buri to v1.3 BuildID: 20140106004001
2) Upon starting the phone skip entering the SIM pin.
3) From the Homescreen, access an app that asks the user to enter their SIM pin (Dialer, Messages, ect.)
4) Enter the correct SIM pin.
5) Observe the user returned to the Homescreen and the app not opening.

Actual:
User cannot open apps by tapping on their icons.

Expected:
Apps to always be responsive to the user.

Environmental Variables:
Device: Buri v1.3 Mozilla RIL
BuildID: 20140106004001
Gaia: 35a60b82f8cf2d759939a350e2dadbb9d8b2f5dc
Gecko: a43cb4b322d3
Version: 28.0a2
Firmware Version: 20131115

Notes:
Restarting the device or accessing setting though the notification bar will cause the apps to respond again.

Repro frequency: 100%
See attached: logcat
My guess is that this is a system app bug.
blocking-b2g: --- → 1.3?
Component: Gaia → Gaia::System
.:First Broken Build:.
Environmental Variables:
Device: Buri 1.3 MOZ
BuildID: 20131210004003
Gaia: 3452fbdb5e1bed0cd27cc6173136537a03e8072f
Gecko: e0c328d99742
Version: 28.0a2
Firmware Version: v1.2_20131115

.:Last Working Build:.
Environmental Variables:
Device: Buri 1.3 MOZ
BuildID: 20131209053402
Gaia: 1d45d1dc3201059d5c8f2efdeb92c04576d8e161
Gecko: 9f12a9fab080
Version: 28.0a1
Firmware Version: v1.2_20131115

Heads up, the first broken build is the first 1.3 aurora build we tested, and the last working is the last central 1.3
Whiteboard: dogfood1.3 → dogfood1.3 [systemsfe]
Hey Joe, 

Can you confirm if this is a comms dialer issue? In the systemsfe triage, questions around ownership came up.

Thanks
Flags: needinfo?(jcheng)
Whiteboard: dogfood1.3 [systemsfe] → dogfood1.3
hey Etienne, mind taking a quick look? Thanks
Flags: needinfo?(jcheng) → needinfo?(etienne)
(In reply to Joe Cheng [:jcheng] from comment #4)
> hey Etienne, mind taking a quick look? Thanks

Well I can't reproduce the bug so I don't think I'll be of any help... :/
Flags: needinfo?(etienne)
QA Wanted - Can we double check the STR here?
Keywords: qawanted
QA Contact: sparsons
STR is correct, I was able to repro on the latest Buri 1.3 Build ID: 20140107004001

Gaia   ff5f06dd321f7d2bf4a5b311ded2c56e865d4f83
SourceStamp 71ad7ff30010
BuildID 20140107004001
Version 28.0a2
Keywords: qawanted
Enpei helped me flash a buri, I can reproduce the bug, it's system related, on it :)
Assignee: nobody → etienne
Attached file Pointer to Gaia PR
Here's a patch.
It wont hurt on master, and once uplifted, it will fix the bug on 1.3.

Tested on both, and the patch applies on 1.3 without conflict.
Attachment #8357143 - Flags: review?(alive)
Comment on attachment 8357143 [details] [review]
Pointer to Gaia PR

Thanks for fixing my bug!
Attachment #8357143 - Flags: review?(alive) → review+
https://github.com/mozilla-b2g/gaia/commit/59cfe743c5b69c4fcf5707168a041563a0501f8b
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
blocking-b2g: 1.3? → 1.3+
Uplifted 59cfe743c5b69c4fcf5707168a041563a0501f8b to:
v1.3: 45d1b05ace73347ac355c1e5d92abecef35cac7d
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: