1126056 - [Settings][SIM Pin] If the user enters a SIM pin incorrectly then leaves, and reopens the SIM pin screen they are not told the number of tries left

Status: RESOLVED WONTFIX

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

Description

[Derek Harris [:DerekH] - Dont need info. Last day 6/5/15]

Description:
The user is not shown the number of tries left to unlock their SIM after dissmissing the SIM pin screen, and then prompting it again.


Prerequisites: Have a SIM card with a SIM pin in the device

Repro Steps:
1) Update a Flame to 20150126010231
2) Open an app to prompt the SIM PIN screen, such as Messages
3) Enter in an incorrect SIM PIN.
4) When told that you have "X" amount of tries left, tap on "Skip"
5) Return home, then reopen the app

Actual:
User is not informed how many tries they have left when the SIM pin screen is shown

Expected:
User is informed of the number of tries they have left to enter in the correct SIM pin until the pin is locked

Environmental Variables:
Device: Flame 3.0 (319Mb)(Kitkat)(Full Flash)
BuildID: 20150126010231
Gaia: 0f662dffef27599443cfcd790c2b39190a2b35c8
Gecko: fa91879c8428
Gonk: e7c90613521145db090dd24147afd5ceb5703190
Version: 38.0a1 (3.0) 
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:38.0) Gecko/38.0 Firefox/38.0

Repro frequency: 15/15 100%
See attached: Logcat, Video - http://youtu.be/MdGkscBabwI

Comment 1

[Derek Harris [:DerekH] - Dont need info. Last day 6/5/15]

This issue DOES reproduce on Flame 2.2, Flame 2.1, and the v18D-1 Base Image

User is not informed how many tries they have left when the SIM pin screen is shown

Device: Flame 2.2 (319mb)(Kitkat)(Full Flash)
Build ID: 20150126002536
Gaia: 0518f4581a0925c0b703d730ef289ab15cbd1216
Gecko: c6aa604a7967
Gonk: e7c90613521145db090dd24147afd5ceb5703190
Version: 37.0a2 (2.2)
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:37.0) Gecko/37.0 Firefox/37.0


Device: Flame 2.1 (319mb)(Kitkat)(Full Flash)
BuildID: 20150126001827
Gaia: 54d92cc0755e5102223276ab23063b5eee74b514
Gecko: 522d6c980917
Gonk: e7c90613521145db090dd24147afd5ceb5703190
Version: 34.0 (2.1) 
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0


Device: Flame Base v18D-1 (319Mb)(Kitkat)
Build ID: 20150106124450
Gaia: 79f6218c4f30c2739575c3ab800078c2cda135cb
Gecko: d9d4000dd43a3637345a41d716dc97fdd700d715
Version: 32.0 (2.0)
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0

Comment 2

[Derek Harris [:DerekH] - Dont need info. Last day 6/5/15]

Correction to Comment 1:

This issue does NOT reproduce on the v18D-1 Base Image

User is informed of the number of tries they have left to enter in the correct SIM pin until the pin is locked

Device: Flame Base v18D-1 (319Mb)(Kitkat)
Build ID: 20150106124450
Gaia: 79f6218c4f30c2739575c3ab800078c2cda135cb
Gecko: d9d4000dd43a3637345a41d716dc97fdd700d715
Version: 32.0 (2.0)
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0

Comment 3

[Peter Bylenga [:PBylenga]]

NI on component owner for nomination decision and assignment.  This is a regression from base image.

Comment 4

[Gerry Chang [:gchang]]

NI developers for more information.

Comment 5

[Arthur Chen [:arthurcc][inactive after 6/30]]

Hi Derek, did you flash pvt build for v2.1 and v2.2? This might make it change from commercial ril to moz ril.

Comment 6

[Derek Harris [:DerekH] - Dont need info. Last day 6/5/15]

Hi Arthur, Yes the environmental variables from comment 1 for 2.1 and 2.2 were pulled from full flashed devices.

Comment 7

[Edgar Chen [:edgar]]

(In reply to Arthur Chen [:arthurcc] from comment #5)
> Hi Derek, did you flash pvt build for v2.1 and v2.2? This might make it
> change from commercial ril to moz ril.

(In reply to Derek Harris [:DerekH] from comment #6)
> Hi Arthur, Yes the environmental variables from comment 1 for 2.1 and 2.2
> were pulled from full flashed devices.

In flame, the Moz RIL doesn't fully support `getting remaining retries`, because it is partner's proprietary feature, it only works perfect with commercial RIL.

Comment 8

[Arthur Chen [:arthurcc][inactive after 6/30]]

Per comment 7, this sounds like an invalid bug. Could you confirm? Thanks.

Comment 9

[Derek Harris [:DerekH] - Dont need info. Last day 6/5/15]

Attachment: shallow_flash_Ril_log.txt

It looks as though a shallow flash will use the MOZ RIL. I have attached my ril log from the shallow flash. I however was using a full flash, and commercial RIL. So I dont believe this is an invalid bug.

Comment 10

[Derek Harris [:DerekH] - Dont need info. Last day 6/5/15]

Attachment: Full_flash_Ril_log.txt

Comment 11

[Edgar Chen [:edgar]]

(In reply to Derek Harris [:DerekH] from comment #9)
> Created attachment 8557231 [details]
> shallow_flash_Ril_log.txt
> 
> It looks as though a shallow flash will use the MOZ RIL. I have attached my
> ril log from the shallow flash. I however was using a full flash, and
                                                ^^^^^^^^^^^^^^^^^^
Do you full flash the image from the pvt build? Full flashing pvt image will still use MOZ RIL.
Only full flashing *base image* will use commercial RIL.

> commercial RIL. So I dont believe this is an invalid bug.

Comment 12

[Edgar Chen [:edgar]]

(In reply to Edgar Chen [:edgar][:echen] from comment #11)
> (In reply to Derek Harris [:DerekH] from comment #9)
> > Created attachment 8557231 [details]
> > shallow_flash_Ril_log.txt
> > 
> > It looks as though a shallow flash will use the MOZ RIL. I have attached my
> > ril log from the shallow flash. I however was using a full flash, and
>                                                 ^^^^^^^^^^^^^^^^^^
> Do you full flash the image from the pvt build? Full flashing pvt image will
> still use MOZ RIL.
> Only full flashing *base image* will use commercial RIL.

BTW, AFAIK, commercial ril only supports 2.0, so I believe the ril used in 2.1 and 2.2 is moz ril.

> 
> > commercial RIL. So I dont believe this is an invalid bug.

Comment 13

[Verson Xiong (Leave from Mozilla)]

Attachment: logcat_0549.txt

I can reproduce this bug on latest v2.1 build,The STR is same as Comment 0.
Reproduce rate:5/5
See attachment:video.mp4 & logcat_0549.txt

Build version:
Flame 2.2(affected):
Build ID               20150420002502
Gaia Revision          c15a2b6d3a783813959c2b3bffd2a131f4270b9e
Gaia Date              2015-04-17 17:49:32
Gecko Revision         https://hg.mozilla.org/releases/mozilla-b2g37_v2_2/rev/cc02ee38b252
Gecko Version          37.0
Device Name            flame
Firmware(Release)      4.4.2
Firmware(Incremental)  eng.cltbld.20150420.041634
Firmware Date          Mon Apr 20 04:16:45 EDT 2015
Bootloader             L1TC000118D0

Flame 3.0(affected):
Build ID               20150420160201
Gaia Revision          a8e4f95dce9db727dda5d408b038f97fb4296557
Gaia Date              2015-04-20 19:30:21
Gecko Revision         https://hg.mozilla.org/mozilla-central/rev/e7112314d9d5
Gecko Version          40.0a1
Device Name            flame
Firmware(Release)      4.4.2
Firmware(Incremental)  eng.cltbld.20150420.191858
Firmware Date          Mon Apr 20 19:19:10 EDT 2015
Bootloader             L1TC000118D0

Comment 14

[Verson Xiong (Leave from Mozilla)]

 
> I can reproduce this bug on latest v2.1 build,The STR is same as Comment 0.

v2.2 & v3.0 build

Comment 15

[Verson Xiong (Leave from Mozilla)]

Attachment: video.mp4

Comment 16

[BMO Automation]

Firefox OS is not being worked on