yashsingh1/xdaforums huggingface dataset:
[Xposed Framework Modules] aidy.lucas:
This app is awesome, set everything under safe to limit at 240. So far no problems, noticed a effect on battery battery drain at idle after a few hours. Superb work fella :thumbup:

sent from my Rooted B/l 4.4.4 kk Xperia D2303
[Xposed Framework Modules] FuMMoD:
Any reason why this keeps appearing? All my other xposed modules are working. I do have XPrivacy installed though and I read it might be causing issues with amplified.
[Xposed Framework Modules] 4Freedom:
I installed thia app but i cant find any difference than before without this.

That's my report.

Should i edit/change some setting?
[Xposed Framework Modules] cryptyk:
Are Location services turned on?

Thanks,

Ryan
[Xposed Framework Modules] Pkt_Lnt:
Yes, you have to customize it for your device amd use.

Better Battery Stats and Wakelock Detector are good analysis tools to know what to change in Amplify for improvements for you.

There is a lot of very good technical discussion in this thread about what and why to block. Read some of the early posts to learn more.
[Xposed Framework Modules] cryptyk:
If you go to Xposed Installer, do you see red error text on the main menu?
[Xposed Framework Modules] FuMMoD:
It did not show up at all in the modules list. Xposed is setup fine. I did a couple of reboots and it automatically populated onto the modules list and I was able to activate it. Weird bug but I guess it could be due to XPrivacy being installed. I have it updated and running right now. Thank you.
[Xposed Framework Modules] aeoveu:
New Xposed out - states to have fixed some bugs us Amplify users have posted in our logcats (I'm about to install so can't comment just yet).

http://xdaforums.com/showthread.php?t=3034811
[Xposed Framework Modules] milojoseph:
Is there a way to manage PowerManagerService.WakeLocks

Sent from my SM-G900T
[Xposed Framework Modules] wrongway213:
Anyone tried this module out in SELinux enforcing yet since alpha 2 came out? I'm curious if this one is running normally in enforcing, as the new alpha of Xposed does not require a permissive kernel anymore to run Xposed, but I am not sure as to how broadly that applies to modules.
[Xposed Framework Modules] Cyclu:
I'm an satisfied user of Amplify and don't complain I said that I'm happy for changing the force close into an error message. I don't have and never had these issues with InApp Billing only I have read that for certains users still have the problem with it which is weird I understand that you can't do more.:)

Except these kinda of wakelocks "*sync*/com.google android.gms..." pay attention please to the word "gms" are the Play Service wakelocks and no System Android verified with BetterBatteryStats (see the screenshot please) Wakelock Detector and Android Tuner and they were before under Play Service in Amplify simply after an Play Service update they are changed places.
[Xposed Framework Modules] Cyclu:
There is no problem with XPrivacy and Amplify only you have to allow your Google account for Amplify in XPrivacy to use the Pro features. That's normal is how InApp Billing works.
[Xposed Framework Modules] dayle_fernandes:
I bought the xposed module. Ever since I restricted several alarms and wakelocks I have had several of these wakelocks. I never had this issue before. I'd appreciate any help. I barely used my phone and this is the case.
[Xposed Framework Modules] s2d4:
Not sure what you are on about, they exist with or without amplify.

And if it is what you restricted, why not just unrestrict them to test since we have no idea what you've done.
[Xposed Framework Modules] FuMMoD:
Great tip sir. Thanks
[Xposed Framework Modules] auggie246:
can't donate, when i click it in-app amplify just crash
[Xposed Framework Modules] cryptyk:
Read the OP.
[Xposed Framework Modules] spupuz:
Anyone knows which service alarm or wakelock can make alarm clock not working? I have stopped only safe wakelock and alarms

prevent alarm clock to work?
[Xposed Framework Modules] aeoveu:
For those who are updating to Android 5.1, xposed doesn't work yet.
[Xposed Framework Modules] MaKTaiL:
Amplify has been acting up since I updated Xposed to Alpha 2. It is not saving my settings and the reset stats button is not working either (at least not how it used to). Anybody having the same problem?

EDIT

Nevermind, changed my SELinux to Permissive and all is well again.

For some reason it changed back to Enforced after I updated Xposed.
[Xposed Framework Modules] s2d4:
Dude, let it boot up in enforced mode and leave it in enforced mode.

Both Xposed and amplify works in enforced mode already.

Search the thread, the developer already mentioned what you are doing as a no no when he released the latest version.
[Xposed Framework Modules] MaKTaiL:
It was not working well for me though and now it is. You didnt have to quote me since I said I fixed it.
[Xposed Framework Modules] s2d4:
OK, keep running it in permissive mode then.
[Xposed Framework Modules] siealex:
Maybe AlarmManager, it controls all timed events including alarm clock.
[Xposed Framework Modules] Sportfreunde:
Google ConfigFetchService has a high wakelock time but low frequency. RILJ and GCoreFlip ar emy two most frequent 'safe to limit' wakelocks.

ActivityManager-Launch is the biggest 'Uknown' wakelock.

Are these safe to limit without causing functional problems? Also what was the Greenify service or alarm or whatever which should be limited but still allow greenify to work?
[Xposed Framework Modules] mwrobe1:
I have had the service Google ConfigFetchService disabled for days with no adverse affects FYI.
[Xposed Framework Modules] orangerot.:
If like to know whats that activitymanager wakelock too.

But seriously you shouldn't touch the greenify stuff. Greenify is already coded to save battery/ressources. The wakelocks are needed to hibernate your apps etc. They won't affect your battery life. Better concentrate on the real battery Killers, not savers.

Gesendet von meinem A0001 mit Tapatalk
[Xposed Framework Modules] Kurupt1:
Is it actually safe to limit the wake locks and alarms in the "Safe to limit" section??
[Xposed Framework Modules] Pkt_Lnt:
For many who tested them, yes. Others have issues with ones like RILJ and AudioMix, etc. Did you see the link to the spreadsheet of testing in post 1?
[Xposed Framework Modules] aidy.lucas:
I have limited everything under safe to limit so far so good.

sent from my Rooted B/l 4.4.4 kk Xperia D2303
[Xposed Framework Modules] Cyclu:
[MENTION=526666]cryptyk[/MENTION] I do not know what to say more to show you that these wakelocks are under wrong package name I have attached two screenshot side by side (BetterBatteryStats vs Amplify) maybe now you will believe me.

As I said before in three applications BetterBatteryStats Wakelock Detector and Android Tuner they are under Play Service only Amplify displays them since an Play Service update under Android System.

Sorry for bothering you with this problem.
[Xposed Framework Modules] mwrobe1:
That wakelock looks like its normal if one has sync turned on for Google Drive. JMHO.

Sent from my SAMSUNG-SGH-I747
[Xposed Framework Modules] Cyclu:
The problem has nothing to do with sync on or off and it's normal that they appear in the wakelockes list.

It's not only for this particularly wakelock the issue is that all these types of wakelocks "*sync*/com.google android.gms..." are under wrong package name.

See the both screenshots again please and compare the package name under wakelocks (Play Service vs System Android).

Edit: In settings of BetterBatteryStats disable filtering stats to see these wakelocks.
[Xposed Framework Modules] mwrobe1:
Well...I guess I learn something new everyday! :)

Sent from my SAMSUNG-SGH-I747
[Xposed Framework Modules] Takamoto:
Hi,I upgrade amplify from 2.0.7 to 3.0.5

App work well but I have force closed when tap on "alarm" and "service".

I'm on jb 4.1.1 and I buyed pro package.

Thanks.
[Xposed Framework Modules] cryptyk:
I always believed you. I understand the issue you're seeing. I've been focused on big problems, like getting this working for all of the people on Lollipop and SELinux. Also fixing crashes and trying to find a way around the Google In App Billing problems. The mismatched package name is a tiny problem that affects almost no one. After some investigation, I'm not going to fix it. Here's why:

BBS and WLD use Android's built in stats. The package name is based on the package name of the *APK* the call was made in. For example, if Facebook grabs a wakelock and calls Google Play Services all the time and kills your battery, BBS will show that as Google Play Services.

Amplify uses the *process* name that requested the wakelock. In the above example, it would say that Facebook was the culprit.

I like the way Amplify does it better because it tells you which processes are killing your battery, rather than the packages they're calling.

Thanks,

Ryan
[Xposed Framework Modules] cryptyk:
Can you grab a logcat for me?

Thanks!

Ryan
[Xposed Framework Modules] Eziogamer:
Will using values like 43200 {12hr} have any effect? If not which is tge max value that can be used? Nd is there any value which can be used to completely eliminate the wakelock..? Thnx
[Xposed Framework Modules] cryptyk:
You can wrap this in CODE sections.

I don't see an Amplify crash in the logs.
[Xposed Framework Modules] byAidan:
Hey does anyone know what the Twitter library scribe service is? Service was started 61k times before I blocked it, does anyone know what it does?

Thanks and I love Amplify!
[Xposed Framework Modules] s2d4:
Logging and data analytics.
[Xposed Framework Modules] cybernetus:
Anyone with problems on the donation ( premium ) ?

My phone was downgraded and when i try to use the premium features i have problems ...
[Xposed Framework Modules] Pkt_Lnt:
There are some solutions to this in post 1 that might help.
[Xposed Framework Modules] cybernetus:
Mate sorry :) I isn't see this on op, thanks for your help :)
[Xposed Framework Modules] Pkt_Lnt:
FAQ for problems​
[Xposed Framework Modules] Cyclu:
Voilà it explains everything I was convinced that there was a problem because these wakelocks was in Amplify under Play Service package name only after an Play Service update they are changed. This update has affected also the experimental features "disable sync of hidden account" in Greenify because even if the sync in settings>account is disabled there are still the corresponding wakelocks even not hidden sync which are disabled for example Google Drive are the wakelocks now that why I want use now Amplify for these things.

Thanks for your detailed explanation I know I'm very curious;) and now I understand perfectly how Amplify works and it's even better if it works in this way.

Good luck Ryan!

Best regards.
[Xposed Framework Modules] enilkcals:
I've started experiencing problems with Amplify, when I start its like the first time its been run so it goes through the checks.

It gets to checking for root access and then complains that the module isn't enable and offers to help Fix It which takes me to Xposed....where the Amplify module is already enabled.

Since it was at the point of checking for root access I figured it would be worth checking using SuperSU Pro, but Amplify isn't listed there, suggesting that its actually not getting root permission (I have rooted my phone).

Rebooting doesn't solve any of this.

On a Samsung Galaxy S4 running Android 4.4.4 Google Play Edition.

Any thoughts/ideas/suggestions would be gratefully received.

Cheers.
[Xposed Framework Modules] cryptyk:
If you go to Xposed Installer and look at the main screen, do you see red text in the "Xposed Framework" section?

Thanks,

Ryan
[Xposed Framework Modules] enilkcals:
Nope, just white text and if I enter the Framework section no red text there either.

I'm considering backing up and flashing the ROM again to see if that sorts things.
[Xposed Framework Modules] kk9999gada:
[MENTION=526666]cryptyk[/MENTION] I am on latest CM11 (M12) build.

The latest Google Play Services is keeping the device awake forever. Any way to resolve this problem?
[Xposed Framework Modules] kurtextrem:
I had the same problem. Switching back to the latest 6.x version fixed it.
[Xposed Framework Modules] guycan:
Do you have a link to that... thanks in advance

SGNote2
[Xposed Framework Modules] Pkt_Lnt:
Search APK Mirror http://www.apkmirror.com/
[Xposed Framework Modules] xI mEzMeRiZe Ix:
Apparently the 7.x version of GPS causes a wakelock on custom ROMs because the SystemUpdateService is constantly running and obviously can't check for an update.
[Xposed Framework Modules] Dovidhalevi:
??

Don't see this service named on my device. Amplify could be set to block it (side-effects?).

With Amplify, and not deactivating GPS/location!!, I am nearly back to the battery life I had before these latest play service upgrades.

If one downgrades, Google will re-upgrade at first chance unless one can uncheck auto-upgrade (but this is not shown like other apps). I would love to because the latest upgrades are unstable on my device!
[Xposed Framework Modules] Pkt_Lnt:
There is much confusion caused by using the same initials GPS for two services.

Global Positioning System

Google Play Services
[Xposed Framework Modules] Cerberus_tm:
I used to disable SystemUpdateService on my previous phone, because it gave similar problems (battery and data usage) on Cyanogen, without Amplify installed. Disabling SystemUpdateService worked perfectly for me. Have you tried doing so?
[Xposed Framework Modules] Langsuir:
I wanted to ask, will this make a difference for someone who keeps all location settings off most of the time?
[Xposed Framework Modules] orangerot.:
Yes it will. You can block other wakelocks if you're using the donate version. It drastically improved my battery life compared to turned off location settings. If you set the nlp wakelocks to 3600 seconds (one hour) can still use location (eg for weather updates etc), but it won't affect your battery life.

In combination with greenify this module will give you a drastically improved battery life,it's really worth a install ;) went from losing ~15% over night to only ~1% since I've installed it. If you configure it the right way (might need some different setups till you find the best) it definitely will make a difference, even if you keep location settings of most of the time.

Gesendet von meinem A0001 mit Tapatalk
[Xposed Framework Modules] xI mEzMeRiZe Ix:
My device is still on Google Play Services 6.x. I was just mentioning something I read regarding people having issues on 7.x.
[Xposed Framework Modules] k8500:
Yup, that's exactly why I came here and also why I originally intended to donate for the pro version of Amplify. However, it seems even Amplify can't stop this one (at least from what I've read), as there are dependencies and it will only get worse. Yup, there's some (intentionally?) ****ty coding in Google Play Services that will keep your device up all night and suck your battery dry if your device doesn't work exactly the way Google intended.

Good luck with that. I know this solution and I've tried this and basically every other solution found on the net. Some solutions actually seem to work, but then, after a few days SystemUpdateService always comes back.

What I'm searching for, as Google Play Services is always the worst culprit is some software that is specifically designed to keep Play Services in check. I'm pretty sure ~80% of what it does is stuff that I don't even need or want. Amplify (from what I've read) does very well for NlpWakelock and for non-Google apps it's almost a perfect solution, but when stuff like SystemUpdateService comes up, you'll need something else.

BTW, I'll donate anyways, even if Amplify can't solve this one. Thanks for the good work, Ryan!
[Xposed Framework Modules] Cerberus_tm:
What you could try is revert to an older version of the Play Services and disable its update mechanism. That should protect you at least for a while—until Google breaks something in the IPAs that makes the old version of Play Services incompatible with something Google, but that should take a while, and you can always update the Play Services by that time.
[Xposed Framework Modules] kk9999gada:
I found the solution after some googling.

Went to Privacy Guard and turned off Location, Keep Awake & Wake up option for Google Play Services. This solution is permanent regardless what version of GPS you are using, it really works and now my phone is normal again.
[Xposed Framework Modules] k8500:
I also did a lot of research on this problem and tried a lot of stuff. Now, I'll only believe that a solution really works if it holds for at least one or two weeks. Besides, turning of "Wake Up" (which I assume will disable ALL wakelocks) for Google Play Services? That will most likely lead to some bad side effects. As an example, Play Services also provides Google Cloud Messaging, a service that's connected to WhatsApp & Facebook notifications among many more.

From what I've read elsewhere in this thread, Amplify can't stop SystemUpdateService. Guess we'll need a silver bullet instead of Amplify ;). Maybe Ryan can explain (or did he already?) what is special about these Google Play Service wakelocks? I fear, even as this one will eventually get solved, there lies more trouble ahead (as Play Services' past shows).
[Xposed Framework Modules] TNSMANI:
Did you try MyAndroidTools? With it I am able to selectively shut off the update service without affecting other activities.
[Xposed Framework Modules] Dovidhalevi:
Definitely a way to do it. Amplify is now handling the problem so I returned those permissions.

I have set amplify to block this service and it has done so three times today so far.
[Xposed Framework Modules] nathanharmonn:
so is it safe to limit the Doze Services? they're producing so many wakelocks for me.
[Xposed Framework Modules] Pkt_Lnt:
I don't remember seeing anyone mention that one. Try it and let us know the result so update the knowledge base here.
[Xposed Framework Modules] nathanharmonn:
okay so 30 minutes into testing the doze services, i only Limited the Doze Services with the highest number of wakelocks, any Doze Service with 15 or more wakelocks got a 600 second check time. so far so good! that was one of the biggest wakelocks for me, and so far the phone seems to be running just as smooth as before.

If anyone knows anything about the Doze Services please let me know, I'm not exactly the best with this stuff.

Let me know if it works at all for you guys!
[Xposed Framework Modules] Pkt_Lnt:
Let it run for a day or two and report back, please. Sometimes conflict only show after some time passes.

Did you search Google of this? I got a few thousands of hits for it. This was first, there are many more.

http://xdaforums.com/showpost.php?p=56608486&postcount=147
[Xposed Framework Modules] nathanharmonn:
that's really weird, i was googling it for a while and decided to ask the masses here, i will report back though i just thought i would give an immediate idea as of now.

---------- Post added at 07:14 PM ---------- Previous post was at 07:12 PM ----------

also verdict is that yes, ambient display doesn't work as well, but hey who really wants to use something that requires 2,000 wake locks a day haha.
[Xposed Framework Modules] mickey4mice:
For those with Google Play Service 7x SystemUpdateService keeping device 100% awake, try Tasker solution posted on xda. I had the same issue, deny SystemUpdateService in Amplify didn't work for me but this Tasker workaround has.

My device is Oneplus One running Paranoid Android v4.5 stable.
[Xposed Framework Modules] milestone97:
Yo guys,

is it safe to use amplify with greenify and boot manager (the app which restricts which apps are allowed on boot)?

And do you think it makes a difference if I use GCM for whatsapp, facebook etc.?
[Xposed Framework Modules] s2d4:
There are 3 places where you need to stop it, not just one.

---------- Post added at 11:43 PM ---------- Previous post was at 11:37 PM ----------

You can do so much more with autostart app than boot manager, like the guy before will be able to search for systemupdateservice and realize there are 3 places, not just one.

No idea what you are trying to ask with your second question. Everybody uses GCM with those apps, its app dependent not user dependent.
[Xposed Framework Modules] mickey4mice:
Do you know the name of the other services need to be stopped to fully plug the leak? I also saw 3 listed but don't know the name of the other 2. It later became 5 when I looked again, sadly just a number no actual service listed. I'd much rather using Amplify to stop this wakelock then Tasker workaround.
[Xposed Framework Modules] Dovidhalevi:
Amplify is stopping mine, but that is just a few time a day, some battery gain, however.

What are the other two?
[Xposed Framework Modules] Cyclu:
I have received yesterday this bull... Play Service 7.0.97 update like everybody not deep sleep and massive wakelocks what surprise:eek: because I always disabled these services and the corresponding broadcast receivers on all my device since HTC HD2 without any problems so now to not having the wakelocks we must re-enable these services to stop the wakelocks we walk on the head:eek:

See the screenshot you have to re-enable three service I have not had to re-enable the corresponding broadcast receivers and now my device sleeps like a baby.

With My Android Tools which I personally prefer over System Tuner 3C Toolbox Pro or Autostart and others similar applications because it has very helpful search function and under about screen the backup option.

So go to Service>Play Service to enable the corresponding service always before searching tap full/short because without doing it can happens that we can't found all items.

My Android Tools link:

https://play.google.com/store/apps/details?id=cn.wq.myandroidtools&hl=en

[MENTION=526666]cryptyk[/MENTION] Hi Ryan justly why Amplify does not find these wakelocks?

I see very often the people's recommend Disable Service app instead My Android Tools

(developed by the same person) they are wrong because disabling only the service without broadcast receiver will cause even more wakelocks this is true for all app's except since latest Play Services update Google has messed up the things

now we have to enable the service to stops the wakelocks. WTF?
[Xposed Framework Modules] Cyclu:
What you see in Autostart is the broadcast receiver and not the service.

---------- Post added at 01:14 PM ---------- Previous post was at 12:43 PM ----------

I don't know why for you stopping only the broadcast receiver for SystemUpdateService works I had to enable the corresponding service instead and leave the broadcast receivers disabled to stops this wakelock.

Anyway see the screenshot for the 2 others receivers but like I said they are the broadcast receivers

and not the services.
[Xposed Framework Modules] Cyclu:
[MENTION=4301853]mickey4mice[/MENTION] Screenshot attached. Sorry again a problem with Xda Premium.
[Xposed Framework Modules] s2d4:
Yeap, I use My android tools as well.

But yeah, the receiver activates the service anyway.

Which is why only disabling the service doesn't work.
[Xposed Framework Modules] mickey4mice:
Not sure if it'd work for you but the Tasker workaround is quite simple and it works for me really well. After I activated the profile, my phone is now back to normal deep sleep level and Google Play Service doesn't show up in the battery usage anymore.

All I had to do in Tasker was to setup a runtime shell command during device bootup to enable/disable com.google.android.gms/.update.SystemUpdateService