Closed Bug 929423 Opened 12 years ago Closed 12 years ago

[Helix] wifi can't be turned on after restart b2g

Categories

(Firefox OS Graveyard :: Wifi, defect)

x86
macOS
defect
Not set
normal

Tracking

(blocking-b2g:hd+)

RESOLVED INVALID
blocking-b2g hd+

People

(Reporter: jj.evelyn, Assigned: lecky.wanglei)

Details

(Whiteboard: [POVB])

STR: 0. make sure wifi is on 1. adb shell stop b2g 2. adb shell start b2g 3. see wifi is turn off, turn on wifi again in Settings Expected result: wifi will be turned on successfully. Actual result: wifi won't be back unless reboot device. If in step 0, the wifi is off, then we can turn wifi on in step 3, but there is no 'onenabled' event fired from Gecko, so the toggle will stay disabled. I also wonder why the wifi is turned off after restart b2g, it shouldn't happen.
> I also wonder why the wifi is turned off after restart b2g, it shouldn't > happen. Wifi setting (wifi.enabled) says it should be on, but wifi interface fail to enable (WifiManager.enabled is false), then connectivity.js in Settings app will reset settings according wifi's real status (Line #39), but at this time, the WifiManager is in a failed state, so toggle wifi setting won't get it back.
blocking-b2g: --- → hd?
Thomas, I suspect it's a porting issue, can you have someone looking into it?
Flags: needinfo?(ttsai)
Flags: needinfo?(ttsai) → needinfo?(kli)
(In reply to Evelyn Hung [:evelyn] from comment #2) > Thomas, I suspect it's a porting issue, can you have someone looking into it? On Helix with partner firmware, restart b2g will cause the wifi doesn't work properly. "adb reboot" is needed after update b2g. Supposely, this is out of b2g control, I will try to get a helix device and check what is wrong in wifi driver OR wpa_supplicant.
Flags: needinfo?(kli)
HD+ing this, this could be severe user impact if b2g somehow restarts during use. Lecky, Can you work with Kaizhen on this?
blocking-b2g: hd? → hd+
Flags: needinfo?(lecky.wanglei)
After b2g is restarted, b2g will try to reconnect to wpa_supplicant. I found that after b2g is restarted, wpa_supplicant will refuse the connection. This is the root caused why wifi will not work properly after b2g restart. ----- W/WifiHW (11387): chip_type = 2.1 W/WifiHW (11387): wifi_start_supplicant_common:supp_prop = init.svc.ath_supplicant W/WifiHW (11387): wifi_connect_to_supplicant:supp_prop = init.svc.ath_supplicant E/WifiHW (11387): Unable to open connection to supplicant on "/data/misc/wpa_supplicant/": Connection refused W/WifiHW (11387): wifi_connect_to_supplicant:supp_prop = init.svc.ath_supplicant E/WifiHW (11387): Unable to open connection to supplicant on "/data/misc/wpa_supplicant/": Connection refused
Lecky, Can you make sure you check this?
Assignee: nobody → lecky.wanglei
Whiteboard: [POVB]
Wayne: In hardware code, the wifi driver need check the wifi whether already running,if already running, it will return directly. ... /* Check whether already running */ if (property_get(supp_prop, supp_status, NULL) && strcmp(supp_status, "running") == 0) { return 0; } ... So, could we sure the wifi state is same with the state before B2G reset?
Flags: needinfo?(lecky.wanglei)
Flags: needinfo?(wchang)
We also try to remove such running check, the wifi state is on after B2G reset. And it need large time to test whether the wifi other function is stability. If it doesnot affect the wifi relation function, we will remove it at next version. Thanks!
Thanks. Please correct this because it impacts development a lot, e.g. when we make reset gaia we need to restart the phone to make wifi work. Also in the unlikely event if user's b2g restarts, they will lose wifi too.
Flags: needinfo?(wchang)
We have solved this probelm in the newest version.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.