Closed
Bug 1017426
Opened 10 years ago
Closed 7 years ago
[Sora][Wi-Fi]DUT will disconnect the AP auto
Categories
(Firefox OS Graveyard :: Wifi, defect, P1)
Firefox OS Graveyard
Wifi
Tracking
(tracking-b2g:backlog)
RESOLVED
INVALID
tracking-b2g | backlog |
People
(Reporter: sync-1, Unassigned)
Details
(Whiteboard: [closeme 6/7/2014])
Attachments
(6 files)
Mozilla build ID:20140422024003 Created an attachment (id=720980) refer the attachment DEFECT DESCRIPTION: DUT will disconnect the AP auto .Then it will connect the same AP auto. REPRODUCING PROCEDURES: 1,connect the AP -> surf the internet ->DUT will disconnect the AP auto .Then it will connect the same AP auto.-> KO
We find that gecko issue "disconnect" and "reassociate" command to supplicant. Can you check whether it is ok?
When can't get dhcp info once, gecko will issue "disconnect" and "reassociate", Is this necessary?
Comment 10•10 years ago
|
||
I'm confused on the STR here. Can you rephrase the STR here? I don't understand how to test this.
Flags: needinfo?(sync-1)
(In reply to Jason Smith [:jsmith] from comment #10) > I'm confused on the STR here. Can you rephrase the STR here? I don't > understand how to test this. I believe the STR is as following: 1. Connect to some Wifi AP 2. Surf the net for a while 3. Suddenly the Wifi will disconnect from the AP 4. And it will connect to that AP again after a while. Could we have QA to test this issue? Suggest to surf the net for at least 10 minutes. Thanks
Flags: needinfo?(sync-1)
Comment 13•10 years ago
|
||
(In reply to Wang Rong from comment #8) > When can't get dhcp info once, gecko will issue "disconnect" and > "reassociate", Is this necessary? There is a retry count when dhcp info is not available. http://dxr.mozilla.org/mozilla-central/source/dom/wifi/WifiWorker.js?from=wifiworker.js&case=true#631
Comment 14•10 years ago
|
||
Please turn on wifi debug log in settings/developer/Wi-Fi output in ADB when reproducing the problem.
Comment 15•10 years ago
|
||
(In reply to Vincent Chang[:vchang] from comment #13) Yes, I noticed that. do we must disconnect and reassociate when dhcp info is not available? And can we get the reason why dhcp info is not available in the log?
Comment 16•10 years ago
|
||
(In reply to Vance Chen [:vchen][vchen@mozilla.com] from comment #11) > I believe the STR is as following: > > 1. Connect to some Wifi AP > 2. Surf the net for a while > 3. Suddenly the Wifi will disconnect from the AP > 4. And it will connect to that AP again after a while. > > Could we have QA to test this issue? Suggest to surf the net for at least 10 > minutes. Followed steps and surfed the net (news.google.com and maps.google.com) for 15 minutes and did not encounter any wifi disconnection. Tested on: Device: Buri MOZ BuildID: 20140530024008 Gaia: 5bd226b03a2d63dfe9df204f7c0afb9984e8fd42 Gecko: 57cd741e4d0b Version: 28.0 Firmware Version: v1.2-device.cfg User Agent: Mozilla/5.0 (Mobile; rv28.0) Gecko/28.0 Firefox/28.0
Keywords: qawanted
Comment 17•10 years ago
|
||
Can't block on something we can't reproduce.
blocking-b2g: 1.3? → backlog
Whiteboard: [closeme 6/7/2014]
Assignee | ||
Updated•9 years ago
|
blocking-b2g: backlog → ---
tracking-b2g:
--- → backlog
Comment 18•8 years ago
|
||
link all Fire C (codename: Sora) bugs to a meta one.
Updated•7 years ago
|
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•