Closed Bug 1021671 Opened 11 years ago Closed 7 years ago

[Flame][V1.4][Wifi]DUT cannot connect to network successfully via WPS Button connection

Categories

(Firefox OS Graveyard :: Wifi, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(b2g-v2.1 affected, b2g-v2.2 affected)

RESOLVED WONTFIX
2.0 S6 (18july)
Tracking Status
b2g-v2.1 --- affected
b2g-v2.2 --- affected

People

(Reporter: panda67231, Assigned: vchang, NeedInfo)

Details

(Whiteboard: [p=2], bamboo, permafail)

Attachments

(6 files)

[1.Description]: DUT cannot connect to network successfully when you connect to a networkvia WPS Button connection way. Attach figure:[WPS time out.png&WPS button connection.png] Attach video:[WPS button connection.mp4 ] Attach log:[logcat0223.txt&bugreport.0223.txt] Occurrence time:02:23-02:25pm [2.Testing Steps]: Precondition: AP: NETGEAR WNDR3700v3 Security mode: wpa-psk/wpa2-psk SSID:Firefox Password:1234567890 1.Launch "Settings"->tap "Wi-Fi"->tap "Connect with WPS" 2.Check "Button connectiong"->tap "ok" and Click WPS button of AP **DUT always displays" WPS in progress..." and can not connect to network successfully 3.Go to setting list **"Wi-Fi" displays "WPS time out" [3.Expected Result]: DUT should connect to network successfully via WPS Button connection [4.Actual Result]: 2.DUT always displays" WPS in progress..." and can not connect to network successfully [5.Reproduction build]: Gaia 7709936aeb21859d1607dbd038489493803bb085 Gecko https://hg.mozilla.org/releases/mozilla-b2g30_v1_4/rev/5bf038fae0f1 BuildID 20140522160202 Version 30.0 [6.Reproduction Frequency]: Always Recurrence,3/3
Attached image WPS time out.png
Attached file bugreport0223.txt
Attached file logcat0223.txt
Status: UNCONFIRMED → NEW
Ever confirmed: true
Take the bug and try to reproduce the problem first.
Assignee: nobody → vchang
I saw below errors when trying to reproduce the problem using my flame in mozilla-central. Not sure if it is the root cause of the problem but I found two problems here. E/GeckoConsole(14477): [JavaScript Error: "Return value of MozWifiConnection.status 'wps-timedout' is not a valid value for enumeration ConnectionStatus."] E/GeckoConsole(14477): [JavaScript Error: "NS_ERROR_UNEXPECTED: " {file: "app://system.gaiamobile.org/js/wifi.js" line: 221}] 1. It takes a long time(about 15 seconds) to connect to AP using WPS, and it seems only work one time. You have to disabling and enabling wifi to make WPS works again. 2. You can see WPS failed before of DISCONNECTED event from wpa_supplicant. wpa_supplicant: wlan0: WPA: No wpa_ie set - cannot generate msg 2/4 wpa_supplicant: wlan0: Request to deauthenticate - bssid=4c:e6:76:a3:07:e8 pending_bssid=00:00:00:00:00:00 reason=1 state=4WAY_HANDSHAKE wpa_supplicant: TDLS: Tear down peers wpa_supplicant: wpa_driver_nl80211_disconnect(reason_code=1)
Target Milestone: --- → 2.0 S6 (18july)
Whiteboard: bamboo → [p=2], bamboo
I filed Bug 1037276 to fix javascript errors. For the second case, we may need someone to check the wpa_supplicant.
Hi Selin, do you know who can help on wpa_supplicant in T2M?
Flags: needinfo?(kli)
I have no contact to T2M, may be Francis can help on this.
Flags: needinfo?(kli) → needinfo?(frlee)
hi Vincent, per talk, please try to test this issue with V122 base image. https://mozilla.app.box.com/files/0/f/1708478428/Foxfone-One
Flags: needinfo?(frlee)
Enclosed is the wps fail log using "logcat -v threadtime | grep wpa_supplicant". STR: 1. turn on wifi, make sure no ssids in known networks. 2. select "Connect with WPS" in setttings app and select "Button connection". 3. Push WPS button in Access point. 4. wait for connecting..... You can find it connect sometimes to the access point successfully. In that case, you can move to step 5. 5. forget the connected AP and return to step 3. Repeat step 3~5 several times, you will find that WPS is very unstable and doesn't work frequently.
Forget to mention that I use the firmware as Francis's suggestion in comment 10.
hi Youlong, please refer to comment11, this issue can be reproduced on v122. please kindly let us know your finding.
Flags: needinfo?(youlong.jiang)
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(ktucker)
Whiteboard: [p=2], bamboo → [p=2], bamboo,[2.1-flame-test-run-2]
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(ktucker)
QA Whiteboard: [QAnalyst-Triage+] → [QAnalyst-Triage+][lead-review+]
QA Whiteboard: [QAnalyst-Triage+][lead-review+] → [QAnalyst-Triage?][lead-review+]
Flags: needinfo?(dharris)
Whiteboard: [p=2], bamboo,[2.1-flame-test-run-2] → [p=2], bamboo,[2.1-flame-test-run-2] [2.1-flame-test-run-3]
QA Whiteboard: [QAnalyst-Triage?][lead-review+] → [QAnalyst-Triage+][lead-review+]
Flags: needinfo?(dharris)
QA Whiteboard: [QAnalyst-Triage+][lead-review+] → [QAnalyst-Triage?][lead-review+]
Flags: needinfo?(dharris)
Whiteboard: [p=2], bamboo,[2.1-flame-test-run-2] [2.1-flame-test-run-3] → [p=2], bamboo, permafail
QA Whiteboard: [QAnalyst-Triage?][lead-review+] → [QAnalyst-Triage+][lead-review+]
Flags: needinfo?(dharris)
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: