Iv been having the same problem as a few others where when I turn on my Wifi sometimes it will connect within seconds and other times it will be stuck on 'optaining ip address'.
Im currently on redpill v4 with kholks 1.2ghz kernel but have switched between different roms and kernels and it wont stop!
The other kernel I use is fauxs 1.3ghz kernel and can't find a certain fix for the problem
Cheers
Sent from my MB860 using XDA App
It's most likely a router problem, not a phone one. Look for updates for your router software, they might fix those kind of stuff
PS: You can always set up fixed IP addresses on your phone if it's still an issue.
turl1 said:
It's most likely a router problem, not a phone one. Look for updates for your router software, they might fix those kind of stuff
PS: You can always set up fixed IP addresses on your phone if it's still an issue.
Click to expand...
Click to collapse
The OP meant the toggle switch sometimes connects and other times gets stuck obtaining IP. You have to push scan manually to get the IP at all. Not a router problem as it is sending the wifi, but sometimes the phone is not registering its there.
Sent from my MB860 using XDA App
I imagine the devs will fix the issue after cm7 is done
Sent from my MB860 using XDA App
I second the router problem. I have to reset my router sometimes to connect.
Iphone > galaxy s 2.
No its not a router problem because it happens wherever I go, its not always happened, just since iv started flashing, when it says obtaining ip it can't actually be doing that because its not scanned and found any networks yet
Sent from my MB860 using XDA App
I had this problem with froyo. When we all got gb it went away.
Sent from my MB860 using xda premium
I have a slightly different problem. When I'm at home on my network, I always connect, fine and dandy, with no interaction needed from me.
At work, we have an open network, but one that requires you to open a browser and agree to the terms and conditions before you can browse. That's probably not anything to do with the issue, but my phone will get stuck in a scanning.... connecting.... disconnected loop. It will never say obtaining IP address during this loop. And then all of a sudden, I'll look at my phone, and there will be the wifi bars in the header. It just all of a sudden decides to work. SHRUG.
jettrue said:
I have a slightly different problem. When I'm at home on my network, I always connect, fine and dandy, with no interaction needed from me.
At work, we have an open network, but one that requires you to open a browser and agree to the terms and conditions before you can browse. That's probably not anything to do with the issue, but my phone will get stuck in a scanning.... connecting.... disconnected loop. It will never say obtaining IP address during this loop. And then all of a sudden, I'll look at my phone, and there will be the wifi bars in the header. It just all of a sudden decides to work. SHRUG.
Click to expand...
Click to collapse
something i tried and has seemed to work. if you go into wifi settings then press the menu key you will see an advanced option. in there is a wi fi sleep police. i changed mine to never from never when plugged in even though it was never plugged in and so far so good.
Related
My WiFi was working fine on my Xoom, and now it gets stuck while "obtaining IP address." It says for a split second "remembered" as if it was connected and starts the ongoing circular process of "obtaining IP address" all over again. I saw that galaxy tab users had this same problem and found a resolution by connecting "static" instead of "DHCP." I didn't try that as I honestly don't know how. What I do know is that there are a few devices like my OG droid, my laptop, my mothers' laptop, my xbox 360 that are connected to the same WiFi network. This randomly happened, when I decided to disconnect from WiFi to run a speed test on 3G and I was unable to connect to WiFi ever since. I tried unplugging/plugging the routers, turning the Xoom off and on, and even went so far as to doing a factory reset on the Xoom and I still can't connect. 3G works fine, but I have a 1GB cap and I would rather only use that while I'm on the go, and obviously WiFi is definitely faster. If I can't resolve this, I still have enough time to return this thing. Call me a newb, but I need a little help!
I know you said you did a factory reset, but google stores wifi passwords in the cloud now. Try making the xoom forget the network you're trying to connect to.
My only other thought is that you need to go into your router's configuration and remove the xoom as a remembered device.
Bauxite said:
I know you said you did a factory reset, but google stores wifi passwords in the cloud now. Try making the xoom forget the network you're trying to connect to.
My only other thought is that you need to go into your router's configuration and remove the xoom as a remembered device.
Click to expand...
Click to collapse
How do I get the xoom to forget the network? How do I remove the xoom as a remembered device? Sorry but I really don't know how to do that..
EDIT: I went into settings>privacy>backup and restore> and unchecked "back up application data, Wi-Fi passwords, and other settings to googles servers and was still unable to connect.
I think if you long press on the wifi network it will give you the option to forget it.
As for the router, do you remember setting it up? The settings pages where you set the wifi name and password and such.. it should have a section where it tells you which devices are connected.
I have pressed "forget network" on the xoom several times when trying to connect. As for the router, do I remember setting it up? No, as a matter of fact I didn't set it up. Could I configure this thing from my laptop?
droiduser1988 said:
I have pressed "forget network" on the xoom several times when trying to connect. As for the router, do I remember setting it up? No, as a matter of fact I didn't set it up. Could I configure this thing from my laptop?
Click to expand...
Click to collapse
Of course, anything that's connected to the router should let you configure it. It's too complex to explain here, but you need to enter the router through it's IP address and find the configuration.
Find the manual for the router you have and go from there.
I'll try to look into that, any idea as to wtf happened? This is beyond an inconvenience..
I'm having much the same problem. After entering the passphrase it says 'obtaining ip address from....' and thats all. It never connects??? I have tried 'forget' several times and no luck.
I have been able to connect to unsecured wifi with no problems.
Use the free app "wifi static". Config to assign you a static IP on that network only and dhcp on others. Its something within android as I have the same issue in my phone with a few networks but not most.
Sent from my Xoom using XDA App
jcampbell037 said:
Use the free app "wifi static". Config to assign you a static IP on that network only and dhcp on others. Its something within android as I have the same issue in my phone with a few networks but not most.
Sent from my Xoom using XDA App
Click to expand...
Click to collapse
OK, tried it. NO GO! After entering the passphrase it STILL says 'obtaining ip address from....' I may be doing something wrong with the app since it comes with absolutely NO directions. If this is going to be an issue average folks will take it back!
Have any of you with this issue verified that the DHCP scope on the wireless network is not full or that DHCP is even allowed? The fact it works one place but not another tells me the issue may be with the network and not the device.
Dave
Sent from my Xoom using XDA App
I was having the same issues as you originally at first until I reset my router and my Xoom.
Sent from my Xoom using XDA App
je2345 said:
I was having the same issues as you originally at first until I reset my router and my Xoom.
Sent from my Xoom using XDA App
Click to expand...
Click to collapse
I also had this issue, I ended up fixing it by upgrading my router BIOS. the version that was on there was dated 2004 (yikes), and though the most current update was only 2006, it seems to have fixed the problem.
That or the reboot after the update as previous poster said and the update didn't really have anything to do with it, but either way it got fixed.
I have the wifi only model of the Xoom and have noticed that my wifi speeds decrease if the unit is left on for a couple of hours. It will only get back to full speed after rebooting. For instance, after bootup I can get up to 20mbps. After an hour or so, I'll drop to 3-5mpbs max. I tried not running anything after bootup except for the speedtest.net app and get the same behavior. Just wondering if anyone else is having this issue. I am running Honeycomb 3.2. I have searched on this forum but no one is having any similar issues, just wifi dropouts. I don't have that problem. The only services running at the time of bootup are Music, Thumbkeyboard, Minimalistic text, Maps and Google Services.
Your router will affect that. I had that issue until I bought a real high speed router. Also check your router settings for the through put speeds. You can set that to 54mb or higher and change to channel 11. See if that helps.
Sent from my ADR6400L using xda premium
I have the D-link DGL4300 router. That's a high end router. But I'll try setting it to Channel 11 to see if that helps. I have the same issues using the wireless at work as I do at home. Hopefully this change helps.
Changing the channel would only improve speed if the channel you are currently using is crowded. Channel is merely frequency. As for slowing, it is probably your routers qos.
Sent from my Xoom using xda premium
Yeah that doesn't work. How do I change my qos?
Sent from my Xoom using Tapatalk
I highly suggest setting up a static IP address if you know how to do so. A static IP is a more direct connection to the device. In other words: Auto settings will do everything by itself to the best of its ability, meanwhile a static IP says that it will go right here to this specific device right now. Thus, you will have a more solid connection to the device with an internet connection.
Setting up a static IP address is really easy, you just have to know a little bit about your router, and know how to work with setting up custom IP addresses. Once you learn it, you would apply that to all of your internet enabled devices, not just the Xoom.
I have all of my devices set up this way, Xoom included. It runs smooth as butter like always.
Setting a Static IP Address in Windows 7
This website has some basic knowledge, although it is for Windows 7. The same rules apply to any other device as well. You'll have to check your wireless router settings and see what devices are connecting to it, and what their IP addresses are. Once you know that... it should be pretty easy to get things rolling. The other basics like subnet mask, and default router are explained in the website.
diablo2224 said:
I highly suggest setting up a static IP address if you know how to do so. A static IP is a more direct connection to the device. In other words: Auto settings will do everything by itself to the best of its ability, meanwhile a static IP says that it will go right here to this specific device right now. Thus, you will have a more solid connection to the device with an internet connection.
Setting up a static IP address is really easy, you just have to know a little bit about your router, and know how to work with setting up custom IP addresses. Once you learn it, you would apply that to all of your internet enabled devices, not just the Xoom.
I have all of my devices set up this way, Xoom included. It runs smooth as butter like always.
Click to expand...
Click to collapse
This is great advice for when the AP you're connecting to has trouble negotiating DHCP, but it seems to me the OP is talking about link speed.
OP: there's a memory leak in some versions of the wifi driver that can cause the symptoms you're seeing. I've seen it a few times even in 3.2, but toggling wifi usually cures it.
I bought a 300mb netgear and it fixed my issue at home. At work is a diff story. Max speed on those routers is 54mb and it pauses all the time. Seems to me the xoom was designed for speed and the cheaper routers can't keep up with the data.
Sent from my ADR6400L using xda premium
your problem might be cache full as it is ok after reboot. try installing a cache cleaner ng apk from market. it can schedule a auto cache clear daily.
Send from my Xoom MZ601 using XDA app
Ok. I think the problem that was sucking down my wifi speeds was a god damn live wallpaper. I downloaded the one called Shadow Galaxy from the market. After I rebooted yesterday, I had changed the wallpaper to a plain one. It's been about 20 hours so far since my last reboot and I'm still getting 15 to 20mbps! I'll keep you guys posted.
ZanshinG1 said:
This is great advice for when the AP you're connecting to has trouble negotiating DHCP, but it seems to me the OP is talking about link speed.
OP: there's a memory leak in some versions of the wifi driver that can cause the symptoms you're seeing. I've seen it a few times even in 3.2, but toggling wifi usually cures it.
Click to expand...
Click to collapse
I kinda figured as much, but y'all seemed to have this down already. Figured I would offer up some useful info to make a more solid internet connection.
If none of the other options helped, in your routers settings (generally 192.168.0.1), probably advanced then quality of service, you can probably turn on or off the native qos, or make an exception. I'm not sure, Im not familiar with d-link software...
Sent from my Xoom using xda premium
Im having the same problem with my Xoom (3.2), after been conected some time to a wifi speed decreased a lot! What i do is turn off then turn it on again, that fixes it
It there a fit for that?
My live wallpaper was the cause of my issue do you have 1 running
Sent from my Xoom using Tapatalk
CyberChulo said:
My live wallpaper was the cause of my issue do you have 1 running
Sent from my Xoom using Tapatalk
Click to expand...
Click to collapse
wouldnt this only be the cause if the live wallpaper connects to the internet... i have one which just uses photos from my sd card... maybe we could try restricting its access to the internet and maybe that will have an affect? I dont know how to restrict internet access though
Just switch it to a stock wallpaper for now and see if that works.
im not using live wallpaper, just an stock one.
I just did the process to restore full speed again, this is happening in all placess i go, at least once at day, i think is a honeycomb (3.2) problem, not just a live wallpaper :-S
There appears to be a problem with new versions of Android and old routers. Many people have reported the "obtaining IP address" loop problem.
Let me explain. I use the leisure facilities in a local hotel. It has a public (open) wifi network. I believe it uses an old router. My Galaxy S2 (Gingerbread) and AsusTransformer (ICS) both connected to this network without problems. I recently replaced the S2 with an S3 (ICS) and my Transformer with a Nexus 7 (Jellybean). Neither of my new devices connect to this network. I have had the same problem in a local cafe.
I have researched this problem. It is not uncommon. It appears to be caused by an odd mix of hardware (router and wifi chipset) and software (later versions of Android). If you are unlucky (like me and some others) you will be unable to connect to some networks.
The solution is to use static IP addressing (since your device is unable to obtain a dynamic IP address). This will allow your device to connect to the network -- but you need to know the correct settings (for static IP addressing) before you can actually use the network.
This problem has been reported by many people. Does anyone know if there is a fix or a workaround?
The only one I can think of it to get hold of a device that does connect to this network and copy the (static IP) settings. But this would only solve it for one location meaning that I will run into it again the next time I try to connect to a network with old hardware.
Sometimes when I get that problem it's due to IP address conflicts on the Windows 7 computers.
I go to the computer and:
http://helpdeskgeek.com/networking/release-and-renew-an-ip-address/
Otherwise I just pull the router out and refresh it, should work for another few weeks or so.
Asovse1 said:
Sometimes when I get that problem it's due to IP address conflicts on the Windows 7 computers.
I go to the computer and:
http://helpdeskgeek.com/networking/release-and-renew-an-ip-address/
Otherwise I just pull the router out and refresh it, should work for another few weeks or so.
Click to expand...
Click to collapse
I don't have access to the PC. It is owned by the hotel. I need a solution that I can apply client (Nexus) side.
Solution
I found a solution. I asked the guy to reset the router and both my Nexus and S3 immediately connected. Someone advised me to do this. I have no idea why it worked. Not really a solution since i cant go round cafes asking people to reset their routers for me.
Is there a way to find out IP, DNS, gateway etc values on Nexus when they are dynamically assigned?
I sometimes have this Problem when starting my accesspoint after enabeling wifi on my N7.
I have to reboot my N7 in that case to get an IP.
Happened to me quite a few times when I went out with it to a restaurant or something. It just loops and loops.
My Nexus (and S3) now connect to the hotel network every time now. So it looks like you only need to ask the owned to reset his router once.
Embraced with this problem
bobbyelliott said:
My Nexus (and S3) now connect to the hotel network every time now. So it looks like you only need to ask the owned to reset his router once.
Click to expand...
Click to collapse
Resetting the modem solves the problem if you don't make any change to the router settings. I don't understand why the hell google is not solving the problem yet...
many users are found to face the same problem..
eve I can connect with my Nokia E72 but not with my N7...
I can get the IP from my cell phone. But come on, what's the point of doing so?? Are you gonna assign the IP for each and every WiFi you connect?? Or if the IP changes everyday??
Static ip won't help, yes you can connect to wifi, but cannot get connection to internet. This is a bug of android, and ITs in Princeton univ. had some investigation. 412 should have fixed it
Sent from my HTC Z710e using xda premium
gcd0318 said:
Static ip won't help, yes you can connect to wifi, but cannot get connection to internet. This is a bug of android, and ITs in Princeton univ. had some investigation. 412 should have fixed it
Sent from my HTC Z710e using xda premium
Click to expand...
Click to collapse
no. The same problem with 4.2.1 on my N7. God,this is really pissing me off !
EDIT: Finally found a solution . Thank god!!
TheDarkDefender said:
no. The same problem with 4.2.1 on my N7. God,this is really pissing me off !
EDIT: Finally found a solution . Thank god!!
Click to expand...
Click to collapse
What was the solution?
bobbyelliott said:
Is there a way to find out IP, DNS, gateway etc values on Nexus when they are dynamically assigned?
Click to expand...
Click to collapse
For a simple display of the values look at something like Network Signal Info of Wifi Analyser (both free)
jet1000 said:
What was the solution?
Click to expand...
Click to collapse
Use a static IP .
Sent from my Nexus 7 using xda app-developers app
You can only get internet access when you'll be using the correct IP, DNS etc. So try to find out what is the working IP setting...
Sent from my Nexus 7 using xda app-developers app
Deleted
I just started having a similar problem. I have a samsung galaxy tab with Sprint. I've had it for a year and this is the first time I've had this trouble.
The only difference is, I cannot connect to any wifi network at all. It keeps hanging on "obtaining IP address" and then disconnects. It doesn't matter if it's my home wifi or school or free wifi in a restaurant.
The only possible connection I can make is that I downloaded Lookout to check it out as a possible security app, I have since uninstalled it but that did not fix my problem.
Continuing to research this but any ideas on how to fix this would be fantastic.
I'm having this problem on my HTC One S. It happened yesterday without warning and it's really annoying. I went to a nearby cafe and the wifi worked perfectly, so it's something wrong here.
Static IP solution connects to me to the network but I can't actually use the internet, so I'm stumped.
i'm getting the same error with AOKP 4.2.2, and also know people with stock 4.2.2 with it.
the only way i found to fix it is to reboot the phone..... and wait for it to happen again and reboot it again
i cannot use static IP since in my university (and some other public places) it is not possible to connect it like that :S
TheDarkDefender said:
no. The same problem with 4.2.1 on my N7. God,this is really pissing me off !
EDIT: Finally found a solution . Thank god!!
Click to expand...
Click to collapse
How did you solve this? I Need help with my tf 300
bobbyelliott said:
There appears to be a problem with new versions of Android and old routers. Many people have reported the "obtaining IP address" loop problem.
Let me explain. I use the leisure facilities in a local hotel. It has a public (open) wifi network. I believe it uses an old router. My Galaxy S2 (Gingerbread) and AsusTransformer (ICS) both connected to this network without problems. I recently replaced the S2 with an S3 (ICS) and my Transformer with a Nexus 7 (Jellybean). Neither of my new devices connect to this network. I have had the same problem in a local cafe.
I have researched this problem. It is not uncommon. It appears to be caused by an odd mix of hardware (router and wifi chipset) and software (later versions of Android). If you are unlucky (like me and some others) you will be unable to connect to some networks.
The solution is to use static IP addressing (since your device is unable to obtain a dynamic IP address). This will allow your device to connect to the network -- but you need to know the correct settings (for static IP addressing) before you can actually use the network.
This problem has been reported by many people. Does anyone know if there is a fix or a workaround?
The only one I can think of it to get hold of a device that does connect to this network and copy the (static IP) settings. But this would only solve it for one location meaning that I will run into it again the next time I try to connect to a network with old hardware.
Click to expand...
Click to collapse
Note: You Must have root.
Go to
/data/misc/dhcp/
and delete all 3 / 4 files there.
And voila it should work.
On my Nexus 10, about 2 weeks old, and running most current version of Android, non-rooted, I can connect to wifi networks, but I do not have access to the internet. It just started today after having no issues whatsoever since I purchased it. It also just happened randomly today out of the blue. For further information, in the top right corner where the wifi "baseball diamond" is, the bars are that grey/white instead of the typical blue. Which I know means that I am connected to the network but without internet access. I have tried restarting my device both powering it off and on, and simply restarting it by holding down the power button. I have tried turning wifi off and on. I have tried the same with airplane mode as well. None of it has worked. I was wondering if anyone knew of any fixes for this issue? Thanks and any help is appreciated.
First I would get the IP of the nexus by long pressing the Wi-Fi network.
Then go on your pc connected to the same router and ping the ip.
For Windows, press Windows, type cmd.exe, enter, then
ping 192.168.1.x
But put in the real address instead.
If you get a reply with a ms value, your tablet is really connected.
If it times out or you get 100% packet loss, then it really isn't connected, or is unresponsive on the network.
Swiped from my Rezound using xda-developers app
When the bars are grey it doesn't necessarily mean that you don't have internet. The bars only turn blue when you are connected to the Google Talk servers. They are blocked at my work but I still have internet access with grey bars.
HillsRider said:
When the bars are grey it doesn't necessarily mean that you don't have internet. The bars only turn blue when you are connected to the Google Talk servers. They are blocked at my work but I still have internet access with grey bars.
Click to expand...
Click to collapse
It just started though and I didn't have problems before. And I am connected to the Google servers on my galaxy s3 just fine on the same wife network. And as for the other poster, how do I ping it on a mac?
mvmacd said:
First I would get the IP of the nexus by long pressing the Wi-Fi network.
Then go on your pc connected to the same router and ping the ip.
For Windows, press Windows, type cmd.exe, enter, then
ping 192.168.1.x
But put in the real address instead.
If you get a reply with a ms value, your tablet is really connected.
If it times out or you get 100% packet loss, then it really isn't connected, or is unresponsive on the network.
Swiped from my Rezound using xda-developers app
Click to expand...
Click to collapse
so i did this on my macbook. and viola it just started working again after I pinged it. It just said "starting ping" on the laptop and never anything else, but hey I am not complaining. so thanks
jscheuner said:
so i did this on my macbook. and viola it just started working again after I pinged it. It just said "starting ping" on the laptop and never anything else, but hey I am not complaining. so thanks
Click to expand...
Click to collapse
So everything worked fine yesterday after doing this. But today it reverted back to what it was doing. Tried pinging the ip again but it didn't work and it gave me 100% packet error or whatever
The ping had nothing to do with it working again, it was just a coincidence. You're having the same wifi problem a lot of us are suffering.
it has to do with the dns settings of the network I am using. And it just seems to come and go in terms of working. Hopefully it is fixable problem within the software
I am having a similar problem, but it happens sporadically and oftentimes fixes itself after about 30 seconds. Is this a known problem and is it hardware? Also, sometimes when I go to open the play store I will get a "No connection" message with the option to retry even when I am fully connected (blue bars and everything). The retry almost always works too. I am curious why this happens and if the two issues are related. Thanks for the forum, folks.
Sent from my Nexus 10 using Tapatalk HD
catfish_stevens said:
I am having a similar problem, but it happens sporadically and oftentimes fixes itself after about 30 seconds. Is this a known problem and is it hardware? Also, sometimes when I go to open the play store I will get a "No connection" message with the option to retry even when I am fully connected (blue bars and everything). The retry almost always works too. I am curious why this happens and if the two issues are related. Thanks for the forum, folks.
Sent from my Nexus 10 using Tapatalk HD
Click to expand...
Click to collapse
Yes, this is a known problem many are experiencing and is most probably software, unfortunately google seems to have a hard time getting their fat fingers off their arse.
Same issue has been driving me crazy. I have to turn Wifi off and on again.
The other, really annoying issue is that when I turn Wifi on in my bedroom, it still connects to the living room router with terrible wifi reception, instead of the nice strong signal from the office router just next door, I have to tell it explicitly connect to the office one.
Alias_neo. Why don't you just rename the network in your room to a different name so the tablet can distinguish between the two
Sent from my Galaxy Nexus using xda app-developers app
surfboard3r said:
Alias_neo. Why don't you just rename the network in your room to a different name so the tablet can distinguish between the two
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
They ARE different names, that's what's bugging me. My SGS3 had no issue, but for some reason the N10 just prefers one once it's set.
Sent from my GT-I9300 using Tapatalk 2
OK this is really pissing me off. Everyone time I go on my nexus device it doesn't automatically connect to the WiFi.. I have to either disable the WiFi and reenable it. Or just click on my network and click connect (it says its saved but doesn't automatically connect when I turn on my device), i tried everything from forgetting every saved network, restarting me device, ect, and its not my routers problem, my DNA connects automatically when I turn it on. Any of you guys had this problem? If so what did you do to fix it?
Sent from my Nexus 7 using xda app-developers app
what router? My nexus 7 is fine and so is my sgs1.
No idea what router I have but that's not the problem, problem is that when I turn on my nexus and get passed the lockscreen, the WiFi would normaly automatically connect. It for some reason stopped doing that and it gets really annoying manually connecting
Sent from my Nexus 7 using xda app-developers app
kernel
PhantomsWay said:
No idea what router I have but that's not the problem, problem is that when I turn on my nexus and get passed the lockscreen, the WiFi would normaly automatically connect. It for some reason stopped doing that and it gets really annoying manually connecting
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
try to change your kernel. the wifi drivers are in the kernel...
Running stock, never changed my ROM or kernel
Sent from my Nexus 7 using xda app-developers app
You could try a different channel on your router
Sent from my Nexus 7 using xda premium
PhantomsWay said:
OK this is really pissing me off. Everyone time I go on my nexus device it doesn't automatically connect to the WiFi.. I have to either disable the WiFi and reenable it. Or just click on my network and click connect (it says its saved but doesn't automatically connect when I turn on my device), i tried everything from forgetting every saved network, restarting me device, ect, and its not my routers problem, my DNA connects automatically when I turn it on. Any of you guys had this problem? If so what did you do to fix it?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Hi,
I share the same problem. Upon a reboot, it will work normally for a while.
Once they symptoms starts, it will refuse to connect most of the time. When it does connect, it will disconnect within a couple of minutes. WPS wont respond either. toggle wifi/airplane mode does not work either.
The only way is to reboot.
However, I did have some findings but couldnt get it fixed! Do this and test if it works for you as well:
Go to terminal (needs to be rooted device):
Simply select the "Take wifilock/B]" option and it will stay connected!
Release it and it will get disconnected and back to the same issue.
Hopefully some experts can give us some pointers?
Temporary fix
I have the same problem. This is what i did to fix it: Settings- Wifi settings- advanced- switch always on to Never, reboot in recovery, clear cache, reboot your device and go back and turn Wifi back to Always on. this is a temporary fix because if you reboot or shutdown your device, you will need to redo the steps. this is a known problem with google's 4.2 jellybean. we need an update soon!
hope it helps you.
Thanks for your help
Sent from my Nexus 7 using xda app-developers app
It won't be much comfort to you, but remember that "it takes two to tango".
Yeah, there's IEEE standards for all of this stuff. Do interop problems still happen? All the frigging time, every day. Sure it is maddening.
And sometimes the problems only manifest themselves with an exact pair of firmware(s) releases between the AP and the client device. I had a WiFi router that would gladly talk to four or five unique types of devices; on the sixth - an Android phone - it would associate & authenticate successfully, but the client device would never get an IP address.
That sure sounds like a problem with the phone, doesn't it?
How did I fix the problem? I upgraded the firmware ... on the router !
Sometimes problems with intermittent connections can be rectified by fooling with things that you might think have no bearing on the problem. For instance, some routers will accept connections in A/B/G/N mode. Do you need all of those? If not, simplify your router's behaviors by disabling non-essential features, e.g. select G-only or N-only.
That's just an example - but the point is that the fewer behaviors either of the devices engage in, the lower the probability that the bug which is shared between them will get expressed.
So, you can either fool around with both devices, only one of them - changing one setting at a time to see if that alters the behavior you observe, or you can throw one device away and start all over with new combinations of devices. The router probably has more knobs which can be turned than the phone does (unless it's not your router, or you don't control it).
Good luck