Database Develop

Battery drain due to Google Maps

Hi guys,
I've had the Xperia Z, and i'm not even remotely close to getting the battery life some people on here are getting.
I'm unrooted and followed the advice on here for better battery life, but still cannot get 4 hours of on screen time.
Anyways, over the weekend, i've noticed Google Maps suddenly taking up huge amounts of battery.
I've barely been using Maps or indeed barely using any app that uses location based services.
Even over night, my battery would drain 15% and Google Maps was clearly the culprit when looking at apps using the battery.
It was even stopping stamina mode from kicking in.
I disabled GPS.
that didn't fix my problem.
I tried to Force Stop Google Maps.
that didn't fix my problem.
For example, i could charge my battery to 100% to reset my battery stats, then do nothing else but immediately watch half an hour of a film, and incredibly Google Maps would magically be the app thats drained the battery the most, like double that of the screen or triple that of media server!
So last night, i reset my phone back to factory settings, reinstalled all my apps, but i haven't applied the Google Maps update.
so far so good. so far, it is behaving itself.
has anyone else had this problem?
I don't know whether i should update Maps or not.
its weird, for the first couple of weeks, it wasn't an issue, so i don't know why it suddenly became a problem, but it was massively draining my battery, even when i had done everything to disable it!
under the reviews in google play, if i filter reviews for just reviews by users with XZ, i can only see one other person complaining of the same problem.
i couldn't find anyone else posting about this issue when i googled it.
So anyone else have this problem, or know why it is/was happening?
thanks,

It isn't the version of maps you are using that causes the issue. It is 'location settings'.
If you go into location settings in Maps, you will see that you can turn on and off things such as Location reporting, Report from this device, Enable location history etc.
Some of these are required to run Google Now to its full potential, however they cause quite a high level of partial wakelocks.
It is up to you whether you have them switched on (with some battery drain), or switched off (with no/little battery drain).

I also noticed a larger than normal battery drain since a couple of days. I can't remember if there was a gmaps update right before the drainage increase.

Just for the sake of repetition silly. This has nothing to do with the Maps version.
FYI - The last Maps update was on 12th March. Point proven therefore.

nobnut said:
It isn't the version of maps you are using that causes the issue. It is 'location settings'.
If you go into location settings in Maps, you will see that you can turn on and off things such as Location reporting, Report from this device, Enable location history etc.
Some of these are required to run Google Now to its full potential, however they cause quite a high level of partial wakelocks.
It is up to you whether you have them switched on (with some battery drain), or switched off (with no/little battery drain).
Click to expand...
Click to collapse
BUT like i said, i had turned all of these off, and MAPS was STILL draining my battery, despite location based services turned off, Maps forced stopped and not even using any location based app.
That is what i am querying. Why was this happening?
random quirk, or a more serious problem?

In that case I have no idea. It doesn't happen for me.
What I have noticed before once or twice however is that my location settings have changed without me doing it manually. This has happened to me twice when I have (un)installed Now.

nobnut said:
In that case I have no idea. It doesn't happen for me.
What I have noticed before once or twice however is that my location settings have changed without me doing it manually. This has happened to me twice when I have (un)installed Now.
Click to expand...
Click to collapse
i'm hoping its just a random quirk.
On friday, i noticed maps was using quite a bit of battery.
Saturday, Sunday and Monday however, it just went crazy.
I could lose 15% battery when my phone was asleep all due to Maps.
well, I reset my phone to factory settings 12 hours ago, and so far the problem has not repeated itself.
i've got GPS on, location based services on, and so far Maps isn't doing anything it shouldn't be doing.
I will definitely keep an eye on it and update this thread as and when.
I've had this phone 3 weeks, so i don't know why it suddenly became a problem on friday. The only thing i changed on friday was i installed new app Google Keep which almost certainly cannot be the culprit that i can see

NlpWakeLock and NlpCollectorWakeLock Discussion

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

Android system draining battery

I'm not sure what's considered high android system but mine is at 29% and looks like it's taking a toll on my battery. When I check the battery usage it's the highest thing listed. How can I lower this or fix this? Any help is greatly appreciated! I love this phone!

same problem here ... android system is at 24% with 59 minutes of CPU usage while screen was about 20% with more than 2 hours of screen on time !?! Why system is killing the cpu so much ? ... TouchWiz !!! *SMH*

Give it a week or so to even out.

This could be any app that is pulling your location. Most pull through your location through google play services, part of the android system. Not defending touchwiz usage but most likely the fault lies elsewhere.

xxsxx said:
This could be any app that is pulling your location. Most pull through your location through google play services, part of the android system. Not defending touchwiz usage but most likely the fault lies elsewhere.
Click to expand...
Click to collapse
I dont think so my location its off and still takes 29%, maybe a kernel issue. I heard they did the update we just got cause battery draining issues. maybe not fixed 100%

I get the same thing and I made sure to turn off notifications and apps that "push" and set em all to manual. I use the same apps and settings on my S5, and LG G3 and would be able to get around 6 hour screen time and total of 17-20 hours per charge. AND on those devices, the screen is usually the highest % and the android system is not even near that %
Right now I'm getting almost about the same as my S5 battery life, maybe a bit shorter...

Same problem here, about 42% on a normal usage. I did not have this problem before, on stock Rom but since I switched to cynanogenmod, my phone can't make it through the day.
What's more, I'd like to know if any of you know an xposed module or an app which can automatically turn switches on/off when starting/closing an app. Like turning GPS on when starting Google Maps and turning it back off when closing the app, for instance.
Sent from my Xperia Z1 Compact using XDA Free mobile app

Good queetion, I'd be interested in that as well
Sent from my SAMSUNG-SM-N910A using XDA Free mobile app

mines also like this

I found this was related to location services and / or google now.
I found these worked for me:
1. Turning GPS location to GPS only (i.e. not using wifi). I believe this stops passive location tracking, which in turns stops the other services always running
2. Turning off location tracking / history. As above, no detailed location, no other fancy things running all the time.
3. Turning off Google Now.
I listed the above in the order I would do it. Using just item one, you still get most of Google Now's functionality.
End of the day, what I found was there was a lot of "smart" stuff going on in the background around your location, and this is what caused most of the CPU time. If you look at your wake locks, you will see it drop off dramatically once you do the above steps.
Some people have reported turning location services back on after a while didn't result in a spike in CPU time.
This isn't a Note 4 thing, more a Android / Google Now thing in my opinion,.
Hope it helps.

mrja22 said:
I found this was related to location services and / or google now.
I found these worked for me:
1. Turning GPS location to GPS only (i.e. not using wifi). I believe this stops passive location tracking, which in turns stops the other services always running
2. Turning off location tracking / history. As above, no detailed location, no other fancy things running all the time.
3. Turning off Google Now.
I listed the above in the order I would do it. Using just item one, you still get most of Google Now's functionality.
End of the day, what I found was there was a lot of "smart" stuff going on in the background around your location, and this is what caused most of the CPU time. If you look at your wake locks, you will see it drop off dramatically once you do the above steps.
Some people have reported turning location services back on after a while didn't result in a spike in CPU time.
This isn't a Note 4 thing, more a Android / Google Now thing in my opinion,.
Hope it helps.
Click to expand...
Click to collapse
thanks for the advice and suggestions, but my s4 and s5 did not have the "android system" so high in usage. i've tried the turning off gps, then back on, and then restart phone thingy, but same results. i just hope sammy would address this issue as it seem pretty widespread.

MMakoto said:
thanks for the advice and suggestions, but my s4 and s5 did not have the "android system" so high in usage. i've tried the turning off gps, then back on, and then restart phone thingy, but same results. i just hope sammy would address this issue as it seem pretty widespread.
Click to expand...
Click to collapse
Just to clarify,Ii suggest turning location to GPS only. And leaving it off.
Turn off location reporting and history also. Then see what results you get and go from there

I'm having the same thing ...

I just received a update that is supposed to fix the battery drain issue. We shall see if it works.

railslave said:
I just received a update that is supposed to fix the battery drain issue. We shall see if it works.
Click to expand...
Click to collapse
The update that came out this week or a different one.

mrja22 said:
I found this was related to location services and / or google now.
I found these worked for me:
1. Turning GPS location to GPS only (i.e. not using wifi). I believe this stops passive location tracking, which in turns stops the other services always running
2. Turning off location tracking / history. As above, no detailed location, no other fancy things running all the time.
3. Turning off Google Now.
I listed the above in the order I would do it. Using just item one, you still get most of Google Now's functionality.
End of the day, what I found was there was a lot of "smart" stuff going on in the background around your location, and this is what caused most of the CPU time. If you look at your wake locks, you will see it drop off dramatically once you do the above steps.
Some people have reported turning location services back on after a while didn't result in a spike in CPU time.
This isn't a Note 4 thing, more a Android / Google Now thing in my opinion,.
Hope it helps.
Click to expand...
Click to collapse
Thanks a lot ...
Location tracking off made a big difference ... Things are already looking good. I will only turn on the GPS when need be.

Mr.37 said:
Thanks a lot ...
Location tracking off made a big difference ... Things are already looking good. I will only turn on the GPS when need be.
Click to expand...
Click to collapse
Good to hear.
I found I can have GPS on without any issues, as long as either Google Now or location tracking was off.

Any more info ?

I am having the same issue in tandem with weak battery signal. Do I wait for Lollipop or do I just sell my N4 and get an S6?

[Q] Battery settings in 23.5.A.1.191

I've noticed that the battery life got worse with the latest 23.5.A.1.191 update. With previous version I could leave the phone on desk overnight and the battery did not drop at all (flat line in the battery usage graph). Now with the Stamina comeback I can see a 10 to 15% drop overnight. Can you please share your ideas what settings I should look into to fix it? Thanks

Have u check your wakelock? Play services often do this idiot bug.

Yes, Play services was the app draining the battery, but I remembered that I installed Google Fit in the meantime. Additionally something got messed up with the location after the last update, so I did not see a detailed route but just a large circle on the map in Fit (maybe permissions for gps location?).
However uninstalling Google Fit fixed it. I woke up today and saw a flat line in the battery usage.

I leave data usage over night and , since I have this phone, my battery draining from Google Play services is abnormal. I only synd gmail, no other service, no other permission. I've used Gservicefix without any result. Does anybody know why?

SoulFury said:
I leave data usage over night and , since I have this phone, my battery draining from Google Play services is abnormal. I only synd gmail, no other service, no other permission. I've used Gservicefix without any result. Does anybody know why?
Click to expand...
Click to collapse
There are lots of reasons why Google Play Services are eating your battery, try a few fixes yourself, check which version of Play Services you have installed , anything older than 9.4.52 needs replacing.
Remove your google account, wipe data for Play Services and Download manager, restart to recovery, wipe cache/dalvik. Restart phone, add account again.
There seems to be issues with fitness trackers and bluetooth, if you have bluetooth on all the time, see what happens if you turn it off?
I can recomend Greenify app that can make a difference in putting apps to sleep, it also helps you see which apps are awake and on.
Check in settings/developer options/running services to see what's on and using most memory, you might be surprised at what you find. To enable developer options go to settings/about phone - press on build 8 times, then you get a message that develper options are availabe in the settings menu.

SoulFury said:
I leave data usage over night and , since I have this phone, my battery draining from Google Play services is abnormal. I only synd gmail, no other service, no other permission. I've used Gservicefix without any result. Does anybody know why?
Click to expand...
Click to collapse
the first couple of days after an update or a factory reset, google play services collects a lot of information. It should go back to normal after some days. Anyway, I can give you some suggestion to limit the battery drain:
- new Stamina is a rebrand of the normal battery saver. Don't keep it always on.
- if you want something reminding the old stamina, download Greenify, follow instruction for adb command to enable Aggressive Doze and enable Doze on the go. Take away optimization from battery advanced setting for apps you need push notification from (e.g. whatsapp)
- disable wifi scanning when wifi is off (search in settings wifi scanning, though the search button. If your language is different from English (US) and you don't find the setting, switch to English (US) to find it)
- restrict google play services background data when not in wifi
- in account/google disable the sync for whatever you don't strictly need (play newstands, g+, ...)
With this settings, I can get 5 hours sot in a couple of day of usage, and almost no battery drain over night.

Well, my daily use consist on:
- Traffic data always on
- watch clock when needed
- +-45min WhatsApp
- Some random search.
- Some rare use of torch
- Sync with Gmail(ONLY Gmail)
I only use wifi for updates and don't have any gps or bluetooth use...Battery last above 48h this way and google services hast half of time with radio antena on.

Odd battery life

Hello,
Since the purchase of my phone XZ1 Compact (G8441), I've been experiencing barely acceptable battery life. This is especially frustrating since I bought this phone having heard that it can last easily 2-3 days, but this is not the case for me (discharging about 4%h on average or 2.5%h with screen off on either wifi or mobile data, with various configurations outside/home/office, i.e. in practice never usable more than a day).
According to *#*#SERVICE#*#*, the battery life is still good (2704 mAh). The issue I am experiencing is most likely due to an unknown software and/or hardware failure leading to lots of wakelocks that prevent the phone from "sleeping"/"dozing" correctly.
I know that MANY users worldwide are experiencing this and Sony never gave an answer to this, according to e.g. the following threads:
https://talk.sonymobile.com/t5/Xper...-drain-after-update-47-1-A-12-235/m-p/1337029
https://talk.sonymobile.com/t5/Xper...-drain-after-47-1-A-12-205-update/m-p/1328053
https://forum.xda-developers.com/xperia-xz1-compact/help/battery-life-bit-odd-t3688342/page8
https://talk.sonymobile.com/t5/Xperia-XZ1-Compact/High-battery-drain/m-p/1326474 https://talk.sonymobile.com/t5/Xper...-drain-after-update-47-1-A-12-270/m-p/1340671 https://talk.sonymobile.com/t5/Xper...pie-battery-drain-CPU-idling-high/m-p/1354891
and many others
In my case the items "NlpWakeLock" and "RILJ_ACK_WL" activate both up to thousands of times every hour. No relevant information could be found about this in the web lookups I've done, and I am not sure this is related to the issue I'm facing. I joined a log of today's better battery stats with a pathetic 1h20 of SOT and 65% discharge, a huge count of wakelocks except when I was listening to music, and an apparent faster discharge with the idle phone than when actually used.
The phone is running the latest downloadable Sony firmware 47.2.A.10.107.
Of course, factory reset was tried with no amelioration and I tried to contact directly Sony which have basically no willingness to help or investigate.
Anyone would have a clue about this?
Thanks,
Alexandre

Do you use Google Now (google assistant) - NlpWakeLock
If not, disable it and see what happens.
This little phone I have for battery life and for banking/authenticator/etc. Not for work. So I have disabled most things I do not need (adb uninstall) - so the battery is quite good on standby.

Thanks for the reply. Unfortunately, as I don't use GoogleNow, the whole Google App is already disabled...
I'll try and do some adb uninstall and will keep you posted

alexounet2 said:
Anyone would have a clue about this?
Click to expand...
Click to collapse
Looking at the bbs stats. The first thing I noticed is that your wifi is on all the time. Try turning it to only when awake and disable the wifi scanning in locatin settings.
RIL wakelocks are on because you have poor signal, it's the number of handhakes your phone does with the local cell tower and if you have bad signal, it gets higher.
Some providers offer home 4g boosters for your home or 'calls over wifi', either of these would reduce your battery usage.

My phone has been flawless (2-3 days on battery when I don't play games) but suddenly it started behaving like described in the original post.
It has 1 day life now and I haven't found the reason for this change. I have removed all recently installed apps, removed all unnecessary apps (including Facebook app), disabled running in background for some (like Messenger), there was no firmware update at that time. Still something is eating up the battery. SmartPanel tool shows that 58% of battery is Unaccounted (next is display and Google Services). I have not done the factory reset yet because I need fully configured phone right now.