If I turn that option off it cant locate me anymore. Are you currently staying at the last location that you were staying while that option was on?
NlpWakeLock and NlpCollectorWakeLock Discussion
- Thread starter DoesntPostAThing
- Start date
Good point, I'm still at the same location, will check when I move tomorrow.
Hello all,
Did anyone notice that now Foursquare APP is consuming a lot of battery due to NlpCollectorWakelock? I've monitored yesterday and since 4.4 KK I have this wakelock constantly ON even that I selected under \Settings\Location\Mode - Battery Saving. So I wonder if there is anyone else who is having this wakelock from Foursquare APP?
If I select from \Settings\Location OFF completely when I'm enter in Foursquare is not letting me to do any check-in due to this settings that is OFF. But before 4.4 I had this Locations stuff to OFF and I was able to check-in
thanks
Did anyone notice that now Foursquare APP is consuming a lot of battery due to NlpCollectorWakelock? I've monitored yesterday and since 4.4 KK I have this wakelock constantly ON even that I selected under \Settings\Location\Mode - Battery Saving. So I wonder if there is anyone else who is having this wakelock from Foursquare APP?
If I select from \Settings\Location OFF completely when I'm enter in Foursquare is not letting me to do any check-in due to this settings that is OFF. But before 4.4 I had this Locations stuff to OFF and I was able to check-in
thanks
lets see if the new 4.4.1 update or the new radio cures this issue, feedback is welcome
I was just having an issue where overnight I started losing 20%+ battery where before it was 4-5%. I removed My T-Mobile, Google Rewards and Foursquare as they were the apps updated during that time. Battery has gone back to normal for me. :highfive:
Follow-up: I did another test last night. All settings were the same except I turned Google Location Reporting and Location History to ON.Ok so I did the overnight test, here are my results:
ROM: Cataclysm Nov 26 stable
Kernel: Stock
Wifi: on all night
Signal strength: Poor. Avg around -100db
Wifi Always scanning: off
Play Store version: 4.4.22
Play services version: 4.0.34
Google Now: On
Bluetooth: Off
NFC: On
Location Settings (these are the key):
Location: On
Mode: Battery Saving
Google Location Reporting: Off
Location History: Off
Battery drain overnight: 0.7% per hour. About 6% total drain over 9 hoursNotice that I started this at 99% battery instead of 100% because I think 100 to 99 takes forever to drop. It's almost like when your car's fuel gauge reads higher than Full. So I started at 99%.
This is definite progress, I really think we need get more folks involved in doing this test for confirmation.
OP: can't thank you enough for getting this started!
EDIT: all of my syncs were on: 3 Gmail accounts, Exchange Email, weather, some widgets, google voice etc.
I still only lost 6% battery during 8 hours and 20 mins but did get about an extra 6-7 minutes combined awake time due to NlpWakelock and NlpCollectorWakeLock.
So my awake time was higher but overall battery drain didn't really change overnight. I'm sure the drain results would be drastically different if I was moving around but this was during sleep at night.
Tomorrow I'm going to try and repeat this test with WakeLockTerminator turned on and filtering all nlp wakelocks.
So, this is what I was talkimg about that I have problems with foursquare and nlpwakecollector. Did anyone have this piece of crap ??
If I'm switching off location, I will not have sense weather also.
It's something related with foursquare but I don't know what.
If I'm switching off location, I will not have sense weather also.
It's something related with foursquare but I don't know what.
Recently Foursquare launched a new feature that check your location even if the app is closed to send notifications with tips and recommendations. You can turn it off somewhere in settings.
I bought my SGS4 recently and I have problems with Nlpwakelock and Play services from the begging.
I already tried changing stock Touchwiz roms (Android 4.3) and now I'm on stock android 4.4 rooted. I already tried: turning off location reporting, location history, Android Device Manager, Google Now, disabling and reinstalling Maps. I deleted Play Store services (in Titanum backup, not disabled but deleted) and downloaded them again. I tried to delete my Google account and reinstall all Google Apps. The only way to stop those wakelocks for me is to disable Network Location, but I rely on this and don't want to lose it. Any help? It's really frustrating. Could it be a hardware issue? Or third party app?
I bought my SGS4 recently and I have problems with Nlpwakelock and Play services from the begging.
I already tried changing stock Touchwiz roms (Android 4.3) and now I'm on stock android 4.4 rooted. I already tried: turning off location reporting, location history, Android Device Manager, Google Now, disabling and reinstalling Maps. I deleted Play Store services (in Titanum backup, not disabled but deleted) and downloaded them again. I tried to delete my Google account and reinstall all Google Apps. The only way to stop those wakelocks for me is to disable Network Location, but I rely on this and don't want to lose it. Any help? It's really frustrating. Could it be a hardware issue? Or third party app?
4.4.1 resolved the issue for me. I got location sharing on and battery time is fantastic
Excuse my ignorance... but where/how do you turn this off?
When you go into Google now click the 3 dot menu on the traffic update. Just click no when it asks you if you want to keep track of your commute. Same for weather.
Sent from my Nexus 5 using Tapatalk
Is anyone still having issues with Google services being a large hit to battery due to the nlp wakelocks.
Sent from my Nexus 5 using Tapatalk
Sent from my Nexus 5 using Tapatalk
MyTmobile has ALWAYS been a Battery hog ever since the Cupcake/Donut days. Usually it has to do with the Battery Saver (ironically). Turn Battery Saver off and the usage goes down conciderably.
I had a weird wakelock the other day, I've read its related with turning off location services entirely.
This was the result (please forgive the darkness of the images, I had Lux in night mode since it was late when I capped the images):
Also, I've noticed wifi being on drains a considerable amount of battery. At 100%, I left my phone unplugged at 1 am and fell asleep. I let the phone do its thing after a reboot, and I had a 9% drain in battery over the course of about 6 hours while I was asleep. Which seems pretty high to me.
This was the result (please forgive the darkness of the images, I had Lux in night mode since it was late when I capped the images):
Also, I've noticed wifi being on drains a considerable amount of battery. At 100%, I left my phone unplugged at 1 am and fell asleep. I let the phone do its thing after a reboot, and I had a 9% drain in battery over the course of about 6 hours while I was asleep. Which seems pretty high to me.
I had that entriesRefresh wakelock on my Nexus 7. I found that as soon as I disabled Location Reporting it would get that wakelock, and as soon as I enabled location reporting it would go away.
Well, as you can see I lost a considerable amount of battery while the wakelock was active. Something like 63% over the course of 4-5 hours.
I guess I'll keep location reporting on to not have that happen again.
I also took the tips of removing the traffic and weather updates from Google Now, and hoping that'll help a bit.
I guess I'll keep location reporting on to not have that happen again.
I also took the tips of removing the traffic and weather updates from Google Now, and hoping that'll help a bit.
Hi
The battery drain caused by these wake-ups and wake-locks are all to do with Google Location services. Specifically when Wi-Fi location services are enabled, in Kit-Kat terms this is High Accuracy and (ironically) Battery Saving modes. GPS is considered a high battery user, but it may not be the worse offender.
When we agree to use Googles Wi-Fi database we agree to send data to Google. This enables the following back ground tasks:
1) Building and updating Googles Wi-Fi database when High Accuracy is selected. Background services will wake the phone, look for Wi-Fi access points nearby, then fire up the GPS to get a precise location, and send that data back to Google, Google uses this to identify Wi-Fi access points and their locations to continually update it's database. They don't drive around in cars any more to collect this data. I'm not sure anyone knows the schedule for this, and it seems sometimes this happens a lot, other times this activity dies away. Perhaps the more we use the Wi-Fi database lookup for locations, the more Google will use our phone later for keeping that database up to date. No such thing as a free lunch.
2) Google doesn't just collect data as to where we are, but it also collects data about how we get to where we are. Some of us will have seen cards in Google Now telling us how much we cycled, ran or walked. In order to work this out, our phones must wake regularly (every n seconds) to do a location lookup to work out the distance we travelled and so the speed we are travelling at. From our location and average speed Google decides if we are walking, jogging, or in a car or train. No doubt there is some attempt at backing off these wake-ups to save battery power, for example if the phone hasn't moved in several hours it will sample less often. Note it doesn't seem to matter if you consume this data, e.g. someone doesn't use Google Now, Google are still gathering and recording this data for their marketing purposes and data mining.
3) Traffic. When Google works out we are travelling by road Google will ramp up sampling rates. Google will gather location data from us, again whether we use that data ourselves or not, to work out congestion and hold-ups on the road and then offer those using Google navigate new routes to avoid problems and hold ups. All of us with an Android device are GPS trackers for Google traffic services.
It has not always been like this, it is only recently Google has ramped up the collection of location data. Google suggest their location framework will use on average no more than 1% of battery power an hour, over 24 hours that is almost a quarter, it adds up. If reception is not good then the constant chatter of data back to Google services could see the phone using a lot more.
The problem with all 3 above is the usage isn't always predictable. So messing around with a few settings might see an improvement for a while, but generally these wake-locks just come back.
The only way to stop these wake-locks is to turn off location services, either completely or just use GPS mode.
This is why using GPS only can now save battery. Modern GPS chips use less power and lock-on quicker, often working in some buildings as well, and avoids having Google use our phones as location trackers.
Regards
Phil
The battery drain caused by these wake-ups and wake-locks are all to do with Google Location services. Specifically when Wi-Fi location services are enabled, in Kit-Kat terms this is High Accuracy and (ironically) Battery Saving modes. GPS is considered a high battery user, but it may not be the worse offender.
When we agree to use Googles Wi-Fi database we agree to send data to Google. This enables the following back ground tasks:
1) Building and updating Googles Wi-Fi database when High Accuracy is selected. Background services will wake the phone, look for Wi-Fi access points nearby, then fire up the GPS to get a precise location, and send that data back to Google, Google uses this to identify Wi-Fi access points and their locations to continually update it's database. They don't drive around in cars any more to collect this data. I'm not sure anyone knows the schedule for this, and it seems sometimes this happens a lot, other times this activity dies away. Perhaps the more we use the Wi-Fi database lookup for locations, the more Google will use our phone later for keeping that database up to date. No such thing as a free lunch.
2) Google doesn't just collect data as to where we are, but it also collects data about how we get to where we are. Some of us will have seen cards in Google Now telling us how much we cycled, ran or walked. In order to work this out, our phones must wake regularly (every n seconds) to do a location lookup to work out the distance we travelled and so the speed we are travelling at. From our location and average speed Google decides if we are walking, jogging, or in a car or train. No doubt there is some attempt at backing off these wake-ups to save battery power, for example if the phone hasn't moved in several hours it will sample less often. Note it doesn't seem to matter if you consume this data, e.g. someone doesn't use Google Now, Google are still gathering and recording this data for their marketing purposes and data mining.
3) Traffic. When Google works out we are travelling by road Google will ramp up sampling rates. Google will gather location data from us, again whether we use that data ourselves or not, to work out congestion and hold-ups on the road and then offer those using Google navigate new routes to avoid problems and hold ups. All of us with an Android device are GPS trackers for Google traffic services.
It has not always been like this, it is only recently Google has ramped up the collection of location data. Google suggest their location framework will use on average no more than 1% of battery power an hour, over 24 hours that is almost a quarter, it adds up. If reception is not good then the constant chatter of data back to Google services could see the phone using a lot more.
The problem with all 3 above is the usage isn't always predictable. So messing around with a few settings might see an improvement for a while, but generally these wake-locks just come back.
The only way to stop these wake-locks is to turn off location services, either completely or just use GPS mode.
This is why using GPS only can now save battery. Modern GPS chips use less power and lock-on quicker, often working in some buildings as well, and avoids having Google use our phones as location trackers.
Regards
Phil
Last edited:
I tried uninstalling Google play services with tibackup as someone suggested, and I accidentally got the play store the first time. I restored the play store from backup, but now it FC's whenever I launch it. I've wiped data on it, wiped and restored play services, but nothing works. I've got xposed installed and had xprivacy, but temporarily disabled it.
Anyone gotten outta this before?
Sent from my Nexus 5 using xda app-developers app
Anyone gotten outta this before?
Sent from my Nexus 5 using xda app-developers app
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone