1152991 - Wi-Fi/wifi not automatically connecting to network after reboot

Status: RESOLVED DUPLICATE of bug 1167466

(Firefox OS Graveyard :: Wifi, defect)

Description

[Sebastian Hengst [:aryx] (needinfo me if it's about an intermittent or backout)]

B2G 2.2 20150409002503 on Flame (v18D base image)

The phone doesn't automatically connect to the wi-fi network after a reboot but it does if it is being charged over USB during the reboot.

The network doesn't broadcast its SSID.

Settings > Wi-Fi lists the network and says that it's "Not in range", but tapping on it will connect to it. Wi-Fi sleep mode is disabled.

Comment 1

[bhavana bajaj [:bajaj]]

Eric, can you check this or request someone from marigold to help here?

Comment 2

[Eric Chang [:ericcc] [:echang]]

FWD to Gerry

Comment 3

[Gerry Chang [:gchang]]

Hi Archaeopteryx,
I can't recreate this issue on 20150409002503 & latest(20150412002502) build. 
Can you provide detailed STR on this?

Comment 4

[Sebastian Hengst [:aryx] (needinfo me if it's about an intermittent or backout)]

My STR on Flame 2.2 20150414002504 (v18D base image):
0. Reset the device.
1. Walk through the tutorial, ignore the Wi-Fi setup (joining hidden Wi-Fi doesn't work there as far as I know, see bug 935487).
2. Go to Settings > Wi-Fi.
3. Tap on 'Manage Networks'.
4. Tap on 'Join hidden network'.
5. Type in the SSID and the password of your hidden Wi-Fi.
Actual & expected result: Wi-Fi connects (status indicator and connections work).
6. Restart the device.
7. I type in my SIM PIN.

Actual result:
No Wi-Fi status indicator, connections fail (if you try to open a page in the browser which you loaded earlier, it will be loaded from cache; checking mails in the E-Mail app will fail).
Expected result:
Automatic connection to Wi-Fi network.

8. Go to Settings > Wi-Fi.
Actual result:
Wi-Fi is listed and has status 'Not in range'.
9. Tap on Wi-Fi.
Actual result:
Wi-Fi connection established.

Annotations: The device is set to German as UI language and I also set some other settings (like no sound/vibration when using the keyboard).

Comment 5

[Gerry Chang [:gchang]]

Hi Archaeopteryx,
I still can't recreate this issue on your build(20150414002504).
I was wondering if it has something to do with AP.
I use my personal phone as portable AP and hide the SSID.
Can you try anther AP?

Comment 6

[Vincent Chang[:vchang][changyihsin]]

Removing nomination since this can no longer be reproduced.
waiting for reporter's response to identify if it's related to AP.

Comment 7

[Sebastian Hengst [:aryx] (needinfo me if it's about an intermittent or backout)]

After switching between 2.2 and 3.0 several times, I could only reproduce once (after flashing a 3.0 version). Closing as WORKSFORME.

Comment 8

[Sebastian Hengst [:aryx] (needinfo me if it's about an intermittent or backout)]

Reopening because after flashing from 2.2 2015040900 to 20150420162501, the issue is back. I have no steps to trigger the issue. But once I see it, it can be reproduced more often than before. Letting the device idle after the restart seems to increase the chances of reproducibility.

Comment 9

[Henry Chang [:hchang]]

Let's see if urandom fixes all the EAP test case failure.

https://treeherder.mozilla.org/#/jobs?repo=try&revision=9be9804afe53

Comment 10

[Henry Chang [:hchang]]

(In reply to Henry Chang [:henry] from comment #9)
> Let's see if urandom fixes all the EAP test case failure.
> 
> https://treeherder.mozilla.org/#/jobs?repo=try&revision=9be9804afe53

Sorry I posted on wrong bug...

Comment 11

[Amy Chung [:Amy]]

I have duplicated this issue, and I found the situations as below :
1. wpa_supplicant already associated, but flame doesn't get any Wifi connection.
2. Used list_networks command on flame, found the wifi connection info exists but flag is disable.
3. I used enable_network command then the wifi connection successfully on flame.

Comment 12

[Henry Chang [:hchang]]

It seems the patch for Bug 1167466 also resolves this issue.

Comment 13

[Amy Chung [:Amy]]

I confirmed the wifi init process, and found it's fail reason is dhcp timed out.
To trace code and find wifi remove network before dhcp timed out,
and finally the root cause is dhcp process running more than once time.
The situation also occurs on https://bugzilla.mozilla.org/show_bug.cgi?id=1167466

Comment 14

[Amy Chung [:Amy]]

RESOLVED DUPLICATE of bug 1167466