Closed
Bug 1090167
Opened 10 years ago
Closed 6 years ago
Roaming Broker 3G (manual) does not work correctly.
Categories
(Firefox OS Graveyard :: Gaia::Settings, defect)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: juanjose.iglesias, Unassigned)
References
Details
Attachments
(3 files)
A special card is need to test this bug, it is Roaming Broker 3G SIM. With the Roaming Broker 3G SIM card, When subscription is changed (i.e. "Broker" to "Home "or "Home" to "Broker") via STK menu manually, the device asks for a PIN in all cases. STEPS: - Insert the Roaming Broker 3G SIM card. - Enter the PIN code - Wait until the DUT register in the network. - Use the STK menu to change between "Home" and "Broker". ACTUAL: When subscription is changed (i.e. "Broker" to "Home "or "Home" to "Broker") via STK menu, the device asks for a PIN in all cases. EXPETED: The DUT should ask about the PIN code only once. I have tested it using Flame master (Gecko eab7ec3 Gaia a12668c) and Flame 2.0 (Gecko 675d616 Gaia 2183b4f).
Reporter | ||
Comment 1•10 years ago
|
||
Reporter | ||
Comment 2•10 years ago
|
||
Updated•10 years ago
|
Component: Gaia → Gaia::Settings
Comment 3•10 years ago
|
||
I saw the same error as in 1089573. Probably are the same issue. See: https://bugzilla.mozilla.org/show_bug.cgi?id=1089573#c2 Adding a dependency. Juanjo can you test this too with the 1089573 proposed patch? Thank you
Depends on: 1089573
Flags: needinfo?(juanjose.iglesias)
Reporter | ||
Comment 4•10 years ago
|
||
I have taken a new log using a flame master (Gecko c0265bd Gaia 0bcc566), with the patch added, and a Broker 3G SIM card. When subscription is changed (i.e. "Broker" to "Home "or "Home" to "Broker") via STK menu, the device asks for a PIN in all cases. The new log is called Broker3G_Manual_RilOn_TracesOn_master.txt
Flags: needinfo?(juanjose.iglesias)
Reporter | ||
Comment 5•10 years ago
|
||
Comment 6•6 years ago
|
||
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•