A beautiful design, inspired by Material Design principles. Your choice of Light or Dark.

A stable blocking engine

Comprehensive measuring of the time wasted and time saved because of alarms and wakelocks

Support for Nougat and SELinux.

A growing list of descriptions of the alarms, services, and wakelocks in plain English (and other languages!)

A Pro package that lets you control any alarm, service, or wakelock on the device

Translated by the community into Chinese, Czech, Finnish, French, German, Greek, Italian, Japanese, Malay, Portuguese, Polish, Romanian, Russian, Spanish, and more

Tasker integration

An open source codebase so you can see how it works, or build it yourself

FAQ for problems

You installed Amplify from the Xposed installer instead of from the Play Store, which causes problems due to a bug in Google Play

You have the Play Store or Google Play Services Greenified

You have blocked some part of the Play Store from running with Service Blocker, or another XPosed module

You purchased Amplify with a different Google account than the one you're using now

You have Lucky Patcher installed

You're from a country where In-App Billing is not available (not common)

You need to update your Google Play Store or Google Play Services (not common)

I just did an update to Amplify in the Play Store and it takes a couple of hours for Google to update their servers with the new version (not common)

Additional details



UPDATE:Hi everyone,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--- Original Post Follows ---Amplify puts you in control of how your device uses your battery by controlling how often your device can wake up, and how long it can stay awake. Use the recommended settings for easy battery savings, or dig in and customize every alarm, service, and wakelock on your device.Here are some highlights:4.0.1 is the latest version, available in the Google Play Store You can learn more at Amplify for Android The In-App purchases allow you to unlock the Pro package that lets you customize the alarms, services, and wakelocks on your device. Without the pro package, you can control the worst battery hogs: NlpWakelock, NlpCollectorWakeLock, ALARM_WAKEUP_LOCATOR, and ALARM_WAKE_ACTIVITY_DETECTION.May you have a long [battery] life!RyanWatch this excellent review by Chris Nacca for an introduction, and to answer most of your questionsThis is frustrating. The reason is because of the way that the Play Store handles In-App-Billing when apps are installed from different places (like sideloading, Xposed repo, and sometimes from the Play Store app). The fix is usually simple:1) Uninstall Amplify from your device2) Go to the Play Store and install Amplify from the Play Store web interface.For some reason this tends to link the accounts more reliably than installing from the Play Store on the device.There are a few reasons this happens. It's always because Google reports that In App Billing isn't available for your device. Here are the causes I've seen:Lucky Patcher makes permanent changes to your system. Simply uninstalling it doesn't work. Here's something to try, courtesy of @ mikeezy187 - Uninstall lucky patcher- Go into settings- Go to apps- Go to Google Play Store- Clear Cache and app data- Uninstall Google Play Store updates and it will ask you if you want to restore Google Play Store to its stock settings- Click Yes- RebootIf you're positive that Xposed is running properly, and that Amplify is checked in the Modules list, and you've done a soft reboot:When it gets stuck, swipe from the left side of the screen, choose Settings, then push the back button to bypass these checks.Cool. Thanks for helping out! Please go file the issue here, on GitHub . You can also upvote bugs and feature requests there.That would be AWESOME. Please check here to get started 1) If Google Location Services are turned on, it sets an alarm to wakeup every 60 seconds, check the network location, and broadcast ALARM_WAKEUP_LOCATOR.2) Everytime ALARM_WAKEUP_LOCATOR fires, Google Search receives the broadcast and grabs an NlpWakeLock and NlpCollectorWakeLock.3) Those wakelocks hold the keep the device on for 5-15 seconds. This means that the device is actually awake for about 15 seconds per minute, or 25% of the time!It depends on the alarm. The defaults are well tested and don't have negative impacts. They just save battery life. If you start blocking unknown alarms and wakelocks, it may stop things from working. You can always disable the module at boot to fix things. The latest knowledge base was created by @ 1ceb0x and is being maintained by the community. I regularly include their findings in Amplify. You can find the knowledge base here: https://docs.google.com/spreadsheets...gid=2072742181 To disable Xposed during boot, you have to repeatedly tap one of the hardware buttons (Power, Volume, or Home) on your device during startup. During boot, your device will vibrate twice when it detects the first key press. You'll then have five seconds to press that same button four more times, with each keystroke producing a short single vibration. After ending with a long vibration, your device will disable and prevent most of Xposed's actions, allowing you to go back to Amplify settings and fix what you broke.Check out this awesome intro video by Shiwak that explains the basics of how Amplify works.Short version: Those aren't really wakelocks. You can ignore them. Please go check in WakeLock Detector , and you'll see that they don't show up there.Long version: Admittedly, I don't know *exactly* why they're showing up in BBS, but not in Wakelock Detector. I did a ton of testing today and can confirm that my device showed 988 NlpWakeLocks in BBS, but only 20 in WLD. During that time, I also had logcat running and a custom hook in the Android stats code. Logcat didn't show any of those phantom wakelocks, the Android stats code doesn't record them, Amplify doesn't see them, and WLD doesn't see them. BBS is [awesomely] open source, so I went digging a bit. I don't see anything obviously wrong in the code, but for some reason it's getting the counts wrong. Here's the interesting piece: It's getting the TIME SPENT in the wakelocks correct. That's why you see something absurd like 2000 wakelocks and only 6 seconds of lock time. If it were really that many wakelocks, your lock time would be much, much higher.It's here: https://github.com/rsteckler/unbounce-android A couple of things:1) Don't judge. I need to do some cleanup, but wanted to post the repo early so people can take a look at what it does.2) Pull requests are welcome.The band will not perform unless there is a bowl of M&Ms backstage, with all of the brown ones removed.It's here: https://github.com/rsteckler/unbounc...commits/master There is no "best" for everyone because every device is different. Check out this helpful thread from @ Celestial Fury for a guide that walks you through an awesome baseline, and gives you advice on how to tune further.An alarm wakes your device from deep sleep, scheduled using the RTC (Real Time Clock). For example, Google Play Services schedules an alarm every 60 seconds to wake up the device with the ALARM_WAKEUP_LOCATOR alarm. That's why I didn't try to stop the wakelocks at first, but instead tried to stop the alarms. I don't even want the device to wakeup in the first place!Once the alarm fires, the Nlp service wants to get your location and send it back to google. This requires keeping the device awake for a few (5-15) seconds. To keep the device awake, Google Play Services grabs the NlpWakeLock. This is the second point we can modify the system, but it only puts the device back to sleep once it's already awake.A couple of other things: This is why I recommend starting with just the alarms. It's less intrusive, and stops the device from waking up at all. Most people will probably be fine with the settings 240, 240, 0, 0. There are other things that can cause an NlpWakeLock, though, including third party apps. If the alarms don't work by themselves for you, you can also slow down the frequency of the wakelocks directly in the settings.Nope. Never have been, and never will be.When you launch the UI, I use Google Analytics to collect some information about your device. Specifically, the version of Amplify that you're using, the type of device you have, what country you're in, the version of Android you're using, etc. I use this information to make the app better. For example, it tells me how many people have the app installed in each country. This helps me know which language translations will be the most helpful. It also helps me know which versions of the app people will be upgrading from so I can make those transitions smooth. In my Google Analytics account, I have the options to share your data with Google and Third parties turned off. You can also read Google's Privacy Policy if you want to know how they use the data.Nope. Never.The data collected for Google Analytics is only used to make the app better. I don't do anything else with it and no third parties get access to it.I don't think there's a way to verify that. You just have to trust me. If that makes you nervous, I encourage you to build the GitHub code yourself.Sadly, no. The Google Play Store Terms of Service require that I use the Google Play Store IAP system to collect donations. I also don't plan on distributing non-Google IAP versions outside of the Play Store because of the effort involved. I'd rather spend my time making Amplify better, instead of maintaining two copies of the code and writing a new donation system. Sorry if you're one of the people affected by that.Thanks, and let me know if it works for you!Ryan