Related
Hi,
can anyone please help me? I recently downloaded and used JuiceDefender on my Desire. I configured a setting that allows the phone to learn what are the Wifi networks that I like to connect to, based on location. I soon noticed that the phone randomely reboots so I uninstalled this application. Well, I completely lost control of my Wifi connection. Even if I turn it off in Android settings, the Wifi just starts by itself and starts scanning for networks, which completely drains my battery. I installed the application again and reversed the location wifi setting but it did not help.
I also did a backup then wiped up my phone, but the Wifi still starts by itself. Is there any solution to this?
Thank you!
hi,
did a backup then wiped up my phone,
Click to expand...
Click to collapse
and the did you restore your backup?? if so i woulfd advice to clear data juice defendre and maybe mail to dev'app
thank you for your answer.
First I uninstalled juicedefender. after seeing that wifi still gets connected, i backed up, i wiped all data on the phone and restored the back up, but without juicedefender (it was not included in the backup). As for the email to the developers, I did that, but I got a response like that: "I don;t think this is possible. Please install our beta application and enjoy." How helpful of them!
Some suggestions
I would be surprised if any app could reboot the phone, even if it crashed.
Do you use tasker or locale? They can start up the wifi.
You could try org.wahtod.wififixer
You could also use something like com.mapeapps.networkcounter to check what is using the wifi. You'll have to reboot after installing it to reset the counters, but then, if it locks on to a wifi straight away, you could see what's using the connection, and maybe work out what's starting it up?
Thank you, I will try what you said. Sometimes the Wifi is just starting, but sometimes it also starts when I open any application that requires an internet connection, even if my data connection is already on. I will come back to report on what you suggested. Thanks again!
I forgot to say that I am not using a tasker. I do have enabled the location services based on network, but I have always had that before, and if the wifi was disconnected in the android settings, then it stayed off. Now it just won;t stay off. The thing is that I don;'t even need wifi, I have a good data plan. But the damn wifi just starts by itself, scanning for networks all the time, draining my battery and interrupting my regular data connection. I am so frustrated! I never had problems with my Desire for one year, and now, after installing this JuideDefender, problems are coming in.
Ok there are a couple of things:
a) If your Wifi is still broken after you uninstalled JD it is most likely not JD who was / is the culprit. You even wiped, so how should JD do this?
b) JD does not turn Wifi back on when you manually turn it off (I am not 100% sure what happens during the training phase, while JD learns you Wifi-Locations, because in these 1-3 days JD might turn Wifi on in "random" locations to enhance the algorithm)
What does the log in JD say (anything about turning Wifi on?)?
Hello,
the JD log says: WIFI turned on by user.
Which of course I have not done. I think my phone is haunted. Leaving JD aside (even if this problem started only after I started to use JD), the problem still exists: my phone turns its WIFI connection by itself, even if I don't want that!
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
Someone has posted this somewhere but I can't find the post again so...
I'm on Task's AOKP (11/18) with the KT747 kernel and I'm getting pretty crazy battery drain with WiFi on. I'm in an LTE coverage area so I'd expect the opposite...
I'm not sure when exactly this started happening, but it had to start within the past few days.
'Android OS' seems to be keeping my device awake for multiple hours, even though my screen time is only a few minutes (see attached images).
I checked my sync settings and nothing's unusual; just calendar, contacts, Gmail, G+, Tasks, and Twitter. Nothing I haven't been syncing forever.
Any idea why this is happening?
Not sure if this is a tw only solution but this solved my android os drain.
Check for gsiff_daemon and qosmgr in system/bin. Rename them and add .bak to both.
I have the same problem as OP but I'm on CM10 with stock kernel and I'm getting nasty battery drain.
MdX MaxX said:
Someone has posted this somewhere but I can't find the post again so...
I'm on Task's AOKP (11/18) with the KT747 kernel and I'm getting pretty crazy battery drain with WiFi on. I'm in an LTE coverage area so I'd expect the opposite...
I'm not sure when exactly this started happening, but it had to start within the past few days.
'Android OS' seems to be keeping my device awake for multiple hours, even though my screen time is only a few minutes (see attached images).
I checked my sync settings and nothing's unusual; just calendar, contacts, Gmail, G+, Tasks, and Twitter. Nothing I haven't been syncing forever.
Any idea why this is happening?
Click to expand...
Click to collapse
After trying what post #2 advised (make sure to reboot)...do a simple test and disable wifi completely for a few hours just to see if the problem goes away and report back.
jefferson9 said:
Not sure if this is a tw only solution but this solved my android os drain.
Check for gsiff_daemon and qosmgr in system/bin. Rename them and add .bak to both.
Click to expand...
Click to collapse
I'm not seeing those in /system/bin so must be TW only.
So it seems like this is a issue with AOSP-based ROMs in general, and not just on the SIII. Seems to happen to some but not others...
I loaded up BetterBatteryStats and checked for wakelocks and sure enough, "wlan_rx_wake" is keeping my phone awake for a good 40 minutes out of an hour of idling.
Doing a quick search for this process yielded many support threads, and reading through them seems to indicate that the wireless network is polling the phone so often that it can't sleep, and this happens on networks with a certain type of security. I'm on my university's WiFi so I'm out of luck as far as changing network settings goes.
Is this happening to anyone else on ktoonsez's AOSP kernel? Maybe the WiFi drivers in the kernel need to be tweaked or something? I may try some other kernels later and see whether that helps (though it'll be hard to tell since I'd be back to stock voltages).
The worst part of this is that I don't even know when this started happening.
MdX MaxX said:
So it seems like this is a issue with AOSP-based ROMs in general, and not just on the SIII. Seems to happen to some but not others...
I loaded up BetterBatteryStats and checked for wakelocks and sure enough, "wlan_rx_wake" is keeping my phone awake for a good 40 minutes out of an hour of idling.
Doing a quick search for this process yielded many support threads, and reading through them seems to indicate that the wireless network is polling the phone so often that it can't sleep, and this happens on networks with a certain type of security. I'm on my university's WiFi so I'm out of luck as far as changing network settings goes.
Is this happening to anyone else on ktoonsez's AOSP kernel? Maybe the WiFi drivers in the kernel need to be tweaked or something? I may try some other kernels later and see whether that helps (though it'll be hard to tell since I'd be back to stock voltages).
The worst part of this is that I don't even know when this started happening.
Click to expand...
Click to collapse
Come to think of it, my stock 4.0.4 rom is doing the same I believe when it is awake. Yesterday, I was looking at available wifi connections, and I noticed that a little indicator with text keeps popping up every 5-10 secs stating that it is looking for available networks.
Perhaps My Wifi is causing excessive drain while awake. During standby, Green Power app turns my Wifi/data off. Also, I am running WPA2 security for Wifi. Now I am curious to see if I can change the polling frequency. Someone mentioned build.prop file may have it.
The ROM I'm on is ParanoidAndroid 3.99-RC2 on an AT&T Galaxy S3. I've been having battery problems for awhile on this phone, but after upgrading to this, it has just gotten much worse. I take a look at BetterBatteryStats and it says my wifi is running all the time. I don't have wifi on most of the time, and I've reset the phone and it is still occurring.
RCizzle65 said:
The ROM I'm on is ParanoidAndroid 3.99-RC2 on an AT&T Galaxy S3. I've been having battery problems for awhile on this phone, but after upgrading to this, it has just gotten much worse. I take a look at BetterBatteryStats and it says my wifi is running all the time. I don't have wifi on most of the time, and I've reset the phone and it is still occurring.
Click to expand...
Click to collapse
I'm on task650's most recent 4.3 ROM and I got the same issue. Its draining 10% batt every hour. Killing me. Reinstalling the ROM or resetting did not help. It has in the past but not this time.
eatkabab said:
I'm on task650's most recent 4.3 ROM and I got the same issue. Its draining 10% batt every hour. Killing me. Reinstalling the ROM or resetting did not help. It has in the past but not this time.
Click to expand...
Click to collapse
I saw this post:
http://forum.xda-developers.com/showthread.php?p=51574320
i am trying it now to see if it really works. I Also have wifi running 100%
RCizzle65 said:
The ROM I'm on is ParanoidAndroid 3.99-RC2 on an AT&T Galaxy S3. I've been having battery problems for awhile on this phone, but after upgrading to this, it has just gotten much worse. I take a look at BetterBatteryStats and it says my wifi is running all the time. I don't have wifi on most of the time, and I've reset the phone and it is still occurring.
Click to expand...
Click to collapse
Is it the wlan_rx_wake stat? This came up on mine last week and I found a solution.
pc103 said:
Is it the wlan_rx_wake stat? This came up on mine last week and I found a solution.
Click to expand...
Click to collapse
What was your solution?
wlan_rx_wake solution
RCizzle65 said:
What was your solution?
Click to expand...
Click to collapse
For wlan_rx_wake, the research was saying this error is triggered by settings and/or background activity on 1 or more particular wlans you connect on (not by anything on your phone). Different posters saw it draining their battery on their school, work or home wifi networks accordingly.
I took 2 approaches: Since it was my home network, I disabled the UPnP service on my main router. I also separately configured a static IP (one that is outside the range of automatic addresses) on my phone for the home wifi connection using the "Modify network config" command available by long pressing an SSID in the list on Wifi settings. It worked. 1.4% / hour overnight drain is restored. (It had risen to 4%).
Both approaches isolate the phone from some types of network broadcast activity that triggers excessive wake time.
For me, seems working this operation
Go to WiFi settings-> Advanced-> Uncheck "Scanning always available"
Credits to @phanitej for this post