WIFI Crash

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Connect to a wireless network (for myself it is wpa2 with an openwrt backend)
2. Keep phone in range of network and periodically wake up phone
3. Do this for a couple days

What is the expected output?

Phone always reconnects to the network, provided it is within range.

What do you see instead?

However, the wireless crashes after an unpredictable amount of time. From my 
experience it could be anything from a couple of hours, to a couple of days to 
repeat the problem. By crash, I mean that it does not reconnect, it can not be 
turned off and then on again. Putting the phone into aeroplane mode and back 
again does not help.

I emphasise that after the issue has occurred, and the user tries to turn off 
the wireless, the user interface does not reflect it. Also if searching for 
wireless networks, none are found.

The only way I have found to remedy the situation is to reboot the phone.

What version of the product are you using? On what operating system?

I am using DHD, I can confirm that this behaviour is exhibited after a full 
wipe, and then flash on rc8. I have experienced the issue on 7.1, 7.2 and 8.

I did not experience the issue on rc7, but I only used it for a day, and have 
not tried any other versions.

I have not tried any later versions due to the effort required to perform a 
full flash. If requested I can try on the latest version.

If anyone knows of any terminal commands that could elucidate the situation 
further, I would be happy to try them.

Original issue reported on code.google.com by kaz.ka...@gmail.com on 24 Sep 2012 at 9:40

Attachments:

• dmesg.wlan.jt8
• logcat.wlan.jt8

[GoogleCodeExporter]

Original comment by MonsterBandit04 on 25 Sep 2012 at 4:57

• Changed state: Accepted

[GoogleCodeExporter]

Im on R11 and im experiencing the same.
As alwsys fully wiped. 
Rgs

Original comment by Frep...@gmail.com on 28 Sep 2012 at 5:04

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

I also encountered this issue on R9.1, R10, R11 (always full wiped before 
flashing and cache/dalvik wiped after flashing).

The only way to reenable wifi is a reboot of the phone.

Best regards and thanks for your great job.

Original comment by maximili...@googlemail.com on 28 Sep 2012 at 5:47

[GoogleCodeExporter]

It's only become a problem since about R8 or R9 for me

Original comment by davemcbr...@gmail.com on 28 Sep 2012 at 5:48

[GoogleCodeExporter]

I am also seeing this issue in R12...only thing to do is reboot the phone.

Original comment by ksh...@gmail.com on 28 Sep 2012 at 1:22

[GoogleCodeExporter]

DHD here. R10 was ok.
In R11 and R12 I have this issue too.

Original comment by patryk.p...@gmail.com on 29 Sep 2012 at 5:35

[GoogleCodeExporter]

This seems to be a temporary fix:
Switch "Keep Wi-Fi on during sleep" to Always

Did not get this issue again on R11 since then - additional power consumption 
is negligible

Original comment by maximili...@googlemail.com on 29 Sep 2012 at 7:27

[GoogleCodeExporter]

WiFi during sleep - Always doesn't work for me. I always use that setting. Its 
default I think. I assumed power consumption via 3G was heavier than WiFi.

The workaround for me is to automatically turn WiFi off when I leave networks I 
connect to. Tasker does this, as well as other apps. I'm under the impression 
it's when transition from a WLAN to cellular data that WiFi becomes locked. 
It's intermittent so it's hard to catch it happening.

Original comment by davemcbr...@gmail.com on 29 Sep 2012 at 7:38

[GoogleCodeExporter]

It happens here also in 12 and 13.

Original comment by ro...@versluis.ca on 30 Sep 2012 at 1:09

[GoogleCodeExporter]

Update with more diagnostics:

Using the debug menu 

*#*#4636#*#* -> WiFi -> WiFi Config

results in the menu crashing, and refusing to open again (until after reboot).

From the terminal, netcfg states that the interface wlan0 is up, but no ip 
address.

Performing 

$ netcfg wlan0 down

does change the state of the interface, so I would assume that the 
hardware/driver has not crashed. It can be put back up the same way:

$ netcfg wlan0 up

but still does not connect.

The use of

$ svc wifi [enable|disable]

is completely ineffectual, even when the wifi is working normally.

Ive also tried to kill the wpa_supplicant, as advised by some wifi bugs on CM 
list, but makes no difference.

I understand that the driver bcmdhd is not compatible with iwconfig, so I was 
wondering if there is a way to manually configure the wireless interface from 
the terminal? This would at least show that this is an Android, rather than a 
driver problem.

Original comment by kaz.ka...@gmail.com on 30 Sep 2012 at 3:07

[GoogleCodeExporter]

I assume all WiFi types are not supported, I am on R15, had same issue on R13, 
I was able to connect to one WiFi network, that WiFi network had no WEP key or 
WPA, (R10) I think allowed me to connect to WiFi. Also I've connected to two 
different internet service providers and two different connections. When I try 
and connect it searches for IP address, says wep key is saved, then turns off 
my WiFi. Please find a fix for this. I love this ROM and dont want to sacrifice 
the features and fixes. Have you reverted to older features, my camera worked 
well a few releases ago, but was terrible before that. I am looking forward to 
a fix. I wish I could donate right now, you are doing such a great job.

Original comment by recogniz...@gmail.com on 3 Oct 2012 at 2:57

[GoogleCodeExporter]

Perhaps this bug is related to 
http://code.google.com/p/android/issues/detail?id=34942

Original comment by chris.ba...@gmail.com on 3 Oct 2012 at 5:53

[GoogleCodeExporter]

Possibly the root cause, do you mean the phone does not handle poor 
connectivity properly, which results in it crashing the wifi?

However, the symptoms I experienced are very different from those of the 
previously mentioned bug. That is, its not a poor signal that is causing me 
problems, its the fact that the wifi can not have its state changed. Even the 
UI shows that it is enabled, after a call to WifiManager.setWifiEnabled(false), 
it is still enabled, and the UI shows that it is.

The solutions mentioned in that bug do not work here, i.e. putting phone in 
aeroplane mode and back.

Original comment by kaz.ka...@gmail.com on 3 Oct 2012 at 6:12

[GoogleCodeExporter]

R17 still got this problem

Original comment by mahakala...@gmail.com on 12 Oct 2012 at 12:33

[GoogleCodeExporter]

This also exists in R21

Original comment by darkmast...@gmail.com on 18 Oct 2012 at 9:31

[GoogleCodeExporter]

Having this problem also on R20. It is working fine for some time period and 
then it is not working. I think in my case it is also somehow connected to use 
airplane mode, usually it is not working after wake up form airplane mode.

Original comment by marjelen...@gmail.com on 19 Oct 2012 at 7:43

[GoogleCodeExporter]

I'm also having this same issue on R21 when this happens.  I cannot turn the 
wifi off in the control panel.  doing a "netcfg wlan0 down" gives me a 
permission denied.  

Original comment by paulchri...@gmail.com on 20 Oct 2012 at 1:41

[GoogleCodeExporter]

Ive noticed the following in a number of logcat's  (across different versions) 
that ive looked at around the time that the wifi stops responding. At least the 
logs ive seen, the unhandled messages and order of them are the same.

I/wpa_supplicant(10124): wlan0: CTRL-EVENT-DRIVER-STATE STOPPED
D/WifiStateMachine( 1643): DriverStoppingState message not handled 0x20001 - 1
D/WifiStateMachine( 1643): DriverStoppingState message not handled 0x2000b - 11
D/WifiStateMachine( 1643): DriverStoppingState message not handled 0x20048 - 72
D/WifiStateMachine( 1643): DriverStoppingState message not handled 0x2004d - 77
D/WifiStateMachine( 1643): DriverStoppingState message not handled 0x20052 - 82
D/WifiStateMachine( 1643): DriverStoppingState message not handled 0x2005b - 91
E/WifiStateMachine( 1643): ENABLE_ALL_NETWORKS command received in stopping 
state, restarting wifi
E/WifiStateMachine( 1643): Error! unhandled message 0x20099 - 153

Im not sure what it means, but the WifiStateMachine does not output any further 
messages after this.

Original comment by kaz.ka...@gmail.com on 20 Oct 2012 at 10:26

[GoogleCodeExporter]

wifi works with jellytime but it kills routers. the router 'internet' light 
blinks constantly and so fast that its almost a solid light.

What happens is I connect to wifi then after the phone is idle for 5-20 minutes 
it shows 'connected' but no internet is available - it is not the phone because 
computers, game consoles, tvs or any other device can no longer connect to that 
network I have ot pull the plug and plug it back in (no delay, just unplug then 
plug it back in right away).

Ive tried the following:
> changing the router wifi channel to EVERY channel, 
> Ive tried static IP, 
> wifi 'never sleep' turned on,
> changing wifi region code to canada
> changing wifi channel to 2.4Ghz only (my router only supports 2.4)

problem seems to be more consistent with Linksys/Cisco routers (I use WRTG54 at 
home and work, there is a new Dlink at work which doesnt seem to be an issue).

Original comment by hsfchefb...@gmail.com on 29 Oct 2012 at 3:34

[GoogleCodeExporter]

I have the same issue even in R30 :( After deep sleep WiFi is not working, I 
can't disable/enable it. It doesn't find any access point. In System 
settings/Wi-Fi I see "Searching for Wi-Fi networks...". Only one solution - 
reboot.

Phone - HTC Desire HD.

Original comment by eimis.si...@gmail.com on 29 Dec 2012 at 1:52

[GoogleCodeExporter]

Also get the same issue in R30 with full wipe - also get the same issue with 
R30 and using kangbang kernel, and also after changing radios a couple of 
times. Definitely seems to be if wi-fi is connected and the phone goes into 
deep sleep the wi-fi state gets stuck and only a reboot fixes it...

Original comment by david.sc...@futrix.com on 10 Jan 2013 at 1:49

[GoogleCodeExporter]

No Wifi with R8. R9. R10.
And no Mobile Data Connection with 4.3

Original comment by thomas.s...@gmail.com on 11 Dec 2013 at 3:36