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.

[UPDATED: SOLVED?] Google Services causing weird battery drain

Interested in solving a real puzzler? Then read on!
The patient: a rooted, otherwise stock Jelly Bean (JRO03C 4.1.1) Galaxy Nexus. Being used as an everyday phone (and a bit of development).
The symptoms: Excessive battery drain by "Google Services", but ONLY on my home Wifi network!
This is where things get weird: on 3G, on my company's work Wifi, and without network, the battery drain is absent. I can *reliably* cause Google Services to start hammering the wakelocks, and stop them, just by moving to a different Wifi hotspot. There's NO change in functionality: Google Talk, Play Store, and network access work exactly the same. Push messages seem to come in normally too, but I haven't tested that very well. There's no configuration change whatsoever.
More details: After installing BetterBatteryStats, I've gotten a better look at the wakelock draining the battery. After gathering stats for 25-30 minutes, the following wakelock is the top user:
Code:
GTALK_ASYNC_CONN_com.google.android.gsf.gtalkservice.AndroidEndpoint (Google Services): 7 m 47 s (467 s) Count:786 30.3%
So, I decided to check logcat for "GTalkService" messages, and see if there's a major difference between work (good) and home (bad).
Turns out I get a lot of the following at home, but not at work:
Code:
[ 08-15 17:36:02.719 709: 709 I/GTalkService/c ]
[[email protected]] connect: acct=1000000, state=CONNECTING
[ 08-15 17:36:34.461 709: 1177 E/GTalkService ]
connectionClosed: no XMPPConnection - That's strange!
This is repeated a LOT and looks like it correlates quite well with the wakelock.
I use the phone, and I would hate to wipe it completely: I would really like to get to the bottom of this.
First of all, I'm not 100% sure this is a Galaxy Nexus only problem. It might be Jelly Bean, or ICS, or whatever. Would you suggest I post on the Google Android bug list, where the crickets chirp, and major bugs disappear into a big Python black hole?
Thanks guys! If only for reading this far!
Update 2012-10-02:
OK, I have eliminated my firewall from the equation: obviously I can't necessarily just whack the work's firewall without consequences. Nothing's blocked, and all services on the phone seem to work.
As for other devices: I dug up my old Nexus One (Gingerbread, stock), and upgraded my Transformer Prime to Jelly Bean. Both do not show the error in logcat, and neither have the battery drain issue. Just for kicks, I checked the version of the Google Services Framework on all three:
Samsung Galaxy Nexus: 4.1.1-398337
ASUS Transformer Prime: 4.1.1-438695
HTC Nexus One: 2.3.6
Wanna bet there's a bug in 4.1.1-398337 that got fixed in 4.1.1-438695?
Further update:
I also tried the following with no success:
Delete app data for Google Services Framework (NOT RECOMMENDED!)
Remove Google accounts from the phone.
Re-add Google accounts to the phone.
Update: 2012-10-04
I think I found a workaround. It looks like it's a domino effect thingy that happens here:
1) I've got a Netgear N600 ADSL/Wifi router at home. On my 2.4GHz radio, I set up two access points: one for my stuff and one for guests. I made sure to delete the guest account from all my Wifi equipment to make sure there's no "fighting" or "flapping".
2) It appears that the phone ignores the Wifi-'stay connected while sleeping' setting, or the radio is broken. When the phone goes to sleep, it disconnects from Wifi.
3) When the phone disconnects from wifi, the Google Services Framework lose connection: this causes the phone to wake up.
4) When the phone wakes up, Wifi gets re-established. This makes Google re-connect.
5) The phone goes back to sleep and we return to step #2.
This causes a LOT of wakeups, lost connections and other crap. Since the phone doesn't lose connection when it's awake, it's fricken difficult to debug. Also, it's NOT a signal quality issue. My phone can be right next to the access point and it wouldn't help.
So, could you guys try different access point settings at home? I've heard WMM, QoS and some of the protocols could cause the Galaxy Nexus's radio in Jelly Bean to go a bit wonky.
-- Jan Gutter

jangutter said:
Interested in solving a real puzzler? Then read on!
The patient: a rooted, otherwise stock Jelly Bean (JRO03C 4.1.1) Galaxy Nexus. Being used as an everyday phone (and a bit of development).
The symptoms: Excessive battery drain by "Google Services", but ONLY on my home Wifi network!
This is where things get weird: on 3G, on my company's work Wifi, and without network, the battery drain is absent. I can *reliably* cause Google Services to start hammering the wakelocks, and stop them, just by moving to a different Wifi hotspot. There's NO change in functionality: Google Talk, Play Store, and network access work exactly the same. Push messages seem to come in normally too, but I haven't tested that very well. There's no configuration change whatsoever.
More details: After installing BetterBatteryStats, I've gotten a better look at the wakelock draining the battery. After gathering stats for 25-30 minutes, the following wakelock is the top user:
Code:
GTALK_ASYNC_CONN_com.google.android.gsf.gtalkservice.AndroidEndpoint (Google Services): 7 m 47 s (467 s) Count:786 30.3%
So, I decided to check logcat for "GTalkService" messages, and see if there's a major difference between work (good) and home (bad).
Turns out I get a lot of the following at home, but not at work:
Code:
[ 08-15 17:36:02.719 709: 709 I/GTalkService/c ]
[[email protected]] connect: acct=1000000, state=CONNECTING
[ 08-15 17:36:34.461 709: 1177 E/GTalkService ]
connectionClosed: no XMPPConnection - That's strange!
This is repeated a LOT and looks like it correlates quite well with the wakelock.
I use the phone, and I would hate to wipe it completely: I would really like to get to the bottom of this.
First of all, I'm not 100% sure this is a Galaxy Nexus only problem. It might be Jelly Bean, or ICS, or whatever. Would you suggest I post on the Google Android bug list, where the crickets chirp, and major bugs disappear into a big Python black hole?
Thanks guys! If only for reading this far!
-- Jan Gutter
Click to expand...
Click to collapse
Could it be that your home router's firewill is somehow blocking parts of GTalk traffic, causing it to continuously retry connecting?

Petrovski80 said:
Could it be that your home router's firewill is somehow blocking parts of GTalk traffic, causing it to continuously retry connecting?
Click to expand...
Click to collapse
Nope, I checked that: there's no firewall. At work there is, but it doesn't affect my phone (services are not affected visibly). Google Talk works fine in both situations.

any developments in this? have an s3 which is behaving similarly. my WiFi is always on as I'm usually near a hotspot at work home /gfs.gtalk_async wake lock showing up in better bat stats. been having battery drain issues for a while now and decided it was time to do some research.turned off pretty much every synch/auto backup app on the phone but still draining, not quite as bad, but still seems to struggle to stay asleep for very long!

Exactly the same
cricka15 said:
any developments in this? have an s3 which is behaving similarly. my WiFi is always on as I'm usually near a hotspot at work home /gfs.gtalk_async wake lock showing up in better bat stats. been having battery drain issues for a while now and decided it was time to do some research.turned off pretty much every synch/auto backup app on the phone but still draining, not quite as bad, but still seems to struggle to stay asleep for very long!
Click to expand...
Click to collapse
Does anyone have solved this.. i have got exactly the same situation as Jan. No trouble at work but only at home.

Not affecting ASUS Transformer Prime
Nothing new here, except I also cross-checked with my ASUS Transformer Prime. There's no drain on it, and also no errors in logcat about GTalkService.
I'll post an update once I've checked my trusty old Nexus One out of storage, that'll happen next week, though.

Interesting note about the wifi. I only seem to get this problem during the week at work, on the weekends it doesn't happen that often. I get poor data connection at work and rely on the wifi instead. I'll try to not use the wifi for a day or so and see if the wakelock is reduced. Thanks for the tip, this has been a problem for a while now.
Galaxy s2 on Sprint

sgtlange said:
Interesting note about the wifi. I only seem to get this problem during the week at work, on the weekends it doesn't happen that often. I get poor data connection at work and rely on the wifi instead. I'll try to not use the wifi for a day or so and see if the wakelock is reduced. Thanks for the tip, this has been a problem for a while now.
Galaxy s2 on Sprint
Click to expand...
Click to collapse
Just take note: in general Wifi uses a LOT less battery than 3G. A better test might be to disable Wifi AND sync.
Jan

some decent insightful ideas here. My S3 on official stock based custom has bad drain over wifi. My google services framework version is the 4.1.1-438695 which isn't affected in your case so it's not that.
Better battery stats at first put google maps as the wakelock so I realised it's location service was left on so I turned that off. Then BBS varies and shows different apps and what not causing wakelocks but the drain remains the same.
My router is an Asus with custom linux firmware Tomato with a robust plethora of functions. I updated it yesterday and put the settings back closer to default. I'll have to try disabling WMM and QoS settings as their both already on at the moment. Also the kernel developer i'm on to quote: "Made a change in wifi offload filtering to deny muticast packets but allow multicast DNS packets."
After leaving wifi on last night the drain still remains at about 10% per 3 hours. Compared to before it used to be almost 15% per 3 hours. BBS doesn't show wlan_rx_wake as the top wakelock as most common before as that's down to running for 8 minutes in 9 hours rather than the top around 45 minutes. Instead battery-monitor is the top at a little over half an hour in the 9 hours. Googling battery-monitor shows little useful information but I assume it's like before where Wifi is waking the device and something OS related that turns on with it gets given the wakelock status although its not the trigger.
I'll have to try disabling WMM, QoS, auto-sync and gtalk and see how I go. Hopefully you're right about it being wifi disconnect related and can be fixed.

Infy_AsiX said:
Googling battery-monitor shows little useful information but I assume it's like before where Wifi is waking the device and something OS related that turns on with it gets given the wakelock status although its not the trigger.
Click to expand...
Click to collapse
Have you tried disabling the WiFi Power Save Mode on the S3? From this article:
http://www.s3forums.com/forum/galaxy-s3-general-discussion/1329-wifi-tip.html
1. Open up the Galaxy S3 phone dialer
2. Dial *#0011#
3. Look for the “ServiceMode” screen and press the left menu button
4. Select “WiFi”
5. You should see that the “WiFi Power Save Mode” button is “ON” – turn it “OFF”'
My colleagues with the same phone has serious battery drain until they use that.
Infy_AsiX said:
I'll have to try disabling WMM, QoS, auto-sync and gtalk and see how I go. Hopefully you're right about it being wifi disconnect related and can be fixed.
Click to expand...
Click to collapse
I seem to recall that the Google framework sends/receives a keep-alive packet once every hour or so. LOTS of stuff in the Android framework keep TCP connections open from the server side because otherwise the service provider just kills them. Blame stateful firewalls.
What could be happening here is that the WiFi chip offloads a number of these functions from the main CPU: i.e. it's got a simple TCP offload stack that just queues data for the main CPU to wake up. If the WiFi chip receives a keep-alive TCP packet with no payload, it doesn't bother to wake up the CPU and just absorbs it. If the WiFi chip goes to sleep, rather, it never receives these, the connection dies and the CPU needs to wake up on timeout and re-establish everything (eating battery in the process). It's paradoxically cheaper to keep the WiFi chip running on full power, than to let it go to sleep. This is pure speculation, and only one of many scenarios that might fit the facts.
The S3 has the *option* to change the WiFi sleep-mode from aggressive (default) to a value that lets the entire system use less battery. The Galaxy Nexus doesn't: which means that it may, or may not have the sleep-mode built in. In any case, it seems my router can remotely trigger disconnects when the main CPU is off, and by switching settings on it, I managed to perform a workaround. Unfortunately the Galaxy Nexus (on Jelly Bean, at least) seems to have a serious bug in this respect, and other people are not so lucky: http://code.google.com/p/android/issues/detail?id=35352
It seems that the core issue (WiFi disconnect), causes a knock-on effect, raising Google Services Framework, Android OS and potentially anything that syncs's battery profile.
Jan

Getting good drain now 1% an hour compared to 3%. Seems setting WMM to auto rather than enabled in tomato fixed it. The night before I had it disabled as well as QoS and it was bad as well. I will test further to be certain what's the scenario.
I've got a second S3 that's been suffering as well. Having two to test makes testing much faster. The service menu power save mode off didn't help. It caused strange disconnects with WMM in all states. S3 wifi menu would state poor connection and wouldn't reconnect. Note the S3 already has strange disconnects to begin with I find but in this case it sometimes wouldn't reconnect. Also restarting the phone resets the power save mode to enabled.
Can't find any information on a difference between enabled and auto in tomato WMM. I'll be sure to keep testing.
Sent from my GT-I9300 using Xparent Cyan Tapatalk 2

New Google Services Framework
Hey guys,
looks like Google Services Framework got a version bump on the latest Galaxy Nexus update: it's now listed as version 4.1.2-485486
This is for JZO54K (4.1.2).
It could be that they've fixed the knock-on effect (but the core issue is likely the same, since the radio code is apparently exactly the same).
Jan

I have this same wakelock on my evo 4g lte. Same log error exactly. Only on my works wifi. Problem is eliminated when running a Vpn on the phone. Only caveat Is all the free vpn services seem to disconnect after a period of inactivity.

I know this is an old topic but I had the same drain (30% overnight) on my Galaxy S2.
After weeks of searching and trying different things I found the solution.
Change DTIM value in your router configuration from 1 (default) to 255.
This value is usually in Advanced->Wireless tab on most routers.
Now my phone uses 2% battery overnight with wifi on, sync on instead of 30%.

Rawi666 said:
I know this is an old topic but I had the same drain (30% overnight) on my Galaxy S2.
After weeks of searching and trying different things I found the solution.
Change DTIM value in your router configuration from 1 (default) to 255.
This value is usually in Advanced->Wireless tab on most routers.
Now my phone uses 2% battery overnight with wifi on, sync on instead of 30%.
Click to expand...
Click to collapse
I tried this and got weird results. My phone couldn't connect to my network, but my tablet could (GT 7510) which also experiences the drain issue. How did you come up with the value 255? Any other value I can try? Thanks
Sent from my SGH-T999 using xda premium

SpinTX said:
I tried this and got weird results. My phone couldn't connect to my network, but my tablet could (GT 7510) which also experiences the drain issue. How did you come up with the value 255? Any other value I can try? Thanks
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Try lowering this value to 10 or 8 and see if it helps.

Rawi666 said:
Try lowering this value to 10 or 8 and see if it helps.
Click to expand...
Click to collapse
Thanks, will give it a shot. Also, because of your post, I discovered that toggling wifi on and off stops Google Services from draining. It will still drain, if your wifi is set to turn off, when the device sleeps. I really think you hit the nail on the head, discovering the source of the problem. It's an issue I have been trying to fix for a long time and your post at least got me to toggling the drain. So thanks again!
Sent from my SGH-T999 using xda premium

Would love to he root cause of this... I had the same problem on my s3 and now on the s4.with and without custom roms etc. The problem only is work, and I'm putting it down to some service that the work firewall or something blocks... Only solution I've come up with is turning off the wifi when I'm at work.. Else I get in excess of 15min /hour of wakelock.
All apps etc. Up to date, sync on/off, no difference, all "location" settings turned off.
I give up.

Wifi signal strength!
Whatever Google did to cause a variety of wakelock problems, having a strong wifi signal seems to solve them. Apparently, wakelocks occur when there are unreliable connections to Google's servers.
Kal

keltickal said:
Whatever Google did to cause a variety of wakelock problems, having a strong wifi signal seems to solve them. Apparently, wakelocks occur when there are unreliable connections to Google's servers.
Kal
Click to expand...
Click to collapse
A friend with the nexus 4 and same problem told me to try disabling Google hangouts (formally talk).. Apparently it keeps refreshing itself once ur signed in (and it signs in automatically)... Will experiment tomorrow at work where I get the problem.
Sent from my GT-I9500 using xda premium

[Q] Push notifications delayed on WIFI

I've seen a few similar threads to the one I'm about to make. I've tried different suggestions which I will post here. Yet, none of them seems to work and I'm curious to see if anyone of you has a fix for my problem. My phone is an unbranded international HOX using the 9.7.2 ARHD rom by Mike1986. Here we go:
Problem
While being on WIFI my push notifications aren't coming through in time. There's a delay from anywhere between a few minutes up to as much as 40+ minutes. The phone doesn't have this issue being on the mobile data network. I'm also not 100% sure if the delay is still there when I'm on an different router. Even when I turn on the screen again, the messages seem to come in randomly.
Settings
WIFI best performance enabled
Static IP by router
WIFI sleep policy: Wifi always on
Tried suggestions
Wakelock: One thread described using an app called REGPON keep-alive, which installs a wakelock onto the phone to keep the data connection alive. This app did not do the trick. It only drained my battery and the messages still didn't come through.
Wifi performance: Set the phone to maximum wifi performance. This seemed to work for a while but ended up not working proper either
Kernel: Try a different kernel was one suggestion. I've switched from Stock to Faux123 010 kernel. This didn't change anything about the WIFI problem.
Static IP + Portforwarding + Disabling router Firewall: I've tried both port forwarding on port 5228 and even the range 5224-5228. I've also tried setting up triggered ranges. Maybe I'm doing something wrong on this part though. The router firewall is disabled and it should no longer block anonymous WAN packages.
Disable SmartSync: With the Suite Tools that are included in Mike1986's rom I've disabled Smartsync. No results as far as the wifi problem goes.
Probing app: I've tried an app that supposedly probes my router at least every minute in order to keep the connection alive.
Switching between b/g/n network: Didn't make a difference. The signal quality of the router is also good.
The only thing that did work for extended periods of time was using this remote control app that allows me to type through my PC keyboard, where the text ended up on the phone. I've also got an app installed to test push notifications. It's capable of making a log. Maybe that'll give you guys more information.
Right now I'm not sure if it's an issue with the HOX or if my router somehow stops the traffic. I don't recall having this problem on my HTC Desire. Does anyone have anymore tips?
Thanks,
Zendio

No problem with Gmail push notification on Stock 2.17.401.2.
Yesterday I still was on ARHD 9.7.2, also there I never noticed any delay.
Edit: this complies to various wifi networks (@home, @office, @parents etc.)

Zendio said:
I've seen a few similar threads to the one I'm about to make. I've tried different suggestions which I will post here. Yet, none of them seems to work and I'm curious to see if anyone of you has a fix for my problem. My phone is an unbranded international HOX using the 9.7.2 ARHD rom by Mike1986. Here we go:
Problem
While being on WIFI my push notifications aren't coming through in time. There's a delay from anywhere between a few minutes up to as much as 40+ minutes. The phone doesn't have this issue being on the mobile data network. I'm also not 100% sure if the delay is still there when I'm on an different router. Even when I turn on the screen again, the messages seem to come in randomly.
Settings
WIFI best performance enabled
Static IP by router
WIFI sleep policy: Wifi always on
Tried suggestions
Wakelock: One thread described using an app called REGPON keep-alive, which installs a wakelock onto the phone to keep the data connection alive. This app did not do the trick. It only drained my battery and the messages still didn't come through.
Wifi performance: Set the phone to maximum wifi performance. This seemed to work for a while but ended up not working proper either
Kernel: Try a different kernel was one suggestion. I've switched from Stock to Faux123 010 kernel. This didn't change anything about the WIFI problem.
Static IP + Portforwarding + Disabling router Firewall: I've tried both port forwarding on port 5228 and even the range 5224-5228. I've also tried setting up triggered ranges. Maybe I'm doing something wrong on this part though. The router firewall is disabled and it should no longer block anonymous WAN packages.
Disable SmartSync: With the Suite Tools that are included in Mike1986's rom I've disabled Smartsync. No results as far as the wifi problem goes.
Probing app: I've tried an app that supposedly probes my router at least every minute in order to keep the connection alive.
Switching between b/g/n network: Didn't make a difference. The signal quality of the router is also good.
The only thing that did work for extended periods of time was using this remote control app that allows me to type through my PC keyboard, where the text ended up on the phone. I've also got an app installed to test push notifications. It's capable of making a log. Maybe that'll give you guys more information.
Right now I'm not sure if it's an issue with the HOX or if my router somehow stops the traffic. I don't recall having this problem on my HTC Desire. Does anyone have anymore tips?
Thanks,
Zendio
Click to expand...
Click to collapse
I am so sorry to hear you are affected by this problem, but also happy someone else is experiencing the exact same thing as I am !!!
I have tried different solutions to no avail.
Would love to hear something on this topic !!

Also I should note, I don't have any kind of task killer installed.
In general use WIFI feels really fluid and responsive. I really have no idea what could cause these problems.

Zendio said:
Also I should note, I don't have any kind of task killer installed.
In general use WIFI feels really fluid and responsive. I really have no idea what could cause these problems.
Click to expand...
Click to collapse
Did we get any update on this, I have the issues on 3 phones..desire HD, sensation and a brand new Galaxy S3

modd1uk said:
Did we get any update on this, I have the issues on 3 phones..desire HD, sensation and a brand new Galaxy S3
Click to expand...
Click to collapse
I hope so. My One S is experiencing the same thing. I've tried everything above. No luck. Some stuff is fairly critical that I get it as soon as it comes in. I might try getting ahold of a Nexus 4 and do some testing with its wifi, just to make sure it isn't a general Android problem.

What router do you have? My issue was any android device in the house. Turned out it was my router, I put a custom firmware on it and all my trouble have gone away. My friend has the WiFi issue on a virgin media superhub.
Sent from my HTC Sensation Z710e using Tapatalk

I have an Asus RT-N66U. Funny you should suggest that. I'd planned to throw Tomato on it tonight and see how that works out. I did some tests at my folks' and their router had the same results. It's some cheap Netgear thing. Not sure of the model at the mo. I'll post back with results. If not tonight, tomorrow some time.

No go
Well that was unsuccessful. Actually it slowed things down. With the default firmware I get notifications from the instant I press power to wake up my phone. With Tomato there was a second or so before I got them.
Time to try DD-WRT tonight to see if that does the same thing.

I have an rt-n56u so the older version of yours and I'm running the Asus wrt that is being made, its fixed all my problems and is awesome tbh.
Sent from my HTC Sensation Z710e using Tapatalk

Set Beacon mode power safe (BMPS) to 0 in WiFi ???.ini config file should resolve this problem.
Such ???.ini config file usually placed under /system/etc/wifi or /system/etc/firmware/wlan/prima/

Wi-Fi unreliable

Recently I've been having problems with Wi-Fi. My phone and nexus 7. They both stay on blue bars all the time claiming they're connected to Google servers. And it'll work good for about 20 seconds and then I'll have no connection for about a minute. Bars will stay blue like its connected and WiFi show that it's fill signal but pages won't load, apps will timeout and YouTube videos won't stream. Makes it impossible to download any Roms or apps at times. This just recently started happening. Videos will stream good for maybe 2 minutes tops. Then pause, after a minute Wi-Fi will stay streaming and going again by itself and stream. I haven't changed my router or is settings. I have static ip's assigned too. All other computers work just fine for internet. Never a problem.
I've tried changing kernels, Roms, complete wipes and reinstalls. Rebooted the router. Nothing fixes it. I'm getting really frustrated. I'm at the point where I'm going trio go buy a new router just cause I want to use 5ghz. Anyways, any suggestions to solve this?

There may be an error in aosp code that can cause wifi instability: http://forum.xda-developers.com/showpost.php?p=35146886&postcount=5128

mwalt2 said:
There may be an error in aosp code that can cause wifi instability: http://forum.xda-developers.com/showpost.php?p=35146886&postcount=5128
Click to expand...
Click to collapse
Weird how it affects just my device in an entire thread with a ton of people using the rom and same kernel.
I went and picked up a new router. I'll see if that fixes it. Thanks for the input though. I appreciate it.

Didn't help with new router. My WiFi still cutting out like crazy on Franco kernel. Almost as soon as I turn off screen. But its not turning WiFi off. Just goes into some sort of state where nothing comes through. When screen on everything is fine though now.

In Wifi settings, you could try unchecking "Avoid Poor Connections" and see if that helps.
Also do you have any other devices at home on the same wifi network - do they experience the same issues, I know where I am if we get a lot of rain, it causes intermittent internet slowdowns, I had similar issues and after testing other devices found this to be my problem not my Wifi.
Also, have you got any cordless phones in the house that might run on the same frequency?
I still have an issue keeping wifi at 100% d/l when the phone is asleep, even though the setting is for always on. It must be a hardware thing for me because every rom I've tried from ICS to the latest JB exhibit the same issue. If I am in a desperate need to d/l a large file on my phone, I just temporarily change the screen display off timer to 10 minutes of so so the wifi will stay at max d/l speed.

https://play.google.com/store/apps/details?id=com.ratcash.wifiperf
Could try this I use on my gnex for voip
Edit I am on a galaxy nexus forum
Sent from my Nexus 7 using Tapatalk 2

Ya avoid poor connections is unchecked. And wifi optimization is unchecked. I've tried putting my router on full auto, tried setting static ip addresses for everything. Changing from wireless n to wireless g. Changing security to off as well. Using the 5ghz band instead of 2.4. The nexus 7 is working perfectly fine with the new router. But my galaxy nexus is totally unreliable. Weird is that it just started happening within past couple weeks. And actually, it was good for the first day or so after new router. I can confirm all other wifi devices jn the house work just fine without any hiccups. I've never had a problem with other devices. No dropouts or anything. It's really puzzling me!
One thing I found weird, if I disable wmm on my router, my nexus 7 and galaxy nexus will not connect. Anyone else get this?

I hope you also have your router firmware completely up to date.

Please read forum rules before posting
Questions go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator

CADude said:
I hope you also have your router firmware completely up to date.
Click to expand...
Click to collapse
Ya my router auto updates itself. Its a Cisco EA6500 in case your wondering and is helpful.

I use my wifi at work and it's very unreliable. At times going into an endless disconnect/reconnect loop. Sometimes restarting the wifi helps or putting it in and out of airplane mode. Other times nothing helps except a reboot of my phone. Some apps may make the issue worse. I don't think there is a fix and waiting for google to fix the flaw a user pointed out earlier.
Sent from my Nexus 7 using Tapatalk 2

chrisinsocalif said:
I use my wifi at work and it's very unreliable. At times going into an endless disconnect/reconnect loop. Sometimes restarting the wifi helps or putting it in and out of airplane mode. Other times nothing helps except a reboot of my phone. Some apps may make the issue worse. I don't think there is a fix and waiting for google to fix the flaw a user pointed out earlier.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Possibly a 4.2 issue. But its not affecting everyone it seems. But i see that there is a huge thread about this at the google site. Not an isolated case

When you say you set a static ip, you set one from the router, have you tried setting a static ip on the phones wifi advanced options as well?
Have you tried different radios?
Sent from my Galaxy Nexus using Tapatalk 2

Yup has happened to me mine connects to the net but has grey bars and doesn't open any websites and apps dont connect to the net a reboot solves the problem

chrisinsocalif said:
When you say you set a static ip, you set one from the router, have you tried setting a static ip on the phones wifi advanced options as well?
Have you tried different radios?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I set static on both router and the phone. I've tried all the north american radios. None of the euro ones. no effect. Sticking to the latest North American radio for now. I've managed to make it work sorta with CM10.1 with stock kernel on completely fresh install. It works, but the down arrow on the Wi-Fi icon stays lit almost 100% of the time. no idea why, only other device that was on all yesterday was the nexus 7, and that was on the 2.4ghz and phone the 5ghz. Huge wlan_rx_wake!

It's likely this:
http://code.google.com/p/android/issues/detail?id=40065&colspec=ID%20Type%20Status%20Owner%20Summary%20Stars&start=1000
See if that sounds about right and if so, you'll just have to wait for a Google Patch.

whitedragonz83 said:
It's likely this:
http://code.google.com/p/android/issues/detail?id=40065&colspec=ID%20Type%20Status%20Owner%20Summary%20Stars&start=1000
See if that sounds about right and if so, you'll just have to wait for a Google Patch.
Click to expand...
Click to collapse
Yeah. Just don't understand how so few here experience this. And only my phone, not my nexus 7 gets this.

M3drvr said:
Yeah. Just don't understand how so few here experience this. And only my phone, not my nexus 7 gets this.
Click to expand...
Click to collapse
When i first updated to 4.2, I was getting crazy dropouts. After unchecking the Wi-fi optimization, it was more consistent but still drops out frequently while at work. There is a known bug with the wifi driver that hasn't been addressed for years, but still trying to find the original articles describing the problems.
It seems you are having tons of issues, worse than most.
If you are having a problems suggested on this site, maybe this can help.
http://goo.gl/voSxF

It affects me as well. Completely random. Everything appears fine except that instead of blue, the icons are grey. Turning off wifi and turning it back on fixes it.
In the link above, there is a comment where you can submit more info for Google to help solving the problem:
http://support.google.com/nexus/bin/request.py?contact_type=bugreport&src=7679593

chrisinsocalif said:
When i first updated to 4.2, I was getting crazy dropouts. After unchecking the Wi-fi optimization, it was more consistent but still drops out frequently while at work. There is a known bug with the wifi driver that hasn't been addressed for years, but still trying to find the original articles describing the problems.
It seems you are having tons of issues, worse than most.
If you are having a problems suggested on this site, maybe this can help.
http://goo.gl/voSxF
Click to expand...
Click to collapse
the weird thing is, it just started happening about 2 weeks ago. It was perfectly fine up until then. Never had an issue with Wi-Fi. If this don't work i might try doing an entire wipe right back to stock and locking bootloader.

CM11 frequently pinging Google in the background

Hi,
I've been on XDA for a while now but never post since I can usually find the answer using search. However this one has me stumped, and I hope the experts here can help determine whats going on....
I noticed on my home router (monitoring IP traffic) that the phone contacts 74.125.X.X websites every few minutes. The various ip addresses resolve to google.com. This occurs constantly, even during sleep, and i'm not sure if this is a ping, or something else.
Thinking this was caused by an app, I clean wiped the phone and installed one of the last few CM11 nighties (even without Gapps), and the pings to 74.125.x.x still continue.
Does anyone else notice the same behavior, and/or know what is causing the pings?

Turn off Android Backup from under settings. Then reboot and check.

Perseus71 said:
Turn off Android Backup from under settings. Then reboot and check.
Click to expand...
Click to collapse
I did try this and there was no change. Note that when I was looking into this with a clean flash of CM11, it didnt even have a google account setup.
It was interesting that the last few days the pinging went away on its own, and the phone stayed in deep sleep. Then during the middle of the night last night, the pinging resumed. The android battery status showed frequent wakes when the pinging began, and 'Phone Idle" seems to be be battery hog. Looking at betterbatterystats, "wlan_wake" and "RILJ" are the culprits for the wakelocks.
One last tidbit....both my S3 running CM11, AND my lady's stock Nexus 5 are showing the same behavior. And they both were quiet for the last few days, and started pinging again last night. Anyone that knows whats going on, please chime in.

Is your Wireless connection really stable ? Please turn off Google Location Reporting and then make sure a stable Wireless is connected before leaving alone overnight.

Perseus71 said:
Is your Wireless connection really stable ? Please turn off Google Location Reporting and then make sure a stable Wireless is connected before leaving alone overnight.
Click to expand...
Click to collapse
Yes. The router is about 15ft away with a great signal. The router is also running Tomato firmware, which has for me been very stable for years.
Location reporting was/is off.

In that case turn off Location Service all together.