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.
I recently performed a full wipe and installed the CM9 4/22 nightly, stock kernel, minimal apps in an effort to discover what was causing MASSIVE battery drain on my VZW SGN.
Using CPUSpy I can see my phone isn't going to sleep, and is staying awake @ 350 MHz for hours, but only when associated to my home (D-Link router) or work's (Cisco AP) 802.11n wireless. I am seeing a TON of Kernel Wakelocks caused by "wlan_rx_wake" via BetterBatteryStats, and this aligns to the overwhelming "Android OS" percentage of what is consuming my battery according to the native ICS app (settings -> battery).
According to the research I did, wlan_rx_wake is an event that wakes the kernel when a message is received via wifi, like a gmail push notification. Seems like something outside of my control. The weird thing is...i don't see these wake-ups on 4G. In fact the phone actually goes to sleep and gets better battery life when I'm NOT tied to wireless. What gives? Is the ROM doing something weird with the wireless? TIA for any advice, it's much appreciated.
Are you using a dynamic IP?
hittingsmoke said:
Are you using a dynamic IP?
Click to expand...
Click to collapse
yep, and i increased my DHCP lease times to 8 days.
i *think* i've discovered what the problem is, using WireShark and my HTPC sniffing out traffic to my wifi-joined cell phone. my router, issued by my ISP, is sending out "who-has" ARP requests to every IP address on my subnet, round-robin style. this is waking up my phone about 2x per minute.
i don't know if my ISP has enabled some ARP thing in the router (i looked in its config, can't figure out a way to disable the network scanning), or if the latest CM9 nightlies (i'm on 4/22) has suddenly decided to start responding to these requests...either way i've got to keep my phone on 4G to save battery. didn't have to do this a few weeks ago. very odd.
I experienced the same (along with wlan_ctrl_wake), and did quite a bit of experimenting: http://forum.xda-developers.com/showthread.php?t=1598581&highlight=cm9+wifi
Some wifi related commits, yet to be merged, 03:48 on May 5, maybe the new drivers will help: http://review.cyanogenmod.com/#/q/branch:ics,n,z
In the interim I either use another kernel, or use strictly data, I find the stock CM9 kernel doesn't drain excessively while on data. If you want to try another kernel instead, I'd recommend CM Plus Tuna; wifi drivers were reverted and a wlan_ctrl commit removed and there is no issue.
CMNein said:
I experienced the same (along with wlan_ctrl_wake), and did quite a bit of experimenting: http://forum.xda-developers.com/showthread.php?t=1598581&highlight=cm9+wifi
Some wifi related commits, yet to be merged, 03:48 on May 5, maybe the new drivers will help: http://review.cyanogenmod.com/#/q/branch:ics,n,z
In the interim I either use another kernel, or use strictly data, I find the stock CM9 kernel doesn't drain excessively while on data. If you want to try another kernel instead, I'd recommend CM Plus Tuna; wifi drivers were reverted and a wlan_ctrl commit removed and there is no issue.
Click to expand...
Click to collapse
Many thanks. I try to run the Franco kernel as well but still see the same issues. gonna just use cell data in the meantime till the wifi gets worked out in CM9
mcgoo99 said:
Many thanks. I try to run the Franco kernel as well but still see the same issues. gonna just use cell data in the meantime till the wifi gets worked out in CM9
Click to expand...
Click to collapse
Your issue sounds more app related possibly, since Franco has different wifi drivers than the stock CM9 kernel, unless he's updated them recently. Perhaps a nandroid and then a wipe (without restoring apps) to narrow it down.
CMNein said:
Your issue sounds more app related possibly, since Franco has different wifi drivers than the stock CM9 kernel, unless he's updated them recently. Perhaps a nandroid and then a wipe (without restoring apps) to narrow it down.
Click to expand...
Click to collapse
I don't think it is app related. I already wiped and installed base CM9, and with just two apps I saw the wlan wakes. I saw them on the Franco kernel as well. I'll try the Franco kernel once more and see if its been fixed.
mcgoo99 said:
I don't think it is app related. I already wiped and installed base CM9, and with just two apps I saw the wlan wakes. I saw them on the Franco kernel as well. I'll try the Franco kernel once more and see if its been fixed.
Click to expand...
Click to collapse
Same behaviour on all routers?
Sent from my Galaxy Nexus
CMNein said:
Same behaviour on all routers?
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
i believe so. i found a new radio for the SGN posted on 5/1, gonna give that a shot, as well as the newest CM9 nightly, 5/7. if i continue to get wakelocks on wifi, i'm wiping and trying again...
EDIT: after wiping and installing JUST CM9 and 4/29 gapps, no apps other than BetterBatteryStats and CPUSpy, i still get a ton of wlan_rx_wakes show up, not allowing my phone to go into deep sleep and keeping it awake. meanwhile, my Samsung Galaxy Tab, running the same CM9 nightly, same gapps, same wifi network, and a TON of apps is sleeping like a baby. i have no explanation for this, and why it's specific to my phone only.
mcgoo99 said:
i believe so. i found a new radio for the SGN posted on 5/1, gonna give that a shot, as well as the newest CM9 nightly, 5/7. if i continue to get wakelocks on wifi, i'm wiping and trying again...
EDIT: after wiping and installing JUST CM9 and 4/29 gapps, no apps other than BetterBatteryStats and CPUSpy, i still get a ton of wlan_rx_wakes show up, not allowing my phone to go into deep sleep and keeping it awake. meanwhile, my Samsung Galaxy Tab, running the same CM9 nightly, same gapps, same wifi network, and a TON of apps is sleeping like a baby. i have no explanation for this, and why it's specific to my phone only.
Click to expand...
Click to collapse
the system restore process is PAINFULL, but here's the edited version. use these directions:
http://forum.xda-developers.com/showthread.php?t=1426207
with this file:
http://www.mediafire.com/?cnqab1sg2b1u93p
to use Odin to restore to 4.0.2 (windows only, sorry).
then reflash clockworkmod recovery, reflash new 4.0.4 radios, wipe EVERYTHING (factory data, cache, system, dalvik, battery stats - i'm doing it all just to be certain) flash CM9 nightly, flash gapps, then wipe again but no system this time (factory data, cache, dalvik, battery stats). reboot. log into the google acount but don't restore any apps, just install CPUSpy after accepting the Play T&C's.
phone sleeps on 4G. phone sleeps on wifi. i'm happy...for now will report back if anything mysterious happens.
I know this is old but I had the same problem with Cyanogenmod 9 Stable. If this bug is this old (and I actually remember having this problem on some of the early nightlys as well but never found a cause) then it's pretty sad they let it sit this long and then release the ROM as stable. Anyway I fixed it by flashing leankernel. That instantly stopped my wlan_rx_wake wakelocks and allowed my phone to deep sleep. Here's the thread I made on rootzwiki if interested
http://rootzwiki.com/topic/32175-cm9-android-os-keeping-phone-awake/
Old issue again, but this issue plagued my nexus 7.
I narrowed down my issue to a wireless HP printer as well. I disabled the wireless since I wasn't using it and my battery is back to normal.
I recently replaced a RoadRunner provided modem "2100" with a personal modem Motorola SB6141. Ever since my "wlan_rx_wake" is draining battery much faster than it use to. Same router (WRT54G). I did also change from Viatalk PAP2T to Ooma Telo phone service, so not sure if that's related. Also upgraded to android 4.3, so another variable. Nexus on Static IP as well as Ooma Telo. Not rooted.
Anything I can try to keep wlan_rx_wak down? (other than shutting off wifi). I use GrooveIP which needs wifi on. It doesn't look like it's the problem.
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
Really odd problem here - as of a couple days ago, everything was working perfectly with my galaxy nexus. I decided to jump over to CM10 (was on codename android, IIRC), right after I think there were some new commits to AOSP.
From here on out, my phone would never enter deep sleep when connected to wifi. Any wifi hotspot - the ones I've been using, a hotspot I created from my desktop - the icon would show the phone constant receiving data via wifi. Using better battery stats, over about 5 hours on my desk, 4.5hrs were spent with a WLAN_RX_WAKE kernel wakelock with my phone sitting at 350MHz instead of deep sleep for that time.
I tried a bunch of different kernels (stock CM10, franco, imoseyon, etc) both new and old versions, but the problem was still there. I tried clean flashing a rom, and only installing better battery stats. Same thing with all kernels.
Factory restored google stock images to BOTH ICS and JB. I still have the problem. Tried disabling google location services. No dice. Tried a couple basebands, but I'm pretty sure that only affects cell/data performance, right?
I honestly have no idea what is going on. I've been on this hotspot (campus wifi) for months now without a problem, and now this. Some threads say that this is caused by DHCP requests from the router, but why would I have not seen this until now? My idle drain was at about 1-2% per hour before this, now it is close to 10-15%.
shadvich said:
Really odd problem here - as of a couple days ago, everything was working perfectly with my galaxy nexus. I decided to jump over to CM10 (was on codename android, IIRC), right after I think there were some new commits to AOSP.
From here on out, my phone would never enter deep sleep when connected to wifi. Any wifi hotspot - the ones I've been using, a hotspot I created from my desktop - the icon would show the phone constant receiving data via wifi. Using better battery stats, over about 5 hours on my desk, 4.5hrs were spent with a WLAN_RX_WAKE kernel wakelock with my phone sitting at 350MHz instead of deep sleep for that time.
I tried a bunch of different kernels (stock CM10, franco, imoseyon, etc) both new and old versions, but the problem was still there. I tried clean flashing a rom, and only installing better battery stats. Same thing with all kernels.
Factory restored google stock images to BOTH ICS and JB. I still have the problem. Tried disabling google location services. No dice. Tried a couple basebands, but I'm pretty sure that only affects cell/data performance, right?
I honestly have no idea what is going on. I've been on this hotspot (campus wifi) for months now without a problem, and now this. Some threads say that this is caused by DHCP requests from the router, but why would I have not seen this until now? My idle drain was at about 1-2% per hour before this, now it is close to 10-15%.
Click to expand...
Click to collapse
This is literally the EXACT SAME problem I'm having...I wish someone could properly explain why this is happening and how to fix it.
Sent from my Galaxy Nexus using xda app-developers app
Not sure if you've tried this and it helps but maybe you can try Network Log or Shark from the store to diagnose this?
Network Log doesn't show up with anything, so the wakelock shouldn't be caused by a rogue app.
Shark, on the other hand, after about 10 seconds of logging, netted me about 300 DHCPv6 'solicit XID' requests. There a bunch of different sources from these requests, they just seem to be other devices on the network pinging my phone to see if it's a DHCPv6 server...?
I've seen some suggestions on other forums to mess around with the router settings, which I can't do because it's campus internet.
Since you've tinkered with rom/kernels etc on phone without any seeming change, it's feasible that there's been some change recently on the other side of the equation namely the network settings of your campus wifi? Maybe your University's tech department has implemented something new etc? Have you tried asking others with wifi enabled phones if they are experiencing this as well?
Found this here (pretty sure you've come across this if you've been googling abt this issue but posting anyways)
"Another more elaborate solution if you rely on that network a lot, is to purchase a wireless bridge or gaming adapter and connect it to your apartment wifi and then connect your own wifi router to that. Then the gaming adapter would get the dhcp IP from your apartment (so who cares if it is renewing it constantly) and your router would treat the connection just as if you were connected directly to an internet connection. Then configure your router for static IP addresses or if your router does not cause issues with DHCP then you don't need static IPs."
from http://rootzwiki.com/topic/16134-kernel-wakelock-wlan-rx-wake/
I know I had an issue with some wlan rx wakelock thing last year but I cannot for the life of me remember how I got rid of it or what changed
Hmm, seems like an okay solution but my friend's devices don't seem to show the same symptom, and since I roam campus alot, a wifi extender wouldn't be ideal.
Bump. Any other ideas?
Sent from my Galaxy Nexus using xda app-developers app
I am seriously ripping my hair out from this goddamn wakelock ****.
I wake up at 9am and have to charge my phone by 4pm because it's at 16% with 40 minutes of screen on time. Seriously? This is a JOKE.
I've checked with BetterBatteryStats and CPU Spy. Both confirm the phone keeps sitting at 350MHz when it's supposed to be sleeping, as well as wlan_rx_wake keeping the phone awake.
I've set my phone to receive a static IP from my router (DIR-655) but it doesn't help. I really don't know WHAT to do. I've downloaded shark to my phone, sniffed packets, but haven't been able to get anything useful out of it since there is a LOT to sift through (unless you know what you're looking for - which I don't).
This is by far the worst bug/issue I have ever encountered with my phone and it is seriously getting on my nerves. I will be forever greatful to anyone who can help me pinpoint the issue and make it stop.
Also, i REFUSE to "go buy a new router" as it's bull****. This is a bug people experience only sometimes it seems and NO ONE has a fix for it. I read somewhere about a fix being implemented in some kernels but they were for other phones, never found anything like it for the GNex. If anyone knows anything about a fix like that, please show me the way.
I already checked for rogue apps, there were none keeping wifi awake. I've even tried with a totally stock, newly flashed phone with stock kernel and everything. NO extra apps installed except shark, CPU spy and betterbatterystats sideloaded. I didn't even input my GMail to stop the syncing. It STILL KEPT MY GODDAMN PHONE AWAKE.
I am SERIOUSLY desperate. Considering just selling my phone and opting for something else if this continues, it totally cripples everything.
/rant over
turn on WiFi, Bluetooth, and GPS, for about 30seconds, then turn them off. put your phone to sleep, then check if you're going into deep sleep. CPU spy is a good app to check if your hitting deep sleep.
Change wireless network encryption? Wpa2, tkip+aes, aes only, tkip only? Wpa?
Change wifi channel?
Edit: scratch that. Try disabling 5ghz band.
Sent from my i9250
I had a similar issue, it turned out it was Dropbox LANSync in my home LAN. I used an experimental forum build on my PC, so it could be this, but in the end I turned LANSync off, since Android doesn't make use of it anyway.
So try this if you have Dropbox running on your network clients.
simms22 said:
turn on WiFi, Bluetooth, and GPS, for about 30seconds, then turn them off. put your phone to sleep, then check if you're going into deep sleep. CPU spy is a good app to check if your hitting deep sleep.
Click to expand...
Click to collapse
At the moment I am fiddling with putting my router into different security configurations, per the quote below. But I will give your idea a try as well.
bk201doesntexist said:
Change wireless network encryption? Wpa2, tkip+aes, aes only, tkip only? Wpa?
Change wifi channel?
Edit: scratch that. Try disabling 5ghz band.
Sent from my i9250
Click to expand...
Click to collapse
5GHz band? Where do I disable this, the phone or the router? My router chooses channel automatically and is set to Auto 20MHz/40MHz channel width.
madd0g said:
I had a similar issue, it turned out it was Dropbox LANSync in my home LAN. I used an experimental forum build on my PC, so it could be this, but in the end I turned LANSync off, since Android doesn't make use of it anyway.
So try this if you have Dropbox running on your network clients.
Click to expand...
Click to collapse
I don't have DropBox on my phone or on any of my PC's
A quick update, I just tried all the suggestions in the quotes in my previous post but to no avail, still getting the wake locks. I'm seriously going crazy.
Turning wifi off did let the phone sleep, but that was expected as the wake lock is related to wifi. Nothing else has worked. NOTHING.
Sent from my Galaxy Nexus using xda app-developers app
EddieN said:
A quick update, I just tried all the suggestions in the quotes in my previous post but to no avail, still getting the wake locks. I'm seriously going crazy.
Turning wifi off did let the phone sleep, but that was expected as the wake lock is related to wifi. Nothing else has worked. NOTHING.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
This issue appeared again for me, it obviously also helps to disable the NETBIOS on your Windows PC network adapter. There are guides for that online. Also get the "Network Log" app in the Play Store, it shows the traffic so you can see which one's are for the kernel (wlan_rx_wake is a kernel wakelock).
Also uPNP feature in router can cause all kind of weird behavior. Better block it from router's firewall.
Sent from my slimbeaned GNex
What baffles me the most is that all of this shouldn't be needed. I shouldn't have to disable netbios and do things to OTHER devices just so my phone sleeps. This is a jellybean issue imo, I never had these problems on ICS.
The experiments continue, updates incoming.
Sent from my Galaxy Nexus using xda app-developers app
I also suspect the major issue was that my wifi channel was the same as the ones around me. When I changed it, the wlan wakelocks went down significantly.
Sent from my Galaxy Nexus using Tapatalk 2
EddieN said:
At the moment I am fiddling with putting my router into different security configurations, per the quote below. But I will give your idea a try as well.
5GHz band? Where do I disable this, the phone or the router? My router chooses channel automatically and is set to Auto 20MHz/40MHz channel width.
I don't have DropBox on my phone or on any of my PC's
Click to expand...
Click to collapse
5 Ghz band is disabled when you enter Wi - Fi - advanced - Wi - Fi frequency band ... It's set to auto by default, you try either 2.4 or 5 ghz on manual and check if that helps ( incase you didnt already )
Does anyone have any news about this issue? I have the same problem and I can't find the solution. I made several test without any good results.
lkeops said:
Does anyone have any news about this issue? I have the same problem and I can't find the solution. I made several test without any good results.
Click to expand...
Click to collapse
Change the Wifi channel.
Sent from my Galaxy Nexus using Tapatalk 2
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.