yashsingh1/xdaforums huggingface dataset:
[Xposed Framework Modules] Javi22:
This thing about Google Play Services it's really a big headache

I also suddenly noticed huge wakelocks from gps, here's what I do and is working so far:

Go to my android tools, services, Google Play Services. This service

SystemUpdateService

Appeared disabled. I just enabled it again, wait two seconds, and disabled it again... Wakelock gone until next reboot... Then repeat the process

Long time ago I installed my android tools and disabled some services and receivers (I think the ones with checkin, update.systemupdate and some else..), so maybe I disabled SystemUpdateService too, don't remember, so maybe you find it enabled, or maybe not. Anyway try doing this. Works for me

Tomorrow I'll try re enabling the receivers that [MENTION=1592495]Cyclu[/MENTION] has posted here, just for testing, maybe battery improves.. Hahah

Well I hope this works for you in case other workaround didn't
[Xposed Framework Modules] Sportfreunde:
Anyone know what this is? It's one of my highest alarms at 423 within a day or two:

Com.android.server.WiFi manager.Action.start-scan

This is another weird alarm at 100:

Com.android.server.WiFi manager.Action.start-scan
[Xposed Framework Modules] Pkt_Lnt:
How much time? I don't worry about something that throws 500 alarms in 24 hours with two minutes use.
[Xposed Framework Modules] s2d4:
If I didn't want it to run, I would.

It's WiFi scanning nearby networks, gets worse with location services for google now.
[Xposed Framework Modules] Cyclu:
Yes exactly how it works I had since several times that setup with the services and the receivers disabled except since latest Play Service update everything has changed I don't understand what is the problem because even when the receivers and the services are disabled there are still the wakelocks as if we have disabled the service without disabling the receiver and like I said I had to enable the services to stop the wakelocks that is very strange.

Thank you I will try it.

Thanks I will try also your solution I hope it will work.
[Xposed Framework Modules] beeshyams:
Hi Ryan

Thanks for a great tool .Have been able to come close to the target and get darn good battery life. 8+ hours SOT with 36 hours of usage

[ROM DISCONTINUED] >> DEEP IMPACT ROM … - Pg. 38 | Samsung Galaxy Note II GT-N7100, N7105 | XDA Forums http://xdaforums.com/show...733262&page=38

a couple of questions

1. How can I take a back up of settings applied , to study at a later point of time in case I went too aggressive

2. Am using pro version bought before becoming xda member ( don't regret that one bit ) but if I download the latest apk from here, A) will my settings remain b) can I roll back to earlier version

Sorry for asking questions that may have been answered already. Kindly point me right way
[Xposed Framework Modules] s2d4:
A possible explanation is that it tries to run and not through receivers (basically looking for state changes/events) on boot up even before BOOT_COMPLETED, then it just locks up because it is disabled.

This appears to explain why the tasker option works in essence.

You may find this to be the case just looking at the logcat whilst booting up.
[Xposed Framework Modules] doubleho:
I fixed the wakelock on my n5 and n6 using the tasker fix, applied the same fix on n9 and it didn't work, weird
[Xposed Framework Modules] Cyclu:
Since I had to reenable also EventLogService and CheckingService in addition to SystemUpdateService the wakelocks are disappeared but now I have constantly this alarms EventLogService$Receiver (see the screenshot) which has exactly the same name as the receiver which is disabled (second screenshot) weird no?

Maybe you explanation is accurate but anyway this Play Service update broke all things I will try amplify this alarms as now it appears in Amplify.

Thanks for the tip about logcat I forgot that I will try it to see what exactly happens.

[MENTION=526666]cryptyk[/MENTION] Nevermind I have found these wakelocks and alarms.
[Xposed Framework Modules] blumenkasten:
I started the activity and service manually. The result was the services were disabled again after running. So it's clear: they run once and disable themselves.
[Xposed Framework Modules] hooliganx:
guys... question ?

I made some modifications in Android Tools and Amplify.. and... if I only uninstall app and reboot (wipe caches) all settings turn back normal?

or I have to re-enable all things I disabled?

n5optislim.aow1980-15.03.14layeredgapps.15.03.13elementalx.2.10rd2.25v4a.2.3.4twrp2.8.3.0

-----------------------------------------------------------
[Xposed Framework Modules] albert107:
Hi, how much $ is the Pro version of Aplify? I couldn't find any info about it and I don't want to intsall Xpossed to check before I know how much is it.
[Xposed Framework Modules] ctzulu:
could anyone get it working on crdroid´s rom ?
[Xposed Framework Modules] -m3tac0rt3x-:
Minimum Donation is 2$. You also have the option for 5$ or 10$. Every option for donation are within the App. ;)
[Xposed Framework Modules] beautifulsun:
I have two very bad battery hogs that runs over 90% of the time.

"PowerManagerService.WakeLocks" (Kernel) and SystemUpdateService (Partial).

Any help?
[Xposed Framework Modules] Cyclu:
You can't do much directly for this kernel wakelock because it is the sum of all the partial wakelocks except trying decrease the partial wakelocks as explained in BetterBatteryStats wiki.

Rationale:*This kernel wakelock is a placeholder for all partial wakelocks being held in userland.

Know actions:*Use "Partial Wakelocks" to drill down the applications / services causing wakelocks.

Known conditions of occurence:

Some devices show userland wakelocks as a total named PowerManagerService

https://github.com/asksven/BetterBatteryStats-Knowledge-Base/wiki/PowerManagerService

For the second wakelock probably you have updated Play Service to version 7.0.... which has screwed up the things read two page back we talked about it.
[Xposed Framework Modules] mattia.b89:
not luck.

the only solution was uninstalling it
[Xposed Framework Modules] s2d4:
Your second one is the main cause for your first one.

Feel free the read through the last couple days of post in this thread where we've just gone through that wake lock and how some of us has eliminated it.
[Xposed Framework Modules] beautifulsun:
I suspected that was something linked to GPS usage of Service Framework so I switched off location profiles in Tasker and limited some wakelock via Amplify, but not so much has changed.
[Xposed Framework Modules] Adywizard:
If you're on cm 12, go into the settings -> privacy -> privacy guard -> advanced -> play services and disable keep awake
[Xposed Framework Modules] beautifulsun:
I will try asap, there are no malus in deactivating the process?
[Xposed Framework Modules] patstar5:
I have rilj wakelock that is taking up alot of time (4:16), can I limit this?
[Xposed Framework Modules] Adywizard:
I didn't notice any issue so far. I've disabled four days ago that service.
[Xposed Framework Modules] Sportfreunde:
Anyone know how Viber can be de-bloated if possible without losing message send/receive functionality? I mean reducing the amount of alarms/wakelocks and even disabling some of its services.
[Xposed Framework Modules] s2d4:
No it is not. OTA has to do with it, not sure what else.

Again, feel free to go through the last couple of days of posts in this thread. We went through how to do it already, please do not ignore this for the 2nd time. Privacy setting on CM12 may help as others have suggested but if the receivers are attempting to activate the service, you may have other wakelocks.
[Xposed Framework Modules] picklu:
I was facing the awake situation after this play services update v 7. I roll back in the previous version 6. Then there is no wakelock.
[Xposed Framework Modules] Cyclu:
No need to reenable all things.

Make sure to force close apps and wipe their cache and data before uninstall to not having the kernel wakelock deleted_wake_locks a reboot should eliminate the wakelock entirely if it's still showing up wipe Cache and Dalvik in the recovery.

Also the Wifi driver is one known source for this kernel wakelocks that are destroyed whenever the driver is unloaded (when Wifi is disabled manually or as part of the turn-off policy). Wakelocks such as wlan_rx_wake and wlan_wake, when the driver is unloaded, will no longer show up in the list and their stats be added to the deleted_wake_locks previous values.
[Xposed Framework Modules] stunner2002:
Installed Amplify to take control over NlpWakelockCollector. Installed it via Xposed and now my phone wont go into deep sleep. 100% time awake.

Didn't change anything else on my phone. Anybody else experiencing this issue?
[Xposed Framework Modules] picklu:
Its because of play services update v 7. This latest update has ruin that!!! Same thing happened to me. I roll back in the previous version of google play services v6 and not facing this wakelock!
[Xposed Framework Modules] Javi22:
How did you downgraded to v6 and kept there? For me it didn't ask to update, didn't even notice it

I post my workaround a few pages before, it works for me but is annoying because I have to make it at every reboot..
[Xposed Framework Modules] picklu:
Same here, I didn't ask me to update! I also didn't even notice that! My Titanium Backup Pro is scheduled to take backup (default backup) twice in a week and I got the previous version from there and restored that version and its working nice upto now! :)
[Xposed Framework Modules] Pkt_Lnt:
www.apkmirror.com

Turn off auto updates in Play Store.
[Xposed Framework Modules] dimm0k:
[MENTION=526666]cryptyk[/MENTION] not sure what's changed exactly between version 3.0.1 and 3.0.5, but I'm facing a serious bug. Unfortunately I didn't notice this sooner and it forced me to wipe my device and reload everything before realizing Amplify was the culprit. With 3.0.5 my phone does not receive any phone calls! I've tried it with wi-fi calling and regular, no calls come in. I've wiped the data from Amplify and even with the defaults the phone does not wake up or ring. If I disable Amplify then calls come in no problem. I've reverted to version 3.0.1 and it works perfectly again. Xposed logs are error free in both instances.

nevermind... for some reason I thought it was Amplify's fault, but it just so happened I rebooted after each time and reboot actually lets one call come in. after that, no calls can be received until I restart again.
[Xposed Framework Modules] Osama Zabin:
Clearing cache/data for the apk you used to modify services/receivers will not revert back your changes for Google Play Services or Google Services Framework...

You have to manually enable them one by one.

---------- Post added at 08:35 AM ---------- Previous post was at 08:34 AM ----------
[Xposed Framework Modules] Cyclu:
I understood the question of [MENTION=992878]hooliganx[/MENTION] differently. ;)

Yes you are right if we uninstall My Android Tools or similar apps itself we have to revert all changes that we have made.
[Xposed Framework Modules] cryptyk:
They shouldn't. Did they go up in the absolute sense? Or just relative to other things?

The reason I ask is because there have been a few people who have said other wakelocks are now at the top of the list. It's not super obvious that this is because Nlp*WakeLock has dropped out of the first position, so now the others are a larger percentage of the wake time.

Thanks,

Ryan
[Xposed Framework Modules] pippideniro:
gonna give a try :good:
[Xposed Framework Modules] shawn0223:
Hey Ryan,

I tried pulling the adb log for you but when i put in that command i got this error.

C:\sdk\platform-tools>adb

logcat -v time | grep "NlpUnbounce\|Xposed"

'grep' is not recognized as an internal or external command,

operable program or batch file.

i tried again without the space between grep and "NlpUnbounce" and got the error below. i even copy pasted the command but its still not working.

C:\sdk\platform-tools>adb

logcat -v time | grep"NlpUnbounce\|Xposed"

The system cannot find the path specified.
[Xposed Framework Modules] briatide:
grep is a command, you can install this for windows http://gnuwin32.sourceforge.net/packages/grep.htm

you could also use cygwin or a linux shell.

offtopic: enforcing a five minute waiting period "between posts" on an edit is really ridiculous
[Xposed Framework Modules] shawn0223:
I installed that package and tried running the command again and its still saying its not a recognized command
[Xposed Framework Modules] briatide:
in that case you will need to specify the path that you installed to. so for instance say you installed to c:\grep\grep.exe

logcat -v time | c:\grep\grep.exe "NlpUnbounce\|Xposed"
[Xposed Framework Modules] shawn0223:
I'm on Windows and a buddy just told me that's a Linux command so it might not work. I'll try the command u posted real quick
[Xposed Framework Modules] Pkt_Lnt:
I would stop listening to that buddy, he is sadly misinformed. Check this post.

http://xdaforums.com/showpost.php?p=55128401&postcount=329
[Xposed Framework Modules] rsngfrce:
According to BetterBatteryStats, the msm_hsic_host kernel wakelock is currently 8h 39m out of 1d 6h 30m since boot, so my kernel wakelock is now huge in the absolute sense. BUT... I stress that I cannot say positively this was caused by installing NlpUnbounce... both just happened recently, but could be unrelated. ACTUALLY... lets not ME be stupid... I will disable NlpUnbounce and report if this changes...

(UPDATE): It is looking now like this was an anomaly, but I'll report the results in a new post once I give it a little more time...
[Xposed Framework Modules] tmr250z:
[MENTION=526666]cryptyk[/MENTION] I enabled Debug Logging and got these errors in the log after I rebooted:

NlpUnbounce: Attempting 19to20 AlarmHook
NlpUnbounce: Failed 19to20 AlarmHook: com.android.server.AlarmManagerService#triggerAlarmsLocked(java.util.ArrayList,long,long)#exact
NlpUnbounce: Attempting 15to18 AlarmHook
NlpUnbounce: Successful 15to18 AlarmHook
NlpUnbounce: Attempting 19to20 WakeLockHook
NlpUnbounce: Failed 19to20 WakeLockHook: com.android.server.power.PowerManagerService#acquireWakeLockInternal(android.os.IBinder,int,java.lang.String,java.lang.String,android.os.WorkSource,int,int)#exact
NlpUnbounce: Attempting 17to18 WakeLockHook
NlpUnbounce: Successful 17to18 WakeLockHook
NlpUnbounce: Attempting 15to16 WakeLockHook
NlpUnbounce: Failed 15to16 WakeLockHook: java.lang.ClassNotFoundException: com.android.server.PowerManagerService

I have a Samsung Galaxy S4, stock Touchwiz rom, Jellybean 4.3, Xposed 2.6.1, NlpUnbounce 1.1.2 default settings
[Xposed Framework Modules] JoeFCaputo113:
Thanks for this amazing module. What would be the effects of having all 4 (LOCATOR, DETECTION, NlpWakeLock & NlpCollectorWakeLock) set to 3600 (once per hour)?
[Xposed Framework Modules] passlogin:
Dear Op, If you recommending 240,240,0,0, why dont you set it as default values?
[Xposed Framework Modules] GermainZ:
Unless I'm missing something, you're not using any of the methods added in the newer API (yet), so it should be enough to change this in the manifest:

<meta-data
android:name="xposedminversion"
android:value="54" />

I'm not sure what's the corresponding value for 2.4.1, though.
[Xposed Framework Modules] metalboy94:
First time it's been so bad on Android System. I was thinking of removing its Location permission. Would this module help any better?
[Xposed Framework Modules] RobLudo:
That's why this module exists. To reduce frequency of nlp wakelocks
[Xposed Framework Modules] metalboy94:
However the description states it removes nlpWakelocks in Google Play Services. Which it does, I do have the mod installed. I was wondering if it can do something about the wakelocks in Android System.
[Xposed Framework Modules] xdagee:
This is interesting; already I have made some manual tweaks by dening play services processes from waking and staying awake.

But since this is an xposed module and its modifications might be easier to implement than the manual tweaks, I will have a look at it and provide feedback after some hours.
[Xposed Framework Modules] Pkt_Lnt:
No one has reported that. Try it and see what your phone does. As stated in the OP, run a baseline with BBS, then try defaults, then try your settings.

I tried as high as 900, 900, 300, 300 and saw no significant improvement over the defaults of 240 for all.
[Xposed Framework Modules] cryptyk:
Those are normal in debug logging mode.
[Xposed Framework Modules] cryptyk:
I recommend 240,240,0,0 as a starting point for people who want to tune their settings. I'm guessing that most people will end up around 240,240,240,240 after tuning, thus the defaults.
[Xposed Framework Modules] hooliganx:
[MENTION=1592495]Cyclu[/MENTION] [MENTION=3019138]Osama Zabin[/MENTION]

thanks guys!

I made a clean flash of a new Slim build by [MENTION=2095315]ezio84[/MENTION] and battery is so much better now.

Play Services don't show up in BBS now.

[emoji6]

n5slim.ezio84-15.03.21layeredgapps.15.03.17

code.blue.r884rd.1.16v4a.2.3.4twrp2.8.3.0

-----------------------------------------------------------
[Xposed Framework Modules] rpr69:
Interesting. I did a dirty flash of the same ROM (been running his ROM for a few weeks) and I still had the wakelock, even with Amplify. I re-enabled the Tasker work around and that fixed it again. Must be the dirty flash somehow.
[Xposed Framework Modules] hooliganx:
perhaps.

I do clean flash when change ROM (when something new came in package [emoji6]).

n5slim.ezio84-15.03.21layeredgapps.15.03.17

code.blue.r884rd.1.16v4a.2.3.4twrp2.8.3.0

-----------------------------------------------------------
[Xposed Framework Modules] picklu:
[MENTION=4403217]Pkt_Lnt[/MENTION] / All: My auto update is turned off but today it automatically update to latest one, just noticed that! How to stop that automatic update! Or what is the workaround for this! Need long time solution.
[Xposed Framework Modules] picklu:
I use AutomateIt Pro, Shell plug-in is required, I did Tasker workaround and I think it's working!

ROOT is required!

1. Boot trigger

2. Action Composite Action:

Shell Command Action "pm enable com.google.android.gms/.update.SystemUpdateService" and tick the "Use Root" option

3. Add another shell command action "pm disable com.google.android.gms/.update.SystemUpdateService" and tick the "Use Root" option

Src: http://xdaforums.com/paranoid-andro...oogle-apps-t2943900/post59350828#post59350828
[Xposed Framework Modules] HsHTCsen:
Hi, does anyone know what this *alarm* wakelock is part of Android System please?
[Xposed Framework Modules] tangcla:
Does anyone have issues with the donation features not working? I noticed it today after I reset the app to defaults. Thought it might have been a system funny so I uninstalled and reinstalled from the Play Store..

It also won't let me donate again (app crashes).
[Xposed Framework Modules] NickosD:
I also have that issue.

Sent from my bacon!!!!!
[Xposed Framework Modules] doubleho:
don't touch it ,I limited it once and result in bootloop
[Xposed Framework Modules] Cyclu:
I have the same problem, Play Service is updated automatically also with auto update off, so downgrading Play Service is a only temporary solution.

I have searched yesterday a solution without success.

Really it should be good, if we can found a workaround.
[Xposed Framework Modules] picklu:
Last night I used tasker solution via my automateIt and it's working now with no wakelock and play services version is 7 updated one! Hope that is the solution up to now!
[Xposed Framework Modules] Ikkuh84:
Can you maybe share the link to that Tasker profile? :o
[Xposed Framework Modules] Cyclu:
Thanks, but I have found the solution for the massive wakelocks and I already amplified an alarm com.google.android.gms.checkin.EventLogService$Receiver which also appeared after the Play Service update, but I would prefer to downgrade the Play Service to version 6.7.76 because before with my setup, I only lost 0.2%-0.3%/h now is 0.7%-0.8% sometimes 1%/h

I know that result is not bad in itself but the draining increased to more than double.

If someone would have a solution it would be perfect.
[Xposed Framework Modules] RedTiger9:
Many good things :) I hope enjoy
[Xposed Framework Modules] Wh1t3Rose:
I''m pretty sure this is the same thing that's in the other thread (I created my own profile without looking at the other thread) and it works fine for me.

https://app.box.com/s/6sb48zj5v0n33kxc3rsw2yjes70nwq9x
[Xposed Framework Modules] picklu:
Please follow this steps! http://xdaforums.com/paranoid-andro...oogle-apps-t2943900/post59350828#post59350828 hope it will work! :)

---------- Post added at 09:56 PM ---------- Previous post was at 09:49 PM ----------

If we downgraded to 6.7.76 and it will automatically updated to the latest one! How you can stop that update!!! In my case my automatic update is off and even though it was updated to 7 :(
[Xposed Framework Modules] Cyclu:
Justly I can't, also I would like to know how stop that update, but I don't found the solution.:confused:
[Xposed Framework Modules] picklu:
same here! :( :confused:
[Xposed Framework Modules] HsHTCsen:
Hi, did u find a way to reduce the wakelocks safely on this *alarm* ?
[Xposed Framework Modules] str8str:
Can someone recommend a good setting for rilj wake lock?
[Xposed Framework Modules] Javi22:
The damn msc wakelock is driving me crazy :S any idea for this one? Maybe disabling something with disable services?

I get a lot of that wakelock, I've tried disabling some services and receivers with my android tools, but not improve
[Xposed Framework Modules] Cyclu:
Personally I never saw that wakelock can you please give us a little more information like BBS or Wakelock Detector screenshot.

I just got another Play Service update 7.0.99 we'll see what Mr. Google prepared for us this time.:rolleyes:
[Xposed Framework Modules] beautifulsun:
Play Service eternal wakelock solution. Worked for me.
[Xposed Framework Modules] Cyclu:
This solution (Disabling the Broadcast Receiver without enabling the below Service it's not always enough, because for those who have disabled this Service: "com.google.android.gms.update. SystemUpdateService" still the massive wakelocks like for me.

I have already given the solution see the posts #4558 #4560 please.
[Xposed Framework Modules] brolic925t:
What's the deal with the licensing? Are all the wakelocks still being limited if it says to donate again? I have to open and click donate to make it crash then send a report to make the donating stuff go away just to make sure its working
[Xposed Framework Modules] Javi22:
Yeah, I will post some ss, but now I'm still testing.. I am playing with my android tools, disabling/enabling services and receivers from Google play services.

Before 7x update, all was perfect, no big drain, I only had checkin and eventlog disabled, but now with 7x, has appeared a big drain

I've already read your advice (enabling services disabling receivers), but still being more drain than with 6x
[Xposed Framework Modules] cavalloz:
i made a donation with my phone, how can i unlock the pro version on my tablet too?

edit: pro features lost even on my phone..
[Xposed Framework Modules] -m3tac0rt3x-:
Have you got LuckyPatch installed? It was a no no for me even though I haven't used LuckyPatcher on any App since I got Lolipop... But because of restoring Titanium Backup it was reinstalled automatically.

Just the fact of it being installed was the cause of Amplify not receiving my donation...

As for the other device... I had to uninstall and reinstall for it to recognize the donation done with my main device!
[Xposed Framework Modules] cavalloz:
no I don't use luckypatcher, I think it is because i have 3 google accounts and something gone wrong, btw i donated again with a different account and so far so good

edit: happened again, lost all pro features. this is annoying
[Xposed Framework Modules] Osama Zabin:
New GPS ver 0.99 is being pushed...

I just came to know after getting several FCs for Google Play Services ( fixed by clearing cache/dalvik through recovery)

I'm expecting some lovely surprises as usual after each update from Google.