yashsingh1/xdaforums huggingface dataset:
[Xposed Framework Modules] mattie_49:
Amplify hasn't been maintained in over a year. That's quite a few Android versions that have passed by. I was a big amplify user here recently. No more. I find it's better without especially in Android 8.0 + . It's much better optimized under the hood then all previous versions of android. And everything you limit in Amplify unless your positive exactly what it does. Controls push notifications e-mails account sync. So on and so on.
[Xposed Framework Modules] boosters:
Is this app working anymore?
[Xposed Framework Modules] x1ld3n:
On Nougat is working well, on Oreo it shows only Wakelocks and Alarms.
[Xposed Framework Modules] infinitiwoods12:
i m on stock note 9. rooted with latest magisk. and latest system xposed installed .

amplify is collecting alarms but not wakelocks.

please help .. what am i missing ..

it used to work great on my note 8 with supersu.

please help
[Xposed Framework Modules] DB126:
Take the opportunity to divest yourself from the chains of alarm and wakelock (symptom vs root cause) management. It is not needed on Android 6+ nor on any device with a clean app portfolio. Alarms and wakelocks are not evil; how the device/apps respond determines if there is an adverse consequence. The world that existed when Amplify was first developed is largely irrelevant on modern hardware, kernels and ROMs.

Do yourself a favor; take 10 min and read through the last 25-50 posts.
[Xposed Framework Modules] infinitiwoods12:
do you also suggest i don't stress debloating for some extra juice on modern hardware
[Xposed Framework Modules] DB126:
Depends on app portfolio. Carrier and "sponsored" apps are often designed to get in your face which can take a toll on battery life. Those items will gravitate toward the top to the list when viewing "battery" under device settings. Do not (NOT!, NOT!!) stress over Android System and/or Google Play Services appearing near the top. Something has to be on top of the list; occupying that position does not automatically equate to 'bad'. Understand nearly every feature and app on your device utilizes Google Play Service to perform core functions such as establishing network connectivity, validating credentials/entitlements, etc. That makes Play Service look like a bad actor when actually it is doing work explicitly requested by apps. The work has to get done somehow; Google's implementation is often more efficient than if the app developer coded it themselves (if permitted to do so). Those playing the ignorant alarm/wakelock/debloat squash game often fail to consider why actions are taking place and/or if those actions actually have an adverse consequence. They see a big, juicy number in Amplify, BBS or some other tool and want to kill it with little/no supporting justification. Then complain about the side-effects of ripping out a kidney. :)

Enjoy your device for what it is. Resist the temptation to manage everything just because it exists or some random poster suggested it's essential to tweak XYZ with little supporting evidence/experience. More likely than not they are some n00b with an oversized opinion on everything.

This guy probably said it best: https://xdaforums.com/showpost.php?p=77199025&postcount=8146
[Xposed Framework Modules] infinitiwoods12:
thank you for the advice .. that relieves a lot..
[Xposed Framework Modules] TNSMANI:
This should be made a 'sticky' somewhere :cool:
[Xposed Framework Modules] Astronanos:
Hello I followed these steps 3 times but still when I add alarms and wakelocks they do not appear on the alarm/wakelock screen under categories(Limited etc)

Using an LG G5 H850 on Fullmics 5.5 Nougat with Magisk
[Xposed Framework Modules] TNSMANI:
It is not because of Play Store not recognising the donation. On some ROMs and devices especially on Nougat, this occurs. Search this thread for your device.
[Xposed Framework Modules] Enzissimo:
Can we hope for a solution for nougat on LG in the future? My LG V20 really needs Amplify :)

Inviato dal mio LG-H918 utilizzando Tapatalk
[Xposed Framework Modules] DB126:
Unlikely as the developer is inactive. And no, your device doesn't "need" Amplify or any other wakelock management tool...especially on Nougat. If you have a wakelock issue (do you really have a wakelock issue??) root cause lies with one or more poorly behaved apps. Fix the problem, not the symptoms.
[Xposed Framework Modules] GuestNoOne:
[MENTION=1335078]Davery[/MENTION]126

Your opinion was presented quite often now. Thank you.

If you will now please let people who desire so talk with each other, like for example tnsmani did?

... because even a freshly installed LinageOS without GApps and just a few open source - ad free- essential Apps, are enaugh that your device only works for 24h. But with the limiting of wakelocks, you can achive in my earlier case easily (without getting this 0.16%/h) like 2.5 days of stand-by time. For people who can wait for a push notification 1 hour, that solution is great.

So - everybody his own.

Thanks

[MENTION=7408621]Oswald Boelcke[/MENTION]

Thank you for your information!

So - let´s see if I will maybe able to use Titanium Backup to just backup my Data of Amplify at some Phone where I am logged into the donators account, and get the needed data, so on my Phone without GApps (and without microG) I maybe will be able to have to donated version.

Would still be great if [MENTION=526666]cryptyk[/MENTION] could reply how I can get the donated version of my account running on a phone without GApps on a more regular way?

Thanks

---------- Post added at 11:42 PM ---------- Previous post was at 11:41 PM ----------

[/COLOR [MENTION=1335078]Davery[/MENTION]126

Your opinion was presented quite often now. Thank you.

If you will now please let people who desire so talk with each other, like for example tnsmani did?

... because even a freshly installed LinageOS without GApps and just a few open source - ad free- essential Apps, are enaugh that your device only works for 24h. But with the limiting of wakelocks, you can achive in my earlier case easily (without getting this 0.16%/h) like 2.5 days of stand-by time. For people who can wait for a push notification 1 hour, that solution is great.

So - everybody his own.

Thanks

[MENTION=7408621]Oswald Boelcke[/MENTION]

Thank you for your information!

So - let´s see if I will maybe able to use Titanium Backup to just backup my Data of Amplify at some Phone where I am logged into the donators account, and get the needed data, so on my Phone without GApps (and without microG) I maybe will be able to have to donated version.

Would still be great if [MENTION=526666]cryptyk[/MENTION] could reply how I can get the donated version of my account running on a phone without GApps on a more regular way?

Thanks
[Xposed Framework Modules] DB126:
Rest assured I will continue to respond to disinformation and ignorance. That does not mean there will never a situation where alarm/wakelock limiting can prove beneficial or even the be the best/only solution. That said, such outliers are few and far between.

Funny you mention 0.16%/h. That's the avg idle drain I get on a device running LOS 12.1 (based on Android 5.1 - not known for being power efficient), GAaps and a representative portfolio of mainstream apps. Only "power management" tool in play is Greenify.
[Xposed Framework Modules] Oswald Boelcke:
If you check cryptyk's profile you'll see that he/she hasn't be logged into XDA since 17 Nov 2017. Amplify itself is also on halt for a year. I personally doubt that you're going to receive any reply even if you continue to mention cryptyk. And maybe Amplify was "qualified" to run on Android 6.1 and below, but for newer Android versions I've my doubts that the changes that came with these versions were/are really implemented in Amplify. I terminated utilisation of Amplify long time ago, and I don't miss the capabilities Amplify promised 12 months ago at all.

I personally give great thanks to @Davey126 for each and every recommendation he's provided in this (in my opinion obsolete) thread and more often in other threads. Davey126 not only delivers good solutions to a problem but also conveys a philosophy/attitude that is absolutely correct - again in my opinion. I searched this thread but haven't found any reply by Davey126 directly addressing you (but I might have missed one) and can't understand your pretty rude offence. When and where did he ever stopped you from talking with other users? I absolutely disagree with your statement; in fact in my opinion Davey126 cannot often enough share his views in this thread. Gratefully I read that he's continuing to respond.:good:
[Xposed Framework Modules] DB126:
I suspect if "alarm" and "wakelock" (oh my...sounds evil!) were named differently...perhaps Hansel and Gretel...this largely misunderstood approach to maximizing the forgotten fruits of life (SOT forever!!) would have collapsed under its own weight long ago. Then again, someone would have renamed them "Hanzel and Gretyl" which would have spawned and entirely new cult-like following.
[Xposed Framework Modules] wallyhenderson:
Have a lot of alarms but no wakelocks and no services shown... any suggestions?

Have the pro version

Thanks in advance
[Xposed Framework Modules] Kucher:
Try to make the dump with BetterBatteryStats and you will see complete information about your phone nightlife.
[Xposed Framework Modules] DB126:
Love the expression "phone nightlife". Have to borrow that ... :)
[Xposed Framework Modules] wallyhenderson:
but i dont want just to "see" want to lock some of that wakelocks and services i dont see.. i mean.. what wakelocks and services its ok to disable...
[Xposed Framework Modules] peterlee928:
the purpose of doing a proper dump file via betterbatterystats as was suggested is to see if there is any excessive idle battery drain. then diagnose what is the best solution to cure that excessive drain (delete bad apps, block wakelocks, new kernel/rom, etc).

there is no point to block wakelocks/services if there is no need. trust me, i used to do exactly that, and it caused many more problems than solutions.

ask yourself what it is that you are trying to accomplish by blocking wakelocks/services. if the goal is to reduce idle battery drain (and it is unclear whether your phone even has this issue), then the first step again is to do a proper idle dumpfile via betterbatterystats. :)
[Xposed Framework Modules] wallyhenderson:
Thanks for your anwer friend, but first of all... i want to see wakelocks and services as i see alarms... just to look and to get app working as it ahould... dot...

Then... i will see if will block any of those or not... i will not block just for block

Anyway... how do i make a dump?
[Xposed Framework Modules] daekdroom:
You don't see wakelocks and services because Amplify doesn't work fully with the latest Android versions (since Nougat, I think), and it's not under development anymore.
[Xposed Framework Modules] peterlee928:
see this post for directions:

https://xdaforums.com/showthread.php?t=1179809&p=15869868
[Xposed Framework Modules] Jakob1379:
Is this mod still under maintenance?
[Xposed Framework Modules] gothicVI:
No

Gesendet von meinem Moto G (5) Plus mit Tapatalk
[Xposed Framework Modules] Jakob1379:
Dangit! Just out of curiosity, are there any alternatives that handles wakelocks?
[Xposed Framework Modules] patrickdrd:
there's an app called wakeblock, search for it (here), but I think it's for android 8+
[Xposed Framework Modules] DB126:
Keep in mind alarm/wakelock blocking on Android 6+ is largely a fool's errand with no significant benefits unless you place side effects and hours of tinkering into that category. Doze does a great job reining in power abusers. If problems still exist there is a bigger issue (root cause) that should be addressed.
[Xposed Framework Modules] Jakob1379:
You would be right if I hadn't found a wakelock sapping my battery on my android 8.0 which doze is not able to handle. But for the most cases you are right.
[Xposed Framework Modules] DB126:
Not the wakelock - just a symptom. Trace back to source and fix the real problem.
[Xposed Framework Modules] don_dolarson:
Best battery saver on Android. +2h SOT more with medium tweaking. A little room still for improvement.
[Xposed Framework Modules] DB126:
Alternatively, identify and address root cause vs masking symptoms. Not sure how one scores +2h SOT improvement tweaking alarms/wakelocks when the device is already awake.
[Xposed Framework Modules] don_dolarson:
Nope, the device isn't awake. Accidentally turned off Xposed some day ago and just after 3% of discharging I've noticed that something has been very bad to battery. 18-20 minut SOT discharges normally within 3% with Amplify and Xposed activated and with accidentally deactivated, not even 10 minutes. Exactly the same usage. Used this module on LG G3, LG G2 Kitkat/Lollipop stock and RR 7.1.2 and it always worked as expected. Less improvement on LG phones when flashed RR roms over stock KK/LL. So far 7h30min SOT within 48h since last charge on 3300mAh (~2800 measured in AccuBattery) battery is quite decent result. Thank you Amplify.
[Xposed Framework Modules] DB126:
Sounds like you have a bad actor in you app suite as there is no other obvious commonality across the various platforms and ROMs in your device portfolio. Amplify is simply muzzling the bad actor(s). If it is working for you, then great. I'd rather solve the real problem.
[Xposed Framework Modules] don_dolarson:
Never had any problems. Just some Google reading, applying modifications and voila. Some extra SOT time to bring.

Got down from 45 android wakelocks to 15, just in an hour, and 15 vs 5 wakelocks/hour by Google Play services.
[Xposed Framework Modules] DB126:
Sure, the way your devices are configured you (apparently) need to whack wakelocks to achieve the same "SOT" that is obtainable on a clean build of a stable rom/kernel with a well behaved app portfolio. I get it...works for you.

In a clean environment suppressing alarms/wakelocks does not equate to significantly improved battery endurance. Simply not the way alarms and wakelocks work on modern kernels/roms.

Granted, the above statement only applies to Android 6+ unless one spends considerable time tweaking the flawed power management framework in Lollipop and below. That's where Amplify got a foothold and actually made sense. A few continue to believe in the presence new realities.

Glad you are happy.
[Xposed Framework Modules] don_dolarson:
Don't think you can achieve over 7h SOT within 48 hours since last charging, without tweaks.
[Xposed Framework Modules] eliezerjk90:
Firstly, you forget that every phones are different. I use redmi note 4 snapdragon and I can easily get around 10 hours SOT with 40 hours on time per charge cycle. All I use is custom kernel (franco kernel) without needing to tweak anything else, let alone block any wakelock.

Secondly, judging battery life performance by solely comparing SOT and charge cycle is hardly a valid method, and here's why. Battery life is affected by many factors, such as network coverage, usage pattern, installed app, configuration, etc. For example, user A uses his phone for heavy media consumption and game, user B using his phone mostly for music listening (with screen off most of the time), user C just use it to read ebook. We can guess that user C will have a long SOT and charge cycle among those three. User B will have "moderate" battery life but with low SOT time, and user A probably will have "worst" SOT and battery life. But in reality, all cases is hardly comparable. Even for same user, the usage pattern will change depends on activities. Not to mention there's often placebo effect.

In short, unless you have a measured and reproducible method to get the statistics, it could potentially mislead. And the other user have a valid point that huge wakelock is only the symptom. It might be more effective to look for the cause.
[Xposed Framework Modules] DB126:
Lol - 8,000 variables rolled into a simple (albeit inaccurate) summarization.

SOT a horrible metric that is rarely reproducible on one device not to mention the vast portfolio of gizmos and configs representing the Android marketplace. If snake oil is your preference keep drinking the coolaid.
[Xposed Framework Modules] eliezerjk90:
Well, in my opinion to call it "snake oil" is a bit harsh. To be fair, this app actually worked for older versions of android. Unfortunately, it just became obsolete now, especially since doze was implemented. So rather than call it "snake oil", I'd prefer to call it "expired medication" instead :p
[Xposed Framework Modules] don_dolarson:
I'm testing in the same environment. And with that Redmi with 4100mAh and Snap 625 10h SOT is nothing impressive. Mid-range processor with big battery. I've custom kernel left to flash. Testing Greenify if it actually does anything.
[Xposed Framework Modules] DB126:
Agreed. The developer was well-intentioned and produced an innovative app to catalog and limit (vs completely block) alarms, wakelocks and select system services. However, numerous issues with this approach quickly became evident as documented in this thread and elsewhere. Erratic device behavior, spontaneous reboots, missed notifications, wakelock storms, high CPU utilization, phones that wouldn't ring, increased battery drain just to call out a few. Still, it was best-of-breed at the time and one of the leading tools used to reign in bad behavior of both Android (pre-Marshmallow) and nasty apps that abused background permissions. All that began to change with the introduction of Doze and Google's tightening policies regarding 'bad' behaviors.

Unfortunately, the common understanding of how alarms, wakelocks and receivers really work has not progressed. Most wakelocks are benign; whether there are listening receiver(s) and the actions receivers (typically an 'app') take determines whether the outcome is viewed positively or negatively. Most of my devices catalog hundreds of app wakelocks per hour yet sleep peacefully and have a satisfactory screen on/screen off battery endurance with no special actions on my part aside from booting apps that clearly don't play by the rules. Kernel wakelocks are a different beast and usually point to a hardware issue such as a dirty fingerprint sensor or other hardware components that are not properly supported by a custom kernel and/or ROM.
[Xposed Framework Modules] williamcll:
I'm not sure if this was discussed but running amplify on virtual xposed causes pro features unavailable.
[Xposed Framework Modules] cryptyk:
Amplify no longer available in the Play Store

Hi everyone,

OP here. It's been a long time since I've checked in, but I want to share some news. I received an email from Google yesterday letting me know that Amplify has been suspended from the Play Store because it changes the way that other apps work, which is against their policy. Google is enforcing this policy much more recently than they had in the past. Numerous other apps have also been taken down: CyanogenMod's installer, LuckyPatcher, Magisk Manager, Viper4Android, etc. I respect Google's policy on this and understand that the Play Store is evolving and needs to be "safe for Grandma" rather than a tool for Power Users like ourselves.

After some consideration, I think that Amplify should remain available. Google's implementation of Doze, Coalesced WakeLocks, and user pressure to deliver apps that don't overuse the battery have made Amplify less critical than it was in the past. Still, there are users on older phones and power users who want to have granular control over their wakelocks and Amplify fills a valuable niche for those people. I'm still considering how to make sure that Amplify remains available for people who need it. I need to find a couple of hours this week to recompile so that it will work without the Google Play Services and decide where to host it. Amplify has always been, and will always remain, an open source project. You're always welcome to download the source yourself from GitHub.

This Amplify thread has over 8,200 posts and over 2 million views. It's the 5th most viewed thread of all-time in the Xposed Modules forum. The app had almost 1 million downloads and a Play Store rating of 4.13 stars. I originally built Amplify for myself because I was frustrated with two particular wakelocks that were misbehaving. I never dreamed it would grow the way it did. I appreciate all of your support throughout the years.

Here's to better battery life!

Ryan
[Xposed Framework Modules] gregferns:
Thanks to you man for this wonderful app.... Rightly said nowadays I'm not using it, but for all the time i didn't with it i was happy... Appreciate your efforts...

I still have an old android which i plan to keep using with android 8 i think... So if you ever do continue it i defibrillator will be using it.

Cheers mate...
[Xposed Framework Modules] Smultie:
Looks good!!! 2 small remarks:

* Opacity of the side menu is a bit high in my opinion (too transparant)

* Can't buy the pro package. "This version of the application is not configured for billing through Google Play. Check the help center for more information".
[Xposed Framework Modules] mannequin:
really good redesign, loving it.
[Xposed Framework Modules] cryptyk:
I took a look and agree about the side menu. Good eye.

The Play Store takes an hour or two to update after a new release. The Pro package should be able to be purchased soon.

Thanks!

Ryan
[Xposed Framework Modules] milojoseph:
:) you just revolutionized the true meaning of wakelock managing......... with this and greenify do i ever need to carry my charger.
[Xposed Framework Modules] Cr3sc3nt:
When the Pro Package becomes available, I'll be sure to sent something your way :) Keep up the great work.
[Xposed Framework Modules] khairulez:
[MENTION=526666]cryptyk[/MENTION]

Installed v1.1.5b on my 4.2.2 i have a lot 'preventing' in log and i need to be patient until you release new one(v1.1.5)..Nah!! it works great!..thank you so much.

And UI is nice too.
[Xposed Framework Modules] xk0niR:
The latest Update does not work for me. I try to open the App via Xposed and it instant crashes.

1.15b2 worked fine for me.

Anyone else havin this issue?

I am running 4.4.4 AOSP Rom (Galaxy S4)
[Xposed Framework Modules] aeoveu:
Can I donate a dollar? I only got one yesterday (Play Survey/offers thingi) and honestly, this is the first time I'll be using that credit. I'm not the credit card type of guy, but I would really like to give you the dollar I earned (for free...) yesterday. It's the only dollar I have, so please, take care of it really well ;)

Update: done! Donated. My very first Google play transaction - on you! It's the least I could do (in my current capacity) to thank you on behalf of myself and everyone else who isn't able to donate.
[Xposed Framework Modules] davtse:
rebooted after installing?
[Xposed Framework Modules] xk0niR:
Yes.

All steps I did:

- Uninstall

- Reboot

- Install

- Reboot

Force Close when trying to open.

Maybe it´s caused by another Module or so.
[Xposed Framework Modules] cryptyk:
Thank you so much. I appreciate the support. Please enjoy your better battery life! With regards to the dollar, I'm going to take the donations so far and treat my girlfriend to an amazing dinner. As I'm signing that check, I'll be thinking about where the meal is coming from for sure.

Thanks,

Ryan (and his girlfriend :))
[Xposed Framework Modules] cryptyk:
Weird. Can you grab a logcat and PM it to me?
[Xposed Framework Modules] cryptyk:
Thank you! 1.1.5 is out now!!!
[Xposed Framework Modules] Pkt_Lnt:
>> ninjaéd <<
[Xposed Framework Modules] kamiller42:
What will Android L mean for NlpUnbounce?

Will this utility be necessary?

My gut feeling is Project Volta reveals to Google the problems, especially with their own Play Services. They claim a 30% battery savings. Sure, we get the savings but that's only because they finally put a leash on what's been a growing problem, again, especially with their Play Services.