Closed Bug 996419 Opened 10 years ago Closed 8 years ago

[OPEN C_1.3]CLIR activation by menu works, but always shows "Network default"

Categories

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

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(tracking-b2g:backlog, b2g-v1.3 unaffected)

RESOLVED INCOMPLETE
tracking-b2g backlog
Tracking Status
b2g-v1.3 --- unaffected

People

(Reporter: tong.wei2, Unassigned)

Details

(Whiteboard: [cert][closeme 4/22/2013])

User Agent: Mozilla/5.0 (Windows NT 5.1; rv:12.0) Gecko/20100101 Firefox/12.0 (Beta/Release)
Build ID: 20120420145725

Steps to reproduce:

A.- Overview Description (technical background, concise explanation of the
bug):
CLIR activation by menu works, but always shows "Network default"
B.- Steps to Reproduce (initial conditions, required resources, step by
step instructions to reproduce):
Settings > Call Sttings > Caller ID > You can set Hide/show number and menu
must show the option chosen 
C.- Actual Result (current bad behaviour that is reported as a bug):
You can choose between: Network default / Hide Number / Show number and the
selection works properly but always shows in settings Network default
D.- Expected Result (correct behaviour wished):
It must show the current configuration


Actual results:

You can choose between: Network default / Hide Number / Show number and the
selection works properly but always shows in settings Network default


Expected results:

It must show the current configuration
blocking-b2g: --- → 1.3?
OS: All → Gonk (Firefox OS)
Hardware: All → ARM
Ni Tong,

Can you please help us with a video here? Logs?

QA,

Please check if reproducible on Moz RIL.
blocking-b2g: 1.3? → 1.3+
Flags: needinfo?(tong.wei2)
Keywords: qawanted
Whiteboard: [cert]
The issue does NOT reproduce on 1.3. The Caller ID correctly displays the selected option upon selecting.

Device: Buri 1.3 MOZ
BuildID: 20140414004002
Gaia: 8b92c56267fe50772095f1f25d6cc1f9c9966eb4
Gecko: 3e26908fca71
Version: 28.0
Firmware Version: v1.2-device.cfg
Over to backlog since we can't reproduce this.
blocking-b2g: 1.3+ → backlog
Whiteboard: [cert] → [cert][closeme 4/22/2013]
It might depends on the carrier. I mean this supplementary service might not be provisioned for the subscriber.
blocking-b2g: backlog → ---
Status: UNCONFIRMED → RESOLVED
Closed: 8 years ago
Flags: needinfo?(tong.wei2)
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.