Closed Bug 784240 Opened 12 years ago Closed 12 years ago

Wifi won't scan after ./flash.sh until rebooting after enabling wifi

Categories

(Firefox OS Graveyard :: General, defect)

Product:
Firefox OS Graveyard
Component:
General
Platform:
x86_64
Linux
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(blocking-basecamp:+)

Status:
RESOLVED FIXED
Project Flags:
blocking-basecamp +

People

(Reporter: dhylands, Assigned: mrbkap)

Details

I'm using a debug build of otoro-ics

If I perform
    ./build.sh && ./flash.sh
then when I go into settings and enable Wifi, it never sees any APs. I work from home - I have 3 APs, I can normally see some of the neighbors APs as well)

If I remove /data/misc/wifi/wpa_supplicant.conf and reboot, then when I start wifi I'm able to see all of the networks fine.
blocking-basecamp: --- → ?
Assignee: nobody → mrbkap
blocking-basecamp: ? → +
So after some more experimentation, removing wpa_supplicant.conf isn't required.

This is the smallest set required to get wifi to work (for me)

./flash.sh
Go into settings, (Wifi says disabled), enable wifi, no APs are shown.
Restart phone (either using adb reboot or Restart from long press on power button)
Go into settings (Wifi says offline), press Wifi, all APs are shown.
If I then disable wifi and reboot the phone, and go into settings again (while Wifi says disabled), then enabling Wifi scans properly.

So it seems that a reboot is required after enabling wifi the first time after a flash before a scan will work.
This seems to be recorded in gaia as https://github.com/mozilla-b2g/gaia/issues/3052. Since it isn't clear yet whether this is a gecko problem or a gaia problem, we should probably leave both open until its resolved.
Summary: Wifi won't scan unless I remove wpa_supplicant.conf → Wifi won't scan after ./flash.sh until rebooting after enabling wifi
I have actually seen it successfully scan, but only after waiting a few minutes.

Perhaps relatedly, my phone doesn't register on the network for about the same amount of time, and it's only after I noticed I was registered on the network that wifi scanning succeeded.
Blake suggested trying on-off-on and  this in fact seems to make the scan work (no reboot required).

Blake thought that the problem might be related to the initial settings value, so I pointed him to gaia/build/settings.js
This was fixed on the gaia side. It turned out to be a packaging problem.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.