1103811 - [FFOS2.0][Woodduck][SEC]PUK2 Block screen can not come out after PUK2 Blocked.

Status: RESOLVED INVALID

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

Description

[sync-1]

DEFECT DESCRIPTION:[SEC]PUK2 Block screen can not come out after PUK2 Blocked.
 
  REPRODUCING PROCEDURES:
 1. Load a simcard to the phone which with PIN2's AttemptsRemaining = 3, 
    PUK2's AttemptsRemaining = 10;
 2. Go to "settings->...>FDN", input incorrect PIN2 Code to block PIN2;
 3. After the PIN2 block, PUNK2 input screen come out;
 4. Input 10 times incorrect PUK2 Code, PUK2 Block screen do not come out--ko1;
 5. PIN2 related function do not disabled.--ko2
 
 
  EXPECTED BEHAVIOUR:
 4. Input 10 times incorrect PUK2 Code, PUK2 Block screen should come out;
 5. PIN2 related function should be disabled.
 
 
  ASSOCIATE SPECIFICATION:
 
  TEST PLAN REFERENCE:
 
  TOOLS AND PLATFORMS USED:
 
  USER IMPACT:
 
  REPRODUCING RATE:
 
  For FT PR, Please list reference mobile's behavior:

Comment 1

[sync-1]

Attachment: mtklog-SWv7G20-p-p27.rar

Comment 2

[Josh Cheng [:josh]]

Hi Shawn,
Could you help to check?

Comment 3

[shawn ku [:sku]]

Hi Woodduck:
 Please help check with your modem to see what will be reported to Gecko/Gaia!!

Thanks!!
Shawn

Comment 4

[shawn ku [:sku]]

Attachment: PUK_Block.log

// RIL_E_PASSWORD_INCORRECT
11-28 17:15:45.287   161   626 I Gecko   : RIL Worker: [0] Solicited response for request type 5, token 142, error 3

// RIL_E_PASSWORD_INCORRECT
11-28 17:15:54.922   161   626 I Gecko   : RIL Worker: [0] Solicited response for request type 5, token 143, error 3

// RIL_E_PASSWORD_INCORRECT
11-28 17:16:10.007   161   626 I Gecko   : RIL Worker: [0] Solicited response for request type 5, token 144, error 3

// RIL_E_PASSWORD_INCORRECT
11-28 17:16:19.202   161   626 I Gecko   : RIL Worker: [0] Solicited response for request type 5, token 145, error 3

// RIL_E_PASSWORD_INCORRECT
11-28 17:16:36.803   161   626 I Gecko   : RIL Worker: [0] Solicited response for request type 5, token 146, error 3

// RIL_E_PASSWORD_INCORRECT
11-28 17:16:47.047   161   626 I Gecko   : RIL Worker: [0] Solicited response for request type 5, token 147, error 3

// RIL_E_PASSWORD_INCORRECT
11-28 17:16:59.135   161   626 I Gecko   : RIL Worker: [0] Solicited response for request type 5, token 148, error 3

// RIL_E_PASSWORD_INCORRECT
11-28 17:17:11.814   161   626 I Gecko   : RIL Worker: [0] Solicited response for request type 5, token 149, error 3

// RIL_E_PASSWORD_INCORRECT
11-28 17:17:20.505   161   626 I Gecko   : RIL Worker: [0] Solicited response for request type 5, token 150, error 3

// RIL_E_GENERIC_FAILURE
11-28 17:17:30.244   161   626 I Gecko   : RIL Worker: [0] Solicited response for request type 5, token 151, error 2

Comment 5

[shawn ku [:sku]]

Hi Reporter,
 It looks like the only way to fix this issue is to check retry count for PUK2.

Pure FxOS does not read retry counter when enter Call Setting.
Might need partner to check if you can implement this by yourself since retry count check is done by your side.

Comment 6

[Peipei Cheng (needinfo if you need my action)]

HI reporter, is there any update on this bugper comment 5?

Comment 7

[sync-1]

hi mozilla:
    there are no progress

Comment 8

[sync-1]

hi mozilla:
    Can you tell me the code which to get retry count?

Comment 9

[Peipei Cheng (needinfo if you need my action)]

shawn, could you please help with comment 8?

Comment 10

[shawn ku [:sku]]

Hi there:

you can check ftu/js/sim_manager.js for the usage.
Example:
var request = icc.mozIcc.getCardLockRetryCount("puk2");
    request.onsuccess = function() {
      var retryCount = request.result.retryCount;
      if (retryCount) {
        // update retry counter on UI
      } else {
        // no more retry
      }
    };
    request.onerror = function() {
      console.error('Could not fetch CardLockRetryCount', request.error.name);
    };

Please let me know if any problem you may have.

Comment 11

[sync-1]

hi mozilla:
    谢谢你的例子，但是在settings中PUK2的显示是在settings/js/simcard_dialog.js文件中。
    目前的问题是当PUK2码错误次数达到10次时，依旧停留在PUK2的界面并且PUk2相关的功能还能使用，但是当PUK2码错误10次后本sim卡应该报废。故当错误次数达到10次时结束PUK2的界面，PUK2的相关功能也应该停止使用。

Comment 12

[shawn ku [:sku]]

(In reply to sync-1 from comment #11)
> hi mozilla:
>     谢谢你的例子，但是在settings中PUK2的显示是在settings/js/simcard_dialog.js文件中。
>    
> 目前的问题是当PUK2码错误次数达到10次时，依旧停留在PUK2的界面并且PUk2相关的功能还能使用，但是当PUK2码错误10次后本sim卡应该报废。
> 故当错误次数达到10次时结束PUK2的界面，PUK2的相关功能也应该停止使用。

You can close the FDN setting, and also disable FDN related feature when retry counter <= 0.

Besides, this is Gaia scope, might need Gaia's help if partner still got issue.

Comment 13

[Josh Cheng [:josh]]

Mail from Chen Ding:
=======================================
dear all:
      https://bugzilla.mozilla.org/show_bug.cgi?id=1103811#c12
这个问题已经修复，提交VAL验证

Best Regards！

丁琛  Alvin   Application Engineer