Closed Bug 943162 Opened 11 years ago Closed 11 years ago

Airplane mode cannot be disabled

Categories

(Firefox OS Graveyard :: Gaia, defect)

x86_64
Linux
defect
Not set
normal

Tracking

(blocking-b2g:-)

RESOLVED WORKSFORME
blocking-b2g -

People

(Reporter: kaze, Assigned: kaze)

References

Details

(Keywords: regression)

I don’t have reliable STR yet. Symptoms:
 • the lockscreen and the statusbar say that Airplane mode is activated — though I’m quite sure I did not enable it;
 • Airplane mode cannot be disabled — neither by the statusbar nor by the Settings app;
 • in the Settings app, the label below “Cellular & Data” is “???” and we get the following error in the console log:

E/GeckoConsole(  403): Content JS WARN at app://settings.gaiamobile.org/js/carrier.js:736 in cr_carrierSettings/initRoamingPreferenceSelector/req.onerror: carrier: GenericFailure

I suspect this is a rather recent regression (~ a couple days). Investigating.
Assignee: nobody → kaze
blocking-b2g: --- → koi?
Putting steps-wanted to see if we can find reliable STR.
(In reply to Fabien Cazenave [:kaze] from comment #0)
> I don’t have reliable STR yet. Symptoms:
>  • the lockscreen and the statusbar say that Airplane mode is activated —
> though I’m quite sure I did not enable it;
>  • Airplane mode cannot be disabled — neither by the statusbar nor by the
> Settings app;
>  • in the Settings app, the label below “Cellular & Data” is “???” and we
> get the following error in the console log:
> 
> E/GeckoConsole(  403): Content JS WARN at
> app://settings.gaiamobile.org/js/carrier.js:736 in
> cr_carrierSettings/initRoamingPreferenceSelector/req.onerror: carrier:
> GenericFailure
> 
> I suspect this is a rather recent regression (~ a couple days).
> Investigating.

On fugu, I see this every time after rebooting; however, I am able to turn off airplane mode.
Hi Kaze, can you check if bug 943193 steps are what you found? I just want to make sure if they are the same bug or not.
Flags: needinfo?(kaze)
(In reply to Enpei from comment #3)
> Hi Kaze, can you check if bug 943193 steps are what you found? I just want
> to make sure if they are the same bug or not.

Another case I met is that when there is only 1 SIM in device, after reboot, I cannot disable airplane mode for couple seconds. So please let me know which one is your case, thanks.
I’m not sure, but I think I have the opposite behavior: the problem disappears when I reboot the device — at least that’s what happened last time I tried. As I’m investigating at the moment, I do my best *not* to reboot the device. Sorry. :-/

On a side note, I think the device is not really in Airplane mode; the RIL is just disabled — hence the “Airplane mode” label in the Settings app. The Settings app also displays a “SIM card not ready” message.
Flags: needinfo?(kaze)
Forgot to say: this happens on my Unagi, latest Gaia & Gecko.
Hi, 

Is this happening with MozRIL or ComRIL?

If confirmed, this is clearly a cert blocker. 

Thks!
David
(In reply to Fabien Cazenave [:kaze] from comment #6)
> Forgot to say: this happens on my Unagi, latest Gaia & Gecko.

Hello Fabien,

What SIM and carrier are you using?

Thanks.
Please help with better STRs.
koi+ for likely cert blocker. In triage we understand that it is difficult to provide STRs and airplane mode v/snot is not easily indicated.
blocking-b2g: koi? → koi+
Fabien, please see comment 8.
Flags: needinfo?(kaze)
See Also: → 944202
QA Contact: sparsons
I cannot repro this on the Buri 1.2 Build ID: 20131202004001

Gaia   075e60c878b0eca68fba9e00bc85cb6eac03578a
SourceStamp 14868788d50e
BuildID 20131202004001
Version 26.0

Could this possibly be Keon specific? Could 944202 be a dupe of this bug?
(In reply to Sarah Parsons from comment #12)
> I cannot repro this on the Buri 1.2 Build ID: 20131202004001
> 
> Gaia   075e60c878b0eca68fba9e00bc85cb6eac03578a
> SourceStamp 14868788d50e
> BuildID 20131202004001
> Version 26.0
> 
> Could this possibly be Keon specific? Could 944202 be a dupe of this bug?

Kaze - What device are you using to reproduce this?
I had this bug on my beloved Unagi.

I could reproduce it last week in Taipei and Amsterdam, but I struggle to reproduce this bug now that I’m back in France. It might be related to a roaming issue… which would explain why José-Manuel had it in Taipei, too.
Flags: needinfo?(kaze)
Kaze,

What are the proposed next steps? What are the devices under investigation?
Flags: needinfo?(kaze)
I don't think we'll be able to block on this unless we can get clear confirmation of this reproducing on a production device.
blocking-b2g: koi+ → koi?
Removing steps-wanted per comment 12 - we've made our attempt at reproduction, but failed to reproduce it.
Keywords: steps-wanted
Minus till reproducibility and better STR
blocking-b2g: koi? → -
I can’t reproduce this bug any more. I’m puzzled because José-Manuel saw it too, but I guess it’s been a coincidence…

Closing as WFM. Sorry for the noise.
Status: NEW → RESOLVED
Closed: 11 years ago
Flags: needinfo?(kaze)
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.