So my phone is basically close to 100% awake due to a constant GPS wakelock. The battery info shows GPSD as the #1 drainer and BetterBatteryStats shows ours of GPS wakelocks. I've read as most GPSD drain threads, but none have been helpful.
These are my current settings:
Location Services -> Access to my location UNCHECKED
Use GPS Satellites DISABLED
Use wireless networks DISABLED
Google Settings -> Access Location UNCHECKED
Location Reporting DISABLED
Location History DISABLED
Android Device Manager -> Remotely locate this device DISABLED
Allow remote lock UNCHECKED
Security -> Remote Controls OFF
Besides that, I've frozen all known apps which use GPS (maps, waze, etc) with Titanium Backup.
I've wiped, and reflashed some roms (ArchiDroid mostly). Usually the drain is not present, but after some days it begins.
The phone may have no GPS wakelocks for some time, then GPSD drainage is triggered after using a GPS apps.
I'm rooted, and running out of options. Is there a way to know which process is invoking the GPS? Any suggestions?
I appreciate the help.
To eliminate software as a cause flash a full stock firmware then factory reset, run it for a few days without installing or restoring any apps/settings.
If it occurs during the test then it might be a hardware fault.
Related
I recently installed Semi V17 and an updated BetterBatteryStats version. With that combination, I noticed that my device was never able to move into deep sleep due to constant location updates, thus causing battery drain. I think I've narrowed down the culprit for my battery drain, however, I'm not sure I know how to resolve it. It appears to be the Latitude support in Google Maps. I'm not enrolled in Latitude, but based on "adb shell dumpsys" output, it appears that it is running and requesting location updates constantly. The following is the registration for location updates from dumpsys. Notice that it is specifying no minimum time or distance, which implies (to me) constant updates.
Code:
Receiver{419e7ad0 Listener [email protected]}mUpdateRecords: {passive=UpdateRecord{421e75a0 mProvider: passive mUid: 10084}}:
passive:
UpdateRecord{421e75a0 mProvider: passive mUid: 10084}
mProvider=passive mReceiver=Receiver{419e7ad0 Listener [email protected]}mUpdateRecords: {passive=UpdateRecord{421e75a0 mProvider: passive mUid: 10084}}
mMinTime=0 mMinDistance=0.0
mSingleShot=false
mUid=10084
Dumpsys identifies the 10084 process as the LocationFriendService:
Code:
*APP* UID 10084 ProcessRecord{41af23e8 13037:com.google.android.apps.maps:LocationFriendService/10084}
class=com.google.googlenav.android.AndroidGmmApplication
Does anyone have any idea how to disable this service without completely freezing/removing the Google Maps application?
Thanks,
Craig
Have you turned off automatic location detection in the Latitude/Maps settings? You can completely disable it or set so it asks you to update it manually.
Also if you have Facebook installed make sure you disable location reporting in your Facebook app settings. That was a big one for me.
One other thing to check is any widgets that use location detection (like weather widgets).
In settings... same place where you enable the GPS.
Strangely, I had to click through to enable Latitude before I could get to the settings to control Latitude and really shut it off. I've now turned off everything I could find related to Latitude and will see if that "sticks". Previously, it would seem to work for some period of time and then all of the sudden start running like crazy, so until I've run like this for at least 24 hours I'm just not going to know if I've truly managed to disable this service.
Next time, check here first.http://www.chucknorrisfacts.com/
Sent from my SAMSUNG-SGH-I777 using Tapatalk 2
csetera said:
Strangely, I had to click through to enable Latitude before I could get to the settings to control Latitude and really shut it off. I've now turned off everything I could find related to Latitude and will see if that "sticks". Previously, it would seem to work for some period of time and then all of the sudden start running like crazy, so until I've run like this for at least 24 hours I'm just not going to know if I've truly managed to disable this service.
Click to expand...
Click to collapse
It appears like disabling all things Latitude has cured my battery drain. If only they hadn't hidden those settings, it would have been way more obvious. Thanks for the tip.
Over the last few days my battery has been draining faster than usual. I've just noticed that the NetworkLocationLocator Google service is at the top of the BetterBatteryStats list, registering 196 partial wakelocks in 2:37 minutes - 13m 4s.
The problem is that I have location tracking turned off in Google Maps (location reporting, location sharing, location history, automatic check-ins and check-in notifications).
Why is the NetworkLocationLocator service draining my battery when I have location settings turned off?
check under location services in settings
Skickat från min GT-I9300 via Tapatalk 2
I had the same issue. Just disconnect the use networks WiFi on settings location and it will solve this problem. I was experience this on stock ics with stock kernel.
Sent from my GT-I9300 using Tapatalk 2
Google now wastes a lot of battery using the process you've mentioned too.
Best way would be as suggested above, uncheck all location related boxes under location settings
Sent from my GT-I9300 using xda premium
Is there any other way to get rid of the frequent NetworkLocationLocator wakelocks than disabling Wifi and Network based Location. I belive the culprit might be an app that asks the service for location and disabling that app (or the location function inside the app) could solve the problem.
Google now is disabled and I don't have Maps installed. Altough I'm having ~2.5 wakelocks per minute. Ideed, disabling network based location solves the issue, but obviously this will prevent some apps that rationally use location from providing 100% functionality (eg. weather apps).
having the same wake lock issues myself since JB 4.1.2 update on my S2, fed up of it taking the battery now. why it polls so often is beyond me.
Turn off location using wireless network under location services setting
Sent from my GT-I9300 using xda premium
xcly said:
Turn off location using wireless network under location services setting
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
That's a workaround. One might need Network Location, so there has to be a real fix of the issue.
xcly said:
Turn off location using wireless network under location services setting
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
_polimorph_ said:
That's a workaround. One might need Network Location, so there has to be a real fix of the issue.
Click to expand...
Click to collapse
yep i turned it off and within an hour i used an app that needed it!
Is there likely to be a full fix to this problem? I have the same kind of issue - I turn off the Wifi/Network option in location options so that Google doesnt poll my location every x minutes, but I find this gives me options with Facebook. Instead of Facebook getting its location in a couple of seconds by asking Google to get it, Facebook instead initiates the GPS in the phone and takes a few minutes to get a lock because i'm inside the house. I'm running cm10.1 not stock btw.
Same issue - SGS2
Hi,
I had exactly the same problem on my Galaxy S2 with MIUI official:
NetworkLocationLocator wakelock from Google Services(not maps, its important!) was up at 8-20% of the time.
I did some research.
First of all, I did full wipe. Wakelock arrived on second reboot after adding google account, so installed apps are not the problem.
I found an opinion that mysterious Google Checkin Service was behind that wakelock, so I disabled that stuff completely by modifying corresponding values in GServices DB. Wakelock was still there.
I am stuck completely, at this point I have no idea what might cause this.
On another rom, 4.2 Paranoid Android, it's all fine, I get only 1-3% of NetworkLocationLocator from GMaps, but thats another story.
If anyone has any ideas - you are welcome.
If there are another MIUI users here - check your battery stats please(stock android battery graph is ok). Do you have 'barcode' on awake graph? If yes - than we have really global problem here...
Bump
this is terrible.
_polimorph_ said:
Is there any other way to get rid of the frequent NetworkLocationLocator wakelocks than disabling Wifi and Network based Location. I belive the culprit might be an app that asks the service for location and disabling that app (or the location function inside the app) could solve the problem.
Google now is disabled and I don't have Maps installed. Altough I'm having ~2.5 wakelocks per minute. Ideed, disabling network based location solves the issue, but obviously this will prevent some apps that rationally use location from providing 100% functionality (eg. weather apps).
Click to expand...
Click to collapse
have you tried google settings -> location -> off
I had the google services issue on M1 and M2.
This work around fixes it for me, only had to do it once on M2.
I reboot into recovery (I'm running clockwork recovery) flash gapps (3/1) reboot.
I DO NOT wipe cache or davalink.
Seems like Google services does it after a new flash but I never really saw a reliable pattern myself.
I'm having the best battery life on M2!
Hope it helps? Let me know.
Bump
This is a horrible issue that is still very present on latest nightlies, and has been for around two months, as of this posting.
Completely disabling location services is not a solution, and it is not a work-around.
We need some ability to trace the source of these location requests. There is no useful information in the logcat.
Location services should be providing some of its own statistics on which applications are polling for location.
seems to have dropped 90% since the google maps update!
Hi,
Whenever the "Use wireless networks" setting is on under "Location services", I get constant "nlpwakelocks" and battery drain.
However, I see that this was supposidely fixed by Google: http://www.androidpolice.com/2013/05/29/download-latest-google-play-store-4-1-10/ (my version is 4.3.11).
Does anyone else have this issue? I've only started looking into wakelocks and have had the phone 5 months and have never had better battery than with this option turned off. Yes the simple answer is "turn it off", but I find I can get location locks quicker with it on, and also my phone can locate me when indoors.
I use Google+ location services so I can locate trusted friends (and they can locate me), and previously Google Latitude, but surely they shouldn't be constantly requesting my location and Android should prevent this in someway?
Cheers.
I too suffered this issue (several times on different roms). Nlpwakelocks appeared in an insanely high abundance (several thousand wakelocks in a single day).
My first fix consisted of uninstalling all updates of google play, google services framework and google play services, clearing caches and deleting the data of the before mentioned in Appmanager, then do a reboot and re-install the updates again. Magically, the number of wakelocks dropped to a quite acceptable level. It still was the major cause of wakelocks, but it didn't drain the battery nearly as much as before. Since then, I had the "Use wireless networks" setting enabled without heavy battery drain. I could happily live with this result.
However, since I updated to 4.3 (CM 10.2), there's no longer a button to uninstall updates of those services in AppManager. Luckily though, clearing caches and data then reboot seems to suffice now.
The only caveeat seems to be google maps. Since the update, you need to be logged in to your google account to see your favorite places in google maps. Unfortunately, maps then begins to poll your location every few minutes, thus raising nlpwakelocks to an alarming level again.
Since I've not found a workaround for this yet, I always logout of google maps after use and login again when needed. Not very comfortable, but this way I'm still able to use Google Now while experiencing an acceptable battery life.
Hope this helps!
Here's the fix, if you're rooted: http://forum.xda-developers.com/xposed/modules/mod-nlpunbounce-reduce-nlp-wakelocks-t2853874
Hey guys,
On my second samsung device and my fifth rom (including eclipse TW, eclipse AOSP, aokp, CM10, now hyperdrive). Have to say thay I'm satisfied with pretty much everything Hyperdrive has to offer, its freaking amazing! One issue doesn't seem to be resolving despite many attempts. My phone stays awake nearly 100% of the time with a wlan_wake wakelock. This isnt the well documented wlan_rx_wake wakelock, which I've also had in the past but managed to squash. I'll recount my findings in some order below.
I installed Hyperdrive, restored some some vital apps. Waited a couple days and found the battery wasn't what I'd hoped it'd be. I usually run with auto sync enabled for total 8 mins per hour (via Tasker) and wifi and mobile data on. I've also used a script that disables IPv6 whenever it connects to a wifi network -- work network has tons of IPv6 broadcasts that were triggering massive wlan_rx_wake wakelocks which were vastly reduced with this fix. Even with these throttles, I noticed that some time after boot (10-15 minutes) on my work as well as home network (10 mixed devices on a belkin router), a wlan_wake wakelock would start triggering and my phone would then stay awake 90-100% of the time, screen on or off.
I went ahead factory reset the phone, loaded just my google account, and found the same problem with autosync on, autosync off, GPS was off, Wifi "always allow scanning" option was disabled in the advanced menu, Google's Wifi network location was disabled, and no 3rd party apps except for BBS installed. Of course, with Wifi disabled, the issue abated but 3g/4g doesn't offer much better battery life than the phone staying awake the whole time. During this time, I used Network Logger and Shark for Root to attempt to identify Wifi traffic and found that a few apps were transmitting frequently, but not enough to keep the phone awake for the amount of time the wakelock indicated. Total battery drain is up to 8-10%/hour with absolutely minimal use. I've never had this particular issue with any other OS i've installed, any ideas what could be going on? Really looking forward to being able to rip through days without charging on Hyperdrive!
I have a Samsung Note 3 and I too have this same problem (except that a factory reset solves it). Can't seem to find a fix. People on internet suggest that it's because of some rogue app but my phone starts behaving like this randomly until I do a factory reset.
One day phone started to lose battery. Using betterBatteryStats I've found that it is caused by kernel wakelock lli_cp_wlock. It appears without any pattern and I can stop it only rebooting the phone. I've tried to reinstall the system and flash newest firmware, but it hasn't helped. Searching the internet I've found that lli is low latency interface controller which is connected in some way to the modem. Any idea how to deal with it? samsung g850f android 5.0.2 stock rom
P.S. sorry for my english, it is not my native language
Same problem exactly here. Doesn't anybody have any clue on what a solution would be? This "lli_cp_wlock" wakelock comes and goes wherever it wants.
magukraine said:
One day phone started to lose battery. Using betterBatteryStats I've found that it is caused by kernel wakelock lli_cp_wlock. It appears without any pattern and I can stop it only rebooting the phone. I've tried to reinstall the system and flash newest firmware, but it hasn't helped. Searching the internet I've found that lli is low latency interface controller which is connected in some way to the modem. Any idea how to deal with it? samsung g850f android 5.0.2 stock rom
P.S. sorry for my english, it is not my native language
Click to expand...
Click to collapse
teo_3 said:
Same problem exactly here. Doesn't anybody have any clue on what a solution would be? This "lli_cp_wlock" wakelock comes and goes wherever it wants.
Click to expand...
Click to collapse
Try to turn off functions or apps that use GPS/location or background syncing,
and turn on GPS/location manually only when you need it.
Functions that use GPS/location like:
Google Location History
My places/Find my phone
Google remote control
Samsung remote control
GeoLookout(weather notifications)
Weather syncing(use current location)
Just check everything in settings/Google settings and turn off those you don't use.
And social networking/messaging/email apps would background sync
or check for push message regularly,
try to turn off sync or turn off app features that use locations or uninstall them
and see if there's difference in battery usage.
hcckyy said:
Try to turn off functions or apps that use GPS/location or background syncing,
and turn on GPS/location manually only when you need it.
Functions that use GPS/location like:
Google Location History
My places/Find my phone
Google remote control
Samsung remote control
GeoLookout(weather notifications)
Weather syncing(use current location)
Just check everything in settings/Google settings and turn off those you don't use.
And social networking/messaging/email apps would background sync
or check for push message regularly,
try to turn off sync or turn off app features that use locations or uninstall them
and see if there's difference in battery usage.
Click to expand...
Click to collapse
All these are done from my part at least and more. Nothing happens. It is not an app problem, it is an Android System battery drain.
I installed BetterBatteryStats_xdaedition_2.2.0.0B5 as a system app,
and here's what I've noticed so far:
The percentage in "Kernel Wakelock" is percentage of time,
not percentage of battery usage.
My percentage of lli_cp_wlock is less than 1%,
so if your percentage is high, it should be related to some apps.
The percentage of battery usage is in "Process",
check here to see what apps drain the battery the most.
The percentage in "Alarms" is percentage of wakeup counts,
have you checked the numbers here?