Closed
Bug 1174355
Opened 9 years ago
Closed 9 years ago
[B2GDroid] Device is still connected to Wi-Fi after disabling Wi-Fi.
Categories
(Firefox OS Graveyard :: General, defect)
Tracking
(b2g-master unaffected)
RESOLVED
DUPLICATE
of bug 1174295
Tracking | Status | |
---|---|---|
b2g-master | --- | unaffected |
People
(Reporter: jthomas, Unassigned)
References
()
Details
(Whiteboard: [3.0-Daily-Testing])
Attachments
(1 file)
1.67 MB,
text/plain
|
Details |
Description: If the Droid is connected to a Wi-Fi network and the user disables the Wi-Fi from the Firefox OS settings, the device will still remain connected to Wi-Fi. Note: The opposite is true. If Wi-Fi through the Droid OS is disabled, attempting to enable Wi-Fi through the Firefox OS settings will not enable Wi-Fi. Repro Steps: Prereq: Device is previously connected to Wi-Fi through Droid OS. Firefox OS must have Wi-Fi enabled as well. 1) Update to B2GDroid 20150608071805 2) Select Settings 3) Select Wi-Fi. 4) Disable Wi-Fi. Actual: Device is still connected to Wi-Fi. Expected: It is expected that disabling Wi-Fi through Firefox OS will additionally disable Wi-Fi in the Droid as well. OR that this Wi-Fi setting may be removed from Settings. Repro frequency: 100%. See attached: Logcat & Video
Reporter | ||
Comment 1•9 years ago
|
||
This issue does NOT occur on the Flame 3.0 Result: Device disconnects from Wi-Fi successfully. Environmental Variables: Device: Flame 3.0 Kitkat Full Flash (319mb) BuildID: 20150612010203 Gaia: 9f36b711af7597a6a32471c3305cf1e2d6947d39 Gecko: 0093691d3715 Gonk: a4f6f31d1fe213ac935ca8ede7d05e47324101a4 Version: 41.0a1 (3.0) Firmware Version: v18D-1 User Agent: Mozilla/5.0 (Mobile; rv:41.0) Gecko/41.0 Firefox/41.0
Blocks: b2gdroid
QA Whiteboard: [QAnalyst-Triage?]
status-b2g-master:
--- → unaffected
Flags: needinfo?(ktucker)
Whiteboard: [3.0-Daily-Testing]
Reporter | ||
Updated•9 years ago
|
Reporter | ||
Updated•9 years ago
|
Updated•9 years ago
|
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(ktucker)
You need to log in
before you can comment on or make changes to this bug.
Description
•