Related
Hi,
I recently bought a captivate from Rogers but use it with fido (same network anyway). I got it rooted and lag fixed (OCLF). I have set the wifi sleep policy to "never" under the advanced menu... yet when my phone screen turns off for a long period (more then 10 minutes, but don't know exactly how long), the wifi turns off and data takes over. Don't know if this is related, but i have installed Juicedefender to control the data.
I searched the internet and different forums, and they all have a solution for the wifi turning off problem: wich is to set the sleep policy to never... well my sleep policy is set to never and it doesn't do it for me...
is this a known issue? is there another app that can interfere with this option...
I called samsung and they want me to do a phone reset... before doing it I want to check with the real expert, for a better solution
Can anyone help please?
Thanks
Disable or uninstall juice defender and any programs that can modify your wifi status, one of the might be overriding your sleep policy.
I tried disabling juicedefender but it still had the same issue...
I will try uninstalling and will let you know
Thanks
Uninstalling Juicedenfender didn't help... same problem
Other potential apps causing this problem:
sipdroid, 3g watchdog but don't think so...
kam777 said:
I tried disabling juicedefender but it still had the same issue...
I will try uninstalling and will let you know
Thanks
Uninstalling Juicedenfender didn't help... same problem
Other potential apps causing this problem:
sipdroid, 3g watchdog but don't think so...
Click to expand...
Click to collapse
I know sipdroid changes the sleep policy.
Sent from my Captivate
Thanks! it was sipdroid, one of the wifi option was on (to improve life battery)...
Hey guys-
Just upgraded to the FR008 Liberated and I dig everything about it but one thing. The battery life was immediately radically reduced from what I was getting with Eclair, and after turning off push and doing everything else to preserve battery life, it seems clear now that the problem is that it is searching for wifi hotspots everywhere.
The Y5 "Battery Saver" utility worked brilliantly on Eclair to turn off the wifi unless I was in a location where I used wifi, and then remembered if I manually turned on wifi in a certain location. I bet this tool increased my battery life by 50% on Eclair. But it totally doesn't work at all on Froyo.
Is there any way to get equivalent functionality from Froyo? Or does anyone know of an update to Y5 that will fix it with Froyo? It doesn't crash, it just doesn't do anything on Froyo.
I tried searching for this but it won't match "Y5" since the word is too short.
I've tried the various things and they all lag the hell out of my phone. And yup, the battery will drain terribly, no one believes it's a problem though, everyone seems to cite "check your apps" and don't realize that people aren't dumb and that the ROM drains battery.
the ROM doesn't drain the battery, but constantly searching for wifi hotspots does. Y5 solved that problem by turning on wifi only when you are in a location where you have configured it to use wifi.
As an example, when I go for a 2-hour bike ride with my phone, it drains the battery about 60% during that two hours, just because I happen to ride through neighborhoods where there are a ton of wifi networks (people's home networks). With Y5 working, it just stopped looking for wifi once I left my house and it only went down about 5-10% during that same 2 hour period.
I'm not sure about liberated, but on cm6 froyo if you go to settings> wireless & networks> wi-fi settings, and then press your menu button three is an advanced option. From in there you can set your wifi sleep policy to disconnect wifi while the screen is off. The phone shouldn't search for a wifi connection when the screen is off in this mode.
Sent from my cm6.1 Aria using XDA App
I suppose that'll help a little bit, but won't help much if the screen is on... like I am using the phone (say, in the car, especially while using navigation)...
Still would be nice if Y5 worked. It was a brilliantly simple solution. Not exactly in the mood to pay $10 for an app to do this but I might have to if it gets too frustrating.
check out Settings Profiles Lite - limited to one rule in the free version and should be able to do what you want.
T
looks like that MIGHT do it, but what a pain to set up for something so simple.
THe wifi sleep thing won't help me, mostly because when wifi goes off and on the network seems to be a bit flaky.
At the moment the only thing that'll work is manually disabling/enabling wifi. However, the widget seems to turn it off only to have it come back on.
sorry to bump, but wondering, does anyone else has a suggestion or a way to get Y5 to work in Froyo?
It said connected in the wifi setting and it shows bars but it just won't load any website in the browser .. anyone got a fix for this?
I have the same issue. Tried different combinations of restarting wifi, turning on/off cell data, on/off wifi calling, etc... all with no result. I've also tried on different networks (both public and private)-- it'd start working for a while and then all of a sudden stop and never work again.
Seems similar to the problem here: forums. t-mobile.c om/t5/T-Mobile-G2x/G2x-WiFi-DNS-issue-not-the-4G-switching-one/m-p/831439 (sorry there's a new user no link restriction)
Does anyone have any suggestions?
Thanks
coldest~~~ said:
It said connected in the wifi setting and it shows bars but it just won't load any website in the browser .. anyone got a fix for this?
Click to expand...
Click to collapse
is it specific to the browser or can you not move any data?
Idk, whenever I have had problems connecting to the tmo network, which is a separate issue.. it was always that wifi calling was still on even tho wifi was turned off. Every time I had probs w/ data on tmo network, it's been wifi calling.. Your case seems to be diff tho.
Is it specific to just your network or all other networks? Try shutting off wifi, reboot... then turn it on again? Idk.. just tossing out ideas.
Some found the root cause and I am posting his finding as I do have the same issue and can reproduce the error:
I think I have discovered a new WiFi-related bug in the G2x's software. I have witnessed this occurring on my phone, and have also reproduced it on a store demo unit. I believe it is unrelated to the switching-to-4G problem people are having with the My Account app, since it occurs even if I have set up the Google account on first boot after a factory reset.
The details of the problem are:
- Every so often, the phone randomly gets stuck in a state where it is not able to initiate any new connections that are made using a DNS name. Attempting to navigate to a web site, h**p://w*w.google.c*m for example, will result in a generic failure message.
- However, attempting to connect directly to an IP address instead of a DNS name works perfectly. For example, navigating to 74.125.225.16 will work fine and will load the Google home page.
- When the phone is in this state, using a DNS lookup tool such as "DNS Lookup" from the Marketplace *will* work, even when using the default DNS server address that the DHCP server is giving the phone.
- The problem has occurred for me when data is off and WiFi is on. I do not know if data being off is a requirement, since this is the way I usually run the phone, so this may be coincidental.
- Switching WiFi off and back on again will *sometimes* work to solve the problem, but sometimes will not. When this doesn't work, switching WiFi off, then switching data on, then back off again, and then finally switching WiFi back on again will occasionally correct the problem. However, I have seen situations where none of these things worked, and the only way to get DNS working again was to factory reset the phone.
- I haven't figured out the exact pattern yet, but this issue seems to occur when the phone has been inactive for a certain period of time. I have often discovered that the phone is in this state upon waking up in the morning after leaving the phone on the charger overnight.
- I have, however, found a method to reproduce the problem that seems to work fairly consistently:
1. Turn WiFi on, and data off.
2. Power cycle the phone.
3. When the phone starts up, start the browser and attempt to browse to w*w.google.c*m. It should fail.
4. Try to browse to 74.125.225.16. It should work.
Just wanted to get this issue in the forums to see how many others have been noticing the same thing.
I know that once the device has less than 10% battery it automatically turns the WiFi off to save battery power. Were the devices this was happening on have a low battery?
Fully charged. It even happens when pluged in with the charger.
My Wifi wouldn't even work if I froze it with Bloat Freezer. It has to run in the background for wifi to work. I found that Wifi can get really inconsistent with it disabled.
smartloom said:
Som
- I haven't figured out the exact pattern yet, but this issue seems to occur when the phone has been inactive for a certain period of time. I have often discovered that the phone is in this state upon waking up in the morning after leaving the phone on the charger .
Click to expand...
Click to collapse
Same problem here. After about 30 minutes of being idle, as soon as I pick up the phone it tries to connect 2g/4g. The log are saying theres no connection, so it appears that wifi its going to sleep and not waking up so android is trying to connect 2g/4g
Really starting to be a pain
I have frozen the bloat, and I think the problem is getting worse.
Toggle airplane mode is a quick workaround to get wifi to wake up
Sent from my LG-P999 using XDA App
Same thing happened to me, I did 2 factory resets, and it seems it has been fixed, don't really know what causes it.
Sent from my LG-P999 using XDA App
This may or may not be related, but...
It looks like I found a hacky fix for the dns/wifi/4g bug: install "Set DNS" from the market.
Now when I go into market, and display my downloaded apps, it jumps from wifi to 4g then back to wifi as it should, fast.
Whether or not it should even do go to 4g is debatable, all I can say is my 2 Galaxy Tabs had the same behavior.
If everyones connectivity issues are really due to the DNS settings getting wiped out, then this will work around the problem until I/we find the location of the actual bug.
Would you guys having this problem also post it here?
http://www.lgforum.com/forum/boards/general/lg/topics/g2x-wifi-problems
Thanks.
I figure the more people that post there, the more the chances are of LG fixing it quickly.
Work around:
enable airplane mode
reboot
enable wifi
wait a few seconds after the wifi connects, background crap stops
disable airplane mode.
The set dns app looks like a winner. Haven't tried it but that's what's
wrong.
The freezing and other suggestions are all useless crap.
Updates...
I did a factory reset and installed JuiceDefender (I don't know which one worked) but it seems to be all fine now... will update if things become problematic again
I've been having this problem as well. I've always been able to fix it by toggling WiFi off and back on again. I downloaded SetDNS and when it happened again last night I tried that and it worked great.
Glad to see it's a software problem and not a hardware problem.
same problem here. hopefully it won't happen in cyanogen mod
boylan said:
Work around:
enable airplane mode
reboot
enable wifi
wait a few seconds after the wifi connects, background crap stops
disable airplane mode.
The set dns app looks like a winner. Haven't tried it but that's what's
wrong.
The freezing and other suggestions are all useless crap.
Click to expand...
Click to collapse
This fixed the problem, at least until the next time I reboot my phone
How do you use SetDNS? This software bug in G2X reboots my router (DGL-4500) sometimes.
Question bout SetDNS app
Does the phone have to be rooted to use the setdns app? I try to use it but it says "Cannot get root. App will not function."
I don't really know if this is peculiar to Glorious Overload (which I've been running for a week or so) or is maybe a kernel problem on the Sidekick 4G.
I want my wifi to stay connected when the screen turns off. I've tried setting the wifi sleep policy to both "never" and "never when plugged in" with limited success. Seems to sometimes stay on and sometimes not. When it gets into the "sometimes not" state, the only cure I have found is rebooting the phone. Other than that, I haven't yet caught a pattern to it.
Anyone have any info or suggestions?
(For those wondering, I want wifi to stay on so that I can use the quite nice "AutoAir" app to turn off my 3G/4G data connection [to save battery] when I'm connected over wifi. And I want that because I'm trying to use "Groove IP" to do all my calls as VoIP, which is somewhat better over wifi when it's available.)
(For those who don't know how to set the wifi sleep policy, try Settings > Wireless and network > Wi-Fi settings. Then hit the menu button and select "Advanced".)
Well, I checked my advanced settings, and mines was on never. I know it's woring because I download a lot of crap, esp via torrent clients. And once I have wifi on, it doesn't use 4g anymore. When I turn it off, 4g comes back. Mind you, I don't use and switcher apps or anything of that matter.
Quite odd that you're having a problem, are you stock GO2?
Sent from my Sidekick 4G running PDT's Glorious Overdose.
Yes, stock GO2.
For me, the behavior is intermittent. Sometimes seems to stay on, but sometimes seems to "forget".
There seem to be a zillion "fix your wifi" or "keep your wifi on" apps in the market, so I am trying a few of those now. (Slow going due to the intermittent nature of the problem I'm trying to solve.)
I noticed at the end of your post that u want to turn off your data and keep your wifi on to save battery, but with our device having wifi on uses more power than data. Mainly because our data and our cell signal are on the same radio, so by turning off data you really are doing nothing, because your cell service is still using the radio, but now that you've turned on wifi you now have the cell/data radio on and your wifi radio on. Really the fact that our cell and data are in the same radio is great because it really cuts down on battery use. So there you go. Learn something new everyday. please thanks this post if you didn't know this or if it helped you.
Sent from my Kindle Fire using XDA
You're right ... I didn't know that.
The other reason I want to keep the wifi on (apart from my faulty reasoning about battery life) is that VoIP is generally better over wifi. It's easy to get that arranged for outgoing calls, but the phone is generally napping for incoming calls.
I may have to rethink my whole strategy for this.
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.