Related
i've had this issue since ive had my nexus 4 on 4.3 and now it continues with my nexus 5 on 4.4
When i'm connected to my home wifi, 'android OS' will show on my battery usage as the highest offender, causing the phone to stay awake 90% of the time. This doesn't happen when im at work on the wifi and also doesn't happen when on mobile data.
Any ideas on this? i'm been messing around with wifi settings but no luck. i have a router and a separate wifi access point at home. Could it be the router?
Thanks
MarkGbe said:
i've had this issue since ive had my nexus 4 on 4.3 and now it continues with my nexus 5 on 4.4
When i'm connected to my home wifi, 'android OS' will show on my battery usage as the highest offender, causing the phone to stay awake 90% of the time. This doesn't happen when im at work on the wifi and also doesn't happen when on mobile data.
Any ideas on this? i'm been messing around with wifi settings but no luck. i have a router and a separate wifi access point at home. Could it be the router?
Thanks
Click to expand...
Click to collapse
Easy fix: Don't connect to home wifi! *lulz*
No really though, tried other ROMs? Could possibly be the router if it doesn't happen to other connections. What router is it?
abtekk said:
Easy fix: Don't connect to home wifi! *lulz*
No really though, tried other ROMs? Could possibly be the router if it doesn't happen to other connections. What router is it?
Click to expand...
Click to collapse
I have not tried roms, its bone stock unrooted. I have a linksys wrt54g router(tomato) and a tplink wa901nd access point(stock firmware , tried openwrt with the same wakelock issues)
I'm thinking i might have to eliminate the access point to see if the issues goes away or not, then maybe replace the router.
MarkGbe said:
I have not tried roms, its bone stock unrooted. I have a linksys wrt54g router(tomato) and a tplink wa901nd access point(stock firmware , tried openwrt with the same wakelock issues)
I'm thinking i might have to eliminate the access point to see if the issues goes away or not, then maybe replace the router.
Click to expand...
Click to collapse
Connect to them both individually, just see if the issue persists. Maybe the router is sending messages to Android?
abtekk said:
Connect to them both individually, just see if the issue persists. Maybe the router is sending messages to Android?
Click to expand...
Click to collapse
thats what im thinking. it also affects my Nexus 7 2013. more testing!
MarkGbe said:
thats what im thinking. it also affects my Nexus 7 2013. more testing!
Click to expand...
Click to collapse
Keep me posted, we'll sort it!
I think I'm getting this as well. If I'm connected to Wifi and leave my phone on standby it will drain 8-12% per hour, but if I leave it on mobile data it will drain only 0.5-1% per hour. I'm going to download BetterBatteryStats and see if I can find the process causing this.
wlan_rx_wake
A fairly common and problematic cause of this can be identified by wlan_rx_wake being the highest wakelock keeping the phone awake as seen in betterbatterystats or similar.
There is a great thread listing all the likely causes:
http://forum.xda-developers.com/showthread.php?t=2519294
But whether you can isolate which cause or whether you can do anything about it is another story. For me it eventually turned out to be traffic generated from Windows machine on my network, I followed the advice to Disable IPv6, IP Helper service, shell hardware detection service and the Windows Media Player Network Sharing Service on each Windows PC and my stay awake time from Android OS plummeted from hours to minutes which I can deal with.
I ended up assigning static IPs to both my nexus 7 and nexus 5 and the issue has been resolved.
Confirmed!
MarkGbe said:
I ended up assigning static IPs to both my nexus 7 and nexus 5 and the issue has been resolved.
Click to expand...
Click to collapse
I saw this on xda portal and I can tell, that problem is resolved when setting PI from DHCP to Static.
At home I have both gadgets connected with manual IP for quite some time
Ended up with great battery life on Mahdi rom (N5)...
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.
Hi All,
I got the Lollipop 5.1 OTA 2 days ago and installed it - everything went smooth and the phone working fine...
But I noticed that if I reboot my router (or turn it off / on again) the Wifi don't reconnect unless I turn on the screen (the second I turn on the screen the wifi connect normally).
I didn't have this issue with Lollipop 5.0.1
P.S.
I know that this is happening because I have a led on my router telling me if any of my Wifi devices is connected or not. And to make sure I also entered the router settings to see if my phone is connected or not.
Anyone noticed that issue with the new lollipop 5.1 ?
Cheers,
I think that your problem is not switching off the router. The problem is when your phone goes to suspension (screen off) and then it drops the wifi off.
My Nexus 5 with 5.1 is doing the same
skorzo said:
I think that your problem is not switching off the router. The problem is when your phone goes to suspension (screen off) and then it drops the wifi off.
My Nexus 5 with 5.1 is doing the same
Click to expand...
Click to collapse
I've got some similar behaviour here, both when updated from 5.0, and with a fresh install from the factory images. When I arrive at a place with known WiFi, the phone only connects once I turned on the screen. After that, it stays connected until I move out of range and back again.
It's probably a matter of responsiveness/battery life. The more it polls for networks, the more battery it uses. It should connect, even with the screen off, within a few minutes.
That being said, I have my wifi set to always stay connected, and I've seen it not connected when I turned the screen on, then connect a couple seconds later. So, there's that. Curious how often it does that.
Aerowinder said:
It's probably a matter of responsiveness/battery life. The more it polls for networks, the more battery it uses. It should connect, even with the screen off, within a few minutes.
Click to expand...
Click to collapse
That's what I suspected. Sometimes, the waiting game works, but I've had my N5 lying on my desk – where it usually gets full WiFi bars – for about 40 minutes the other day, still it did not connect until I turned the screen on.
Edit: Just now, my phone disconnected from WiFi when the screen turned off, which leads me to believe that this is all caused by the WiFi sleep policy. Could it be that Google messed up something there?
dadrc said:
That's what I suspected. Sometimes, the waiting game works, but I've had my N5 lying on my desk – where it usually gets full WiFi bars – for about 40 minutes the other day, still it did not connect until I turned the screen on.
Edit: Just now, my phone disconnected from WiFi when the screen turned off, which leads me to believe that this is all caused by the WiFi sleep policy. Could it be that Google messed up something there?
Click to expand...
Click to collapse
My "research" has led me to believe this is the case.
Anything in terms of a workaround?
I came across those settings in the developer options (see screenshot), especially the "Always allow WiFi Roam Scans" looked promising. Been playing with them, but so far no luck.
Hi All,
exactly the same issues as yours guys are happening since I received the OTA 5.1 and installed it !
I Guess something messed up with this new update in regard of the wifi... as you mentioned.
If you come across a workaround or a confirmation from "Google" please share.
Cheers,
(With almost everyone nowadays having data ..it is difficult to notice such a behavior due to the fast wifi/data switching)
I have seen this happen as well. My battery graph will even show a missing area for WiFi indicating it turned itself on and off twice within a few hours and then stayed on after that.
Google just now released LMY47I, has anyone had a chance to see if that version fixes our problem? Once I'm off work (in about 8 hours), I'll give it a whirl and report back.
Tasker will help you
OsBuilder said:
Tasker will help you
Click to expand...
Click to collapse
Could you please elaborate on that? I'm familiar with Tasker, but I can't think of a way of dealing with this, since I'm not sure what actually happens with the WiFi. The settings appear untouched.
dadrc said:
Could you please elaborate on that? I'm familiar with Tasker, but I can't think of a way of dealing with this, since I'm not sure what actually happens with the WiFi. The settings appear untouched.
Click to expand...
Click to collapse
I'm sorry, but my phone is now in the service center , and press that I do not remember specifically . The idea is that when you disable wifi, a time interval is forced to connect to a particular network . Look presence on the internet , here is full of instructions.
dadrc said:
Google just now released LMY47I, has anyone had a chance to see if that version fixes our problem? Once I'm off work (in about 8 hours), I'll give it a whirl and report back.
Click to expand...
Click to collapse
http://www.androidpolice.com/android_aosp_changelogs/android-5.1.0_r1-to-android-5.1.0_r3-AOSP-changelog.html
Almost all of the changes on these different builds are SIM related for specific carriers.
LMY47I was only released to LGD821 devices with SIM cards from Indian and Australian carriers
Same problem here. I am slowly losing faith in Google. Get the frickin basics going guys!!!
Back to my 5.0.1 build.
I've gone back to 5.0.1, too. Pity, except for this I was pretty happy with 5.1. Maybe 5.1.1 will actually be usable.
Do you think it can be related to Issue 163350? code.google.com/p/android/issues/detail?id=163350
I have just reported that, but I'm still trying to understand if it just happens to me or what.
fabiastik said:
Do you think it can be related to Issue 163350? code.google.com/p/android/issues/detail?id=163350
I have just reported that, but I'm still trying to understand if it just happens to me or what.
Click to expand...
Click to collapse
I think the solution is "use vibrate mode on". Get your device to vibrate mod and test it.
I am waiting for your feedback.
MindLeader said:
I think the solution is "use vibrate mode on". Get your device to vibrate mod and test it.
I am waiting for your feedback.
Click to expand...
Click to collapse
This trick didn't work.
I have this proble too
I'm not sure if this is a Nexus 5 problem or a 6.0 Marshmallow problem but the problem occurred after the update to 6.0 on both Nexus 5s for me and my wife.
There seems to be some bug with my phone while it is asleep (screen is off but phone is on). When it is in this mode, it will not stay connected to wifi. For example, when I enter an area that has wifi, my phone will not connect. It will only connect when I wake the phone. And this isn't just a matter of the phone taking a while to connect. It NEVER connects. Before the update, my phone used to make a connection with my home router before I even walked inside. Now, I can be inside for hours and the phone never connects, until I wake it up. As soon as I wake the phone, the phone makes the connection with no problem. After a few minutes of the phone being asleep, I will wake the phone and the wifi connection will be gone. Now that it is awake again, it connects again with no problem.
I have tried forgetting the network and creating a new one, I have tried different routers, I have tried wiping the cache partition. I haven't tried a full factory reset, and I'd prefer not to, but I guess I will if I have to.
Just thought I would check here first and see if anyone had other thoughts.
Settings - wifi - menu - advanced - Second choice down from the top - choose how to keep WiFi depending on your battery charge %. Regards. Alessandro
Alessandro
vn800art said:
Settings - wifi - menu - advanced - Second choice down from the top - choose how to keep WiFi depending on your battery charge %. Regards. Alessandro
Alessandro
Click to expand...
Click to collapse
Thanks for the reply. Yes, that is what I thought at first also. I meant to say in my original post that my wifi settings are set to "Always On" during sleep. I've tried toggling that between the settings but still have the trouble.
Sorry, my Nex 5 has not this issue on Android 6 build MRA58K.
Alessandro
Yup, have the same issue. When the phone goes to sleep, it seems to disconnects from the wifi and never connects after I wake the phone. When I go into the wifi settings, I see "WIFI Connection Failure". I have to reconnect manually. Like the OP, have it set to always on as well. I also know it's not a router issue because I've tried this on four different routers (two linksys, one Dlink, one TPLink) All same results.
Wonder if this is a phone issue?
Please go here and click on the star to vote for this issue.
https://code.google.com/p/android/issues/detail?id=190667
Google upped this to a high priority Friday morning (Nov 6). The bad news is I think there a couple different WiFi symptoms being discussed here. Most of what is being discussed is the issue being discussed here (not reconnecting when the screen is off).
No idea when this will be fixed, so I build a Tasker profile to toggle WiFi every 15 minutes when not already connected to force a reconnect. I’ve observed it getting disconnected on its own overnight. This should avoid unnecessarily using cellular data.
I’m perpetually waiting for the next release of Android to fix annoying bugs.
vn800art said:
Settings - wifi - menu - advanced - Second choice down from the top - choose how to keep WiFi depending on your battery charge %. Regards. Alessandro
Alessandro
Click to expand...
Click to collapse
GaryP2 said:
Please go here and click on the star to vote for this issue.
https://code.google.com/p/android/issues/detail?id=190667
Google upped this to a high priority Friday morning (Nov 6). The bad news is I think there a couple different WiFi symptoms being discussed here. Most of what is being discussed is the issue being discussed here (not reconnecting when the screen is off).
No idea when this will be fixed, so I build a Tasker profile to toggle WiFi every 15 minutes when not already connected to force a reconnect. I’ve observed it getting disconnected on its own overnight. This should avoid unnecessarily using cellular data.
I’m perpetually waiting for the next release of Android to fix annoying bugs.
Click to expand...
Click to collapse
Thanks for the update Gary. The comment #6 describes my situation exactly. In doing some troubleshooting of my own, I find the disconnection trouble to happen less while on a 5Ghz network vs 2.5. I still have the trouble of it not connecting initially when I come into range, but I find that it is able to hold the connection while asleep.
I am also experiencing this on my Nexus 5 and also found and starred the thread above.
I just listened to 20min of streaming with Spotify to then realize that it had gone into Doze and used the mobile data!
This is more than annoying...
Maybe by disabling Doze for some specific connectivity-related system app? Anyone tried that?
Yes, I moved virtually all of the services type of apps (the ones with the green generic Android icon) to the battery not optimized list. It didn't make any difference for me.
In some ways it seems like it might be a Doze problem, and in other ways it doesn't. Doze shouldn't be affecting anything when the phone is in my pocket and I walk in the house to my WiFi. It also shouldn't be affecting anything when the phone is being charged, which is when I see frequent WiFi disconnects.
It will be real disappointing if this isn't fixed with 6.0.1.
This is still an issue with 6.0.1. Nexus 5 (2013) 6.0.1 MMB29K updated through OTA ZIP pushed with ADB.
Things work properly for a while right after a reboot and then WiFi never connects until the screen is turned on.
Google Connectivity Services C.1.6.7 (2466695) update didn’t make a difference either.
Same problem as the thread starter. HTC A9 anroid 6.0. (newest available OS)
Same problem here with a Nexus 5 .
Please star the problem if you have it.
https://code.google.com/p/android/issues/detail?id=170078
Has anyone tested with a non-stock kernel ?
I'm asking because the problem seems +/- resolved on CM13 (non caf).
No counting CM13, do you know of a more stable rom with the problem resolved?
Does anyone here have Wemo devices? I am reading that wemos, and possibly other devices that emit their own wireless network, may cause problems. I have several of these devices around the house, and wonder if that might be contributing. However, that only would solve the dropped connection bug I have, not the failing to connect while asleep but I have.
Hi mates, my Nexus 5 (android 6.0.1,M8974A-2.0.50.2.29) gets the same troubles with wifi connection but today I tried to put some apps in non optimized list of Doze and seems workig fine.
Thats my non optimized Doze list:
-Google Play Services
-System UI
Try it and let me know if it works properly.
frontomix said:
Hi mates, my Nexus 5 (android 6.0.1,M8974A-2.0.50.2.29) gets the same troubles with wifi connection but today I tried to put some apps in non optimized list of Doze and seems workig fine.
Thats my non optimized Doze list:
-Google Play Services
-System UI
Try it and let me know if it works properly.
Click to expand...
Click to collapse
I had Google Play Services already set to not optimize, but hadn't tried System UI. I will try that out and see what happens.
whitenack said:
I had Google Play Services already set to not optimize, but hadn't tried System UI. I will try that out and see what happens.
Click to expand...
Click to collapse
Welp, that didn't work. Still have the error after not optimizing System UI in addition to Google Play Services.
I don't know if the issue is resolved, but at least for me, it never worked fine so many days after testing some new workaround.
So, this was what I did in my Nexus 5 (latest build, MOB30H).
Uninstall or deactivate Google Connectivity Services, reset your network settings (you will lose your Wifi networks and BT pairings), reboot.
My Nexus 5 has been connecting to the wifi networks even with the screen off for the last 6 days.
Miguun said:
I don't know if the issue is resolved, but at least for me, it never worked fine so many days after testing some new workaround.
So, this was what I did in my Nexus 5 (latest build, MOB30H).
Uninstall or deactivate Google Connectivity Services, reset your network settings (you will lose your Wifi networks and BT pairings), reboot.
My Nexus 5 has been connecting to the wifi networks even with the screen off for the last 6 days.
Click to expand...
Click to collapse
Miguun, has the error returned, or still fixed? I just got the May update, so fingers crossed that fixes it. Otherwise, I guess I'll try your fix. I don't look forward to entering the wifi network information again.
Yup, it is still working !!
Hi everyone,
So I updated my p40 pro (GMS installed) to EMUI11 last week via OTA.
I noticed that after the update the wifi response is not good, i.e. many apps that I use are slow in the initial loading of content (internet based like ebay, etc). After that, they somehow work better. I checked in various WIFI networks and getting the same result, so I suppose that it is the update to blame. All apps load immediately in mobile data, so this also confirms the wifi issue for me.
I remember having a similar problem the first time i got the device and loaded GMS, but after the second time the problem was gone.
Tried wiping cache but no dice.
Anyone noticing the above in their devices? Any tips?
cheers,
t
Anyone?
For users experiencing the same issue I noticed foll:
After some messing around I reset network settings and after restart the phone WiFi connection is snappy again.
What I notice though is that in case I unfreeze gsf and then re-freeze it, the problem incurs again, so surely something is happening at that point; I then have to once again reset network settings so that it does not lag.
OK, so I finally found the culprit of the sh*tty Wi-Fi after the update to EMUI11:
There is a software bug for sure, due to which by the time that you enable WiFi calling on the device, all apps are slow to load content(besides the browser and social apps which work OK).
I have been constantly resetting network settings to fix the issue, issue was fixed but as soon as I enabled WiFi calling, things started to get problematic.
After switching WiFi calling off, problem immediately disappears, so surely this is a bug which was not present in previous firmwares.
Thanks for updating your thread! I had the same issue with some apps, but not all of them. Also, I was able to use these apps on Wifi using a VPN connection. After disabling Wifi calling the problem disappeared. The issue occurred after updating to EMUI 11.
I wonder why there aren't more people complaining about that.
snookdog said:
Thanks for updating your thread! I had the same issue with some apps, but not all of them. Also, I was able to use these apps on Wifi using a VPN connection. After disabling Wifi calling the problem disappeared. The issue occurred after updating to EMUI 11.
I wonder why there aren't more people complaining about that.
Click to expand...
Click to collapse
Honestly? I have no idea, but it is a really sh*tty bug for me, since I have been using WiFi calling for a long time (network reception in my home is bad). I hope Huawei or even some dev finds a fix soon..
Today i updated firmware to 168 but the problem still persists.
Another thing I noticed though is that you do not have to fully switch off WiFi calling, but only not to set it in WiFi preferred, instead leave it to mobile network preferred. The caveat tho is that when you have it in mobile network preferred, even if you have 1 bar of signal it will rarely switch to WiFi calling, so it is pointless.
OK, I think that the emui 11 update has ruined the phone due to this WiFi calling problem. It is almost unusable, every phonecall in my house ends up in call dropping, so the update got me in a position to either set wifi preferred in WiFi calling and have most of the apps lagging like hell, or to set it to mobile preferred and have usable apps but dropped calls all the time.
What a mess.
Indeed, thanks a lot for updating your thread!
The downloading lag I had on many apps (Gmail...) was driving me crazy!!
I disabled wifi calling (I couldn't until now, as I didn't have any reception in my old house) and downloads work again smoothly!
(I'm on 11.0.0.168)
thanito said:
Hi everyone,
So I updated my p40 pro (GMS installed) to EMUI11 last week via OTA.
I noticed that after the update the wifi response is not good, i.e. many apps that I use are slow in the initial loading of content (internet based like ebay, etc). After that, they somehow work better. I checked in various WIFI networks and getting the same result, so I suppose that it is the update to blame. All apps load immediately in mobile data, so this also confirms the wifi issue for me.
I remember having a similar problem the first time i got the device and loaded GMS, but after the second time the problem was gone.
Tried wiping cache but no dice.
Anyone noticing the above in their devices? Any tips?
cheers,
t
Click to expand...
Click to collapse
hi i have the same exact problem you have described, and possibly started after i upgraded to EMUI 11.0 as well, but i havent noticed before. Most of the apps are lagging like hell and most of the times i end up switching to mobile data as it seems faster (though i have 300 mbps wifi connection). Let me try disabling Wifi calling and see if this helps with the issue.
skyisblue79 said:
hi i have the same exact problem you have described, and possibly started after i upgraded to EMUI 11.0 as well, but i havent noticed before. Most of the apps are lagging like hell and most of the times i end up switching to mobile data as it seems faster (though i have 300 mbps wifi connection). Let me try disabling Wifi calling and see if this helps with the issue.
Click to expand...
Click to collapse
Did you try? I am sure it will solve the lagging issue
thanito said:
Did you try? I am sure it will solve the lagging issue
Click to expand...
Click to collapse
Yes it indeed helped now.. Apps load much faster after disabling wi-fi calling. Guess we need to raise this as bug with Huawei.
skyisblue79 said:
Yes it indeed helped now.. Apps load much faster after disabling wi-fi calling. Guess we need to raise this as bug with Huawei.
Click to expand...
Click to collapse
If you know the way, yes... I personally raised this issue to Huawei support hotline a few days after the update, but I never heard from them again.
oh my god, i resetted my phone and re-googlefierd it now 4 times until i found out those problems are just "wifi-calling" related.
problem still persists on latest 11.0.0.196
was anybody able to fix this?
osahitzelgsngar said:
oh my god, i resetted my phone and re-googlefierd it now 4 times until i found out those problems are just "wifi-calling" related.
problem still persists on latest 11.0.0.196
was anybody able to fix this?
Click to expand...
Click to collapse
I guess not, unfortunately the only solution for me was to switch wifi calling off. personally I switched to S21 ultra. Even though I believe that overall it was a downgrade move, god I was so frustrated not being able to use WiFi calling at my home, so this was the main reason of me switching to S21 Ultra. I still have the p40 pro sitting in a drawer, hoping that someone may fix this at some point I really miss the epic low light cameras and it's form factor (s21u too big for my taste and also when taking photos at night it's shyte compared to p40 pro)
Omg, thank you. It has been bothering me for months. Normally I just turn off and on wifi, to get the apps to have axcess to internet when I need to. But normally the have trouble again after short time. But now after setting it to 'operator preffered' and not 'wifi-preffered', it works like a charm. Ofcourse I do not have problems with the operator-signals...
But thanx again
Thank you so, so much! This was driving me nuts. You made my phone usable again
Seems like the Problem got fixed somehow silently.... im now on 11.0.0.223 & Updated all huawei apps to latest, and VoWifi seems to work fine now, at least for me...
can anyone confirm ?
My p40 pro is currently sitting at my drawer since I bought a S21U, but I will check to see if it works.