1152472 - Disabling Airplane mode does not reconnect wifi to a previously connected state

Status: RESOLVED WORKSFORME

(Firefox OS Graveyard :: Vendcom, defect)

Description

[Bhavna Sharma]

Steps to reproduce
1. Turn Wifi ON
2. Connect it to a access point and make sure it connects and there is connectivity available.
3. Turn airplane mode ON
4. Wait a few seconds and turn airplane mode back to OFF

What we see:
Wifi appears to turn back ON in the notification UI, and we get the wifi.enabled notification. But it does not connect back to the previously connected access point. 

What is expected:
Wifi must reconnect back to a previous access point that it is connected to.

Note: This issue is seen only when toggling airplane mode from the notification UI. If it is done from the Settings UI , it works fine.

Comment 1

[Mike Lee [:mlee]]

Tim,

Please have someone on your team look into this.

Thanks,
Mike

Comment 2

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

Set a tracking flag.

Comment 3

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

EJ, could you help check this issue? Thanks.

Comment 4

[EJ Chen [:eragonj][:小龍哥][Contributor mode on](inactive)]

I can try to see what's going on here, but can you provide your device information, regression rate and detailed STR with screencast ? 

And also, if possible, can you set a regression-window flag ?

Thanks.

Comment 5

[Bhavna Sharma]

Not sure if device information matters here, this is reproduced on v2.2

I do not have the regression window of this issue, not sure when it stopped working, but it is a basic OS feature and must work.

Comment 6

[EJ Chen [:eragonj][:小龍哥][Contributor mode on](inactive)]

Ahh, the reason why I tried to ask for more information is because that would help me make sure when / where the problem would happen easily because I can't reproduce that on my Flame with latest 2.2 Build.

So, can you provide needed information ? I thought this is our formal working flow, isn't it ?

At the same time, I would still try to dig out the problem if possible. Thanks.

Comment 7

[howie [:howie]]

qawanted to check if this is regression, if so, please help to find a regression window, thanks.

Comment 8

[Bhavna Sharma]

Sure i'll try, though i am not sure if this is a regression or not.

The issue is reproducible only from the notification window, not from the settings menu. Are you trying it from the notification screen ? After turning the airplane mode to ON, the wifi icon turns back to ON, but there there is actually no wifi connection.

Comment 9

[Jayme Mercado [:JMercado] (Inactive 3/4/2016)]

I spent 30 minutes each on both 2.2 and 3.0 trying to reproduce this issue with no luck.  Leaving the tag so someone else can try.  If the reporter can give any more information to help with reproduction that would be great.

Environmental Variables:
Device: Flame 3.0
BuildID: 20150409085330
Gaia: eaf69e651e19b98c096f8e63b9829fb31df50927
Gecko: dd32e3ff3717
Version: 40.0a1 (3.0) 
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:40.0) Gecko/40.0 Firefox/40.0

Environmental Variables:
Device: Flame 2.2
BuildID: 20150409102936
Gaia: 0bfb78bb850cd2f47e97a6107d2ace5d21efbac3
Gecko: cb3537ce1f8e
Version: 37.0 (2.2) 
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:37.0) Gecko/37.0 Firefox/37.0

Comment 10

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

I tried this at least 30 times on Flame 2.2 and was not able to reproduce this issue.

The phone always reconnected to the previously connected WiFi connection without issue.

Environmental Variables:
Device: Flame 2.2 (Full Flash)(KK)(319mb)
BuildID: 20150410002502
Gaia: df0e04acad7c8c993f6ffe07b0ccb0ec20ee50bb
Gecko: 091b1cc1240b
Gonk: ebad7da532429a6f5efadc00bf6ad8a41288a429
Version: 37.0 (2.2) 
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:37.0) Gecko/37.0 Firefox/37.0

Leaving qawanted for someone else to try.

Comment 11

[bhavana bajaj [:bajaj]]

Thanks, guys.

EJ/Bhavna, I guess QA here at mozilla can't help here, so I am removing the tag. Seems to be device specific.

Comment 12

[Peter Bylenga [:PBylenga]]

Adding qawhiteboard tag qaexclude to remove this one from our queries as we can't reproduce on our devices.  Leaving the window wanted tag for someone with the device to try to find the window (if possible).

Comment 13

[EJ Chen [:eragonj][:小龍哥][Contributor mode on](inactive)]

Ok thanks all for clarifying this.

It seems that this bug is device specific (not sure whether related codebases were changed or not), if there is any missing prerequisites or something, feel free to add them here and ping us.

For now, I'll de-assign myself first and focus on other bugs. THanks

Comment 14

[Ken Chang[:kenkai]]

A device-specific issue, changing component.

Comment 15

[bhavana bajaj [:bajaj]]

I am removing the nom for now as I had a discussion with Inder from CAF on this and since it led to being a device specific issue, he mentioned he's going to check on his side.

Comment 16

[shawn ku [:sku]]

Hi Bhavna:
 We cannot repo. this issue by using nexus5-L, could you please try to provide more detail STR or log?

Comment 17

[shawn ku [:sku]]

NI? seinlin to aware this issue.

Comment 18

[Bhavna Sharma]

I am not able to reproduce the issue on flame.

Comment 19

[Kai-Zhen Li [:seinlin][:kli]]

It is more likely a device specific issue, please ni me again if I can help something.