Related
When I got the phone my battery was pretty phenomenal (comparatively speaking). But it seems since I took the update that Sprint pushed out a few weeks ago, the battery can't make it more than a few hours with light/moderate use. Its really horrid to be honest. Hoping the eventual 4.2.2 OTA will fix this. But in the meantime I wanted to know if anyone else was having this issue and possibly help identify the source of the problem. (By the way I am not rooted)
daltonroland said:
When I got the phone my battery was pretty phenomenal (comparatively speaking). But it seems since I took the update that Sprint pushed out a few weeks ago, the battery can't make it more than a few hours with light/moderate use. Its really horrid to be honest. Hoping the eventual 4.2.2 OTA will fix this. But in the meantime I wanted to know if anyone else was having this issue and possibly help identify the source of the problem. (By the way I am not rooted)
Click to expand...
Click to collapse
Have you checked the version of your Google Play Services APK? It can cause a particularly nasty bug on HTC devices.
Rirere said:
Have you checked the version of your Google Play Services APK? It can cause a particularly nasty bug on HTC devices.
Click to expand...
Click to collapse
Play Services is v 3.1.36 but the actual Play Store is v 4.1.10 which is said to "fix battery drain issue." Still seems to be draining pretty rapidly. Any fix you know of?
Can we see your usage stats?
daltonroland said:
Play Services is v 3.1.36 but the actual Play Store is v 4.1.10 which is said to "fix battery drain issue." Still seems to be draining pretty rapidly. Any fix you know of?
Click to expand...
Click to collapse
The Play Store update should have also pushed Play Services, so yeah. Could we see your usage and also your app list/sync settings?
I'm in the same boat, even after the Google Play Store fix.
Seriously, we need usage stats.
Sorry, been working in home WiFi.
Hardly been using the phone since I still have my old Evo LTE and the battery is better on that.
Sent from my HTCONE using xda app-developers app
Sent from my HTCONE using xda app-developers app
Wifi used up 43% of 60% of your battery? That's like a quarter of your battery gone! Am I the only one who thinks that's weird? Can we see the graph and awake time etc? (Sorry for the trouble, but it's the only way we can tell)
---------- Post added at 11:44 AM ---------- Previous post was at 11:34 AM ----------
daltonroland said:
Sorry, been working in home WiFi.
Click to expand...
Click to collapse
Just wanted to ask, what does that mean? (Not trying to be negative in any way)
sauprankul said:
Wifi used up 43% of 60% of your battery? That's like a quarter of your battery gone! Am I the only one who thinks that's weird? Can we see the graph and awake time etc? (Sorry for the trouble, but it's the only way we can tell)
---------- Post added at 11:44 AM ---------- Previous post was at 11:34 AM ----------
Just wanted to ask, what does that mean? (Not trying to be negative in any way)
Click to expand...
Click to collapse
Well, in fairness for the last week or so I've been charging the phone and leaving it in my room. The screenshot was after like a day and a half in which a hardly used it and had WiFi on.
By working on home WiFi I meant talking to ISP and bumping up speeds, for the second time in a week.
I'll post the graph when I get home from work or early tomorrow as the phone has been unplugged for about 20 minutes.
Sent from my HTCONE using xda app-developers app
It won't hurt if you actually use it. Watching vids/playing games prevents blown up stats like that.
EDIT: Please, also include stats like screen time, awake time, cell reception, Wifi etc.
This was at work. I hardly use my phone at work fyi.
Sent from my HTCONE using xda app-developers app
Dropped 25 ish percent in 6 hours? What seems to be the problem?
With your usage, that would give you a day. I'm happy with 11 hours.
But with no internet connection and hardly any use. It concerns me because usually it would drop 5 maybe 10%. It was great on sleep.
Sent from my HTCONE using xda app-developers app
OK, now that I think about it, you're right. I remember getting more than 2 days on standby with absolutely no use (on wifi).
A day with that kind of usage is really not that good. It's weird because your stats don't show anything odd. I'd like to see some moderate to heavy usage stats though. The kind you say gives you 5 hours. That would help more.
Here you go. About 50% gone in about an hour of use (on WiFi) mostly on YouTube/Twitter or music with regular use of ATK.
Sent from my HTCONE using xda app-developers app
I'm having a serious battery drain issue with my Sprint One also, though I don't remember exactly when it started - it might very well have been that OTA update.
My battery drains when the phone is asleep. The phone will be dead in just over 24 hours from 100%, with less than one hour of screen usage. The integrated "usage" monitor shows that WiFi consumes this power , whether or not WiFi is in use. I have a paid task manager app that can track stats over time, and according to it, the processor appears to be running at ~15% constantly when the screen is off. I've tried disabling WiFi and having the phone sleep on just the cell network, to no avail. I first thought that perhaps the poor service at my house was causing it. However, I watched the battery drain at exactly the same rate when in an area with perfect coverage.
Here's the weird part - I tried airplane mode'ing my phone. Airplane mode doesn't seem to stop it. In fact, airplane mode seemed to accelerate the drain! I find it simply unacceptable that my phone will die like this with almost no usage.
I feel that the problem is not a rogue third-party app I have installed. I've used the "disable" option on Facebook, Twitter, and I've removed several other suspected apps. It makes no difference. I even suspected my task manager app; I tried removing it and looking at the integrated one, and there was no difference.
flyboy21141 said:
I'm having a serious battery drain issue with my Sprint One also, though I don't remember exactly when it started - it might very well have been that OTA update.
My battery drains when the phone is asleep. The phone will be dead in just over 24 hours from 100%, with less than one hour of screen usage. The integrated "usage" monitor shows that WiFi consumes this power , whether or not WiFi is in use. I have a paid task manager app that can track stats over time, and according to it, the processor appears to be running at ~15% constantly when the screen is off. I've tried disabling WiFi and having the phone sleep on just the cell network, to no avail. I first thought that perhaps the poor service at my house was causing it. However, I watched the battery drain at exactly the same rate when in an area with perfect coverage.
Here's the weird part - I tried airplane mode'ing my phone. Airplane mode doesn't seem to stop it. In fact, airplane mode seemed to accelerate the drain! I find it simply unacceptable that my phone will die like this with almost no usage.
I feel that the problem is not a rogue third-party app I have installed. I've used the "disable" option on Facebook, Twitter, and I've removed several other suspected apps. It makes no difference. I even suspected my task manager app; I tried removing it and looking at the integrated one, and there was no difference.
Click to expand...
Click to collapse
Check to make sure never auto turn on Wi-Fi is checked in Wi-Fi advanced settings. I was going to suggest poor reception since that kills my battery, but you mentioned trying airplane mode.
With screen off and nothing running, it's not surprising that Wi-Fi is the main battery drain. But it is too fast in my opinion too.
Sent from my HTCONE using Tapatalk 2
Is high performance Wi-Fi disabled?
Sent from my HTCONE using xda app-developers app
Since upgrading to 4.3 android system is taking a lot of battery and the phone won't deep sleep. I'm on stock 4.3 ge ROM and I wiped everything even SD card.
I was wondering if anyone else was experiencing this or if anyone knows the culprit.
I see NLP wakelock and nlpcollector wake lock but not too sure what apps or app is using this wake lock or how to track it down. Any help appreciated thanks.
Sent from my HTC One using Tapatalk 4
you have locaiton reporting on in maps?
Yes...I always have it on...I'll try turning it off
Sent from my HTC One using Tapatalk 4
Are you using Better Battery Stats?
bobruels44 said:
Are you using Better Battery Stats?
Click to expand...
Click to collapse
Using wake lock detector. I'm under the impression they both do the same thing. Its happening on both my tablet (n10) and my phone...so weird..I guess I'll wipe and just not restore apps. I was just curious if anyone else was having these issues.
Sent from my HTC One using Tapatalk 4
with any app that uses location reporting you'll get the NLPwakelock. it is quite annoying but theres not much you can do about it. you can mitigate it by not using maps. or by turning off location sharing or unchecking "location & google search" under location options. that has helped my battery quite a bit.
just as a reference for my battery life:
total on time: 13 h
deep sleep: 10h11m
awake: 2h47m
screen on: 46m
wifi 2h50m
@73% battery. which i think is ok. have i had better yes. but 27% for 12 hours of standby and 45m of screen on. sure. if anyone else has any suggestions WITHOUT sacrificing autosync, maps, gmail, blinkfeed, and weather sync let me know!
Yeah I have android system as 42% usage. And strangely, gallery is at 44%..
Anyone else getting this ?
Sent from my HTC One using Tapatalk 4
syaoran68 said:
with any app that uses location reporting you'll get the NLPwakelock. it is quite annoying but theres not much you can do about it. you can mitigate it by not using maps. or by turning off location sharing or unchecking "location & google search" under location options. that has helped my battery quite a bit.
just as a reference for my battery life:
total on time: 13 h
deep sleep: 10h11m
awake: 2h47m
screen on: 46m
wifi 2h50m
@73% battery. which i think is ok. have i had better yes. but 27% for 12 hours of standby and 45m of screen on. sure. if anyone else has any suggestions WITHOUT sacrificing autosync, maps, gmail, blinkfeed, and weather sync let me know!
Click to expand...
Click to collapse
It's not just that, I restored my Nexus 10 and now the problem is gone but still happening on my HTC One, not sure what it could be, tired of restoring my phone lol. I deleted the HTC Debug app and that helped a little because that was part of the Android system usage, but I still have other stuff. Trying to narrow it down.
Serious_Beans said:
It's not just that, I restored my Nexus 10 and now the problem is gone but still happening on my HTC One, not sure what it could be, tired of restoring my phone lol. I deleted the HTC Debug app and that helped a little because that was part of the Android system usage, but I still have other stuff. Trying to narrow it down.
Click to expand...
Click to collapse
What are you using to check this? the built in battery stats or something like GSAM Battery Monitor?
I ask because ive been getting this on ALL 4.3 ROMs but it seems to be operating normally by looking at the third party app like GSAM. It makes no sense to me.
I am having the exact same problem on my HTC One 4.3. Stock battery app shows from 70%-95% of system usage. Downloaded battery doctor and it is coming from the Gallery app. I tried literally everything, from hard reset to disabling the Gallery app. I have been researching and trying to fix it all day, seriously driving me insane. I just switched to android, and I am trying my hardest not to regret it.
Any help would be very grateful.
I have the same problem as the OP, I'm using a Nexus 4 with Android 4.3. The problem is not that there are some wakelocks, the problem for me is that after using Google Maps the phone won't go into deep sleep at all until I reboot, it is all the time kept awake by this nlp wakelock.
Dreiberg said:
I have the same problem as the OP, I'm using a Nexus 4 with Android 4.3. The problem is not that there are some wakelocks, the problem for me is that after using Google Maps the phone won't go into deep sleep at all until I reboot, it is all the time kept awake by this nlp wakelock.
Click to expand...
Click to collapse
Some people have it, some don't not sure what it is, but hopefully Google or some 3rd party ROM developers fix it.
On some occasions (about twice a week) I have a dramatic battery drain on my Note. It discharges faster than USB/pluged charger provides power, even in airplane-mode. After rebooting everything is fine again... for a few days. Manually killing the process "gpsd" cures this behaviour as well.
As reported by BetterBatteryStats I could not detect any unusual wakelocks... or am I reading it wrong?
This did not oocure before I switched from Paranoid Android 2.57 (JB 4.1.2) to StuNNeR 2 (JB 4.2.2).
However, I'm not allowed to post in the dev-thread for the rom.
According to quite a few reports I read about anything similar (esp. for S3), this issue should be fixed since JB 4.2.0... so either I didn't understand the circumstances (quite probably) or this is something completely different.
What can I do about this? Constantly checking battery charge and/or CPU usage is hardly an option :/
Interesting! Does your phone lag when battery drains, do you have wifi connection issues?
I'm suffering from battery drains and wifi issue. I will check what "top" would show and update you. I'm on sweet rom v10 by the way.
Sent from my GT-N7000 using XDA Premium 4 mobile app
juliobahar said:
Interesting! Does your phone lag when battery drains, do you have wifi connection issues?
Click to expand...
Click to collapse
Wifi is usually fine.
Lags sometimes occur, but I'm not sure if they are connectet to the battery drain. I had the impression they happen mostly when the phone switches from wifi to 3G or vice versa.
Any wild location services running on the background?
I think CIA might be tracking you
Sent from my GT-N7000 using Tapatalk 4
projeto56 said:
Any wild location services running on the background?
Click to expand...
Click to collapse
None that I'm aware of
The only ones that come to mind are Maps/Navigation, Ingress and Facebook. Neither should have been active during these hours.
Is there a way to monitor which app could cause gpsd to use 50% CPU for hours?
For now I'll try swiching off "Wi-Fi & mobile network location" in Location Settings and wait if it happens again...
Mercurye said:
None that I'm aware of
The only ones that come to mind are Maps/Navigation, Ingress and Facebook. Neither should have been active during these hours.
Is there a way to monitor which app could cause gpsd to use 50% CPU for hours?
For now I'll try swiching off "Wi-Fi & mobile network location" in Location Settings and wait if it happens again...
Click to expand...
Click to collapse
Could be location history and location reporting that run automaticaly on the background. It happened a few times with me. Mainly when i force closed my camera app when it was trying to geo tag mt photos. Then the GPS would keep trying to get my location even tough i wasn't using the app anymore.
Some people say that GPSD has nothing to do with gps positioning, but i don't know.
Sent from my Transformer TF101 using Tapatalk 4
Anyone fixed the issue?
Firstly, this is not another thread to complain about your horrible battery life due to Google Play Services. I'm tired of those (mostly on Reddit, but some here too. Either way, none of that here ). This is instead to try and find a root cause for it. "It's Google's fault" is not good enough for me, and if you truly care about your battery life it shouldn't be for you either. If all you're after is an easy way out to get your battery life back, then this thread is not for you. We're here to reach a solution where you can get location services and good battery life. I've done if before, on my Galaxy Nexus on 4.3, but it seems that something is wrong in KitKat. Let this be a place where we all dig deeper into this issue, perform tests, gather results, and then share and discuss them. Here's what I've got so far:
The wakelocks that cause this battery drain are NlpWakeLock and NlpCollectorWakeLock. Nlp stands for network location provider. As you may know, Android provides developers with two ways of gathering location information. One is through the GPS_PROVIDER, which uses the GPS, and the other is through NETWORK_PROVIDER, which uses cell towers and WiFi APs to get your position. According to their developer website[1] , NETWORK_PROVIDER uses less battery, is faster, but is less accurate. GPS uses more battery, takes longer, but is good if you want an accurate location. I'm assuming this particular wakelock uses NETWORK_PROVIDER.
I also did some digging using ROM Toolbox Pro's autostart manager. My guess was that Google Play Services must be triggered every time a certain intent is broadcasted, since nothing obvious is telling it to run. Turns out there are quite a few. 30, to be exact. However, many of them have to do with GCM and we don't really care about those. One of particular interest is one called com.google.android.location.internal.NlpNetworkProviderSettingsUpdateReceiver. It listens for the intent android.location.PROVIDERS_CHANGED. The LocationManager API's documentation[2] tells us this:
Broadcast intent action when the configured location providers change. For use with isProviderEnabled(String). If you're interacting with the LOCATION_MODE API, use MODE_CHANGED_ACTION instead.
Click to expand...
Click to collapse
I'd assume that this means when you change your location providers, such as enabling/disabling data, WiFi, GPS, etc.
However, location reporting only seems to use network location. If you're on KitKat, go to the location settings and choose device only. Then choose battery saving. It asks you to accept location reporting. Same thing when you choose high accuracy. What do both of those have in common? Network location. You can switch between those two as much as you want and it won't ask you to accept again. However, once you switch to device only and back it will ask you. This shows that it only uses network location.
I find that Google (Play) Services has 5% (+/- 1%) keep awake. Tested on both Nexus 5 running KRT16M and Galaxy Nexus running JWR66V. Both use a certain time of GPS, although that number is never increasing. I assume this is some sort of initial one-time lock. It can be disregarded.
One more thing I noticed is that this Google Play Services issue is much more prominent on KitKat. While they have happened before, often times a simple Play Store update would fix it. This time it seems to be location based. Guess what changed in KitKat? The way you deal with location settings. It may be that the way location settings are grouped in KitKat cause that intent to keep firing, and that in turn triggers something that eventually ends up being what you see as NlpWakeLock.
What I'm going to try next is disabling that intent receiver and then monitor that wakelock as well as if location reporting still works. Feel free to play around, and be sure to share your results.
To those who are suffering from these wakelocks, could you please share your settings? Such as what type of location mode you have (high accuracy, battery saving, device only), WiFi on or off, data on or off, signal strength, WiFi always scanning, Play Store and Play Services version, what device you have, Android build number, and what ROM/kernel you're using if you are using one? Any other info such as screenshots of battery screen, betterbatterystats, wakelock detectors, etc. will all be welcomed.
Here is the Reddit thread I created discussing the same issue: http://www.reddit.com/r/Android/comments/1rvmlr/nlpwakelock_and_nlpcollectorwakelock_discussion/
I don't have this device, nor do I know if I'll be getting it, but I must say that I applaud your method.
Bravo!
I just turn location reporting off then select 'battery saving' setting & accept the request for reporting when it pops up. This allows you to use network location without logging. Google now & maps work fine although not quite as accurate. I just turn on gps if i need navigation. Never get more than 2% usage from play services & it's giving me a total kept awake time of about 28mins out of 12hrs of use with 3hrs screen on time.
Sent from my Nexus 5 using Tapatalk
If I disable the wifi and 3g, leave my phone on battery saving location, google location set to on, it is using wifi always scanning only and it didnt consume 1% battery in a whole night
stumpy352 said:
I just turn location reporting off then select 'battery saving' setting & accept the request for reporting when it pops up. This allows you to use network location without logging. Google now & maps work fine although not quite as accurate. I just turn on gps if i need navigation. Never get more than 2% usage from play services & it's giving me a total kept awake time of about 28mins out of 12hrs of use with 3hrs screen on time.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
That is working for me right now.
Sent from my Nexus 5 using Tapatalk 2
ickboblikescheese said:
To those who are suffering from these wakelocks, could you please share your settings? Such as what type of location mode you have (high accuracy, battery saving, device only), WiFi on or off, data on or off, signal strength, WiFi always scanning, Play Store and Play Services version, what device you have, Android build number, and what ROM/kernel you're using if you are using one? Any other info such as screenshots of battery screen, betterbatterystats, wakelock detectors, etc. will all be welcomed.
Click to expand...
Click to collapse
I am experiencing this issue on my Nexus 5, as confirmed by betterbatterystats (NlpCollectorWakelock 5.5% awake time)
ROM: CyanogenMod 11 alpha
Build Number: KRT16S
Location Mode: High accuracy
Location Reporting: Off
WiFi On: Sometimes
Play Store Version: 4.4.22
Play Services Version: 4.0.34
This issue first appeared for me the other day. I noticed that my device was not appearing in the online Android Device Manager, nor the desktop version of the Play Store. To fix the ADM issue, I disabled remote wipe, cleared data for Play Services, reenabled remote wipe, and rebooted. To fix my device not appearing in the Play Store, I cleared data for the Play Store app. Both issues were thereafter resolved, but now I am experiencing the Network Location battery drain.
Is it possible the problem is related to requests from Android Device Manager? I was under the impression that location for that purpose was 'on demand' instead of logged, but what do I know.
Thanks for doing this! Others, please feel free to use my comment as a template, and post your own data.
So I was playing around with autostart, and I accidentally caused a bunch of FCs for Play Services. Ended up freezing/defrosting and then uninstalling updates then let it update itself, and I noticed this (may or may not have anything to do with what I did): Even though it wakelocks, it barely uses up any batter. I was in an area of 2-3 bar HSPA+, with sync on, location reporting on at high accuracy, etc. and it drained 1% per hour. Still kept phone awake ~5% of the time, but battery usage was significantly better over what I recorded to be 4.8%/hour from last Friday.
EDIT: The only other change I can think of making is temporarily freezing Cerberus. I'll have to look more into that. However, check which apps are requesting your location. The new location settings in KitKat make this simple enough. For me it's only Google Now and Google Play Services, and whatever app that happens to require GPS such as camera (geotagging) and maps.
ickboblikescheese said:
So I was playing around with autostart, and I accidentally caused a bunch of FCs for Play Services. Ended up freezing/defrosting and then uninstalling updates then let it update itself, and I noticed this (may or may not have anything to do with what I did): Even though it wakelocks, it barely uses up any batter. I was in an area of 2-3 bar HSPA+, with sync on, location reporting on at high accuracy, etc. and it drained 1% per hour. Still kept phone awake ~5% of the time, but battery usage was significantly better over what I recorded to be 4.8%/hour from last Friday.
Click to expand...
Click to collapse
So, how should I replicate this? I'm using the Xposed Module that dev posted in your Reddit post.
stumpy352 said:
I just turn location reporting off then select 'battery saving' setting & accept the request for reporting when it pops up. This allows you to use network location without logging. Google now & maps work fine although not quite as accurate. I just turn on gps if i need navigation. Never get more than 2% usage from play services & it's giving me a total kept awake time of about 28mins out of 12hrs of use with 3hrs screen on time.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
How do you do this exactly? If I turn location reporting off, then I can't select the battery saving method because it's greyed out. This also causes location based cards to stop working on Google Now and Maps can't locate me either.
---------- Post added at 11:24 PM ---------- Previous post was at 11:19 PM ----------
natezire71 said:
So, how should I replicate this? I'm using the Xposed Module that dev posted in your Reddit post.
Click to expand...
Click to collapse
Use Titanium Backup to FIRST backup Google Play Services. Then use it to uninstall GooglePlay Services. Then open Google Now or Maps, they will ask you install Google Play Services and take you to the app store.
If anything goes wrong, use Titanium to restore.
You need location toggled on. Go down to location services & click on Google Location Reporting. Select off for both settings. Then go back out & select battery saving mode & accept the terms.
Sent from my Nexus 5 using Tapatalk
stumpy352 said:
You need location toggled on. Go down to location services & click on Google Location Reporting. Select off for both settings. Then go back out & select battery saving mode & accept the terms.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Turns out that's exactly how I had set up after all, doh! Thank you.
I have actually been getting really decent battery life, noticeably better than my HTC One, with exactly similar usage patterns and same apps installed etc.
Also, Play Services is not the only app that uses this NlpWakeLock. Facebook also uses it & in my case has the highest time kept awake. I turned off location in chat & noticed that it is much better.
Sent from my Nexus 5 using Tapatalk
That's what I thought too. That could explain why some people have this issue more than others.
Sent from my Nexus 5
ickboblikescheese said:
That's what I thought too. That could explain why some people have this issue more than others.
Sent from my Nexus 5
Click to expand...
Click to collapse
Have you tried the Xposed module that filters wake locks? I've been using it and the NLP counts have drastically dropped
No, not using xposed. I understand that wake locks must occur for accurate location services (otherwise what is doing the reporting). What shouldn't be there is the incredible battery drain. Wake locks don't necessarily mean battery drain. You could have a 1h wake lock and drain 1% battery, or a 5 min wake lock that keeps CPU on high frequency causing a 10% battery drain. I don't mind wake locks as long as battery isn't affected too much.
Sent from my Nexus 5
ickboblikescheese said:
No, not using xposed. I understand that wake locks must occur for accurate location services (otherwise what is doing the reporting). What shouldn't be there is the incredible battery drain. Wake locks don't necessarily mean battery drain. You could have a 1h wake lock and drain 1% battery, or a 5 min wake lock that keeps CPU on high frequency causing a 10% battery drain. I don't mind wake locks as long as battery isn't affected too much.
Sent from my Nexus 5
Click to expand...
Click to collapse
That was the point of this module. https://play.google.com/store/apps/details?id=in.andro.wlt. Take a look and read the description. From my understanding, the location stuff still works--which for me has been the case. However, it stops the unnecessary wakelocks. I would like to believe my battery has improved.
Nice thread!!
I've changed my location settings and I'll report if it works!!!
Thanks!!!
natezire71 said:
That was the point of this module. https://play.google.com/store/apps/details?id=in.andro.wlt. Take a look and read the description. From my understanding, the location stuff still works--which for me has been the case. However, it stops the unnecessary wakelocks. I would like to believe my battery has improved.
Click to expand...
Click to collapse
Please keep us posted on this works out for you, it looks really promising!
the7thson said:
Please keep us posted on this works out for you, it looks really promising!
Click to expand...
Click to collapse
I think it's working.
natezire71 said:
I think it's working.
Click to expand...
Click to collapse
Can you tell us which apps you disabled wake locks for?
Sent from my Nexus 7 using Tapatalk 4
wlan_wow_ml is causing the majority of my drain. I'm not too familiar with this one. msm_serial_hs_rx is also very high. I've tried everything I can to get better battery life. I average about 20hours with 4-4.5hours screen on time.
Any ideas?
I get a lot of this wake lock as well, no idea what it is
The first one is the connection to a wireless network. No idea on the second. Download gsam battery monitor. Let it run for 24 hrs after a full charge. Gsam has a built in app called app sucker. Open that and at the top there is a drop down menu to view kernel wake locks. Then you can select each one and after that opens there's a button that says Google me. That'll tell you what each one is.
Sent from my Nexus 10 using XDA Free mobile app
I posted this on the Motorola Support forums as well as a question on the msm_hsic_host wakelock and one person said this
"I think that the "wlan_wow_wl wakelock" is a software lock included in the Android OS and installed so that your phone does not wake every time it sees your (or other) wireless network access points. I believe the msm_hsic_host wakelock is related to the data radio for the same purpose. Both designed to keep battery drain to a minimum when the phone is idle.."
so guess these wakelocks are good to have.
So these are wakelocks to avoid wakelocks? Lol
cyberr8der said:
So these are wakelocks to avoid wakelocks? Lol
Click to expand...
Click to collapse
i guess?? lol
These wakelocks are too high to ignore...
It seems to be related to qualcomm drivers and afaik they already fixed it, but we need to wait for Motorola to implement the fix in a future update.
I have the same problem. This caused my battery to drop 10% idling for 6 hours with no apps installed. I hope it gets fixed soon.
Here we go again...
8 hours awake (because of msm_hsic_host and wlan_wow_wl)... This can't be right.
Is there any solution with battery drain"wlan_wow_wl wakelock"?
ramzal said:
wlan_wow_ml is causing the majority of my drain. I'm not too familiar with this one. msm_serial_hs_rx is also very high. I've tried everything I can to get better battery life. I average about 20hours with 4-4.5hours screen on time.
Any ideas?
Click to expand...
Click to collapse
Do you have this app installed : https://play.google.com/store/apps/details?id=net.loadinghome.smartunlock
Or anything similar that uses some kind of rule based on wireless SSID ?
Or even an wireless files sharing app that stays on ?
That wlan_wow_wl is cased of periodic scans of the wireless status IMO, like searching for networks around you or looking if you are still connected to certain network!
You could try disabling "always WiFi scan". In Android 5 is found under advance settings from WiFi menu(from the 3dots menu), in Android 6 is found under geolocalisation (GPS) in the search menu(from the 3dots menu)
Inviato dal mio XT1575 utilizzando Tapatalk