Related
im trying for a week now to get around an issue that is costing me my nerves and renders my phone useless, especially on travel without roaming and data-plan. after screenoff my nexus kills the wifi connection, after some time though, 30 minutes, 1 hour, it seems to change. my company uses skype as the primary means to communitate and i'm just cut off, won't receive important mails, messages, whatever.
when i switch my phone back on wifi starts up again, if im quick enough the settings reveal "avoided poor internet connection" in the hotspots status. so basically it looses the signal for a moment and is not able to connect back on its own. i read 4.0.1 had a setting to circumvent that but since 4.0.2 it's gone. of course keep-alive-during-sleep is checked to "always" in the settings and i tried just about anything, changing basebands, factory resets, cache wipe, etc. nothing helped. the weirdest thing i that the battery stats to not reflect it, the blue wifi line is uninterrupted all the way.
i searched and found dozens of people complaining about this but no solution anywhere. they switched phones and had the same problems still. from little fragments i collected it seems that samsung devices had this issue before, cm7 supposedly fixed a hardware driver that had issues with certain wifi devices on certain frequencies.
im on AOKP b27 now (powersaver on or off with setting to untouched or "leave on" made no difference), leankernel, xxkl1 baseband. today i went back to stock 4.0.2 to see if that does something. still, has anyone here similar problems and maybe even solutions? what about the cyanogens "nexus one sleep fix" i read about, anyone can provide links or informations?
Did you try settings - wifi - menu - advanced - keep wifi on during sleep - always
Sent from my Galaxy Nexus using xda premium
Try changing that setting. I know 2.x defaulted to turn wifi off during sleep but I thought they changed that in ICS. Either way that sounds like the problem.
its not that setting, it's the first thing i checked. it's set to "always" and it should never kill wifi in theory. from what i have read by now it seems more of a wider problem, a software or hardware related issue affecting all nexus devices. most people don't know about it since it only fails for certain routers having certain settings (which other phones digest without problems though). i also never knew it until i had to stay one month in a place with a wifi-hotspot my phone doesn't like. my gf's s2 has no problems at all, neither have our laptops.
here on xda people have switched their devices because of that problem, got new ones and the problem persisted. i have installed roms, kernels, stock-images, basebands, nothing helped and i am sure the problem won't go away if i exchange the device. i knew i'd probably not gain much by asking again, threads like this can be found here, on rootzwiki, google, etc., but i was hoping to gather a little more knowledge. to read about cm7's patch for a similar issue on the nexus one gave me hope that something must be out there ...
btw, stock ICS seems to have the best reception by now, it stays connected for hours. but once it looses it, it won't re-connect aswell. my experiences are worse with AOKP. and it sucks because i love that rom so much. i guess when i'm home again it wont bother me since my own wifi is okay - but man, here, in another country it really hits me.
i had the same problem, seems like the connection would drop when the wifi signal is weak regardless of what settings you choose. i saw this problem on 4.01 and 4.02 stock, and apex rom. i had to switch to a router that could broadcast a stronger signal. i would get about 80-90 dbm with the old router and the new gone give 60-70 dbm. it seemed to have fixed the problem, i havent seen my gnex drop the wifi since i got the new router a few weeks ago.
Ive heard some people have a bug with wifi sleep policy setting not working. But mine seems to actually work. Set to "never" is the best choice and after hours of screen off my wifi is still connected.
Maybe try that setting a few times to kill the bug.
“never"should actually kill wifi immediately after screen off I think. If it doesn't that would be just another bug. I read somewhere that for some people setting it to never resolved the issue but i tried pretty much every setting by now, nothing worked out though. I became so desperate I installed wifi monitor apps that reset wifi after they figure it got dropped, but not even these patches could revive it in some occasions. The only thing that works for sure is switching on the screen every now and then.
It's a wifi sleep policy. So never = never sleep.
Weird, mine says "keep wifi alive during sleep": always, when plugged in, never. our I miss something and there's another setting I haven't tried yet.
this may fix ur problem... for rooted phone
http.s://play.google.com/store/apps/details?id=co.in.zextr.wcf&hl=en
Click to expand...
Click to collapse
do you have " avoid poor connections" unchecked?
martonikaj said:
It's a wifi sleep policy. So never = never sleep.
Click to expand...
Click to collapse
How do you get that? It says "Keep Wi-Fi on during sleep", which implies "never" would always keep the Wi-Fi off during sleep.
Hello,
I've searched around the Epic 4G Touch forums as best I could, but sadly I couldn't find anything that was exactly this problem (although I found some interesting articles about wifi sleep time but they don't seem to apply). I'm experiencing an annoying issue where I can connect Wifi just fine, but if the phone is left for a small period of time (~10 minutes), wifi appears as if it's still connected, however it cannot send/receive data. When this happens, the wifi status says it's "connected", but there is no data connection. The only way to to get the data back is to turn off wifi, wait for 3/4G connection to initialize, then turn Wifi back on to refresh it...then it's fine again until I set the phone down again.
I had this problem on stock EL29, so I rooted and flashed Phantom Blazer ROM (very cool ROM, but I'm still experiencing the same issue). After reading the threads on here about wifi sleep times (apparently they're backwards with ICS roms), I've experimented with every setting, yet I still have the same issue--Wifi is fine as long as I'm using the phone, I set it down, after about 10 minutes pick it back up, says it's still connected, but no data connection.
has anybody experienced this problem with this phone? I'm about to unroot my phone/go back to factory so I can take it in to a Sprint store, the problem is they (trying not to be offensive) don't seem to know very much about this device. I thought I'd ask the pros before I return it, get an iPhone, and have to eat my words about how cool Android is vs. iPhone in front of all my friends. I'm hoping there's a reliable ROM or app that can resolve this vs. having to just replace the device!
Thanks for your help!
I'm not the only one
I'm not the only one with this problem:
edit: I can't post links to androidforums.com or anywhere else, but this same problem is all over the interwebs and nobody has a solution.
I'm sure it's not my router as my ASUS tablet/laptops/girlfriend's iPhone experiences no connectivity problems. I'm thinking this is a hardware problem with some of these devices. I will unroot/reset to factory tonight and let you know what happens.
What channel is your router on? And what type is it A/B/G/N?
This is s known TW ICS bug, most likely kernel related. Almost everyone is having this issue and there is no fix until Samsung decides to repair it. There are quite a few posts similar to this one. If you're using XDA's search function, it's not very good. Try using Google next time and search XDA that way.
Sent from my SPH-D710 using Xparent ICS Tapatalk 2
Hey guys, thanks for the response. Just before I unrooted/reset to factory I tried one last solution--download an app called "Wifi Fixer". It has resolved a lot of these problems. It's not 100%, but after testing it for a day so far, I've only had to manually refresh the connection once or twice. It's a lot better, even liveable, and I won't be resetting to factory afterall, at least not until Samsung provides an update. So if anyone is having the same problem, try Wifi Fixer, hopefully it gives you a similar level of success...I'm not super happy about having to run another background process all the time, but it doesn't seem to affect battery, and the fix it provides is worth it to me.
Cheers!
Huh - a couple of things. Noticed this problem crept back in FF18 and didn't know why until I went back and checked the wpa_supplicant.conf that I'm using. The line ap_scan=2 was missing; after adding it back in the signal strength is back to full and stable.
I'll bump the thread but it appears the config changes here still hold after all:
http://forum.xda-developers.com/showthread.php?t=1569348
This should also avoid having the WiFi fixer there as you can specify the country in wpa_supplicant.conf manually.
Thanks for looking in to this! A couple questions from a noob like me though:
When you say the problem crept back in FF18 ... what does that mean? Is that something that exists in the "stock" version of the Epic 4G touch from Sprint?
The manual config file tweaks you're describing ... is that something I can perform myself?
Basically I'm wondering if it's "safe" to revert to stock in order to get consistent wifi signal, or if it's something I'm experiencing because of the ROM I'm using.
Thanks!
So I have tried to trace my issue to it's roots and after a lot of investigation I decided to make this thread.
The issue:
When connecting to home wifi network I get "Authentication error occurred" even though it's the good password.
It first occurred on stock 4.1.1 ROM with stock Kernel even before rooting. What's more interesting is that I've successfully used the same wifi network for around a month. Other devices connect just fine, no settings on the router changed when this started happening. Didn't fiddle with any settings on the phone neither. I can connect to free wifi APs just fine.
What I've tried:
Dialing *#0011# and from service mode disabling wifi power saving feature.
Using all possible encryption combinations on the router (Open - no password, WEP, WPA-PSK AES and/or TKIP, WPA2-PSK AES and/or TKIP or both WPA and WPA2 at the same time), switching channels, disabling 802.11n mode.
Using some modded wpa_supplicant files from this thread.
Using a bad password just to get a different error.
Downloading some other wifi connectors from the Play Store including Wifi Connection Manager which claims to "Fix device Wi-Fi problems." by cleaning the stored wifi config files and maybe something more.
Flashed Omega v10 ROM with Perseus kernel.
All these things and basically any combinations of them worked to no avail. And the only thing that helped was being very close to the router. That way I manage to connect but moving a couple of meters away, like to a nearby room, and it starts giving the same error even though the network strength is still full at that point.
My thoughts:
I saw a similar issue at a couple of places including a similar thread last active dec 23rd, Android issues on code.google.com and androidforums, but no solutions found there worked. Also comparing how my old original Note and an even older LG P500 perform, the wifi signal is obviously weaker on the Note 2. My area is not heavy on wifi networks, so my guess is there's something wrong with wifi drivers or configuration. Sooooo.... What can I do to remedy this issue and also is there any way to beef up my wifi in the process?
OrangGeeGee said:
So I have tried to trace my issue to it's roots and after a lot of investigation I decided to make this thread.
The issue:
When connecting to home wifi network I get "Authentication error occurred" even though it's the good password.
It first occurred on stock 4.1.1 ROM with stock Kernel even before rooting. What's more interesting is that I've successfully used the same wifi network for around a month. Other devices connect just fine, no settings on the router changed when this started happening. Didn't fiddle with any settings on the phone neither. I can connect to free wifi APs just fine.
What I've tried:
Dialing *#0011# and from service mode disabling wifi power saving feature.
Using all possible encryption combinations on the router (Open - no password, WEP, WPA-PSK AES and/or TKIP, WPA2-PSK AES and/or TKIP or both WPA and WPA2 at the same time), switching channels, disabling 802.11n mode.
Using some modded wpa_supplicant files from this thread.
Using a bad password just to get a different error.
Downloading some other wifi connectors from the Play Store including Wifi Connection Manager which claims to "Fix device Wi-Fi problems." by cleaning the stored wifi config files and maybe something more.
Flashed Omega v10 ROM with Perseus kernel.
All these things and basically any combinations of them worked to no avail. And the only thing that helped was being very close to the router. That way I manage to connect but moving a couple of meters away, like to a nearby room, and it starts giving the same error even though the network strength is still full at that point.
My thoughts:
I saw a similar issue at a couple of places including a similar thread last active dec 23rd, Android issues on code.google.com and androidforums, but no solutions found there worked. Also comparing how my old original Note and an even older LG P500 perform, the wifi signal is obviously weaker on the Note 2. My area is not heavy on wifi networks, so my guess is there's something wrong with wifi drivers or configuration. Sooooo.... What can I do to remedy this issue and also is there any way to beef up my wifi in the process?
Click to expand...
Click to collapse
I had somewhat the same issue. Autentication error.Even though WIfi worked properly on my Galaxy y.
From v9, I flashed v6 Omega and then everything was working fine. So go ahead and flash Omega v6.
And after that did you go back to a Jelly Bean ROM?
Edit: at first I figured omega v6 wasn't JB, but then I checked... For the peace on my mind I'll try flashing Omega v6 later today.
OrangGeeGee said:
And after that did you go back to a Jelly Bean ROM?
Click to expand...
Click to collapse
When I went to v6, all was working well. But when v10 was released,i flashed it,hopiing that the wifi issue is not there but alas same result.
Before flashing,I made a backup of my wifi folder found in root folder /etc/wifi .
After flashing v10, and overwriting the wifi folder with the one that i had backed up, the issue was solved even on 4.1.2 for me.
Worth a try mate.
Do report back.
zeeshanonlyme said:
When I went to v6, all was working well. But when v10 was released,i flashed it,hopiing that the wifi issue is not there but alas same result.
Before flashing,I made a backup of my wifi folder found in root folder /etc/wifi .
After flashing v10, and overwriting the wifi folder with the one that i had backed up, the issue was solved even on 4.1.2 for me.
Worth a try mate.
Do report back.
Click to expand...
Click to collapse
Sounds very interesting. Will report Dunno if an upcoming exam is more important than solving this issue now
OrangGeeGee said:
Sounds very interesting. Will report Dunno if an upcoming exam is more important than solving this issue now
Click to expand...
Click to collapse
The curiosity will hamper your exam!
Is it today?
Well there's 24 hours left, but work and catch-up for half a year is no small feat
To follow up, did flashing Omega v6 work?
i'm really keen to know as I am having the problem currently.
Authentication Problem Wifi - solved for me
Hi folks - I had the same issue with my Galaxy Note I717 (it's the AT&T Note 1) that I got yesterday. I have no problem with my T959 Vibrant to connect to my router at all. But the Note always gave me the authentication problem. So I took it with me to work today and no problems at all to connect to Wifi over there - everything just worked fine.
Back at home - same issue. So I was thinking about to reset my router when I saw this button on it's side and I remembered that I had read something in the settings of my phone.
So that's what I did: When choosing the network on the phone I went to advanced settings. WPS - here I choose Push Button. After that I pushed the button on my router and voila everything worked as supposed.
After switching Wifi off and back on there was no authentication problem anymore. So to confirm the whole thing I let the phone forget the connection and I had the same authentication problem. After choosing WPS "push button" and pushing the button on the router everything worked again.
I don't know - maybe it's just basics for a lot of guys here, but I was glad to figure that out by myself and maybe it helps someone else.
In the case that it might be important - my Note runs stock ICS 4.0.4, stock kernel. is rooted and unlocked. The Vibrant runs ICS Passion V13.1 and Kernel Kiss Yum Yum Good #2. The router is a D-Link DIR 655 Wireless N
Following up the thread:
No, flashing omega v6 didn't work for me.
What I found out is actually 5 GHz band routers work just fine (for example at my university) and all the 2.4 GHz ones give the same error if I'm not close enough to them (something like 5 meters with straight visibility and 2 meters behind closed doors with my home router Comtrend WAP 5813n).
I have called Samsung's Warranty Center to ask for assistance and since we don't have official Samsung service centers in Lithuania, they told me partnered service centers might just return the phone to me as it is and so they would call me when they found out more about this issue (that was almost 2 weeks ago). Will call them again tomorrow and will post any updates if the story develops.
EDIT: After talking to them they apologized for taking so long and assured me I was not forgotten and the issue was forwarded to UK because they have no records/info about it here in Lithuania. Strange thing is I still have my phone, they didn't even wanna check it out.
Note 2 wireless issues
Lads I tried EVERYTHING to get connection working after it dropped on me after a month. Done everything I have read on every forum. EVERYTHING. All other Samsung devices work fine except this note 2! One other odd thing I discovered. It connects fine to any modem or roster fine then when try again on each it won't. You tell me guys? I had it with this issue. Help before I chuck it in Port Phillip Bay!
Hello Jumbo,
i had the same problem and read a lot threads about this error message.
For me it looks like not all who get this error have the same problem.
Some wrote that they fixed it by
- exchanging the wifi folder with the one from 4.1.1..
- flashed a different kernel
- downgraded to 4.1.2
- changed wifi energy saving stuff
- messed around with their routers
and so on..
I also did all this stuff but with no success..
In my case I figured out that
- the same problem exist on 3 different routers (so it couldn't be a router issue)
- the wifi speed (when I sometimes got connected) kept falling from 65MBit down to 5MBit
and by having a wifi connection, I couldn't reach any webpage.
- then I recognised, that I only had a working connection, when I was close
to my router, like 1 or 2 meters without anything between us. In this case
I had no problems with authentication and to surf on the web.
I decided to send my Note2 in for a repair, and guess what... They changed my
Mainboard and since then, everything is back to work..
How long did it take for the repair? I can't imagine being without my phone for an extended period....
I know, it's an addiction, but I'm ok with that..
Steve
I have an identical issue with my S3 GT-I9300
For a totally reliable wifi connection, I've had to site the cradle for the phone on top of my router!
Am out of warranty, so if anyone finds a fix for this that does not involve a mainboard change...
(My first post on this site- I just wish it had been a fix rather than a query)
fuzzer said:
How long did it take for the repair? I can't imagine being without my phone for an extended period....
I know, it's an addiction, but I'm ok with that..
Steve
Click to expand...
Click to collapse
Sorry for the late answer.
My repair took 1 week...
shipped it to w-support on Monday and got it back Saturday.
I was really happy with w-support here in Germany.
I've reset my device to stock and so far it's been sitting @ warranty center for a week, no answer about the roots of the problem yet..
May have found a solution
Hi,
I had the similar problem. With me it started happening after I changed to a Zyxel modem. After some investigation I noticed that in the Zyxel the default gateway is set at 192.168.1.254 whereas most other brands use 192.168.1.1.
Have an inkling that Android doesn't play nice with non-192.168.1.1 gateways.
So changed this in the router settings.
To be sure I also allocated fixed IP on the LAN to my devices and made sure that in the advanced settings of my WiFi network on the Android device I made sure the primary and secondary DNS addresses matched those that the router uses.
Oh.. And to top it all off I fixed the broadcast channel of the router to channel 11 (Probably best you use an app like WiFi Analyser from the Play Store to find the channel that works best for you)
This seems to have solved it for me for now. (I know, not a very scientific method, but got fed up with trying to isolate the culprit)
BTW. Am running (1) Galaxy Note on latest stock ROM (rooted though) (2) Galaxy Tab 2 7" (stock JB ROM - non rooted).
Hope this helps..
Sounds so strange that gateways and channels did it for you. I've tried to change channels on my router with no results. Also I have tried way too many routers before I decided router settings were not a problem. I guess we may have different kind of hardware/software faults resulting in same error message.
OrangGeeGee said:
Sounds so strange that gateways and channels did it for you. I've tried to change channels on my router with no results. Also I have tried way too many routers before I decided router settings were not a problem. I guess we may have different kind of hardware/software faults resulting in same error message.
Click to expand...
Click to collapse
I know. It is weird.
Mind you only a few hours have passed since my changes. I'll keep an eye on it if it reverts to it's old state.
Ok.
Had the same issue again this morning, but oddly enough, once it connects, it stays connected. Also when the phone is put to sleep.
Sent from my GT-N7000 using xda app-developers app
so, I've read around here on the XDA forum about problems with wifi connectivity where we have full bars for wifi but they are gray and you are not getting out. many describe my situation but I've not seen any real solutions...
my problem is that I can connect to my wifi router without issue but then a random amount of time later, sometimes fairly quickly and sometimes it's hours later, I will pick up the phone and see full bars but they are gray and I'm not getting out. I can try opening a terminal window and pinging the gateway/dns servers and can't even reach the gateway.
things I have tried:
- turned off MAC filtering on the wifi AP
- switched from a 5 GHZ wifi on the AP to 2.4 GHZ net on the AP and vice versa
- manually set the phone wifi preference to one or the other (5 or 2.4)
- battery pull on the phone
- delete network settings for my AP and reconfigure
I have not yet tried a static IP config on the phone but I can easily try that... {edited to add} well, I tried static config and that didn't help at all...
one other tidbit of info, I have a work Blackberry with wifi and it never loses wifi connectivity so this is a problem unique to my Nexus.
I'm running Cyanogen 10.0.0-toro and no, I haven't tried a full wipe and reload yet.
thoughts or suggestions?
I'm not trying to threadjack here, but I just wanted to share my experiences.
I've been have the exact same thing happen to my phone (Nexus maguro). I've tried every JB rom I could find, several different kernels and my wifi eventually always goes grey on me. All network activities stop. I'm back on stock everything right now and it still happens.
It happens on my home wifi as well as work wifi.
I'm about to puttstock ICS on my phone and try that out for a couple days.
Anyway, good luck with your problems, i'm going to follow this thread in hopes you'll get a solution that may help me.
If I do figure anything out i'll post back.
jrmacarthur said:
I'm not trying to threadjack here, but I just wanted to share my experiences.
I've been have the exact same thing happen to my phone (Nexus maguro). I've tried every JB rom I could find, several different kernels and my wifi eventually always goes grey on me. All network activities stop. I'm back on stock everything right now and it still happens.
It happens on my home wifi as well as work wifi.
I'm about to puttstock ICS on my phone and try that out for a couple days.
Anyway, good luck with your problems, i'm going to follow this thread in hopes you'll get a solution that may help me.
If I do figure anything out i'll post back.
Click to expand...
Click to collapse
seems that this is a topic that has been posted on a bit over time with no real single culprit or fix. I'll post back if I figure anything out... I know in the Cyanogen thread, I saw info that stated that the MAC address of the phone was changing and I'm going to try and determine if that is happening to mine.
I have the same issue. Sometimes even when i pick up the phone, if i look fast enough i see that the Wi-Fi bars weren't even there! Thats only 1 out of 5 times though. The other time its usually just grey bars. Sometimes it actually will click back and they'll flash to blue and grey 2-3 times and then go solid blue. Then sometimes like you, they'll stay grey. I've tried everything too...reverting to stock, Different kernels, ROMs, routers, static IP, 2.4 or 5ghz, full auto mode. The only fix that makes it a little more reliable, is using Wi-Fi PM Fast. But even that, is not reliable. I'd say its about 50% reliable then, for a huge sacrfice in battery life. For me i've noticed this started to happen with 4.2. Before that i never had a problem. All other devices though no problem. My Nexus 7 is just fine. But the galaxy nexus, no matter what router or where i am, the Wi-Fi is totally unreliable. For me, it happens within 2 minutes that it will disconnect most times. Then 1 in 10 times it'll be fine for 10 hours.
In all honesty, i've given up. Just come to deal with it. Use mobile networks when i'm not needing to download. I can download files and stream music just fine too. If there is traffic going through, it never disconnects. But when its just sitting there without traffic, it disconnects, or, loses connection to google servers i should say.
well that's not good to hear...
I installed stock 4.0.4 a couple days ago and have not had my wifi go grey on me yet.
Sent from my Galaxy Nexus using Tapatalk 2
jrmacarthur said:
I installed stock 4.0.4 a couple days ago and have not had my wifi go grey on me yet.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
yeah, I love Cyanogen so not willing to go back to stock... waiting for them to finish 10.1 and I guess I'll see how it behaves then.
Hi all,
Just to say that I have the same problem. I have been upgraded from ICS to 4.2 and nothing had happened but I had to downgrade to 4.1.1 (AOKP Build 4) due to other issues and after that I started notice the WiFi problem.
At first I thought it was when the screen went off, but I has happened with screen on too. I have to turn WiFi off and the back on to connect properly again, very annoying.
As I said I started noticing this after I downgraded, but then again, I had used AOKP 4.1.1 before without this issue. I think that it is time to change my phone :/
tgeery said:
so, I've read around here on the XDA forum about problems with wifi connectivity where we have full bars for wifi but they are gray and you are not getting out. many describe my situation but I've not seen any real solutions...
my problem is that I can connect to my wifi router without issue but then a random amount of time later, sometimes fairly quickly and sometimes it's hours later, I will pick up the phone and see full bars but they are gray and I'm not getting out. I can try opening a terminal window and pinging the gateway/dns servers and can't even reach the gateway.
things I have tried:
- turned off MAC filtering on the wifi AP
- switched from a 5 GHZ wifi on the AP to 2.4 GHZ net on the AP and vice versa
- manually set the phone wifi preference to one or the other (5 or 2.4)
- battery pull on the phone
- delete network settings for my AP and reconfigure
I have not yet tried a static IP config on the phone but I can easily try that... {edited to add} well, I tried static config and that didn't help at all...
one other tidbit of info, I have a work Blackberry with wifi and it never loses wifi connectivity so this is a problem unique to my Nexus.
I'm running Cyanogen 10.0.0-toro and no, I haven't tried a full wipe and reload yet.
thoughts or suggestions?
Click to expand...
Click to collapse
I'm on Muzzy 4.2.2 and I'm currently having the same problem. It's not a new problem since I remember having it months ago (disabled my phone's WiFi because I kept missing emails and other notifications - grew tired of dealing with it). I thought it was my router, so I swapped it with a newer one recently, but it carried forward (old router was TRENDnet Draft N and the new one is ASUS RT-N66U).
I would like to know how to properly troubleshoot this problem.
I'm glad I didnt have to create a thread for this. I have been facing this problem quite a lot. I can confirm that WiFi works absolutely fine until 4.1.2, whether it is stock or CM10 (I havent tried the other ROMs yet). I have faced this problem only from 4.2. It still exists on 4.2.2. Happens on all the ROMs I have tried till now including CM10.1 nightly as well as the stock factory image.
When the phone is sleeping, it seems to lose WiFi connectivity and when woken up, the WiFi bars is grey though it is full. If I am very lucky, it will turn blue automatically. Most of the times, I have to switch WiFi off and back on for it to connect properly.
Anyone knows the root cause for this? In case this has been discussed in any other thread?
subhramani said:
I'm glad I didnt have to create a thread for this. I have been facing this problem quite a lot. I can confirm that WiFi works absolutely fine until 4.1.2, whether it is stock or CM10 (I havent tried the other ROMs yet). I have faced this problem only from 4.2. It still exists on 4.2.2. Happens on all the ROMs I have tried till now including CM10.1 nightly as well as the stock factory image.
When the phone is sleeping, it seems to lose WiFi connectivity and when woken up, the WiFi bars is grey though it is full. If I am very lucky, it will turn blue automatically. Most of the times, I have to switch WiFi off and back on for it to connect properly.
Anyone knows the root cause for this? In case this has been discussed in any other thread?
Click to expand...
Click to collapse
have you posted this information over in any of the threads where the developers are working such as Cyanogen in an effort to bring this issue to the forefront for more visibility?
I have had those wifi problems with every android version and rom I had on my GNex as far as I can remember.
Sometimes it will be able to reconnect but sometimes I have to disable and re-enable wifi to get it back.
I too thought that it might have been my crappy router as I have had multiple problems with it over the years (some Linksys router).
This is really annoying because it won't receive any e-mails until I randomly decide to have a look at my phone. :/
Fabur87 said:
I have had those wifi problems with every android version and rom I had on my GNex as far as I can remember.
Sometimes it will be able to reconnect but sometimes I have to disable and re-enable wifi to get it back.
I too thought that it might have been my crappy router as I have had multiple problems with it over the years (some Linksys router).
This is really annoying because it won't receive any e-mails until I randomly decide to have a look at my phone. :/
Click to expand...
Click to collapse
trust me, I understand your frustration... some days, I can go almost all day without loosing wifi data throughput and other days it won't last 10 minutes without going to gray bars.
unfortunately, no one is sharing any fixes which tells me that no one has a good handle on the problem.
Same issue for me on stock Android 4.2.2. Leave WiFi on overnight and when I wake up its connected to WiFi but gray bars...
Sent from my Galaxy Nexus using xda premium
The update to 4.2.2 drivers have fixed all WiFi issues for me. For the first time since 4.1 I can now use WiFi optimization now. And WiFi is fully reliable.
tgeery said:
so, I've read around here on the XDA forum about problems with wifi connectivity where we have full bars for wifi but they are gray and you are not getting out. many describe my situation but I've not seen any real solutions...
my problem is that I can connect to my wifi router without issue but then a random amount of time later, sometimes fairly quickly and sometimes it's hours later, I will pick up the phone and see full bars but they are gray and I'm not getting out. I can try opening a terminal window and pinging the gateway/dns servers and can't even reach the gateway.
things I have tried:
- turned off MAC filtering on the wifi AP
- switched from a 5 GHZ wifi on the AP to 2.4 GHZ net on the AP and vice versa
- manually set the phone wifi preference to one or the other (5 or 2.4)
- battery pull on the phone
- delete network settings for my AP and reconfigure
I have not yet tried a static IP config on the phone but I can easily try that... {edited to add} well, I tried static config and that didn't help at all...
one other tidbit of info, I have a work Blackberry with wifi and it never loses wifi connectivity so this is a problem unique to my Nexus.
I'm running Cyanogen 10.0.0-toro and no, I haven't tried a full wipe and reload yet.
thoughts or suggestions?
Click to expand...
Click to collapse
same thing happened to me on toroplus sourcery 5.1, after trying everything i could think of and talking to one of the devs, i finally did a fresh download of rom and gapps. wiped cache,wiped dalvik, factory reset, wipe system, deleted android folder off of storage then installed the fresh download of rom and gapps and its been working great for me since. hope this helps.
M3drvr said:
The update to 4.2.2 drivers have fixed all WiFi issues for me. For the first time since 4.1 I can now use WiFi optimization now. And WiFi is fully reliable.
Click to expand...
Click to collapse
Can you elaborate on this? I've flashed 5 different modems and still get this problem... it happens to my cell service bars, as well. Would love to know what the cause is.
aqcon said:
Can you elaborate on this? I've flashed 5 different modems and still get this problem... it happens to my cell service bars, as well. Would love to know what the cause is.
Click to expand...
Click to collapse
i just know ever since moving to a 4.2.2 kernel that has the 4.2.2 drivers my wifi has been stable. I know there was a post in the anarkia thread with the ak kernel that had the drivers. but i believe most any 4.2.2 kernel would have them implemented. i do have the newest bootloader and radio too. but i know as soon add i got the 4.2.2 drivers all issues were resolved wifi wise. of course i think if you have a 4.2.2 kennel you'll have them.
M3drvr said:
The update to 4.2.2 drivers have fixed all WiFi issues for me. For the first time since 4.1 I can now use WiFi optimization now. And WiFi is fully reliable.
Click to expand...
Click to collapse
I'm looking forward to that update - I've been watching the Cyanogen threads for when I think the 10.1 has matured enough to become my daily driver... good to know you've had positive results!
Temporary solution
me facing same issues , Solution would be to use an app called wifi fixer by zanish-g1 from the play store ...
it worked for me !! :good:
Hey guys. I'm having a very weird WiFi issue on my A520F.
Today the WiFi froze. It wouldn't turn off when I switched it off. After I while it turned off but took ages to turn it on again.
I factory reseted the device because I thought it was a software issue. It didn't work - after the first boot it was the same.
After a while after this, the WiFi started working again, but only for a period of time, then it would just freeze again for apparently no reason. Switching it off and on solves the issue for a while, then it freezes again saying that my WiFi is limited.
I can't take any logs since I'm not rooted (and don't have a PC to use ADB), and this is really scaring me since it happened out of nowhere. An hour before this started happening WiFi was working just fine.
I haven't installed anything unusual today, just connected for the first time on a new, but trusted, WiFi.
I've also reseted my WiFi router to its factory settings, thinking that it could be the issue, but the problem persisted. My Chromecast works just fine on the very same network.
Did this happened to anyone before? I've tried to root my phone a while back and, since it didn't worked out, I gave up and flashed the latest firmware from my country. This phone originally came with German firmware in it and I flashed it to a Brazilian one, which is the one I'm using and had no issues so far.
Can this be a hardware issue?
Thanks in advance!
So I guess I'll end up solving this on the weirdest way I can imagine.
After I posted I logged into my modem's settings and took a log at its logs. Seems that the moment this issue started to happen was near the time that the DNS server my modem was using started to fail.
I never thought that such a simple thing could mess this things like this. I mean, the DNS server is essential, but how that could freeze my phone's WiFi? Either way, I changed the DNS to Google's DNS and since then I haven't had any freeze or disconnetion. I'll test a bit more to see if the problem is gone.
Well, I do believe that I found the root of the problem.
As some of you may know, modems tend to stay on for a very long period of time (no one wants to lose internet connection, so we rarely reboot then), and for reasons I don't know (and as a tech support guy I've seen this happen A LOT) they freeze sometimes and only work again after being completely turned off and on.
Since the issue started again when I was messing with the modem settings (trying to change the DNS again to see if the problem would return), I decided to give my modem a few minutes of rest.
After that, I've powered it on again and went through the initial setup (my ISP provides an simple wizard when you first connect to the WiFi) and up until now I'm not having issues.
I'll wait a few more hours to report again, but so far so good.
So it seems that giving those things a few minutes rest every month or so isn't a bad thing at all.