Closed
Bug 1021423
Opened 11 years ago
Closed 11 years ago
Difficult to toggle wifi in settings
Categories
(Firefox OS Graveyard :: Gaia::Settings, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 1009725
People
(Reporter: pdehaan, Unassigned)
Details
(Keywords: regression, Whiteboard: [2.0-FL-bug-bash][FT:System-Platform])
STR:
1. Open Settings app.
2. Go to wi-fi.
3. Tap the "wi-fi" label in the header.
Actual results:
It only seems to register every 3-4th click and often is unresponsive. Sometimes I need to go back to main settings and back to Wifi.
Updated•11 years ago
|
Whiteboard: [2.0-FL-bug-bash]
Comment 1•11 years ago
|
||
Marking as 2.0? blocker as it seems to be a basic use case malfunctioning.
blocking-b2g: --- → 2.0?
Component: Wifi → Gaia::Settings
Whiteboard: [2.0-FL-bug-bash] → [2.0-FL-bug-bash][FT:System-Platform]
Comment 2•11 years ago
|
||
QA wanted to see if this issue is reproducible on 1.4. Removed 2.0? blocker while waiting more data.
blocking-b2g: 2.0? → ---
Keywords: qawanted
Comment 3•11 years ago
|
||
Not sure if this is duplicated to bug 1017385. The wifi toggle is unresponsive when wifi is turned off.
This issue DOES reproduce on Flame 1.4
Flame 1.4
Environmental Variables:
Device: Flame 1.4
Build ID: 20140610000204
Gaia: 57c6a24f7c7d16aac132f3cecd3ff9ee8d53cf78
Gecko: 54a7aa1a0423
Version: 30.0 (1.4)
Firmware Version: v10G-2
User Agent: Mozilla/5.0 (Mobile; rv:30.0) Gecko/30.0 Firefox/30.0
When toggling the wifi off, the user has to wait ~12 seconds to have the ability to toggle wifi back on
Keywords: qawanted
This issue does NOT occur on Buri 1.4
Buri 1.4
Environmental Variables:
Device: Buri 1.4
Build ID: 20140610063002
Gaia: c39db439202b29897bee9896bc789e6782809f3a
Gecko: edd648be2b07
Version: 30.0 (1.4) MOZ
Firmware Version: v1.2device.cfg
User Agent: Mozilla/5.0 (Mobile; rv:30.0) Gecko/30.0 Firefox/30.0
When toggling the wifi off, the user can immediately turn the wifi back on
Keywords: qawanted
Comment 7•11 years ago
|
||
Okay. As Vincent suggested, we hit a known issue.
You need to log in
before you can comment on or make changes to this bug.
Description
•