[Dialer][USSD] 'Change SIM PIN' MMI code incorrectly requires the user to select 'Send' to activate the code.



4 years ago
11 months ago


(Reporter: Marty, Unassigned)


Gonk (Firefox OS)

Firefox Tracking Flags

(tracking-b2g:backlog, b2g-v2.0 affected, b2g-v2.1 affected, b2g-v2.2 affected, b2g-master affected)


(Whiteboard: [3.0-Daily-Testing], URL)


(1 attachment)



4 years ago
Created attachment 8566779 [details]

The following MMI service code may be used in Dialer to change the SIM PIN on the device:

After typing this code format into the Dialer via the keypad, the user must then hit the SEND button to activate this code.

3GPP specifications state in section 6.6.2: "Note that the SEND function is not used in these procedures."

-Abbreviated Dialing Codes are activated when the '#' key is tapped. The Send button is not needed.

Repro Steps:
1) Update a Flame to 20150219010228
2) Ensure that a SIM with an enabled SIM PIN is currently in the device.
3) Open the Dialer app and input the code "**04*OLD_PIN*NEW_PIN*NEW_PIN#"

The code is viewable in the Dialer field, but is not activated until the Send button is tapped.

The code is executed when the final '#' character is input for the code.

Environmental Variables:
Device: Flame 3.0 (319MB)(Full Flash)
Build ID: 20150219010228
Gaia: 620aecfde85a8b093247837c55de2708e22be1e1
Gecko: 360b5f211180
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: 5/5
See attached: logcat, video (URL)

Comment 1

4 years ago
This issue DOES occur in Flame 2.2, 2.1 and 2.0 builds.
The user must tap the Send button to activate the Change SIM PIN MMI Code.

Environmental Variables:
Device: Flame 2.2 (319MB)(Full Flash)
Build ID: 20150219002504
Gaia: ce79d35b92261e7cbfeaefebf87859ebeb0979b4
Gecko: 159a3907b959
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

Environmental Variables:
Device: Flame 2.1 (319MB)(Full Flash)
Build ID: 20150210002200
Gaia: 7dd130a312f12c89b2d41948f8557effa56afbf6
Gecko: 2de03dfa9aac
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

Environmental Variables:
Device: Flame 2.0 (319MB)(Full Flash)
Build ID: 20150210000201
Gaia: 2989f2b2bd12fcc0e9c017d2db766e76a55873b8
Gecko: 2ca6a9e7cb81
Gonk: e7c90613521145db090dd24147afd5ceb5703190
Version: 32.0 (2.0)
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(pbylenga)
NI on component owner for nomination decision and assignment.
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(pbylenga) → needinfo?(jlorenzo)
The specs are not exactly respected, but it looks minor enough to not block on it.
Flags: needinfo?(jlorenzo)
Flags: needinfo?(htsai)
Flags: needinfo?(htsai)
(In reply to Johan Lorenzo [:jlorenzo] (QA) from comment #3)
> The specs are not exactly respected, but it looks minor enough to not block
> on it.

Unless this blocks certification, I agree that it doesn't look worth being blocked, given that this behavior doesn't block a real use case.

If we want to support this, we might need webAPI changes.
I don't think we need webAPI changes for this; it should be fixable in the dialer by automatically invoking dial() when the user types the last character and we recognize this pattern. We already do something similar for getting the IMEI code(s) (*#06#) and speed dial numbers (N(N)(N)#) which have the same behavior.
tracking-b2g: --- → -
tracking-b2g: - → backlog
Priority: -- → P3

Comment 6

11 months ago
Firefox OS is not being worked on
Last Resolved: 11 months ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.