Develop Bugs

[Q] wifi "avoided poor internet connection", screeoff kills connection

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.

Stock Jelly Bean - Battery Problem - Awake Issues

Hi folks,
I am experiencing a battery drain problem after upgrading my Gnex-gsm via OTA to 4.1.1 (from 4.0.4). I thought that is due to some applications or settings so factory default my device. The only application I installed was Cpu Spy (and better battery stats) to find the culprit. Result was still the same. I googled similar issues introduced by jelly bean but couldn't find a permanent and satisfying solution. Here are the details:
- I had a stock rom/kernel when I was at 4.0.4 (flashed android factory image manually) and didn't see any service/app waking my device like this.
- I upgraded via single OTA to 4.1.1 and started experiencing battery drain to high awake times (%50ish deep sleep, %50ish 350+700mhz). This is not affected after I factory default/wipe cache (as well as dalvik cache).
- After testing several combinations (like disabling google backup service, turning off google sync., disabling gps etc.) the only way to stop this drain is either disabling WiFi (my 3g data packet is still active) or leaving WiFi ON but not connecting it to any gateway. I haven't changed my gateway and my friend with the very same Jelly Bean Gnex is connected to it without having any battery drain problem.
- I wiped my phone 4-5 times and even tried setting up without any Google account, the result is same.
- I flashed latest franco kernel for jelly bean, nothing has changed.
- I modified all wifi options (Avoiding poor connections (I do have good wifi and 3g reception) and let wifi sleep during sleep) but that havent changed things much.
According to my tests, RILJ, GTALK_ASYNC and connectivity service are causing high awake times (their order changes time to time).
You can see my attachments for details. The only thing I haven't tried is flashing a jelly bean custom rom but I am leaving it for the last resort.
I will be really glad if you can put some reasoning about this issue because it is making me crazy

http://forum.xda-developers.com/wiki/Wakelocks#RILJ
Dialer RILJ is the userland counterpart of the RIL (radio interface lib). RILJ handles whatever the phone need to tell or get from the RIL = phone, e.g. dialing but also coarse location.
Click to expand...
Click to collapse
I would try disabling location services to see if that's causing your issue. I noted worse battery life with location services enabled.

Hi Cilraaz,
I had tried that before but retried again. Unfortunately the amount of wakelocks have not been reduced.
Thanks for the references by the way
Cilraaz said:
http://forum.xda-developers.com/wiki/Wakelocks#RILJ
I would try disabling location services to see if that's causing your issue. I noted worse battery life with location services enabled.
Click to expand...
Click to collapse

Using the JB + stock kernel Franco realized that consumption is very high, especially with the screen connected ...
I removed the location data and still got the high consumption and had no decrease in power consumption ..

Maaaan... I am suffering from the same issue with jelly bean stock...
I have tried all the things u mentioned nothing helped.
The strange thing is that it's only consuming on wifi when it should drain less power.
I would be so happy to find a solution...
Sent from my Galaxy Nexus using Tapatalk 2

Tonight I did a test with all syncs and 3g enabled and now it totally seems that it's definitely the wifi that keeps waking up the device... Grrrrrrrrrrrrr
Tapatalk 2-vel küldve az én Galaxy Nexus-ről

It is clear that we are experiencing the very same problem. The problem is due to wifi connection for sure.
I guess one of the system processes do keep trying to reach a server or something if and only if wifi connection is valid.
I have tried 2 different ROMS (one is pure AOSP and the other one is liquidsmooth alpha w/ trinity kernel). Unfortunately the problem persists
I am going to investigate the problem and use a sniffer to track wireless activity.
The thing is this is happening even device is fully formatted (/data /cache /system /sdcard and dalvik cache)
Am I missing any partitions that may affect this and remained dirty?. Hope anyone have any idea.

Ok, after diagnosing the sniffer I find that JellyBean Gnex keeps reconnecting to the access point even tough it is not sending deauth/disassoc. It is not the case with 4.0.4 (probably changes in wpa_supplicant caused this).
Each reconnection request triggers RILJ/Gtalk async. bla bla and causing device to stay awake. I will check wpa_supplicant logs and find out the reason behind the reconnection decision.
Using a cisco gateway (with same wireless settings) fixes the problem.

Not so in my case. Very less awake times and excellent battery life.
Sent from my Galaxy Nexus using Tapatalk 2

Yup that's very strange actually that not all Gnex owners experience this issue. Would be great to find the difference between those devices and ours.
Sent from my Galaxy Nexus using Tapatalk 2

cankavera said:
Ok, after diagnosing the sniffer I find that JellyBean Gnex keeps reconnecting to the access point even tough it is not sending deauth/disassoc. It is not the case with 4.0.4 (probably changes in wpa_supplicant caused this).
Each reconnection request triggers RILJ/Gtalk async. bla bla and causing device to stay awake. I will check wpa_supplicant logs and find out the reason behind the reconnection decision.
Using a cisco gateway (with same wireless settings) fixes the problem.
Click to expand...
Click to collapse
Yeah man that sounds like a progress
Sent from my Galaxy Nexus using Tapatalk 2

You could always try adding the following to build.prop:
Code:
wifi.supplicant_scan_interval=1800
That would make your wifi only scan for a stronger AP every 30 minutes.

Thanks for the suggestion Cilraaz, unfortunately it didn't help. I need a way to increase debug level of wpa_supplicant (using wpa_cli level didnt work).
Dmesg gives a hint though. When device is trying to sleep, a kernel message (no IPv6 router) triggers disconnect (and it reconnects right after). This happens continuously every 10-20secs and waking the device.
<7>[ 86.163146] wlan0: no IPv6 routers present
<3>[ 91.762573] CFG80211-ERROR) wl_notify_connect_status : link down, calling cfg80211_disconnected with deauth_reason:0
<6>[ 91.772399] cfg80211: Calling CRDA to update world regulatory domain
<4>[ 93.140258] wl_bss_connect_done succeeded
<6>[ 93.191009] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
<4>[ 93.349090] wl_bss_connect_done succeeded
Why the hell device needs a IPv6 router? It shoudl be ok with IPv4.
Cilraaz said:
You could always try adding the following to build.prop:
Code:
wifi.supplicant_scan_interval=1800
That would make your wifi only scan for a stronger AP every 30 minutes.
Click to expand...
Click to collapse

Wow. Hope Google is heading this way as well...
Sent from my Galaxy Nexus using Tapatalk 2

Avoid poor connections
Disabling "Avoid poor connections" from Wi-Fi settings fixed the problem for me

laithmurad said:
Disabling "Avoid poor connections" from Wi-Fi settings fixed the problem for me
Click to expand...
Click to collapse
Tried this right now but didn't help for me that's soooooo frustrating!
Sent from my Galaxy Nexus using Tapatalk 2

Anyone having a progress here?
Would be good to reach Google and ask their opinion about that...

That was the first thing I had tried but reconnections are not happening due to poor connection. Signal strength is pretty good (around -40 -50dBm)
and it is still happening.
I also flashed 4.1.1 factory image (as well as AOKP, CM10 and one more jelly bean custom firmware) after wiping everything and I am still experiencing the problem.
I am going to try using 4.0.4 wpa_supplicant binary in a 4.1.1 rom. Albeit, I suspect the problem is introduced by new kernel. (I am not sure 4.0.4 kernel is compatible with 4.1.1 rom, anyone have any ideas?)
laithmurad said:
Disabling "Avoid poor connections" from Wi-Fi settings fixed the problem for me
Click to expand...
Click to collapse

cankavera said:
That was the first thing I had tried but reconnections are not happening due to poor connection. Signal strength is pretty good (around -40 -50dBm)
and it is still happening.
I also flashed 4.1.1 factory image (as well as AOKP, CM10 and one more jelly bean custom firmware) after wiping everything and I am still experiencing the problem.
I am going to try using 4.0.4 wpa_supplicant binary in a 4.1.1 rom. Albeit, I suspect the problem is introduced by new kernel. (I am not sure 4.0.4 kernel is compatible with 4.1.1 rom, anyone have any ideas?)
Click to expand...
Click to collapse
This options was 1st introduced in 4.0.1 and it was terrible for me when enabled, Google removed it since 4.0.2, and now its back on 4.1.1, I only get like 10 Hours while this option is checked, when unchecked battery lasts more than 22 Hours, I guess what happens is that Wi-Fi keeps disconnecting and switching to 3G, then goes back to Wi-Fi frequently.

Cankavera!
Somehow it seems I am unable to send you a PM.
Can you confirm that replacing your router fixed the issue with high waked up times?
I am using a quite old MSI RG60 router so if you say its enough to replace it I will do it...

[Q] Lose wifi down after screen off?

I have been having this problem for about the last 3 days where I lose the downstream from my wifi after the screen turns off. The wifi is still connected and blue, and within the wifi bars there are the two grey arrows for up and down. The up arrow still flashes meaning the wifi upload is still connected, but the download arrow no longer shows. I'm able to regain the wifi downstream by toggling wifi off and then back on. As long as I don't let my phone go into sleep then I maintain wifi connectivity, but as soon as it goes into sleep I will have to toggle wfi to regain full connection again.
I'm running AOKP JB build 1 with franco kernel nightly 283. I haven't made any recent changes to my router or wifi settings. It seems to have just started happening in the last 2-3 days. My first guess is that there were some wifi issues with recent Google wifi drivers that were included in the franco kernel. Apparently the more recent nightlies reverted the wifi drivers to avoid the problems, but maybe I still have the old drivers despite running a more recent build? Like the got stuck or something on the drivers with problems. I only suggest this because I was reading around in other threads were someone mentioned if you flashed a kernel with new drivers and then another kernel with the old drivers, the only way to actually revert the drivers is to wipe and flash a fresh ROM.
However, if anyone is aware of any other possible solutions then I'm open to suggestions. Oh yeah, before it's mentioned I also have wifi set to always on, and the router is running WPA2 (AES) and the phone has a static IP. I realize this is most likely a kernel problem since that's really all that's changed in the last few days (flashing new nightlies) but I'm unable to post in the development threads and reading through his thread, no one else seems to be having this problem

If you think it could be kernel related, why not flash a stable Franco release?
You could also just upgrade to aokp build 4 then see if wifi is properly, then flash the kernel, there might be your answer.
Sent from my Galaxy Nexus using Tapatalk 2

Fire n mage said:
If you think it could be kernel related, why not flash a stable Franco release?
You could also just upgrade to aokp build 4 then see if wifi is properly, then flash the kernel, there might be your answer.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I've tried reverting to an older nightly, or even to the stable Milestone 5 but with no affect. That's why I'm wondering if it's possible once the updated wifi drivers are flashed, even flashing a different Kernel with the older drivers won't overwrite the drivers since they aren't the most up-to-date.
As far as flashing the newest build of AOKP, I was planning on doing that this weekend to see if it helps. But until then I was hoping someone here may have some answers, because even flashing a new ROM doesn't guarantee a fix.

I'm using nightly 282 of the French Revolution HD 6.1.0 +, and have not had this problem. I was having this problem one day that, with the CM10 Nightly. But I decided as follows:
Settings / Wifi / Advanced / Keep Wifi during inactivity.
Test to see ae of the right.

Settings > WiFi > Menu(the 3 dots) > Advance > Keep WiFi on during sleep > profit

Franco setting
I think your problem is releated to Wifi Driver, of couse wifi driver goes to battery safe mode when you screenoff
It's not releated to your router, for simple reason this is phone problem
It's can be ( mach do it first ) settings, upto android 4x series wifi have wifi autodisconnect on screenoff ( using data instead or nothing ), theorically data cause less battery drain than wifi, this is the sense of this value, and it's to prefer instead juice defender or another non-system app.
You can always disable wifi_pm on franco using
Code:
echo 0 > /sys/module/bcmdhd/parameters/wifi_pm
This dont allow to wifi driver screenoff modes ( less wireless performance -> less battery usage ) but increase battery drain from wireless on screenoff

Mobile data randomly not working...

Within the last couple of weeks, I have to enable/disable airplane mode to get my data to work. It's random throughout the day. I've checked to make sure mobile data is enabled when it's not working, and it is. It shows 4G at the top, but just won't send/receive data. I wasn't having this problem when I first upgraded to JB, so I'm not sure what's going one. Anybody have similar problems/tips?

stbtigerr said:
Within the last couple of weeks, I have to enable/disable airplane mode to get my data to work. It's random throughout the day. I've checked to make sure mobile data is enabled when it's not working, and it is. It shows 4G at the top, but just won't send/receive data. I wasn't having this problem when I first upgraded to JB, so I'm not sure what's going one. Anybody have similar problems/tips?
Click to expand...
Click to collapse
Are you running a ROM other than stock? There have been hiccups similar to this on some AOSP ROMs, but I can't immediately think of anything that would be causing this on a (mostly?) stock ROM.

smelenchuk said:
Are you running a ROM other than stock? There have been hiccups similar to this on some AOSP ROMs, but I can't immediately think of anything that would be causing this on a (mostly?) stock ROM.
Click to expand...
Click to collapse
Sorry, I meant to stay I'm completely stock in the OP.

common issue with note II and my GSIII
looks like the same issue is happening on the Note II - thread.
For me, it seems like it happens more frequently when I leave a wifi connection; I have to enable airplane mode & disable it to connect to 4G LTE (band 14). I'm not rooted, so I can't run the logger that's suggested in the Note II thread. FWIW: it appears to affect me with or without Onavo VPN running.
Any suggestions would be helpful. My next thought is to figure out a way to ping/test the connection to the AT&T tower/gateway next time I run into the issue before using the airplane mode fix.
my GSIII config:
AT&T version
Jelly Bean 4.1.1 Stock (Samsung) ROM
Kernel 3.0.31-274808
Baseband I747UCDLK3

[Q] losing wifi connectivity- full bars but all gray

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: