Take the 2-minute tour ×
Android Enthusiasts Stack Exchange is a question and answer site for enthusiasts and power users of the Android operating system. It's 100% free, no registration required.

Occassionally my Wi-Fi goes into this weird state where the phone "thinks" I'm connected, but the connection simply doesn't work. Apps still seem to think I have connectivity, though they can't actually connect to anything, and the status bar still shows that I'm connected to Wi-Fi. Turning Wi-Fi off and back on resolves the issue, and this occurs on multiple networks.

It seems sort of like whatever service manages the Wi-Fi connection gets killed occasionally. It usually happens when I've been playing a game (that doesn't access the Internet) for a while or if my phone's been sitting for a while; it never happens while I'm actively using the connection. I have my Wi-Fi timeout set to "Never" and the normal timeout isn't the issue since my phone regularly lasts several hours without the Wi-Fi dying. Sometimes it dies a couple times in a day, and recently I went a week or so without it happening.

How can I fix this or prevent the service from being killed (if that's indeed what's happening)? Shouldn't that be a system process that never gets killed? (Does Android ever kill system processes other than when they crash?) Could it be related to TouchWiz? I have an SGS Vibrant running 2.2 (Bionix NextGen v1, but this has occurred on multiple ROMs).

share|improve this question
1  
My wife's Galaxy S Captivate has been experiencing a similar issue. It's running CM7 nightlies, so it doesn't look like it's limited to TouchWiz. –  Chahk Oct 4 '11 at 19:51
    
Have you considered that it may be a problem with the custom ROM? I don't think that android is to blame for this. But this behavior sounds like an old/buggy WiFi driver, which is where the sock rom may be better. –  Flow Oct 4 '11 at 20:08
    
@Flow My ROM is heavily-stock based, as are others I've tried; the drivers are stock, anyways. –  Matthew Read Oct 4 '11 at 20:32
    
FTR, I've gone through two Captivates. The first one was so buggy, that practically nothing worked (including this WiFi issue). I took it to ATT; they verified it was defective and replaced. However, I still had issues with WiFi. I've installed the app and look forward to wifi improvements. –  ray023 Apr 3 '12 at 17:41
add comment

1 Answer 1

up vote 6 down vote accepted

This could be a solution, but it's more a hint at the issue:

The ZTE Blade suffers with losing it's Wi-Fi connection when it comes back from sleep. Perhaps you have a similar issue?
The app Blade Wifi Fix by AA Android available from Google Play Store, fixes it on the Blade, you could give it a try:

Some people with the ZTE Blade / Orange San Francisco phone find that the Wifi doesn't always come back on after the phone wakes up from being locked or asleep.

Install this and you wont know its there until you wake up your phone and the Wifi jams, at which point it will flash a message to tell you its fixing it.

share|improve this answer
    
Thanks, I'll test it out. I'm fairly confident it's not related to sleep, but I'll try anything once :P. Edit: It's been a while and I haven't encountered the issue again since I installed this. I think this has solved the issue, though it's unfortunate that it doesn't keep the Wi-Fi alive while the screen is off. Thanks! –  Matthew Read Oct 5 '11 at 14:55
    
Update -- it still happens occasionally, the app only repairs the connection some of the time unfortunately. –  Matthew Read Apr 3 '12 at 16:26
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.