819947 - No WiFi networks detected during FTU experience

Status: RESOLVED FIXED

(Firefox OS Graveyard :: Wifi, defect, P1)

Description

[Gervase Markham [:gerv]]

Attachment: adb logcat output

New Unagi phone. Going through first-time user experience, no wifi networks detected. WiFi Analyser on my personal Android phone detects 3, although only one (mine) at high power.

logcat attached. There's clearly 2 wifi-related errors in it, but they aren't very informative. Let me know what else I can do.

WiFi network is 802.11g+n, coming out of one of these:
http://www.billion.com/product/wireless/BiPAC-7800N-11n-ADSL2-Broadband-Firewall-Router-Gigabit.html . I tried turning off wireless security, and turning on 802.11b, but neither helped.

I'll let you know if it detects them once the phone is up and running properly.

Gerv

Comment 1

[Gervase Markham [:gerv]]

Yes, once I'm through the first-time experience, the phone can see all local WiFi networks and connect to mine.

Gerv

Comment 2

[Doug Turner (:dougt)]

blake, can you look at the log and determine how bad this problem is?

Comment 3

[Vincent Chang[:vchang][changyihsin]]

Can you turn on wifi debug message located in 
Settings/Device information/More Information/Developer/Wi-Fi output in adb and help to reproduce the problem ?

Comment 4

[Gervase Markham [:gerv]]

Attachment: More detailed log

I turned on the setting and re-ran the FTU app (using the button in the Developer options), but I could still see my wireless networks. So I rebooted the phone and re-ran the FTU app, and the problem reproduced itself. However, the log seems to be no more detailed in this regard; the error is the same. (The wifi debug setting is still on.)

The 2 errors we saw before appear as a pair several times towards the end of the log because I pressed the "Refresh" button on the Wifi page a couple of times.

Gerv

Comment 5

[Blake Kaplan (:mrbkap) (inactive)]

It's hard to tell with the information given here. I'm a little surprised that we're seeing the error message twice (do we have two instances of the ftu app running?) and in general I think that callers of getNetworks need to retry if it fails. That being said, I filed bug 820648 with a patch that should help shed at least a little light on things.

One possibility that's seems reasonable to me is that we're not actually starting wifi (otherwise, I'd expect to see at least a couple of random messages coming from wpa_supplicant in the log). I'm not sure why that would happen though, unless we're somehow running the ftu app with a bad settings database or something.

Comment 6

[Gervase Markham [:gerv]]

This was a standard Unagi phone flashed by Desktop and, the first time I saw the bug at least, it was the very first "first run". So I would hope we don't have two instances of the FTU app running! And it would be odd if we had a bad settings database.

I will certainly retest when that patch lands.

Gerv

Comment 7

[Andrew Overholt [:overholt]]

(In reply to Gervase Markham [:gerv] from comment #6)
> I will certainly retest when that patch lands.

Thanks, Gerv.  Please put info here once you've got it.

This is a blocker because we need wifi to be rock solid for v1.

Comment 8

[Blake Kaplan (:mrbkap) (inactive)]

Gerv, if you're on nightly, you should see this in the next update that you do.

Comment 9

[[:Cww]]

I've flashed a few phones and some people have come back. Here's what I now know:

1) It seems to be worse if people wait a while before going through the FTE (So we may be turning off wifi to save power?)

2) If you go through all the FTE anyway, check settings, you find that WiFi is OFF. (as in the switch is off).  Turning it back on makes wifi work fine.

3) Re-flashing the phone after turning on wifi makes it work as well (but that could be a result of not waiting a long time -- see 1.

Comment 10

[Andrew Overholt [:overholt]]

(In reply to [:Cww] from comment #9)
> I've flashed a few phones and some people have come back. Here's what I now
> know:
> 
> 1) It seems to be worse if people wait a while before going through the FTE
> (So we may be turning off wifi to save power?)

Do we, Blake?

Comment 12

[Gervase Markham [:gerv]]

Attachment: Another, more recent log

I've managed to reproduce this.

- Reflashed phone
- Went through FTU; problem manifested. Did not do anything with data or wifi.
- Went to Settings and turned on "Wifi in ADB"
- Used button in settings to rerun FTU app
- Reproduced problem

See attached log. However, it doesn't seem much better than the previous one :-|

I _think_ my build has the fixes Blake did. I built it very recently. However, the build date and the git commit date displayed in the settings app are variant, which is a bit weird. I will try pulling and building again.

Gerv

Comment 13

[Gervase Markham [:gerv]]

I think this may be simply because the FTU app is not correctly turning on the Wifi.

I flashed and went through FTU, but failed to reproduce. (I saw two networks.) I went into Settings, where the summary screen claimed Wifi was off, but going into the Wifi settings suggested it was on. So I turned it off. I then reran the FTU app. It couldn't see the networks. I _assume_ FTU turns on Wifi if it's off, and has, or should have, permissions to do so. Is that not so? If so, it's failing to do it right.

Gerv

Comment 15

[Gervase Markham [:gerv]]

Attachment: Reproduction of problem with extra WiFi logging

Here's a log where I've finally got this to work, with the extra Wifi logging mrbkap asked for. 

However, pressing Refresh _did_ cause the network list to come up, so I can't guarantee it's exactly the same problem. The log includes that Refresh at the end, so don't be fooled. See line 2103.

Gerv

Comment 16

[Gervase Markham [:gerv]]

I've had a few more goes at this, and I still can't get it to break 'permanently' - i.e. at the moment, the list _does_ come up blank first time, but Refresh brings up the correct networks. As in the most recently-attached log.

Gerv

Comment 17

[Marcia Knous [:marcia]]

I saw this today during smoketesting (20121226 build), and it happened when I invoked FTU using the developer panel. In my case the refresh button didn't work. Will do a little more testing around this today.

Comment 18

[Blake Kaplan (:mrbkap) (inactive)]

Attachment: Movement...

This pull request fixes at least one problem that Gerv noticed: FTU doesn't turn wifi on when it's launched. It shouldn't fix the problem where the refresh button never works, though it adds logging that might help shed light on what's going on for that case. I'll write another patch next week to fix the case where we race turning on wifi with doing a scan (which Gerv has definitely seen: that's the case where the initial list is empty but hitting the refresh button works).

Hopefully once this patch is merged, someone will hit this bug and we'll be able to see what's going on. Also note that it's very possible that this is simply a symptom of bug 809663.

Comment 19

[Francisco Jordano [:arcturus] [:francisco]]

:fernando.campo are you working on a similar bug?

Can you review Blake patch?

Comment 20

[Francisco Jordano [:arcturus] [:francisco]]

Comment on attachment 696411 [details]
Movement...

Asking fcampo for review as he is working on FTU and I'm on PTO till the 7th of Jan.

Thanks.

Comment 21

[Jonas Sicking (:sicking) No longer reading bugmail consistently]

Is there a reason not to re-scan on a timer, that gives the best chance of detecting networks if the user is moving around, or just turned on the wifi, or the on-device wifi just got started.

Comment 22

[Blake Kaplan (:mrbkap) (inactive)]

(In reply to Jonas Sicking (:sicking) from comment #21)
> Is there a reason not to re-scan on a timer, that gives the best chance of
> detecting networks if the user is moving around, or just turned on the wifi,
> or the on-device wifi just got started.

We apparently decided not to do that for the settings page and I didn't want to be inconsistent.

Comment 23

[Vivien Nicolas (:vingtetun) (:21) - (NOT reading bugmails, needinfo? please)]

Comment on attachment 696411 [details]
Movement...

Let's land that ASAP in order to have more infos about the real issue.

Comment 24

[Vivien Nicolas (:vingtetun) (:21) - (NOT reading bugmails, needinfo? please)]

https://github.com/mozilla-b2g/gaia/commit/59804bdde55a04a062623aeedbe6f907599cebe0

Comment 25

[Blake Kaplan (:mrbkap) (inactive)]

Hey Gerv and Marcia,

Now that this patch has landed, if you reproduce the problem where clicking 'refresh' never displays any networks (assuming that there should be networks in range) the logcat should now contain useful info.

Comment 26

[Johnny Stenback (:jst)]

Given that the known issues are now fixed here, we're marking this fixed now. If we find more problems relating to wifi in FTU, we'll file new bugs for that.