I want to share this for anyone who cares. I've done a few things which have given me Google Now back (I love having the suggested web articles to read which is why I even care in the first place) and I don't seem to get drain from it. Keep in mind this probably nukes search location abilities but not anything else that uses location. And it may still work, I however don't use Now for weather and daily commutes so they aren't a factor for me. Feedback welcomed as those might still work as well...
I went full retard on Search/Now by taking these steps (i have no idea what helped and what isn't needed so debug if you want, or just do everything)
Made Search a system App
Disabling 3 (Google Play Services) services in system tuner (ReportingAndroidService, LocationReportingService, ReportingSyncService)
https://dl.dropboxusercontent.com/u/38436349/2014-05-30 13.53.41.png
Setting the alarm multiplier x100 for search in the xposed module "per app hacking"
https://dl.dropboxusercontent.com/u/38436349/2014-05-30 13.57.07.png
I revoked wakelock permissions in App ops x
https://dl.dropboxusercontent.com/u/38436349/2014-05-31 14.01.05.png
And I also cut the wakeup path velvet.location.LocationReceiver via greenify but then un-greenified search. Don't know if this has any effect but it's something I did.
Final thoughts:
Overnight I had around 1% battery drain per hour with Gmail syncing every 2 hours so it's what I would expect
I had a lot of the NlpCollectorWakeLocks but no associated drain from them. There was something like 7 minutes worth and if they were true wakelocks, along with the other ones listed (some tasker, some gmail, some wifi), there would've been more than 1% per hour drain. I think they are just done when the phone is awake from something else (ie: a gmail sync) and recorded by BBS as wakes but they actually aren't waking the phone. Maybe an app issue with BBS.
I went full retard on Search/Now by taking these steps (i have no idea what helped and what isn't needed so debug if you want, or just do everything)
Made Search a system App
Disabling 3 (Google Play Services) services in system tuner (ReportingAndroidService, LocationReportingService, ReportingSyncService)
https://dl.dropboxusercontent.com/u/38436349/2014-05-30 13.53.41.png
Setting the alarm multiplier x100 for search in the xposed module "per app hacking"
https://dl.dropboxusercontent.com/u/38436349/2014-05-30 13.57.07.png
I revoked wakelock permissions in App ops x
https://dl.dropboxusercontent.com/u/38436349/2014-05-31 14.01.05.png
And I also cut the wakeup path velvet.location.LocationReceiver via greenify but then un-greenified search. Don't know if this has any effect but it's something I did.
Final thoughts:
Overnight I had around 1% battery drain per hour with Gmail syncing every 2 hours so it's what I would expect
I had a lot of the NlpCollectorWakeLocks but no associated drain from them. There was something like 7 minutes worth and if they were true wakelocks, along with the other ones listed (some tasker, some gmail, some wifi), there would've been more than 1% per hour drain. I think they are just done when the phone is awake from something else (ie: a gmail sync) and recorded by BBS as wakes but they actually aren't waking the phone. Maybe an app issue with BBS.
Last edited:



