Closed
Bug 951926
Opened 12 years ago
Closed 8 years ago
[B2G][Settings] When the Caller ID is enabled or disabled using the dialer it will show incorrectly in settings
Categories
(Firefox OS Graveyard :: Gaia::Settings, defect)
Tracking
(b2g-v1.2 affected, b2g-v1.3 affected, b2g-v1.4 affected)
RESOLVED
WONTFIX
People
(Reporter: KTucker, Unassigned)
Details
(Whiteboard: permafail)
Attachments
(1 file)
|
1.02 MB,
video/mp4
|
Details |
Description:
When the Caller ID is enabled or disabled using the dialer it will show incorrectly in settings. If the user dials *31# to show the number, it will show "Hide number" under Caller ID in settings. If the user dials #31# to hide the number, Caller ID in settings will show "Show number".
Repro Steps:
1) Updated Buri to Build ID: 20131218004002
2) Open the dialer and dial "*31#" and tap the green call button.
3) Tap on the "Home button" phone and tap on the "Settings" icon.
4) Tap on "Call Settings".
5) Look at the setting under "Caller ID".
6) Repeat steps 2 through 5 but dial "#31#" to hide the number instead of "*31#".
Actual:
Dialing *31# to show the number will show "Hide number" under Caller ID in settings and dialing "#31# to the hide the number will show "Show Number" under Caller ID in settings.
Expected:
The correct setting should be shown under Caller ID. When the user dials "*31#", the Caller ID should say "Show number" in settings. When the user dials "#31#", the Caller ID should say "Hide Number" in settings.
Environmental Variables
Device: Buri v 1.3.0 Mozilla RIL
Build ID: 20131218004002
Gecko: http://hg.mozilla.org/releases/mozilla-aurora/rev/369bdbff6c38
Gaia: a99b23e73fe5630a877004746d0e7fcec1b6d653
Platform Version: 28.0a2
RIL Version: 01.02.00.019.082
Notes:
Repro frequency: 100%
Link to failed test case: https://moztrap.mozilla.org/manage/case/9568/
See attached: video, logcat
Comment 1•12 years ago
|
||
This is a dupe of a known bug.
Whiteboard: burirun1.3-1 → burirun1.3-1 DUPEME
Comment 2•12 years ago
|
||
Ah - now I see why this was filed. This is a followup to bug 937389.
Whiteboard: burirun1.3-1 DUPEME → burirun1.3-1
Comment 3•12 years ago
|
||
(In reply to ktucker from comment #0)
> When the Caller ID is enabled or disabled using the dialer it will show
> incorrectly in settings. If the user dials *31# to show the number, it will
> show "Hide number" under Caller ID in settings. If the user dials #31# to
> hide the number, Caller ID in settings will show "Show number".
This is not correct. `*31#` hides the calling line identification and `#31#` shows the calling line identification.
> Actual:
> Dialing *31# to show the number will show "Hide number" under Caller ID in
> settings and dialing "#31# to the hide the number will show "Show Number"
> under Caller ID in settings.
This is what is expected.
> Expected:
> The correct setting should be shown under Caller ID. When the user dials
> "*31#", the Caller ID should say "Show number" in settings. When the user
> dials "#31#", the Caller ID should say "Hide Number" in settings.
This is not correct.
Updated•12 years ago
|
Whiteboard: burirun1.3-1 → burirun1.3-1 burirun1.3-2
Updated•12 years ago
|
Whiteboard: burirun1.3-1 burirun1.3-2 → burirun1.3-1 burirun1.3-2 burirun1.3-3
| Reporter | ||
Updated•12 years ago
|
Whiteboard: burirun1.3-1 burirun1.3-2 burirun1.3-3 → permafail
| Reporter | ||
Updated•12 years ago
|
status-b2g-v1.4:
--- → affected
Comment 4•12 years ago
|
||
(In reply to José Antonio Olivera Ortega [:jaoo] from comment #3)
> (In reply to ktucker from comment #0)
> > Expected:
> > The correct setting should be shown under Caller ID. When the user dials
> > "*31#", the Caller ID should say "Show number" in settings. When the user
> > dials "#31#", the Caller ID should say "Hide Number" in settings.
>
> This is not correct.
I would like to repeat that this is not correct and this bug should be close as INVALID.
Please refer to [1] to know about this MMI code.
[1] http://www.etsi.org/deliver/etsi_ts/122000_122099/122081/11.01.00_60/ts_122081v110100p.pdf
Comment 5•8 years ago
|
||
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•