Closed Bug 911434 Opened 12 years ago Closed 10 years ago

[B2G][Helix][dialer][tongxiao]The UE could not make a emergency call when in the PIN/PUK interface.

Categories

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

defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: lecky.wanglei, Unassigned)

Details

User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; MALC; aff-kingsoft-ciba; .NET4.0C; .NET4.0E; Tablet PC 2.0) Steps to reproduce: 【Detail Description*】:The UE could not make a emergency call when in the PIN/PUK interface. 【Repro Steps*】: 1.Open the PIN/PUK check . 2.Restart the UE . 3.There will be a prompt to you to input the PIN/PUK code. 4.Check if we could dial the emergency number. 【Expect Result*】: We could dial the emergency number. 【Real Result*】: We could not dial the emergency number. 【Test Count*】:10 【Found Count*】:10 【Gaia commit ID*】:c0ea0a4943dc8d3751b07f5b5c5d3abe06364a14 【Gecko commit ID*】: 170f9e477571127cd40997fa2abe262ed43f0e4d 【Network environment】: 【Resume operation】: 【Carrier】:
Severity: normal → blocker
blocking-b2g: --- → hd?
Priority: -- → P2
any update?
any update?
Is this a feature, would not solved on V1.1HD?
Flags: needinfo?(wchang)
Duplicate of bug 908004
Status: UNCONFIRMED → RESOLVED
Closed: 12 years ago
Flags: needinfo?(wchang)
Resolution: --- → DUPLICATE
Hi , I'm sorry the description above is not clear. I mean that there is no emergency call button in the PIN/PUK-code-input interface.
Status: RESOLVED → UNCONFIRMED
Flags: needinfo?(wchang)
Resolution: DUPLICATE → ---
Flagging UX, we should consider adding emergency call possibility from PIN/PUK locked screen. Hi Lecky, This will not be changed on v1.1, and not likely v1.2 (unless it has already been changed). UX will need to review how this can be added.
Flags: needinfo?(wchang) → needinfo?(firefoxos-ux-bugzilla)
Removing hd?, flagging koi? or nom 1.3? if more appropriate. Please consider this as it seems to be standard practice on other OSes.
blocking-b2g: hd? → koi?
I am flagging Joe, to see if this is or should be included in the 1.3 backlog. Joe can determine if this needs to be included, if this is a certification requirement, etc. If this feature is included, I will flag Jacqueline to advise on the UX for it.
Flags: needinfo?(firefoxos-ux-bugzilla) → needinfo?(jcheng)
This is a feature request and I think we'd want this. Not a blocker for 1.2 though.
blocking-b2g: koi? → ---
1.3? so it gets discussed in v1.3 triages
blocking-b2g: --- → 1.3?
Flags: needinfo?(jcheng)
Hi Beatriz: As Wayne Chang Says:" This will not be changed on v1.1, and not likely v1.2 (unless it has already been changed).". Do the current problem will be accepted? 1. there is no emergency call button in the PIN/PUK-code-input interface. But after quit the interface ,wo also can call the emergency number in the dialer interface. Thanks!
Flags: needinfo?(brg)
(In reply to lecky from comment #11) > Hi Beatriz: > > As Wayne Chang Says:" This will not be changed on v1.1, and not likely > v1.2 (unless it has already been changed).". > > Do the current problem will be accepted? > > 1. there is no emergency call button in the PIN/PUK-code-input interface. > But after quit the interface ,wo also can call the emergency number in the > dialer interface. > > Thanks! For TEF this is a new feature not in 1.1 scope so no need to support it in 1.1HD.
Flags: needinfo?(brg)
triage: add to backlog bug 891754
blocking-b2g: 1.3? → ---
Status: UNCONFIRMED → RESOLVED
Closed: 12 years ago11 years ago
Resolution: --- → WONTFIX
Lecky, I guess you did not want to close this feature request bug which tracks the implementation of a new Comms feature.
Status: RESOLVED → REOPENED
Ever confirmed: true
Resolution: WONTFIX → ---
I've just verified the current behavior and we support calling emergency number without inputting the PIN/PUK code with the three following UX flows: 1) Turn on the phone, you will be prompted for the PIN/PUK code, this can be skipped, to call an emergency number open the dialer and follow with flow 2 2) Open the dialer, you will be prompted for the PIN/PUK code, this can be skipped and then you are able to call an emergency number 3) Have the screen lock enabled with a passcode lock enabled, lock the screen and enter the emergency call app from the passcode lock prompt, you are then able to dial an emergency number directly, no PIN/PUK code prompt is shown Considering the above I'd be tempted of closing this as RESOLVED FIXED unless we want to modify the UX flow of the first case so that you don't have to skip the PIN/PUK prompt twice. Comment 6 suggests having an option to go into the emergency call dialer directly from the PIN/PUK prompt instead of having to skip it and go into the dialer (and having to skip it again). Carrie, what do you think?
Flags: needinfo?(cawang)
Hi, What Gabriele described in comment 15 is the correct behavior. Personally I think we can redesign the PIN/PUK page but that will be a system-wise change and we need to reach an agreement with the Settings. I'd like to know Jenny's opinion on this one. Thanks!
Flags: needinfo?(cawang) → needinfo?(jelee)
Hello, As Gabriele mentioned in comment 15, I think our current design is acceptable. PIN/PUK code input screen appears at various places, for example, entering Message will trigger the screen, at this point, making emergency call is not what user intends to do. As a result, emphasizing "you can still make emergency call when SIM is locked" would seem unnecessary and further complicates the PIN/PUK screen. Thanks!
Flags: needinfo?(jelee)
Thanks for the feedback Carrie, Jenny. I'm thus closing this as FIXED since we can indeed make emergency calls even when the phone is locked with PIN/PUK (comment 15).
Status: REOPENED → RESOLVED
Closed: 11 years ago10 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.