Closed Bug 849443 Opened 13 years ago Closed 13 years ago

[PUK] SIM PUK countdown resets after rebooting the device

Categories

(Firefox OS Graveyard :: Gaia, defect)

Product:
Firefox OS Graveyard
Component:
Gaia
Platform:
ARM
Gonk (Firefox OS)
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(blocking-b2g:leo+, b2g18 affected, b2g18-v1.0.1 affected)

Status:
RESOLVED INVALID
Project Flags:
blocking-b2g leo+
Tracking Flags:
Tracking Status
b2g18 --- affected
b2g18-v1.0.1 --- affected

People

(Reporter: nhirata, Assigned: anshulj)

Details

Attachments

(5 files)

screenshot
332.19 KB, image/jpeg
Details
logcat before reboot w/ ril debug true
235.74 KB, text/plain
Details
logcat after reboot w/ ril debug true
187.25 KB, text/plain
Details
logcat before reboot w/ ril debug true : take 2
405.41 KB, text/plain
Details
logcat after reboot w/ ril debug true : take 2
713.73 KB, text/plain
Details
Attached image screenshot —
"mozilla-central" revision="cb432984d5ce" "integration/gaia-central" revision="df56729d46b7" gecko.git revision="0be8fda9a032227e46bb011fda43aa589c632033" gaia.git revision="c7ac21c48e3718a178340a56b17a0508ae903aba" 2013-03-08-03-10-58_MC ## Repro : 1. setup pin code 2. fail pin code 3 times 3. reflash the phone 4. mess up on the puk (should see 9 tries left) 5. mess up on the puk again (should see 8 tries left) 6. reboot the phone 7. mess up on the puk ## Expected : should see 7 tries left ## Actual : 9 tries left ## Note : setting to blocking because I think this might be a telecom blocker.
Naoki, does the fix to bug 849200 also fixes this one?
qawanted to retry after comment 1. if it still reproduces, we can leo+ this. it's not good to incorrectly show users the number of retries left, if it's not correct. (resetting SIM PUK is a pain!)
Keywords: qawanted
naoki, give this another spin?
Flags: needinfo?(nhirata.bugzilla)
This bug still occurs: 20130321031038 Build ID: "mozilla-central" revision="1d6fe70c79c5" "integration/gaia-central" revision="9d1760ae0b13" "gecko.git" revision="a611bf4139e881c21ec23fd0807e472711c8ace4" "gaia.git" revision="72bba6330849f93e55fcddc8be73edda72fb3c9b" Sorry I didn't see the comment earlier. Alive, if you want to get my attention on a bug, please mark them as needinfo on me and/or qawanted in the keyword as tchung has done. There are so many bugs, that I filter on these as higher priority.
Flags: needinfo?(nhirata.bugzilla)
Keywords: qawanted
qawanted: Is 1.0.1 also affected? Kevin, do you know who the best assignee here is?
Assignee: nobody → khu
blocking-b2g: leo? → leo+
Keywords: qawanted
1.0.1 is also affected : Gecko http://hg.mozilla.org/releases/mozilla-b2g18_v1_0_1/rev/4931ec89ebbe Gaia 701b594c3e320030c538aa19f702764b29a6cc1c BuildID 20130325070201 Version 18.0
status-b2g18: --- → affected
status-b2g18-v1.0.1: --- → affected
Keywords: qawanted
I am not able to reproduce the issue. After step 7, I see 7 tried left on the UI. Are you using commercial RIL and if yes which AU?
Flags: needinfo?(nhirata.bugzilla)
This is still occurring in the build I used today: Gecko http://hg.mozilla.org/releases/mozilla-b2g18/rev/d467369d1b0c Gaia 06e0e5ce42bdfb62bdbe38271de6b5b2d9e40e75 BuildID 20130403070204 Version 18.0 platform/abi/cpp is tagged with AU_LINUX_GECKO_ICS_STRAWBERRY_V1.01.00.01.19.039 : 6426040f1be4a844082c9769171ce7f5341a5528 Hrm. Looking at the checkin, it looks like somehow I'm using the older version of the RIL? I'll see if I can get it updated and then try again.
Flags: needinfo?(nhirata.bugzilla)
Turns out that the ril build isn't in the source.xml as I thought... I am using ril01.01.00.19.050 I see that there's still a .062 build that just got released. Asking to have it to the latest.
@nhirata, .62 is a V1 AU (01.00.01.19.062) AU while .050 you mentioned above is V1.1 AU. I think you are interested in v1.1 AU so 0.50 is the lastest we have. Can you please provide me the android main logs and the android radio logs for the issue since I am unable to reproduce this issue?
Yes, thanks. Catlee also let me be aware of the situation. Sorry for the confusion. I thought perhaps I did something wrong. Attached is the pre-reboot logcat.
Nhirata, from the logs I do see that after reboot telephony reported that the retries left are 9 instead of 7. However you didn't provide the android radio logs so I can not confirm if that is what RIL reports. Please run the following command and get me the logs. adb logcat -b radio -b main -v time
Anshul, it looks like you're the one who could help this case. Please tell me if it's not the case, then I can find someone else to help. Thanks!
Assignee: khu → anshulj
@khu, yes I can help but I need the requested logs.
Thank you, Anshul!
Nhirata, please provide the logs as requested pet my comment #13
Flags: needinfo?(nhirata.bugzilla)
Hi Anshul, here are the requested logs. Thanks for marking it needinfo. That helps keep things on my radar.
Naoki, from the logs clearly RIL is notifying that the PUK retries left are 9 instead of 7. Doesn't seem like anything wrong with the telephony code. I would have to follow up with the modem team. Could you please collect QXDM logs and file a case against Qualcomm. Please let me know the case number so I can follow up on that and will close this bug.
Flags: needinfo?(nhirata.bugzilla)
I am sorry, Anshul, I'm not sure how to collect QXDM logs and file against Qualcomm. Could you specify how I would go about doing this please? FYI, I work for Mozilla directly.
Flags: needinfo?(nhirata.bugzilla)
Per comment 7, we may just want to WFM this issue. Maybe something wrong with the Mozilla build
Further, the screenshot looks to be a unagi so who knows was going on beneath Gecko on that device.
Not able to reproduce the issue on ZTE inari.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: