960327 - [B2G][Settings][Cellular &Data] Switching from "manual network" to "automatic", device doesn't connect to network automatically

Status: RESOLVED DUPLICATE of bug 1036210

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

Description

[sarsenyev]

Attachment: log1.15.2014final.txt

Description:
For the test I used AT&T SIM card
Cellular signal is lost and no access to SIM card after switching back from manual operator to automatic, 
Not restarting, not resetting, not reflashing are helped only reimaging to the base image can restore the device

Repro Steps:
1) Updated Buri to BuildID: 20140115004003
2) Open "Settings" from home screen
3) Navigate to "Cellular & Data"
4) Go to :Network operator"
5) Change "Network type" to "Automatic"
6) Switch "Automatic selection" off
7) Choose some different available network and try to connect it
8) After connection is failed try to connect again
9) While it's still trying to connect it switch back to the "Automatic selection"  and verify the signal bar is with no signal and then restart the device

Actual:
SIM card is no longer available, even when restarting, resetting, reflashing, only reimage helps to restore the device

Expected:
When the device is switched to automatic, the device is automatically connecting to the network

Environmental Variables:
Device: Buri 1.3 MOZ
BuildID: 20140115004003
Gaia: 14e199d6a9ad917eacad883820a9f7619dbf42c8
Gecko: d7260b206e91
Version: 28.0a2
Firmware Version: v1.2-device.cfg

Notes: Step 5 is crucial without changing to "Automatic" I couldn't reproduce it
Repro frequency: 100%
See attached:  logcat

Comment 1

[Jason Smith [:jsmith]]

Does this reproduce on 1.2 or 1.1?

Comment 2

[Sarah Parsons]

This issue does reproduce on 1.1 and 1.2. After reverting back to an older base 20131115, We were still able to reproduce this issue on the 1.1, 1.2 and 1.3 branches.

Comment 4

[David Baron :dbaron: (⌚️UTC-4, no longer working on Mozilla)]

There are more details in bug 969079, including (1) that it's not possible to get back and fix the settings once the phone thinks it doesn't have a SIM card and (2) that the bug is fixed by "adb shell b2g stop" and "adb shell b2g start", but comes back again after a full reboot.

Comment 5

[Natalya Kot [:nkot]]

Hit this issue today by accident. 

Simple STR:
1) Updated Buri to BuildID: 20140304040200
2) Open Settings --> Cell&Data --> Network Operator
3) Select automatic --> OK
4) Restart
==> device won't longer recognize SIM 

Restart,reset, reflash, putting different SIM into device - nothing helps to recover... only running "adb shell stop b2g", "adb shell start b2g" helps

Is this going to be fixed? imagine if the user runs into this issue..

Comment 6

[Jason Smith [:jsmith]]

The original bug as filed here I thought had a recovery path to my understanding. For example, can you recover from switching the network operator flag?

Comment 7

[Natalya Kot [:nkot]]

(In reply to Jason Smith [:jsmith] from comment #6)
> The original bug as filed here I thought had a recovery path to my
> understanding. For example, can you recover from switching the network
> operator flag?

No, once got into this state Cell&Data becomes inaccessible so there is no way to switch the network operator flag. See also comment 4.

Comment 8

[Jason Smith [:jsmith]]

(In reply to Natalya Kot [:nkot] from comment #7)
> (In reply to Jason Smith [:jsmith] from comment #6)
> > The original bug as filed here I thought had a recovery path to my
> > understanding. For example, can you recover from switching the network
> > operator flag?
> 
> No, once got into this state Cell&Data becomes inaccessible so there is no
> way to switch the network operator flag. See also comment 4.

In the absolute worst case, I would expect that someone would pull the SIM card out & put it back in if they hit this bug to try to workaround it. The reason for this is that our target markets commonly involve users swapping SIMs, so they do know how to switch out SIMs easily.

Comment 9

[KTucker [:KTucker][Inactive 3/4/2016]]

There is not a workaround for this issue to our knowledge besides rebasing the phone. The phone will not read any SIMs after encountering this issue. We have tried multiple SIMs to no avail. The phone becomes basically inoperable. In my opinion, the end user will take their phone back to the carrier if they encounter this issue.

Comment 10

[Jason Smith [:jsmith]]

Ken - Is there anyone you could recommend here that could give input here on what a user could do workaround this problem? I want to see if we can get a user doc written up here on SUMO in case someone else hits this.

Comment 11

[Ken Chang[:kenkai]]

(In reply to Jason Smith [:jsmith] from comment #10)
> Ken - Is there anyone you could recommend here that could give input here on
> what a user could do workaround this problem? I want to see if we can get a
> user doc written up here on SUMO in case someone else hits this.
I wonder if this is a modem issue. It seems that modem recognizes the SIM is not available after being not able to camp on network. Let's see what's happened. By the way, is it also happened in other vendor's device?

Edgar, can you please analyze this bug?

Comment 12

[Jason Smith [:jsmith]]

(In reply to Ken Chang[:ken] from comment #11)
> (In reply to Jason Smith [:jsmith] from comment #10)
> > Ken - Is there anyone you could recommend here that could give input here on
> > what a user could do workaround this problem? I want to see if we can get a
> > user doc written up here on SUMO in case someone else hits this.
> I wonder if this is a modem issue. It seems that modem recognizes the SIM is
> not available after being not able to camp on network. Let's see what's
> happened. By the way, is it also happened in other vendor's device?

Don't know - we've only reproduced this on Buri so far.

Adding qawanted to check if this happens on Leo as well as a point of comparison.

Comment 13

[Edgar Chen [:edgar]]

I think we have two different bug here:
1). ((Settings --> Cell&Data --> Network Operator --> Network Type))
    Switching "Network Type" to "Automatic" then reboot device, device can not detect sim card.
    This only can be recovered by restarting b2g, but device can not detect sim again after full reboot. 
    Like bug 969079 and comment #5.
2). ((Settings --> Cell&Data --> Network Operator --> Automatic selection))
    Switching "Automatic selection" to off, and choose some network and try to connect it.
    After connection is failed, switching "Automatic selection" back to on. But device doesn't 
    automatically connect to network.
    More like comment #0 and also the bug title.

I suggest don't make bug 969079 as a duplicated one and tracking 1) in bug 969079.
And let this bug tracking 2).

Comment 14

[Ken Chang[:kenkai]]

(In reply to Edgar Chen [:edgar][:echen] from comment #13)
> I think we have two different bug here:
> 1). ((Settings --> Cell&Data --> Network Operator --> Network Type))
>     Switching "Network Type" to "Automatic" then reboot device, device can
> not detect sim card.
>     This only can be recovered by restarting b2g, but device can not detect
> sim again after full reboot. 
It is strange for this result. What is difference between restarting b2g and rebooting device.
It is supposed to be same for B2G.

> 2). ((Settings --> Cell&Data --> Network Operator --> Automatic selection))
>     Switching "Automatic selection" to off, and choose some network and try
> to connect it.
>     After connection is failed, switching "Automatic selection" back to on.
> But device doesn't 
>     automatically connect to network.
>     More like comment #0 and also the bug title.
Do you mean that RIL have sent "automatic selection command" to RILD/Modem but RILD/Modem doesn't act rightly?

Comment 15

[Edgar Chen [:edgar]]

(In reply to Ken Chang[:ken] from comment #14)
> (In reply to Edgar Chen [:edgar][:echen] from comment #13)
> > I think we have two different bug here:
> > 1). ((Settings --> Cell&Data --> Network Operator --> Network Type))
> >     Switching "Network Type" to "Automatic" then reboot device, device can
> > not detect sim card.
> >     This only can be recovered by restarting b2g, but device can not detect
> > sim again after full reboot. 
> It is strange for this result. What is difference between restarting b2g and
> rebooting device.
> It is supposed to be same for B2G.

I am still trying to figure out why restarting b2g helps.
BTW, I found it also can be recovered by airplane mode off/on.

Comment 16

[Edgar Chen [:edgar]]

Change the title for tracking the issue of ((Settings --> Cell&Data --> Network Operator --> Automatic selection)) [1]

[1] Please see comment #13.

Comment 17

[Edgar Chen [:edgar]]

Attachment: buri_network_selection.txt

Log for device doesn't connect to network automatically after switching from "manual network" to "automatic".

Comment 18

[Edgar Chen [:edgar]]

(In reply to Edgar Chen [:edgar][:echen] from comment #17)
> Created attachment 8387496 [details]
> buri_network_selection.txt
> 
> Log for device doesn't connect to network automatically after switching from
> "manual network" to "automatic".

(In reply to Edgar Chen [:edgar][:echen] from comment #17)
> Created attachment 8387496 [details]
> buri_network_selection.txt
> 
> Log for device doesn't connect to network automatically after switching from
> "manual network" to "automatic".

Gecko doesn't allow to switch to automatic selection if the previous selection request is still under processing. In such case, api caller will get an Exception.

====
03-07 18:39:07.509   501   501 E GeckoConsole: [JavaScript Error: "[Exception... "'Error: Already selecting a network: [xpconnect wrapped nsIDOMMozMobileNetworkInfo]' when calling method: [nsIMobileConnectionProvider::selectNetworkAutomatically]"  nsresult: "0x8057001c (NS_ERROR_XPC_JS_THREW_JS_OBJECT)"  location: "JS frame :: app://settings.gaiamobile.org/js/carrier.js :: cs_initOperatorSelector/opAutoSelectInput.onchange :: line 371"  data: no]" {file: "app://settings.gaiamobile.org/js/carrier.js" line: 371}]
====

I think gaia may need to handle this kinds of situation.

Comment 19

[Edgar Chen [:edgar]]

(In reply to Edgar Chen [:edgar][:echen] from comment #18)
> (In reply to Edgar Chen [:edgar][:echen] from comment #17)
> > Created attachment 8387496 [details]
> > buri_network_selection.txt
> > 
> > Log for device doesn't connect to network automatically after switching from
> > "manual network" to "automatic".
> 
> Gecko doesn't allow to switch to automatic selection if the previous
> selection request is still under processing. In such case, api caller will
> get an Exception.
> 
> ====
> 03-07 18:39:07.509   501   501 E GeckoConsole: [JavaScript Error:
> "[Exception... "'Error: Already selecting a network: [xpconnect wrapped
> nsIDOMMozMobileNetworkInfo]' when calling method:
> [nsIMobileConnectionProvider::selectNetworkAutomatically]"  nsresult:
> "0x8057001c (NS_ERROR_XPC_JS_THREW_JS_OBJECT)"  location: "JS frame ::
> app://settings.gaiamobile.org/js/carrier.js ::
> cs_initOperatorSelector/opAutoSelectInput.onchange :: line 371"  data: no]"
> {file: "app://settings.gaiamobile.org/js/carrier.js" line: 371}]
> ====
> 
> I think gaia may need to handle this kinds of situation.

Hi Arthur, may I have your opinion here? Thank you.

Comment 20

[Jason Smith [:jsmith]]

Ivan - Since we're prioritizing quality work for 1.4, any chance you can add this to the todo list for 1.4 stability? Rel man & I thought this wouldn't block the release since we shipped 1.1 with the bug, but this is something that would be a really good idea to fix, as it's currently a foot gun that risks blocking access to the SIM card.

Comment 21

[Jason Smith [:jsmith]]

(In reply to Jason Smith [:jsmith] from comment #20)
> Ivan - Since we're prioritizing quality work for 1.4, any chance you can add
> this to the todo list for 1.4 stability? Rel man & I thought this wouldn't
> block the release since we shipped 1.1 with the bug, but this is something
> that would be a really good idea to fix, as it's currently a foot gun that
> risks blocking access to the SIM card.

Note - this bug & bug 969079 would be good candidates for quality work.

Comment 22

[Arthur Chen [:arthurcc][inactive after 6/30]]

(In reply to Edgar Chen [:edgar][:echen] from comment #19)
> (In reply to Edgar Chen [:edgar][:echen] from comment #18)
> > (In reply to Edgar Chen [:edgar][:echen] from comment #17)
> > > Created attachment 8387496 [details]
> > > buri_network_selection.txt
> > > 
> > > Log for device doesn't connect to network automatically after switching from
> > > "manual network" to "automatic".
> > 
> > Gecko doesn't allow to switch to automatic selection if the previous
> > selection request is still under processing. In such case, api caller will
> > get an Exception.
> > 
> > ====
> > 03-07 18:39:07.509   501   501 E GeckoConsole: [JavaScript Error:
> > "[Exception... "'Error: Already selecting a network: [xpconnect wrapped
> > nsIDOMMozMobileNetworkInfo]' when calling method:
> > [nsIMobileConnectionProvider::selectNetworkAutomatically]"  nsresult:
> > "0x8057001c (NS_ERROR_XPC_JS_THREW_JS_OBJECT)"  location: "JS frame ::
> > app://settings.gaiamobile.org/js/carrier.js ::
> > cs_initOperatorSelector/opAutoSelectInput.onchange :: line 371"  data: no]"
> > {file: "app://settings.gaiamobile.org/js/carrier.js" line: 371}]
> > ====
> > 
> > I think gaia may need to handle this kinds of situation.
> 
> Hi Arthur, may I have your opinion here? Thank you.

As you suggested, I think gaia should handle this.

Comment 23

[Ivan Tsay (:ITsay)]

Hi Jason,

I've talked to Arthur and he will look into this bug to see if the gaia work is enough to fix this issue based on comment 22. Target to fix this one in 1.4 stability.