Related
I have battery drain issue when I use wi-fi for few min and then turn it off. After this the battery drains crazy but if I never turned on Wifi battery drain is normal.
Another issue is when Today Touch plugin's weather is updated by Wifi then it won't update with Active Sync connection?
Did anybody see these problems? Anybody has solutions?
I probably cannot help you other than to remind you that the gurus here will need more information so that they can help you. What device do you have, what ROM, what programs you've installed, etc. Also, these issues have been discussed numerous times with various ROMS, so searching will probably yield a great deal of information. Good luck.
My device is on XDAR2a release. Touch stuff and that is all nothing fancy. I am sure we are all talking about HTC wizard/cingular 8125.
dhanamjay said:
I have battery drain issue when I use wi-fi for few min and then turn it off. After this the battery drains crazy but if I never turned on Wifi battery drain is normal.
Another issue is when Today Touch plugin's weather is updated by Wifi then it won't update with Active Sync connection?
Did anybody see these problems? Anybody has solutions?
Click to expand...
Click to collapse
Wifi always takes alot of battery, make sure it's off, and also turn off incoming beam option in setting.
if you're reading the drain info from a program like batterystatus...give it some time after you turn off wifi for the information to refresh. wifi has a large drain on the battery...so it just might be residual information.
I am posting this as it is very hard to wade through information in forums. I'm hoping the following will be useful to those, who like me, experienced battery drain caused by Android Wake Locks after upgrading to MJ7 / MK2.
I am 100% certain the battery drain in MJ7/MK2 is caused by connecting to WIFI networks in environments that have multiple AP's. i.e. once WIFI roams from one AP to another the battery drain starts. All my testing confirms this - consistently. I have actually tested being connected to one AP in a multiple AP environment for a long period and observed no wake locks on Android OS. Yet as soon I move to another location (i.e when I make it roam) the wake lock and battery drain starts. All this rubbish about clearing cache, factory resetting, nobbling your phone and so on are all stabs in the dark - It's the reboot that temporarily fixes it so people mistakenly put two and two together. So, if you use WIFI in a large building with multiple AP's try forgetting the network and not connecting to WIFI with multiple AP's. If you have already connected to a SSID with multiple AP's reboot your phone because once the battery drain starts it does not seem to stop until you reboot. You don't have to disable WIFI at all as scanning does not cause the wake lock. I have tested this thoroughly and so far I have not had any battery drain since not connecting to SSIDs with multiple APs. I can also back this up as I can create battery drain at will by simply connecting to a WIFI environment with an SSID distributed over multiple AD's.
My battery life is again fantastic and I am happy now that I know the cause.
Pretty poor testing by Samsung/Google as I see in past versions of Android Roaming has been an issue.
mongoose3800 said:
I am posting this as it is very hard to wade through information in forums. I'm hoping the following will be useful to those, who like me, experienced battery drain caused by Android Wake Locks after upgrading to MJ7 / MK2.
I am 100% certain the battery drain in MJ7/MK2 is caused by connecting to WIFI networks in environments that have multiple AP's. i.e. once WIFI roams from one AP to another the battery drain starts. All my testing confirms this - consistently. I have actually tested being connected to one AP in a multiple AP environment for a long period and observed no wake locks on Android OS. Yet as soon I move to another location (i.e when I make it roam) the wake lock and battery drain starts. All this rubbish about clearing cache, factory resetting, nobbling your phone and so on are all stabs in the dark - It's the reboot that temporarily fixes it so people mistakenly put two and two together. So, if you use WIFI in a large building with multiple AP's try forgetting the network and not connecting to WIFI with multiple AP's. If you have already connected to a SSID with multiple AP's reboot your phone because once the battery drain starts it does not seem to stop until you reboot. You don't have to disable WIFI at all as scanning does not cause the wake lock. I have tested this thoroughly and so far I have not had any battery drain since not connecting to SSIDs with multiple APs. I can also back this up as I can create battery drain at will by simply connecting to a WIFI environment with an SSID distributed over multiple AD's.
My battery life is again fantastic and I am happy now that I know the cause.
Pretty poor testing by Samsung/Google as I see in past versions of Android Roaming has been an issue.
Click to expand...
Click to collapse
Funny thing is that when i am using mobile data the drain is worse, So I'm pretty sure this is not the main issue man. Also, I have a Mobile 'WiFi' router. Only me has WiFi connection in my entire hostel. So I don't really think it's the issue. Good finds tho! It will definitely help someone. Cheers!
Agree with stanley, this is not the only cause.
39089665568
vndnguyen said:
Agree with stanley, this is not the only cause.
Click to expand...
Click to collapse
Agreed. There are many things that will cause elevated use. But Im talking the rapid drain that occurs when you're not using the phone. Ever since taking the action I describbed my battery life has been excellent. Eg 94% after 14 odd hours with no use. And, I'm still connecting to my home wifi. Beforehand it could be below 60% with no use and this is the real problem people are talking about. Hope that makes sense.
Actually it's the opposite. If you set up your modem to have a separate AP for the phone and isolate it from the rest of the network, you'll have much better battery life on wifi because you'll stop your phone from waking up by broadcast packets.
aydc said:
Actually it's the opposite. If you set up your modem to have a separate AP for the phone and isolate it from the rest of the network, you'll have much better battery life on wifi because you'll stop your phone from waking up by broadcast packets.
Click to expand...
Click to collapse
I don't get it. What am I supposed to do exactly?
aydc said:
Actually it's the opposite. If you set up your modem to have a separate AP for the phone and isolate it from the rest of the network, you'll have much better battery life on wifi because you'll stop your phone from waking up by broadcast packets.
Click to expand...
Click to collapse
What about unicast traffic? i know the Client Isolation sort of "VLAN"s every client associated, just wondering if that might affect client to client communication?
Good point btw, im also wondering how many services wake the damn thing up, waking up over network is more an enterprise workstation scenario...to me it sounds like HotSpot 2.0 services being active, but i have not enabled it.
HS2.0 can let client and AP sort of talk without associating.
Nazty111 said:
I don't get it. What am I supposed to do exactly?
Click to expand...
Click to collapse
Most modems have a sort of 'guest mode' or allow you to open another access point and isolate it from the rest of the network. If you connect your phone to this guest access point or isolated access point, your phone will reach internet without problems, but will not reach the local network through the router. Nor will any other device on the network reach your phone.
Most of the problems with Wifi draining battery, like wifi wakelocks, occurs because devices on the network keep sending packets to the phone waking it up. With the method I describe above, you will isolate your phone and the phone will remain in deep sleep, significantly increasing battery life.
aydc said:
Most modems have a sort of 'guest mode' or allow you to open another access point and isolate it from the rest of the network. If you connect your phone to this guest access point or isolated access point, your phone will reach internet without problems, but will not reach the local network through the router. Nor will any other device on the network reach your phone.
Most of the problems with Wifi draining battery, like wifi wakelocks, occurs because devices on the network keep sending packets to the phone waking it up. With the method I describe above, you will isolate your phone and the phone will remain in deep sleep, significantly increasing battery life.
Click to expand...
Click to collapse
This is very true. Back on my old GNex i used to have crazy wifi wakelocks and I couldn't for the life of me figure it out. I never figured it out, actually. But I am positive it is one of the two PC's on my network that are broadcasting packets across the network, waking my phone up. I haven't had time to extensively test the wifi wakelock in the environment i've previously encountered it in to see if it still applies, but since I haven't changed anything regarding any of the two computers involved on that network, I'm positive I will have the same wifi wakelock issue when I get back and test. Is there a way (besides using Shark) to see what programs are broadcasting packets across the network?
But to get back on topic, I am experiencing battery drain connected to ONE router with ONE AP. I am in an apartment building with several other routers nearby, though. Maybe they are broadcasting packets somehow that the kernel is interpreting and keeping the phone awake? However it seems as though the Android OS bug keeps coming back for everyone no matter what, even in airplane mode.
Wifi has evolved a lot the last decade, not just by technology standards but into integration as well. carriers use them as small cells, we'll see them more often in the future (malls, stadiums, etc), and HS2.0 adds to make it a bit more seamless, they call it offload, taking your data needs through small wifi cells rather then the macro cells (3g, 4g), hence offload.
my point is that they would have never invested in that if the wifi chips inside consumer products were not efficient enough, so nearby APs shouldnt be a problem at all. But im still puzzled for what would one need the waking up process through wifi?
If Wifi is the general bugger, then somebody throw an eye on the Passport service, thats the consumer name for HS 2.0 services.
PS, tested AP Isolation on my sh!tty WRT120N, no difference unfortuantely.
Will there be a future update from Sammy or will we get Kitkat directly
Sent from my SM-N900 using Tapatalk
Just a follow up. I have still had no battery drain since avoiding connecting to wifi networks that use multiple APs. Now, i only connect to wifi networks where i know there is only one AP. Before I stumbled across this the drain and Android os wake lock was bad, really bad, after I had connected to large wifi networks - I just hadn't put two and two together. This is more than coincidence - my testing is sound and replicable. And, this week I have been in remote areas with weak to no 3g signal and the battery life has still been fantastic and no wake locks so that sort of rules that out - Sure there is a little increase in battery usage but nothing dramatic, something to be expected and certainly not something to complain about. I have seen many claims to fix battery drain but these are just fine tuning and not addressing the major drain caused by Android OS wake locks. Clearly, there must be an issue with the wifi software driver in MJ7/MK2 and I hope Samsung/Google are aware of it. The annoying thing is getting Samsung to acknowledge the issue and take feedback.
I get wake locks even if I manually turn wifi off and only use data. When I use wifi i am connected to only one AP and I still get wake locks. The wake locks aren't apps, they are "Powermanager.wakelocks" and "Powermanager.Display" and show up as "Android OS" in battery settings.
I am still not convinced avoiding multiple AP wifi networks is the one-for-all solution for everyone.
However, I have put "wifi on during sleep" to "never," yet my phone slept maybe 50% yesterday but wifi was on 100% of the time. Why is this? Shouldn't it have turned off the 50% that the phone was sleeping?
Something is weird with the wifi module..
Sent from my SM-N9005 using xda app-developers app
EddieN said:
I get wake locks even if I manually turn wifi off and only use data. When I use wifi i am connected to only one AP and I still get wake locks. The wake locks aren't apps, they are "Powermanager.wakelocks" and "Powermanager.Display" and show up as "Android OS" in battery settings.
I am still not convinced avoiding multiple AP wifi networks is the one-for-all solution for everyone.
However, I have put "wifi on during sleep" to "never," yet my phone slept maybe 50% yesterday but wifi was on 100% of the time. Why is this? Shouldn't it have turned off the 50% that the phone was sleeping?
Something is weird with the wifi module..
Sent from my SM-N9005 using xda app-developers app
Click to expand...
Click to collapse
Have you ruled out any other wifi connections? Have you tried rebooting if you have connected to another wifi network? Have you tried forgetting all wifi networks? Reboot after forgetting all networks. Then give it a couple of days with out connecting to any wifi network - just a test to confirm it is wifi related. I tend to think setting wifi to never on during sleep makes no difference - I had previously tried it too. Once the drain starts the only way to stop it is to reboot.
mongoose3800 said:
Have you ruled out any other wifi connections? Have you tried rebooting if you have connected to another wifi network? Have you tried forgetting all wifi networks? Reboot after forgetting all networks. Then give it a couple of days with out connecting to any wifi network - just a test to confirm it is wifi related. I tend to think setting wifi to never on during sleep makes no difference - I had previously tried it too. Once the drain starts the only way to stop it is to reboot.
Click to expand...
Click to collapse
Yes, just last week I was on another Wifi AP about ~300km away (totally different environment) and I still had the same wake locks. I have rebooted when connecting to another wifi network. I have tried forgetting all wifi networks i have connected to, and reconnecting to them. I have also rebooted once forgetting networks. During this time I also took the liberty of doing the normal rounds of disabling location services etc. before rebooting, but nevertheless i did reboot once forgetting the network. All networks I have been connected to have been single-AP wifi networks.
I have not let it sit for a few days without connecting to any wifi networks. That's the only thing I haven't tried. However I have let it go a whole day with wifi turned off (and only data enabled), but the same wakelocks persisted. For me it's always "Powermanage.Display" and "Powermanager.Wakelocks" no matter how long i just let my phone sit around with the screen turned off. I have it right beside me so I always have visual access to the screen in case the phone wakes up on its own, but it never has. I guess I could try turning wifi off for a few days and seeing how it fares, but I doubt I will see any difference (wake lock wise).
I'm thinking something is strange with the wifi module anyway. Surely wifi should turn off by itself once the phone sleeps, right? Like I said in my other post, my phone slept maybe 50-60% of the time on a 14 hour day. That means Wifi should have been on 40-50% of that time, and off 50-60% since the phone technically should have been sleeping. Yet I can see in the battery settings menu that wifi is a solid green bar all across the 14 hours.
EddieN said:
Yes, just last week I was on another Wifi AP about ~300km away (totally different environment) and I still had the same wake locks. I have rebooted when connecting to another wifi network. I have tried forgetting all wifi networks i have connected to, and reconnecting to them. I have also rebooted once forgetting networks. During this time I also took the liberty of doing the normal rounds of disabling location services etc. before rebooting, but nevertheless i did reboot once forgetting the network. All networks I have been connected to have been single-AP wifi networks.
I have not let it sit for a few days without connecting to any wifi networks. That's the only thing I haven't tried. However I have let it go a whole day with wifi turned off (and only data enabled), but the same wakelocks persisted. For me it's always "Powermanage.Display" and "Powermanager.Wakelocks" no matter how long i just let my phone sit around with the screen turned off. I have it right beside me so I always have visual access to the screen in case the phone wakes up on its own, but it never has. I guess I could try turning wifi off for a few days and seeing how it fares, but I doubt I will see any difference (wake lock wise).
I'm thinking something is strange with the wifi module anyway. Surely wifi should turn off by itself once the phone sleeps, right? Like I said in my other post, my phone slept maybe 50-60% of the time on a 14 hour day. That means Wifi should have been on 40-50% of that time, and off 50-60% since the phone technically should have been sleeping. Yet I can see in the battery settings menu that wifi is a solid green bar all across the 14 hours.
Click to expand...
Click to collapse
Well that's interesting. At least in both cases we know it's Wi Fi. I wonder if it's something if it comes down to the type of connection. Eg 2.4 vs 5ghz
mongoose3800 said:
Well that's interesting. At least in both cases we know it's Wi Fi. I wonder if it's something if it comes down to the type of connection. Eg 2.4 vs 5ghz
Click to expand...
Click to collapse
It could be. Both networks I have been connected to have been 2.4GHz Wireless-N capable routers. I just find it odd that a lot of things don't add up when looking at awake times in Settings -> Battery and comparing it to kernel/partial wakelocks in BBS/WLD/CPU Spy. All of the times seem to be roughly in the same ballpark, but they never add up to correspond to each other. Surely there must be information missing in this regard.
I can confirm the WiFi issue on my N9005 but there's another one.
1. Wifi: I experienced this at my university, where we have good Wifi coverage on the whole campus. They use Radius for logging in. After using Wifi for about 15min, I had these wakelocks, which didn't stop until I rebooted the phone. Since I knew this, I haven't been using Wifi there any more. But: In the meantime, I did a factory reset and got this little stability update. A few days ago, I gave it a try again. Used Wifi at university for ~25min and hat no issues. Maybe it's gone, I will test again some day.
2. I had an app called "gentle alarm". On my GNexus, which I used before my Note 3, I also had wakelocks, but couldn't figure out what it was, since wakelock detector, better battery stats etc. didn't show more than PowermanagerService.Wakelocks/Display. So I got my new Note 3 and still had these Wakelocks - I did much Monitoring and: It was this tiny alarm app. Very funny: After having excluded every other possibility and having the wakelocks active I uninstalled the app on my Note 3 and it instantly rebooted!
Great battery life now.
Hope this helps someone. BTW: The Wifi issue on larger networks seems to be a problem not only on Samsung phones, many people are experiencing this (e.g. found similar reports for Nexus 5...).
duffmannr3 said:
I can confirm the WiFi issue on my N9005 but there's another one.
1. Wifi: I experienced this at my university, where we have good Wifi coverage on the whole campus. They use Radius for logging in. After using Wifi for about 15min, I had these wakelocks, which didn't stop until I rebooted the phone. Since I knew this, I haven't been using Wifi there any more. But: In the meantime, I did a factory reset and got this little stability update. A few days ago, I gave it a try again. Used Wifi at university for ~25min and hat no issues. Maybe it's gone, I will test again some day.
2. I had an app called "gentle alarm". On my GNexus, which I used before my Note 3, I also had wakelocks, but couldn't figure out what it was, since wakelock detector, better battery stats etc. didn't show more than PowermanagerService.Wakelocks/Display. So I got my new Note 3 and still had these Wakelocks - I did much Monitoring and: It was this tiny alarm app. Very funny: After having excluded every other possibility and having the wakelocks active I uninstalled the app on my Note 3 and it instantly rebooted!
Great battery life now.
Hope this helps someone. BTW: The Wifi issue on larger networks seems to be a problem not only on Samsung phones, many people are experiencing this (e.g. found similar reports for Nexus 5...).
Click to expand...
Click to collapse
Thanks for your input. Is the wifi issue you are talking about the fact that it doesnt turn off when having "wifi on during sleep -> never" set? Or the multiple-AP issue the thread is talking about?
What stability update is it that you have received? What country are you in and what firmware are you using? Did you get this stability update while on MJ7/MK2 firmware? I haven't received any notification for a stability update OTA...
Thanks for the Powermanager.Display/Wakelock issue. I guess I will have to sift through my apps and uninstall each, one by one, to see if the wakelocks disappear. If not, there is some other issue
EddieN said:
Is the wifi issue you are talking about the fact that it doesnt turn off when having "wifi on during sleep -> never" set? Or the multiple-AP issue the thread is talking about?
Click to expand...
Click to collapse
It's the issue about "multiple" APs, but I don't think that it is about the number of APs. What I have read is that there is so much traffic on those big networks, e.g. broadcasts from other devices. I don't know how it should be with your problem that wifi doesn't turn off - can you see if it's reconnecting after some standby time? If yes, then wifi is turned off during sleep, but is just not shown in statistics.
EddieN said:
What stability update is it that you have received? What country are you in and what firmware are you using? Did you get this stability update while on MJ7/MK2 firmware? I haven't received any notification for a stability update OTA...
Click to expand...
Click to collapse
I'm currently on MJ7/MK2. My device is unbranded and I'm living in Germany. It came on 26th of December and was about 30MB or so.
EddieN said:
Thanks for the Powermanager.Display/Wakelock issue. I guess I will have to sift through my apps and uninstall each, one by one, to see if the wakelocks disappear. If not, there is some other issue
Click to expand...
Click to collapse
It's definitely worth a try! There was absolutely no hint that pointed to this one app. I started with having a look at the battery statistics ~every 30min after a fresh reboot. After a few days it was clear that it only could be the alarm app, battery draining started only in the morning.
Wow, so this is pretty interesting. Today I was fiddling around with VPNs (ends up being unrelated), and noticed that my wifi speed as shown by Speedtest was HORRIBLE. like 1mb - 6mb when it should have been close to 70mb. Not only that but while it was testing it would freeze several times during the downloads and uploads. We actually returned my husband's first tablet because of this issue, thinking it was a hardware problem. After an hour or so of fiddling around trying to figure out what happened, I noticed that Location services was on. Usually I keep this turned off on my tablet. I turned it off and ran speedtest again and what do you know. My wifi speed was back to where it should be and there were no freezes.
So what I'm wondering is... has anyone else noticed this problem? Can you reproduce it? Why would this be happening? Can anyone think of a fix for it? Most of the time keeping Location turned off won't be a problem for me, but Aereo for example, needs it turned on in order to stream shows.
One thing of note is that SpeedTest seems to rely on location services since when you fire it up with location services set to high accuracy mode the GPS radio fires up in notification panel. I'm not entirely sure that it'd be a fair assessment to say that the setting affects all wifi connectivity speeds when enabled as opposed to reduced speed during GPS use.
That said, I can't say that i'm seeing the same thing using Ookla's SpeedTest app. At first I thought I did but after toggling location services a couple times things settled in and i get consistent 55-60Mbps download test results whether location services is on or off or in high/low accuracy mode. My test results on the tablet match consistently with those of my rMBP in the same room on the same router (in the next room) using a 5ghz wireless n network.
I've never turned location services off on my tablet, opting instead to always leave it in low power mode (GPS isnt my thing, I use my cell phone for that) and have never had issues with wifi speed.
When I went back to see if I could reproduce it by turning Location back on.. it was fine. So I have no idea what's going on, lol. Maybe after leaving location on for a while it starts to degrade? I might test that out eventually. Just glad it is working better now.
Anyone else with WiFi issues? 90% of the time I have no problems but 10% of the time it seems the connection hangs. Data transfer will pause and resume 30 secs or a minute later. I have tested this with speed test and was able to reproduce. Happens on both my 2ghz and 5ghz networks. I am rooted but I'm going to do a factory reset to see if issue persists. I do know it's not my WiFi as my other devices have no trouble. But this is quite annoying.
Sent from my HTC6525LVW using Tapatalk
murryrulz said:
Anyone else with WiFi issues? 90% of the time I have no problems but 10% of the time it seems the connection hangs. Data transfer will pause and resume 30 secs or a minute later. I have tested this with speed test and was able to reproduce. Happens on both my 2ghz and 5ghz networks. I am rooted but I'm going to do a factory reset to see if issue persists. I do know it's not my WiFi as my other devices have no trouble. But this is quite annoying.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
Are you by chance using an Apple router or access point? For some reason, they don't seem to play well with Android devices, including my M8. I've had a similar experience with 4 Android devices and 2 different Apple routers. The devices continuously disconnect and reconnect.
No I'm using an Asus ac66. The funny thing is the connection doesn't drop. It always says connected. The data just stops flowing and then starts again. For example I'll run a speed test and the download will pause then start up again. Very odd. Never had a phone do this before
Sent from my Nexus 7 using Tapatalk
I've got an Apple Airport Extreme. I also have several Android devices. Have had many that I no long have or use. I've never had any problem with my wifi on any of them. I have to wonder if your problem isn't related to something else. Or, possibly your router needs to be replaced. Might be a matter of settings too. But, like I said, I've never had any problems with mine.
Within the "Advanced Wi-Fi" settings there is an auto-enabled option called "Wi-Fi Optimization" which minimizes battery usage when Wi-Fi is on. I assume this monitors for extended periods of inactivity (screen off, no active downloads, etc.) and temporarily disables/hibernates Wi-Fi activity.
I've kept this option enabled and haven't had any issues so far, but maybe you could try testing with/without this setting enabled? Another thing to try would be checking highly-used radio channels in your area with an application like InSSIDer and making sure your router is broadcasting on a low-use channel. I see no correlation with the radio channel and your new M8, but it's worth a try
insertnewsn said:
Within the "Advanced Wi-Fi" settings there is an auto-enabled option called "Wi-Fi Optimization" which minimizes battery usage when Wi-Fi is on. I assume this monitors for extended periods of inactivity (screen off, no active downloads, etc.) and temporarily disables/hibernates Wi-Fi activity.
I've kept this option enabled and haven't had any issues so far, but maybe you could try testing with/without this setting enabled? Another thing to try would be checking highly-used radio channels in your area with an application like InSSIDer and making sure your router is broadcasting on a low-use channel. I see no correlation with the radio channel and your new M8, but it's worth a try
Click to expand...
Click to collapse
I have the same issues. and ive turned off wifi optimizaiton, ive set my wifi control frequency to 149, ive tried to switch between 2.4 and 5ghz. i feel like my issue is with the phone not picking up the wifi signals very well... we live in a brick house, and the asus ac68u sits right in the middle of th house, and my room is only right around the corner. everyone elses phone picks up 5ghz or 2.4ghz frequency fine in my room, even my gf's M8 (we bought ours from verizon same time for the deal). i literally get wifi in my rom 10% of the time or its choppy and slow. so everytime im in my room i have to switch to cellular :|
After using 6.0 for a day or so, I noticed that the WiFi was draining huge amount of juice from the phone, even taking the top spot on the battery chart. This seems to happen even if the WiFi is turned off.
http://i.imgur.com/X2YoNvv.png
So how can we fix this? Well, we'll have to go through bunch of settings to do so. It seems like Google deliberately hid this deep inside location settings. This is how we can "temporarily" fix this issue: Head to Settings -> Location -> Click those 3 dots at the top right corner -> Scanning -> Turn off both WiFi scanning and Bluetooth scanning.
Even with this "fix" I noticed that it keeps draining battery life for no reason, not as much, but the problem still exists. This shouldn't happen! Especially when Marshmallow was built around battery life improvements. The fact that this bug has been causing problems since M Preview #3 shows either Google "missed" this chaos of a bug (or) only cares about that juicy location data. This should be a straightforward-user-friendly option, not one that is buried behind buttons and menus.
It's not a bug, it's a feature
Had the same issue after flashing the factory image. So I flashed 5.1.1 again booted the phone then rebooted into recovery and sideloaded the 6.0 OTA. Booted the phone and preformed a factory reset. Now I don't have that problem.
jdawg0024 said:
Had the same issue after flashing the factory image. So I flashed 5.1.1 again booted the phone then rebooted into recovery and sideloaded the 6.0 OTA. Booted the phone and preformed a factory reset. Now I don't have that problem.
Click to expand...
Click to collapse
Pics
im currently having this exact issue.
I had same problem also tried disabling Wi-Fi scanning and automatically turning off Wi-Fi when idle but it did not give better results.
Just today i switched phone Wi-Fi to 2.4 GHZ only mode - this workaround seem to work, no drain any more.
DaimonPl said:
I had same problem also tried disabling Wi-Fi scanning and automatically turning off Wi-Fi when idle but it did not give better results.
Just today i switched phone Wi-Fi to 2.4 GHZ only mode - this workaround seem to work, no drain any more.
Click to expand...
Click to collapse
Thanks for that. This actually sounds possible.
On the first day when I flashed 6.0 with OTA, I really felt that the battery life has extended.
Then I switched through a lot of settings and also ended up with 2.4 and 5 (auto) on wifi.
Disabling all wifi related options did not help at all....
Will try this out now. :good:
I'm having severe delays with my wifi on my N5 with 6.0. In speedtest I'm pushing over 90mbps on 5GHz band, but it takes over 30 seconds to load a webpage/ apps. It's not gradually loading it's almost like a stall. Then after the page or app loads instantly. Why is this happening? Is it a severe delay to the server? IDK wtf is going on... I don't have battery drain issues from the wifi this is a different issue.
Same problem... Scanning and wifi off! Wifi drain. At first sight problem only seems to manifest while no wifi available. Tried the 2.4ghz only and seems to reduce though not eliminate the problem...
DaimonPl said:
I had same problem also tried disabling Wi-Fi scanning and automatically turning off Wi-Fi when idle but it did not give better results.
Just today i switched phone Wi-Fi to 2.4 GHZ only mode - this workaround seem to work, no drain any more.
Click to expand...
Click to collapse
Works indeed better.. Wifi disappears from the Battery Usage chart, but when it was supposed to went on idle while I put it away, draining started again it seems.
There is a fat bug in the Power-Management in Android M 6.0 final, if you ask me...
All, please check whether it is actually drain or merely incorrect reporting of battery statistics. Symptoms seem similar to this thread
Remember battery 'drain' is where the level is falling at an abnormally fast rate. If WiFi is merely appearing at the top of the stats, but your battery life is actually fine, then it's not drain.
You need to leave your phone over several hours, and take measurements. When investigating or troubleshooting, then logically change one thing at a time, and re-measure again over a long period of time for comparison.
eddiehk6 said:
All, please check whether it is actually drain or merely incorrect reporting of battery statistics. Symptoms seem similar to this thread
Remember battery 'drain' is where the level is falling at an abnormally fast rate. If WiFi is merely appearing at the top of the stats, but your battery life is actually fine, then it's not drain.
You need to leave your phone over several hours, and take measurements. When investigating or troubleshooting, then logically change one thing at a time, and re-measure again over a long period of time for comparison.
Click to expand...
Click to collapse
There is definitely a drain problem... because of Google Play Services not letting System into sleep mode and pulling constantly on Wifi...
That is how I think it comes to the problem.
Mine is now running smoothly, after I went into: Settings > Apps > Google Play Services (and maybe also Google Play Store) > hit menu ... > Deinstall Updates > Restart
If you go back into Play Store later on, it updates to the current version.
I also reseted the Network Settings... somewhere.
I tried what was suggested by others in this thread and din't have any luck. I posted how I solved the issue here:
reddit dot com/r/Nexus5/comments/3npesh/wifi_drain_persists_in_android_m_final_release/cvwo3x5
I did another modification. In Location settings I changed mode to device only (GPS).
So together:
- set WIFI to 2GHz only
- disable wifi scanning in location settings
- set location scanning to device only (GPS)
- set WIFI to automatically turn off in idle mode (advanced wifi settings)
WIFI is no longer main battery consumer (screen is now as expected). I'm not sure which of those is crucial but they all look like may improve things a bit (and together give big difference)
.
I thought this was bugging me too. WiFi is top of the list in battery stats. But then I disabled ElementalX gestures (doubletap2wake in my case) and that improved things a lot. Even though WiFi is still reported as the biggest power user.
This may be just me and of course it could always be better, but it might be worth giving this a try.
I'm having his exact issue. It's with any resources I access through WiFi, from sftp to ftp to web data, internal and external lans, internet, etc. It's definitely a 6.0 issue. I had it on preview 3 as well, and it was bad enough make me downgrade at the time. Now the official release is out and doing the same thing, I'm REALLY hoping they can fix this soon. It's practically unusable if you don't have dial-up time to kill.
Check my previous post - it completely fixed problem for me
I've experienced the same issue, after a week from the ota update (week in which I had a great battery lifetime), the problem arose out of the nowhere, and after searching the web for a workaround, it seems that putting the wifi in 2.4 ghz only made the trick...
Really hope that google will fix this soon...
eyesore said:
There is definitely a drain problem... because of Google Play Services not letting System into sleep mode and pulling constantly on Wifi...
That is how I think it comes to the problem.
Mine is now running smoothly, after I went into: Settings > Apps > Google Play Services (and maybe also Google Play Store) > hit menu ... > Deinstall Updates > Restart
If you go back into Play Store later on, it updates to the current version.
I also reseted the Network Settings... somewhere.
Click to expand...
Click to collapse
This is the only thing that worked fully for me. Getting it to 2GHz made it a little bit better but didn't actually solve it. Uninstalling updates from play services and play store solved it for good and I didn't have to flash 5.1.1 and ota update.
:good:Thanks eyesore!
Hello. I have this issue... I disabled localisation through WiFi and I have also done a network settings reset but the problem still persists (not too much as before -45%- but around 25%).
How can I solve?