• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

Possible NlpCollectorWakelock/NlpWakelock fix

Search This thread

burningembers

Senior Member
Sep 11, 2010
418
195
Since day 1, despite factory resets and freezing bloat, my LG G2 has experienced some *insane* wakelocks around NlpCollectorWakelock and NlpWakeLock. We're talking about 2 hours every 10 hours or so of uptime, basically destroying my battery life.

Now, the simple fix for this is to turn off Wifi/Mobile Network Location, voila, phone deep sleeps, life is good. Except this doesn't fly for me, because I still want to use Google Now, and I can use it just fine on my S4 without this insanity.

To get a little better insight, metric-wise, I pulled Velvet.apk from /system/app and self-installed Google Search straight from the market (essentially Google Now) so that I could keep tabs on it in Greenify.

Turns out Google Search was running as much as 200 times per hour and causing wake-up ~5-10 times per hour. I could practically refresh and just watch the count go up and up.

So on a whim, being rooted and a little bit of a risk-taker, I used Titanium Backup and uninstalled Google Play Services. Null. Gone. Kaput.

Then when I launched Google Now again, it requested I nab Google Play Services from the market. So I did. I installed, rebooted.

To my surprise, in the last five hours since doing that, Google Search has run 12 times, and woken up 12 times. Better Battery Stats is reporting NlpCollectorWakeLock at 2 minutes and 8 seconds for ~5 hours uptime, and NlpWakeLock at 2 minutes and 43 seconds.

Anyone else want to take the dive with me and see if this gives them as significant of a before/after as it did for me? My phone is deep sleeping like a champ now and I really hope this keeps up.

tl;dr: Uninstall Google Play Services from /system/app using Titanium Backup, launch Maps or Google Now and then re-install Google Play Services from the market. Reboot. See if location service related wakelocks drop significantly. Rejoice if they do. Lament further if they don't.
 

lastdeadmouse

Senior Member
Well, I removed Google play services and installed via market this morning. I'm still seeing a ****load of NLP wakelocks, but on the att version I haven't figured out how to completely remove search. Could that be the issue?

Sent from my LG-D800 using Tapatalk 4
 

burningembers

Senior Member
Sep 11, 2010
418
195
Well, I removed Google play services and installed via market this morning. I'm still seeing a ****load of NLP wakelocks, but on the att version I haven't figured out how to completely remove search. Could that be the issue?

Sent from my LG-D800 using Tapatalk 4

Oops, I guess I forgot to mention that I also removed Velvet.apk from /system/app (LG's pre-installed Google Search), and reinstalled that from the market as well. Not sure if that is related.

I, too, have the AT&T version. I will run some more tests today. But so far today with 1 hour screen-on, I have an up time of a little north of 2 hours, with an estimated 60 hours remaining. Obviously that isn't realistic, but by this time before I would be seeing an estimated time of about 9 hours remaining and be sub-90% battery life.
 

lastdeadmouse

Senior Member
Oops, I guess I forgot to mention that I also removed Velvet.apk from /system/app (LG's pre-installed Google Search), and reinstalled that from the market as well. Not sure if that is related.

I, too, have the AT&T version. I will run some more tests today. But so far today with 1 hour screen-on, I have an up time of a little north of 2 hours, with an estimated 60 hours remaining. Obviously that isn't realistic, but by this time before I would be seeing an estimated time of about 9 hours remaining and be sub-90% battery life.

I have no velvet.apk in /system/app
I've been trying to get the market's search installed for the widget for days, lol.

Sent from my LG-D800 using Tapatalk 4
 

zxrax

Senior Member
Feb 22, 2011
115
9
(Northeast Georgia)
I don't have a velvet.apk either but I just did what you did aside from that. We'll see how things go.

Sent from my LG-D800 using xda app-developers app
 

burningembers

Senior Member
Sep 11, 2010
418
195
I have no velvet.apk in /system/app
I've been trying to get the market's search installed for the widget for days, lol.

Sent from my LG-D800 using Tapatalk 4

I don't have a velvet.apk either but I just did what you did aside from that. We'll see how things go.

Sent from my LG-D800 using xda app-developers app

Weird! I wonder why I have/had a Velvet.apk.

Anyway, since my initial post, I've continued monitoring. My runs/wakes are WAY down, trending to about 1-3 per hour, down from a crap ton. My overall wakelock time is roughly 20 seconds per hour, or roughly 8 minutes or so per day, way down from nearly 2 hours/day before. My battery life has gone way up, I'm super happy.
 

kjplaysguitar

Member
Oct 17, 2009
18
0
will not uninstall

Tried to do the same with the Verizon G2 and when trying to uninstall this i get a message from titanium back saying it will reboot twice for this to complete, but upon first reboot it boots in to team win recovery? how do i get this complete its process because Google services is always the highest on battery usage on my phone.
 

burningembers

Senior Member
Sep 11, 2010
418
195
Tried to do the same with the Verizon G2 and when trying to uninstall this i get a message from titanium back saying it will reboot twice for this to complete, but upon first reboot it boots in to team win recovery? how do i get this complete its process because Google services is always the highest on battery usage on my phone.

Huh, unfortunately I'm on the AT&T, so it is hard for me to comment.

When I did it via TB, it uninstalled in the same session, no reboot. No notification about rebooting twice.

Any other VZW users out there that can comment?
 

zxrax

Senior Member
Feb 22, 2011
115
9
(Northeast Georgia)
After an hour of idle time my time held awake by NLP wakelocks specifically is only three minutes, a far cry from the eight to ten I was seeing earlier. Will continue to monitor.

Sent from my LG-D800 using xda app-developers app
 

iowabowtech

Senior Member
May 31, 2010
385
59
Des Moines
I'm on vzw and didn't have a problem deleting Google Play Services. Wakelocks are way down for me too since using the Play Store version. Good find. I was noticing very high wakelock on this for the last several days.
 

zxrax

Senior Member
Feb 22, 2011
115
9
(Northeast Georgia)
OP, what are your settings on these three pages?

http://imgur.com/a/jc8lo

I'm still getting a ton of wakelocks. Not as much time spent held awake but nowhere near as low down as 1-3 wakes per hour . In 1h48m of non-screen time (out of the past 2h23m), I've got NLPCollectorWakelock waking my device 82 times for ~4 minutes of time held awake and NLPWakelock waking my device **284**(!!) times for 3 and a half minutes of time held awake...

EDIT: just uninstalled an app called "LGSearchProvider.apk" using Titanium Backup. Perhaps this is the same thing as the velvet.apk you were talking about earlier by a different name?
 
Last edited:

burningembers

Senior Member
Sep 11, 2010
418
195
I already uninstalled Google search via TB, should I still see this velvet.apk?

Sent from my LG-D800 using xda app-developers app

Nope, Velvet.apk was the /system/app's Google Search from factory.

OP, what are your settings on these three pages?

http://imgur.com/a/jc8lo

I'm still getting a ton of wakelocks. Not as much time spent held awake but nowhere near as low down as 1-3 wakes per hour . In 1h48m of non-screen time (out of the past 2h23m), I've got NLPCollectorWakelock waking my device 82 times for ~4 minutes of time held awake and NLPWakelock waking my device **284**(!!) times for 3 and a half minutes of time held awake...

EDIT: just uninstalled an app called "LGSearchProvider.apk" using Titanium Backup. Perhaps this is the same thing as the velvet.apk you were talking about earlier by a different name?

My settings match yours except I have Remote Wipe ability turned off, I still have my phone reporting a location to ADB, though.

Since my last post, I've seen a huge uptick in Google Search runs in Greenify (about 100 in an hour). However, only 5 wakes, and only 26 seconds of wakelock in that same hour. Will report more later.
 

akong702

Senior Member
Jul 14, 2010
145
7
Las Vegas
I uninstalled the search, and Google play services, restarted, reinstalled, and restarted again. So far this is what I have is it normal?

Sent from my LG-D801 using xda app-developers app
 

Attachments

  • uploadfromtaptalk1379965226376.jpg
    uploadfromtaptalk1379965226376.jpg
    141.5 KB · Views: 2,627

burningembers

Senior Member
Sep 11, 2010
418
195
I uninstalled the search, and Google play services, restarted, reinstalled, and restarted again. So far this is what I have is it normal?

Sent from my LG-D801 using xda app-developers app

I'm not sure there. It looks like you just have some initial Audio wakelocks from maybe a music player or your start-up noise.

You should check Android System or Google Services for things related to NlpCollectorWakelock or NlpWakelock.

---

Updates on my own report. For some reason Google Keep has shot to the top trending at 4 minutes/hour of wakelock time. I have no idea why, I'm not actively using it, or its widget. I'm greenifying it now to get rid of the noise.
 

zxrax

Senior Member
Feb 22, 2011
115
9
(Northeast Georgia)
Well, in 1h50m of uptime (30m screentime), according to GSam, NlpCollectorWakelock has kept my phone awake for ~6m. It's the only thing under Google Services that's kept my phone awake longer than 30 seconds. Nlpwakelock is virtually nonexistent, 9.8s of awake time.

edit: when i click 'manage' on GSam on the "Google Services" that's causing wakelocks it takes me to Google Bookmark Sync in particular. Coincidence? I froze bookmark sync since it's something I don't use anyways, we'll see what happens...I don't see how it could possibly be the culprit but you never know.
 
Last edited:

burningembers

Senior Member
Sep 11, 2010
418
195
Well, in 1h50m of uptime (30m screentime), according to GSam, NlpCollectorWakelock has kept my phone awake for ~6m. It's the only thing under Google Services that's kept my phone awake longer than 30 seconds. Nlpwakelock is virtually nonexistent, 9.8s of awake time.

edit: when i click 'manage' on GSam on the "Google Services" that's causing wakelocks it takes me to Google Bookmark Sync in particular. Coincidence? I froze bookmark sync since it's something I don't use anyways, we'll see what happens...I don't see how it could possibly be the culprit but you never know.

Interesting. I hadn't gone that deep via GSam, I may do it now though just to see. Good call.

edit: Mine just takes me to Google Services, sad panda.
 
Last edited:

thanasisc4

Senior Member
Feb 19, 2011
191
40
I have the T-Mobile variant and wanted to confirm that OP's instructions fix the issue. My device started out with great battery life and one day suddenly took a dive thanks to this issue.

I used TiBu to uninstall Google play services and Google search (which turned out to be velvet.apk) and reinstalled both via play store.

Screen went back to bring number 1 battery drainer for me whereas before Google pay services was in the lead by a wide margin.

Thanks OP.

Sent from my LG-D801 using xda app-developers app
 

Top Liked Posts

  • There are no posts matching your filters.
  • 23
    Since day 1, despite factory resets and freezing bloat, my LG G2 has experienced some *insane* wakelocks around NlpCollectorWakelock and NlpWakeLock. We're talking about 2 hours every 10 hours or so of uptime, basically destroying my battery life.

    Now, the simple fix for this is to turn off Wifi/Mobile Network Location, voila, phone deep sleeps, life is good. Except this doesn't fly for me, because I still want to use Google Now, and I can use it just fine on my S4 without this insanity.

    To get a little better insight, metric-wise, I pulled Velvet.apk from /system/app and self-installed Google Search straight from the market (essentially Google Now) so that I could keep tabs on it in Greenify.

    Turns out Google Search was running as much as 200 times per hour and causing wake-up ~5-10 times per hour. I could practically refresh and just watch the count go up and up.

    So on a whim, being rooted and a little bit of a risk-taker, I used Titanium Backup and uninstalled Google Play Services. Null. Gone. Kaput.

    Then when I launched Google Now again, it requested I nab Google Play Services from the market. So I did. I installed, rebooted.

    To my surprise, in the last five hours since doing that, Google Search has run 12 times, and woken up 12 times. Better Battery Stats is reporting NlpCollectorWakeLock at 2 minutes and 8 seconds for ~5 hours uptime, and NlpWakeLock at 2 minutes and 43 seconds.

    Anyone else want to take the dive with me and see if this gives them as significant of a before/after as it did for me? My phone is deep sleeping like a champ now and I really hope this keeps up.

    tl;dr: Uninstall Google Play Services from /system/app using Titanium Backup, launch Maps or Google Now and then re-install Google Play Services from the market. Reboot. See if location service related wakelocks drop significantly. Rejoice if they do. Lament further if they don't.
    3
    If you have a Nexus 5/ are on KitKat...

    DON'T DELETE GOOGLE SERVICES IF YOU ARE ON A NEXUS 5 OR KITKAT 4.4
    IF YOU DELETE GOOGLE SERVICES YOU'LL HAVE TO RE INSTALL THE ROM

    If you delete Google services, you cant reinstall it from the play store because the store stops working. Even if it was working, The play store doesn't show GSF for kitkat devices since its already baked into KitKat.

    luckily i had a backup of my system partition from before i flashed a kernel,
    otherwise i would have had to reflash the ROM.
    2
    The recent update to play services drastically improves wakelock battery drain. I leave reporting ect on now.