Closed Bug 1001616 Opened 6 years ago Closed 2 years ago

[B2G][Settings][FDN] The user enters an infinte sending state when they dial a valid MMI code with FDN enabled

Categories

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

ARM
Gonk (Firefox OS)
defect
Not set

Tracking

(b2g-v1.3T affected, b2g-v1.4 affected)

RESOLVED WONTFIX
Tracking Status
b2g-v1.3T --- affected
b2g-v1.4 --- affected

People

(Reporter: rkunkel, Unassigned)

Details

(Whiteboard: [tarako-exploratory])

Attachments

(2 files)

Attached file log_20140425_1220_.txt
Description:
When the user has FDN enabled and they try to use MMI codes, no error or warning message is prompted to the user that FDN is in operation. This causes the user to become stuck on a sending screen until the cancel the operation.

Repro Steps:
1) Update a Tarako device to v1.3 BuildID: 20140423014003
2) Settings > Call Settings > Select SIM > Fixed dialing numbers > Enable > Enter SIM PIN 2 
3) Open dialer, dial *43# - This will enable call waiting
4) Observe user gets stuck in 'Sending...' loop until they cancel the process

Actual:
User gets stuck in 'Sending...' loop until they cancel the process

Expected:
Error message prompting user that FDN is enabled

v1.3 Environmental Variables:
Device: Tarako v1.3 MOZ
BuildID: 20140423014003
Gaia: 9aa9b04049f0291b124c50e0f9c3ce0e1f547725
Gecko: 5dc3e5ec4178
Version: 28.1
Firmware Version: sp6821

Repro frequency: 100%
See attached: logcat, firewatch
I was able to reproduce this issue on the latest v1.4 Buri build:

4/23 Environmental Variables:
Device: Buri v1.4 MOZ RIL
BuildID: 20140423000203
Gaia: 25d53d442cbf17c150575c98979e957ae040e023
Gecko: 2d1b4d36eef9
Version: 30.0a2
Firmware Version: V1.2-device.cfg
Does this reproduce on a 1.3 build?
Keywords: qawanted
Issue reproduces on a Buri with 1.3 100%

1.3 Environmental Variables:
Device: buri 1.3 MOZ
BuildID: 20140429024001
Gaia: caab7a78f0c04913f48a3051259663ee85625906
Gecko: f84a8ffbc552
Version: 28.0
Firmware Version: V1.2-device.cfg
Keywords: qawanted
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.