Closed
Bug 846646
Opened 11 years ago
Closed 9 years ago
B2G: Wifi hotspot not resumed after turning airplane mode on->off
Categories
(Firefox OS Graveyard :: Gaia::Settings, defect)
Tracking
(blocking-b2g:2.5?, b2g-v2.2 affected, b2g-master affected)
RESOLVED
INVALID
blocking-b2g | 2.5? |
People
(Reporter: swu, Unassigned)
Details
(Whiteboard: [3.0-Daily-Testing][Spark])
STR: 1. Enable Data connection and Wifi hotspot 2. Make sure Wifi hotspot is on 3. Turn on airplane mode 4. Turn off airplane mode Expected: Wifi hotspot is on after airplane mode off. Actual: Wifi hotspot is off after airplane mode off.
Absolutely right. I just want to be infomed when the pr is fixed, so I leave this redundant comment. Forgive me, guys, I just wanna know.
Comment 2•9 years ago
|
||
This reproduces on Flame 2.2, 3.0, and Aries, adding results and environmental variables. Flame 2.2: Actual Result: After turning on/off airport mode, the device's hotspot is not re-enabled. Environmental Variables: Device: Flame 2.2 Build ID: 20150618002507 Gaia: 3414b07dc489976bf510fd8042c0af3b1192c160 Gecko: a2db74491088 Gonk: bd9cb3af2a0354577a6903917bc826489050b40d Version: 37.0 (2.2) Firmware Version: v18D-1 User Agent: Mozilla/5.0 (Mobile; rv:37.0) Gecko/37.0 Firefox/37.0 Flame 3.0: Actual Result: After turning on/off airport mode, the device's hotspot is not re-enabled. Environmental Variables: Device: Flame 3.0 BuildID: 20150618010201 Gaia: b404c41c5471c31610e64defb74ec066b411e724 Gecko: a3f280b6f8d5 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 Aries: Actual Result: After turning on/off airport mode, the device's hotspot is not re-enabled. Environmental Variables: Device: Aries 3.0 BuildID: 20150618064850 Gaia: ac61ff69e03db3d4ca752d6b4a29c93633127b8d Gecko: b018f8e192cb1116442370f81b0832362b8124df Gonk: 2916e2368074b5383c80bf5a0fba3fc83ba310bd Version: 41.0a1 (3.0) Firmware Version: D5803_23.1.A.1.28_NCB.ftf User Agent: Mozilla/5.0 (Mobile; rv:41.0) Gecko/41.0 Firefox/41.0
status-b2g-v2.2:
--- → affected
status-b2g-master:
--- → affected
Whiteboard: [3.0-Daily-Testing][Spark]
Comment 3•9 years ago
|
||
Hi Henry, Can you help to dispatch this to right owner?
Flags: needinfo?(hchang)
Comment 4•9 years ago
|
||
(In reply to Gerry Chang [:cfchang] from comment #3) > Hi Henry, > Can you help to dispatch this to right owner? I'd like to know if this is by design or a bug first :p My android phone acts the same. Maybe ... the current settings app owner could help check.
Flags: needinfo?(hchang)
Comment 5•9 years ago
|
||
(In reply to Henry Chang [:henry] from comment #4) > (In reply to Gerry Chang [:cfchang] from comment #3) > > Hi Henry, > > Can you help to dispatch this to right owner? > > I'd like to know if this is by design or a bug first :p > My android phone acts the same. Maybe ... the current settings app owner > could help check. Fred, do you have any idea about this bug (or feature)? Thanks!
Flags: needinfo?(gasolin)
Comment 6•9 years ago
|
||
In my knowledge we only handle radio/wifi/bluetooth on/off when toggle the Airplane Mode button. https://github.com/mozilla-b2g/gaia/blob/master/apps/system/js/airplane_mode.js Let UX decide if we need handle Wifi-Hotspot or not.
Flags: needinfo?(gasolin) → needinfo?(hhsu)
Comment 7•9 years ago
|
||
I don't think we really need to re-enable Wifi hotspot once the user turn off airplane mode. Airplane mode was designed for user to turn off radio/wifi/BT and still use the phone on the airplane. If we decide to switch Wifi hotspot on after user turn off airplane mode, users might have forgotten they have turned on hotspot before and will be charged with extra data fees. Also, we have the same behavior as Android and Blackberry, so I don't see this as a serious issue.
Flags: needinfo?(hhsu)
Comment 8•9 years ago
|
||
According to comment 7. Close it as an invalid bug.
Status: NEW → RESOLVED
blocking-b2g: --- → 2.5?
Closed: 9 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•