Closed
Bug 804466
Opened 13 years ago
Closed 12 years ago
Phone does not auto-search for new networks at a new location properly if previously connected to a now-out-of-range wifi network
Categories
(Firefox OS Graveyard :: Gaia, defect, P3)
Tracking
(blocking-basecamp:+)
RESOLVED
DUPLICATE
of bug 796640
blocking-basecamp | + |
People
(Reporter: gkw, Unassigned)
Details
(Keywords: b2g-testdriver, unagi)
1. Turn on wifi.
2. Connect to a network (e.g. Mozilla-G).
3. Check that you can connect to internet successfully.
4. Walk out of the wifi, such that you are out of range. i.e. go home. (and maybe also go to Home screen)
5. At home, with working wifi setup, unlock phone and go to Settings app.
6. Go to Wifi.
7. Wifi says it's on, but no networks are found.
Workaround:
Disable wifi, then re-enable it again.
Home network (2.4Ghz) is now found, and with password (which is entered successfully), connects successfully too.
===
My Git commit info currently shows:
2012-10-17 12:16:24
e3efbd0411218762cf9a62278bf58ee513ff331f
Also, seeing my comments in https://b2gtestdrivers.allizom.org/comments_table - my build ID currently is:
20121018092134
![]() |
Reporter | |
Updated•12 years ago
|
OS: Mac OS X → Gonk (Firefox OS)
![]() |
Reporter | |
Updated•12 years ago
|
blocking-basecamp: --- → ?
Comment 1•12 years ago
|
||
Tony, can you verify if this is resolved? Thank you.
blocking-basecamp: ? → +
Keywords: qawanted
Comment 2•12 years ago
|
||
Tony, verify it on the master build as opposed to dogfood/nightly build. Thanks.
![]() |
Reporter | |
Updated•12 years ago
|
Hardware: x86 → ARM
Updated•12 years ago
|
blocking-basecamp: + → ?
Hardware: ARM → x86
Updated•12 years ago
|
blocking-basecamp: ? → +
Priority: -- → P3
Whiteboard: DUPEME
I saw this just today on the otoro device. I believe this may be a dup as well.
Updated•12 years ago
|
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•