Closed
Bug 865124
Opened 11 years ago
Closed 6 years ago
[Buri][WIFI]The Link speed display 0 Mbit/s when connect to one AP security with WPA2
Categories
(Firefox OS Graveyard :: Wifi, defect, P2)
Tracking
(blocking-b2g:-)
RESOLVED
WONTFIX
blocking-b2g | - |
People
(Reporter: sync-1, Unassigned)
Details
Attachments
(1 file)
450.95 KB,
image/png
|
Details |
AU_LINUX_GECKO_ICS_STRAWBERRY_V1.01.00.01.019.077 Firefox os v1.0.1 Mozilla build ID:20130414070204 +++ This bug was initially created as a clone of Bug #445318 +++ Created an attachment (id=397038) picture DEFECT DESCRIPTION: The Link speed display 0 Mbit/s when connect to one AP security with WPA2 REPRODUCING PROCEDURES: 1.use an andriod phone as AP,security:WPA2-PSK 2.connect to this AP 3.After connect successfully ,check the information of AP,find the Link speed display 0 Mbit/s->KO1 EXPECTED BEHAVIOUR: 1.Link speed should display normal ASSOCIATE SPECIFICATION: TEST PLAN REFERENCE: TOOLS AND PLATFORMS USED: USER IMPACT: REPRODUCING RATE: For FT PR, Please list reference mobile's behavior: ++++++++++ end of initial bug #445318 description ++++++++++ CONTACT INFO (Name,Phone number): DEFECT DESCRIPTION: REPRODUCING PROCEDURES: EXPECTED BEHAVIOUR: ASSOCIATE SPECIFICATION: TEST PLAN REFERENCE: TOOLS AND PLATFORMS USED: USER IMPACT: REPRODUCING RATE: For FT PR, Please list reference mobile's behavior:
Comment 3•11 years ago
|
||
I tried to dump the log for linkspeed from WifiWorker.js and found this value is zero. The value of RSSI seems normal as expected (-26dBm ~ -40dBm). These two values are gotten from wpa_supplicant and I think it should look into it from partner side.
Comment 4•11 years ago
|
||
Does this still a problem ? Can we close it based on comment 3 ?
Flags: needinfo?(sync-1)
Updated•11 years ago
|
Flags: needinfo?(sync-1)
Updated•10 years ago
|
blocking-b2g: --- → -
Comment 5•6 years ago
|
||
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•