yashsingh1/xdaforums huggingface dataset:
[Xposed Framework Modules] TNSMANI:
I don't think that it is strange. It is a natural corollary of blocking the service. Since the service is blocked, it is not launched. (I may be wrong but to me it seems natural).
[Xposed Framework Modules] namitutonka:
I limited these four wakelocks:

com.google.android.finsky.instantapps.statussync.StatusSyncService:launch

com.google.android.finsky.instantapps.statussync.StatusSyncService:run

com.google.android.finsky.instantapps.PhenotypeUpdateService:launch

com.google.android.finsky.instantapps.PhenotypeUpdateService:run

All of them except com.google.android.finsky.instantapps.statussync.StatusSyncService:launch are listed under the Limited category. This wakelock has vanished. It is not listed in any category; neither Limited, Safe to Limit, Unknown, nor Not safe to limit. :eek:

In the 15 hours since limiting these wakelocks, they only have fired once, with zero seconds duration. Very low and insignificant numbers.

The following services have only been denied once:

com.android.vending/com.google.android.finsky.instantapps.statussync.S tatussyncService

com.android.vending/com.google.android.finsky.instantapps.PhenotypeUpd ateService

The following service has zero denials so far:

com.google.android.gms/.instantapps.routing.DomainFilterUpdateService
[Xposed Framework Modules] breacherman:
Oh, well does that version even work on nougat?

Edit: Doesen't look like, it timer isn't even starting...

'
[Xposed Framework Modules] eliezerjk90:
I use the latest version with nougat abd there is no problem at all
[Xposed Framework Modules] Richardd14:
can someone tell me if the amplify is working on oreo RR , in special the SERVICES section? for me is working only Wakelocks and Alarms, and in Services isnt show something...why? is a problem from amplify or from the dev of the rom?
[Xposed Framework Modules] Professor1991:
I can't seem to find this on the spreadsheet (Apologies if it is indeed on it) but is ConnectivityService safe to amplify ?

This wakelock is the biggest culprit on my device. I keep my phone on airplane mode (It doesn't have a SIM) and use WiFi when required but whenever I switch WiFi, this causes a surge in wakelocks. I can understand it if I left Wifi on, and it wasn't connected to a known network so it was constantly searching, but this happens when WiFi is off. I can't imagine it being on the Cellular side, due to me keeping the phone in airplane mode.

Also is NetScheduler also safe as well. That is culprit No2 on my device.

Thanks,
[Xposed Framework Modules] TNSMANI:
Connectivityservice - "Service responsible for tracking data connection / apn, establish and maintain connections. This wakelock is held during transition between data connections." This is the explanation given by the dev of BBS.

If you deny data connectivity (mobile or wifi), then all the apps and processes needing it will wait (if they are properly and sensibly developed) and pounce the moment data is available. Keeping wifi off doesn't prevent apps from searching for data since even when wifi is off certain apps and services, especially Google's, will look for it.

May be inserting a sim and disabling data before removing the sim and enabling airplane mode may reduce the wakelock. This is only a conjecture and without any basis except that sometimes I had also faced a similar issue in my N4.
[Xposed Framework Modules] DB126:
Aside from the alarming wakelocks (pun intended) one has to question if the observed behavior has a negative consequence. Is there a correlation between the "culprits" and excessive (operative word) battery drain? Despite the ominous label "wakelocks" do always lead to wakeups and/or extended wake time. Nor is modest screen-off wake time necessarily detrimental as modern devices often idle very efficiently.
[Xposed Framework Modules] Victorman86:
I have many random reboots, Google App forecloses and no any energysaving effect with Amplify recommended settings from first page.

OS: Xperia Oreo. Please help.
[Xposed Framework Modules] DB126:
Request: "Please help".

Answer: Uninstall Amplify! Totally unnecessary on Oreo and arguably any ROM based on Android 6+. A quick thread scan will surface far, far more issues than benefits. Which is completely consistent with the ill advised practice of limiting alarms and wakelocks.
[Xposed Framework Modules] SGH-i200:
I'm using the RunInBackgroundSetter by [MENTION=4467676]MrBIMC[/MENTION] for Android 7.1. RTC alarms and Wakelock have been important in 4.4.*

https://labs.xda-developers.com/store/app/com.pavelsikun.runinbackgroundpermissionsetter
[Xposed Framework Modules] DB126:
In Android 4.4/5.1 alarm and wakelock limiting arguably had greater benefit although there were usually better ways to deal with rogue drainers. Makes little to no sense on Android 6+. Yes, you will still see a ton of alarm and WL activity but the true litmus test is battery drain which doze manages nicely.
[Xposed Framework Modules] partyman66:
Any idea why Amplify 4.0.1 would show no data on Android 7.0 LG V20 with stock rooted ROM(with mk2000 kernel)?

I'm using SuperSU for root with TWRP recovery. All I see in Amplify is the counting timer but every single other stat says 0, and when I go to ALARMS, WAKE LOCKS, or SERVICES it just shows the category headers with nothing beneath them.
[Xposed Framework Modules] TNSMANI:
A simple search of this thread with "LG v20" would have showed that it is not compatible.
[Xposed Framework Modules] Zincoshine:
Oh it's necessary if you have WeChat installed...
[Xposed Framework Modules] DB126:
Probably not but it appears the decision has been made so no point in discussing alternatives (nor is there any need if Amplify is serving your needs with no side effects).
[Xposed Framework Modules] mattie_49:
what did you limit this 2 and did device work properly
[Xposed Framework Modules] mattie_49:
Anyone know what alarm or wakelock I blocked that keeps play store from showing which apps I've purchased. Unticked amplify rebooted and reinstalled app without purchasing again. Please and thank you beforehand.
[Xposed Framework Modules] DB126:
How about not mucking with alarms/wakelocks in the first place? Unless you are running some ancient ROM or fall into to the ½% 'special needs' category wakelock blocking is largely a fool's errand. If the motive is battery endurance find the root cause of excess drain and deal with it properly.
[Xposed Framework Modules] TNSMANI:
Lockbox relates to locating device and either lock it or delete sensitive info in case the phone is stolen. If you limit these, Lockbox will not work properly and you will lose its functionality.
[Xposed Framework Modules] patrickdrd:
I love amplify and I installed on my nougat phone with the same settings I was using in kk and lp phones and it works great, I don't know why people write here to criticize it..
[Xposed Framework Modules] marcdw:
I don't think it's so much criticism of Amplify as it about folks trying to manage wakelocks and alarms on newer Androids when it isn't really necessary.

In some cases the desire to manage is actually hurting instead of helping.

On another note, my long-running PAC-MAN Lollipop (main/daily on my G3) had been Amplified & Greenified but idle drain was an almost steady 1.6%/hr. I was okay with that given what was on the phone.

Once I managed broadcast receivers (analytics, measurements, firebase) idle drain doesn't go above 0.5% most of the time. Sleeps much better with no ill effects.

Been on that ROM since 2015. ?

Moto G5S Plus XT1806, FrankenROM Oreo, MultiROM, Tapatalk 4.9.5
[Xposed Framework Modules] patrickdrd:
of couse I'm managing services and broadcast receivers as well, despite the fact that my android version is newer (7.1.2),

I just don't want unnecessary things running on my phone (like wearables e.g., and more so, analytics, crashlytics and advertisement caches)
[Xposed Framework Modules] RASTAVIPER:
Having Oreo 8.1 out, describing 7.1.2 as newer what do u mean exactly?

Most people complain about app to be more optimised for OREO I guess.

Unleashed by my rooted OP3T on 8.0
[Xposed Framework Modules] marcdw:
Newer than the Lollipop I had mentioned before as well as his KK/LP ROMs.

Moto G5S Plus XT1806, BootleggersROM-Shishufied, microG (NoGapps), MultiROM, Tapatalk 4.9.5
[Xposed Framework Modules] x1ld3n:
Is there any way to make it show services on Oreo?
[Xposed Framework Modules] mattie_49:
It does if it's ticked in settings. Mixed in with wakelocks. Look closely. MyAndroidtools from the play store does the trick.
[Xposed Framework Modules] x1ld3n:
I was using it on Nougat and the problem is that some services that I disabled with MyAndroidTools appear in Amplify because it only disables devices not blocking and those services are enabled by themselves.
[Xposed Framework Modules] mattie_49:
Believe it or not. The only way I could get services to stick was to do them one at a time through Myandroidtools. I'm currently on Oreo. And only had to kill off analytics again. All the other 138 services have stayed off. Try this thread helped me much.

https://xdaforums.com/oneplus-3/how-to/guide-stop-google-play-services-t3549760/page23
[Xposed Framework Modules] TNSMANI:
The dev of MyAndroidTools has developed another app called MyAndroidTools Xposed Module which is available in the Xposed repo. If you use Xposed, this module will enable you to block the auto-re-enabling of some Services/components. They stay disabled.

[MENTION=2338414]mattie_49[/MENTION]
[Xposed Framework Modules] x1ld3n:
This module partially works but some services are still not blocked. For example Twitter's "com.twitter.android/com.twitter.analytics.service.ScribeService" service. I disabled it, then blocked twitter in the MyAndroidTools module and this service is still appearing in the Amplify.
[Xposed Framework Modules] TNSMANI:
Are you doing it correctly? Block/disable the service in MAT app and when it appears in the MAT Xposed module log as restarted, touch it and blacklist it.
[Xposed Framework Modules] x1ld3n:
I disabled that service in MAT, the blocked it in MAT Xposed module and and even restart the phone. Then I opened Twitter app and I see in Amplify that this service was started about 20-30 times.
[Xposed Framework Modules] TNSMANI:
Read again what I said. The first part of disabling the service in MAT is ok. But you don't tick Twitter in the Blacklist of MAT Xposed module. You go to "log" in the module and click the service when it appears there and when the dialogue box appears to add it to the Blacklist, you select it.
[Xposed Framework Modules] x1ld3n:
It does not even appear in the log. I ticked Twitter in blacklist.

https://imgur.com/a/eBwNPCH
[Xposed Framework Modules] Dominius:
Is way to export all blocked wakelocks and alarms when I make wipe on my phone?
[Xposed Framework Modules] mattie_49:
Backup amplify through titanium. When you restore on new rom everything still blocked on new build
[Xposed Framework Modules] DB126:
Here's a thought: try running w/o Amplify or any other form of alarm/wakelock blocking on a clean ROM for 48 hours. Might be surprised.
[Xposed Framework Modules] mattie_49:
I'm very surprised have been running 3 days without. I really think there are way less background apps performing tasks. Almost as if it creates it's own wakelocks by being limited. Really crazy I was sold on amplify. Now without it almost seems better on Android 8.0. Won't know for sure for a few more days but sure seems that way.
[Xposed Framework Modules] Depressed T.Bear:
Not surprising, since Android 7/8 I read that blocking wakelocks is not really efficient because there have been a lot of work done under the hood. Amplify seems to have a negative effect regarding battery life and performance now.
[Xposed Framework Modules] x1ld3n:
Without Amplify deep sleep percentage is around 80. With Amplify it is 99%, sometimes even 100%.
[Xposed Framework Modules] Depressed T.Bear:
Yes, it heavily depends on your device, android version and personal configuration. I tested it for quite some time. Only my old devices with android 4 and 6 amplify was awesomely great. Now on my OnePlus 6 with 8.1 it's a) hard to get it running since the app seems to be abandoned and b) when I got it to work, it has a negativ effect on battery life overall.

Deepsleep is not everything imho
[Xposed Framework Modules] x1ld3n:
I'm using Greenify in Shallow hibernation mode and I don't have problem with wakelocks with my apps. All the partial wakelocks that prevent my phone to go into deep sleep are some system wakelocks. Btw I'm on official Lineage OS 15.1
[Xposed Framework Modules] x1ld3n:
I'm using Greenify in Shallow hibernation mode and I dont have problems with wakelocks from my installed apps. All the partial wakelocks that prevent my phone to go into deep sleep are some system wakelocks. Btw I'm on official Lineage OS 15.1
[Xposed Framework Modules] DB126:
The behaviors you describe have been well documented in this thread and others. Doubters conveniently skip those posts or spin up self-serving theories that have no basis in reality (sigh - unsubstantiated opinions are on par with unrefutable facts in today's world). Alarms and wakelocks are not evil in isolation; how your device/apps respond is what determines the overall experience which *can* be marred by excessive battery drain - usually by 'bad actors' running in the background. Android 6+ moderates this behavior via Doze and other mechanisms. Google has also cracked down on sloppy coding practices and unscrupulous behaviors both in its own portfolio and apps hosted in the Play Store. Homegrown countermeasures that were occasionally beneficial in the JB/KK/LP days are almost always counterproductive today.

Best practice is to identify and dispense with misbehaving apps. However, even those simple steps are largely unnecessary on modern devices running Android 7/8/P with a reasonably curated app portfolio. Everything just 'works'. As you are rediscovering.

Purists will attempt to call out metrics such as "huge" alarm/wakelock counts and deep sleep percentages below 98-99% as justification to take action. The former are largely benign (counts in isolation are meaningless); the latter is far less important on modern devices that sip power at low frequencies allowing devices/apps to efficiently perform beneficial background tasks. Visibility to Android internals does not equate to a problem. Idle drain is the metric to watch ... not deep sleep, alarms, wakelocks, phase of the moon, etc.

---------- Post added at 07:58 AM ---------- Previous post was at 07:42 AM ----------

Deep sleep percentage does not tell the whole story and is not necessarily an indicator of excessive battery drain. I have seen devices that bounce in and out of deep sleep achieve idle drain rates well under 1%/hr. "System wakelocks" (which need further investigation as many are triggered by apps and/or rogue sensors) on a custom ROMs are often the result of poor compatibility with the underlying hardware and/or attempts to circumvent native Android/Google behaviors. Some Lineage builds attempt to address the former by including a 'custom' kernel. However, unless that kernel has been tuned for your specific hardware it will likely perform no better...and often worse...than the stock kernel. More self-inflicted pain.

If Amplify (and other forms of alarm/wakelock limiting/blocking) solves your problem w/o side effects then obviously there is no reason to change direction. That said, there are almost always side effects that either go unnoticed or are conveniently ignored. Have fun.
[Xposed Framework Modules] Dominius:
You have worse battery life with amplify with stock Oxygen OS right? I also have oneplus with stock os, but 3t, and this is might be a reason why i don't have satisfactional battery life?
[Xposed Framework Modules] Depressed T.Bear:
That's right, at least for me.

I'd suggest that you deactivate amplify and test it on your own for a couple of days ;)
[Xposed Framework Modules] mattie_49:
I'm getting much better off charger hours and sot without amplify and xposed. Much smoother and getting all my notifications,calls etc. Definitely not needed on Oreo
[Xposed Framework Modules] Depressed T.Bear:
Yes I share this opinion. Maybe it'll be one day useful again - but since Ryan wasn't seen online since nearly one year, we can't hope for official Oreo+ support.

Btw, something terrible must have happened to him, his whole digital life is stuck since the end of last year (website, LinkedIn, YouTube, Instagram and so on :(...)

Everyone should keep in mind that Amplify only supports Andoird up to Nougat (until now)! And things were changing under the hood since then. So noone should expect it to work on Oreo+ like it did on earlier Android versions.
[Xposed Framework Modules] patzzz:
I'm using a Resurrection Remix build based on Oreo and Amplify is blocking Wakelocks and Alarms without problems, although it isn't blocking Services because the Services list is empty, but this isn't a problem for me.

Why do you say that Amplify should not work on Oreo+ like it did on earlier Android versions?
[Xposed Framework Modules] Depressed T.Bear:
The app itself should work. But according to many posts across the internet (forums, playstore etc.) it somehow drains the battery, has problems to detect root and so on.

I don't wanna say the app is bad, it's just not updated against the latest version of Android. Everyone should try it for his-/ herself!

At least for me and some others I spoke to
[Xposed Framework Modules] patzzz:
OK, I'll try without Amplify.

Thanks.
[Xposed Framework Modules] DB126:
Engaging in alarm/wakelock management is a largely fools errand - especially on Android 6+ as explained in numerous posts to this thread and others. But the "internet" is full of folly and miracle solutions that defy root cause analysis and remediation (alt-facts are all the rage). Excessive alarms/wakelocks are symptoms of an underlying issue, not causes. Figure out what's really keeping your device awake and fix the problem. There are no panaceas.

Wakelocks have zero bearing on SOT despite the ignorant claims of those who attempt to draw lines between unrelated dots.
[Xposed Framework Modules] Depressed T.Bear:
Totally true, exactly what I was trying to convey. Except for one little detail here, regarding Amplify, the approach was/isn't to entirely block wake-locks, but to limit them. This actually had a positive effect on older phones regarding battery-life (of course not on SOT ;) ). On newer Android versions I (personally) can't recommend it anymore.

Thanks for your contribution Davey :good:
[Xposed Framework Modules] DB126:
Yep - hence the term "wakelock management" which encompasses blocking, limiting and all other forms of knob turning. All of which are akin to taking an analgesic for chronic (vs acute) pain. Feels good, but does not address the underlying issue...even on older Android builds.
[Xposed Framework Modules] x1ld3n:
I was using the phone a few days without Amplify, and yes, it's better without it.
[Xposed Framework Modules] mattie_49:
And not getting any crazy wakelocks like I was before when limiting everything. Android 8.0 truly is better optimized. I noticed also that not going into settings/apps and turning off run in background keeps play services chill as well. Blocking background use or data seems to make it go berzerk
[Xposed Framework Modules] sguerra923:
So it sounds like with running oreo it's not beneficial to have amplify? Just curious what people think? Thanks in advance!
[Xposed Framework Modules] mattie_49:
Read the last 10 pages. Definitely getting a better all around experience. No issues from limiting the wrong things and countless hours googling what's this and what's that. I even followed some good guides on what to limit. No good for Android 8.0 better battery life without
[Xposed Framework Modules] DB126:
There are very few (arguably no) scenarios where wakelock limiting/blocking is preferable to addressing root cause regardless of Android version. This is especially true on Android 6+.
[Xposed Framework Modules] TNSMANI:
Not at all required on Oreo.
[Xposed Framework Modules] ianmacd:
Which isn't to say that Amplify should never be used, even on Android 6+, because one can't always address the root cause, or if one can, it may require full removal of a needed package.

View wakelock management as a last resort, not a first, always understand what you're limiting and why, and know how to measure the effect of any changes you make. If you do that, you won't go too far wrong.
[Xposed Framework Modules] DB126:
Agreed; solid guidance for most - albeit an easy escape for those maligned by internet nonsense and eager to jump at perceived easy fixes ignoring likely consequences. Crowd sourcing has its place and can be exceptionally powerful when properly filtered. "Technical solutions" aimed at consumer electronics (often warped by largely baseless beliefs/perceptions) generally do not lend themselves to the model.
[Xposed Framework Modules] ianmacd:
And nowhere is more rumour, half-truth, pseudo-science and outright bull**** propagated than in the world of Android battery performance. XDA's cup runneth over with it, and it's the users themselves perpetuating all of the myths, with nothing more to back them up than meaningless screenshots and "I heard this from a lot of other users, too." Bah.
[Xposed Framework Modules] GuestNoOne:
Peace Ryan,

I use Amplify and donated the Pro Package in the past. Now I do want to keep out gapps completely, not even using the pico. Without the Google IAP I do not got the pro anymore.

So, is there - even if you don't want to write 2 versions - any solution to people like me?

Ty
[Xposed Framework Modules] gothicVI:
Most likely not going to happen, since op has been absent from the thread for months.

Gesendet von meinem Moto G (5) Plus mit Tapatalk
[Xposed Framework Modules] beanbean50:
just wait a few moments and I'm sure the Recognized Troll will be here telling you that you don't need this app anymore (he's been trolling battery saving threads for years, always with the same negative comments)
[Xposed Framework Modules] mattie_49:
This really is true. Funny but true won't be long now.
[Xposed Framework Modules] DB126:
Fake news; it's now legit to live in an echo chamber and believe what you want in the absence of factual distractions. Trolls only serve to reinforce illusions.
[Xposed Framework Modules] GuestNoOne:
[MENTION=526666]cryptyk[/MENTION]

Maybe quoting you will help :p

Do you maybe got any comment to my previous post for me?

Ty
[Xposed Framework Modules] Au5t1n:
Not much activity about the descriptions in a long time. Just thought I'd repost the knowledge base link for reference https://docs.google.com/spreadsheet...IX0gYFBe1K8_R3NBloP4Q1FgpIU/edit?usp=drivesdk
[Xposed Framework Modules] Oswald Boelcke:
All of our devices are GApps free and running with microG (installed with the support/use of NanoDroid). The by the developer of NanoDroid modified Google Play Store is the one and only Google application on our devices. And as you see in the attached screenshot, the donation is indicated in Amplify.

Important as mentioned in the OP, don't use Amplify from the Xposed repo!

If Interested, when µG (and through it Google Play Store) is running, simply download and install Amplify from the play store. Before opening/launching Amplify the first time, ensure Amplify has internet access. Now Amplify is automatically recognising the donation. If desired you can now withdraw internet access from Amplify as I e.g. did. Nevertheless, Amplify will stay in the "donation mode" even after a reboot.
[Xposed Framework Modules] andreasy:
I know that this doesn't sound reasonable but when I have Amplify enabled, my phone doesn't wake up for notifications (i.e. Viber messages) and when I disable it, messages come (maybe with small delay or no delay at all). The thing is that I don't have anything related to Viber included.

I attach my Amplify configuration and also, for some reason services list is empty although on previous ROMS I had a visible list