981537 - [Call settings] Unable to enable or disable call forwarding correctly but get "Call settings error" message only for certain SIM cards.

Status: RESOLVED WONTFIX

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

Description

[Enpei]

Attachment: 2014-03-10-16-45-21.png

Test with CHT, FET and Vibo SIM cards in Taiwan, here are the results:
1. CHT: Able to enable/disable all items under Call forwarding section, log buri_forward_pass.txt
2. FET: Unable to enable/disable all items under Call forwarding section, log buri_forward_fail.txt
3. Vibo: Except "Always forward", unable to enable/disable all other items under Call forwarding section, log buri_forward_fail_partial.txt

When it fails, "Call settings error" message pops up. Found this on both v1.3 and 1.4 build.


* Build Number  
Gaia      6c109df47006b08c082761c0ddd6ba53a864983a
Gecko     https://hg.mozilla.org/mozilla-central/rev/21f293fc8d34
BuildID   20140309160201
Version   30.0a1

* Occurrence rate
100%

Comment 1

[Enpei]

Attachment: buri_forward_pass.txt

Comment 2

[Enpei]

Attachment: buri_forward_fail.txt

Comment 3

[Enpei]

Attachment: buri_forward_fail_partial.txt

Comment 4

[José Antonio Olivera Ortega [:jaoo]]

(In reply to Enpei from comment #0)
> Test with CHT, FET and Vibo SIM cards in Taiwan, here are the results:
> 1. CHT: Able to enable/disable all items under Call forwarding section, log
> buri_forward_pass.txt
> 2. FET: Unable to enable/disable all items under Call forwarding section,
> log buri_forward_fail.txt
> 3. Vibo: Except "Always forward", unable to enable/disable all other items
> under Call forwarding section, log buri_forward_fail_partial.txt
> 
> When it fails, "Call settings error" message pops up. Found this on both
> v1.3 and 1.4 build.

The carrier might not allow the user to change/disable/enable call forwarding rules for states 'no reply', ''

I'll take a look at it but there have not been changes in this logic for a while so I guess these issues are related to the ICC card used in the tests.

Comment 5

[José Antonio Olivera Ortega [:jaoo]]

(In reply to José Antonio Olivera Ortega [:jaoo] from comment #4)
> The carrier might not allow the user to change/disable/enable call
> forwarding rules for states 'no reply', ''

The states I tried to mention were 'no reply', 'busy' and 'unreachable'.

Comment 6

[bhavana bajaj [:bajaj]]

is this bug sim specific  ? Traige was unclear what kind of sim's would be impacted. Is this something a real world user will hit ? Unclear why this would be a blocker.

If 1.3 is affected,  why is this blocking nominated only for 1.4 ? Its confusing if this is a nice-to-have or a real blocker.

Comment 7

[Joe Cheng [:jcheng] (please needinfo)]

does it happen on both fugu and buri?

since this can be market specific, so far we have not heard about this from markets we launched in. minus for now and please work on this and land on trunk. thanks

Comment 8

[Rachel Pribble [:rpribble]]

We are seeing this issue on the Buri v1.4 MOZ ril and the Tarako v1.3T MOZ ril, as well.

Environmental Variables:
Device: Buri v1.4 MOZ ril
BuildID: 20140428000206
Gaia: d23e479e8a4ce0bc620acb2d7e2f82801aa4d0ea
Gecko: 36f67ce46855
Version: 30.0a2
Firmware Version: v1.2-device.cfg

1.3t Environmental Variables:
Device: Tarako 1.3t
BuildID: 20140428014001
Gaia: 8895b180ed636069473703d0e7b73086989601ce
Gecko: 7caf4b5abfce
Version: 28.1
Firmware Version: sp6821

On both the latest Buri and Tarako builds, the user is able to enable the call forwarding options, but then is unable to disable call forwarding or edit the specified phone number once it's been activated. The entered phone number remains locked and faded grey.

We were unable to reproduce the issue on an Android device, it appears to be functioning correctly.

Comment 9

[Rachel Pribble [:rpribble]]

Attachment: BuriScreenshot.png

Comment 10

[BMO Automation]

Firefox OS is not being worked on