Brevent, black prevent, can app-standby (since Android 6.0, not supported on some devices) or force-stop apps without Root, prevent apps from running in long time.
Brevent never brevent apps not in Bervent list. If apps are launched then quit (tapping Back or so), Brevent will app-standby them; if apps timed out in standby, or swiped from recents screen, Brevent will force-stop them. Whenever apps are waken without activity, Brevent will force-stop them.
Apps in Brevent list can be set “allow sync” to receive notifications or do sync jobs. Brevent won’t standby “allow sync” apps, and Brevent won’t force-stop “allow sync” apps with notifications or running in background.
Brevent supports Android 5.0 to 8.1, requires “USB debugging” in “developer options”.
Since Android 8, Brevent won’t work if debugging is off or USB option is changed. If debugging turns off when you unplug the cable, please change USB option. Normally, it’s OK to keep USB option as default.
- fix process count
- add show os apps (for normal users)
- optimize and remove option "check notification"
- dynamic enalbe and disable disabled-gms
- add option "dynamic disable" (experimental)
Don't turn off USB Debugging or change USB options on Android 8+.
Be careful to brevent system apps, core apps or frequently-used apps.
Have the APK file for an alpha, beta, or staged rollout update? Just drop it below, fill in any details you know, and we'll do the rest!
Note: We’ll decline all APKs with ‘debug’ certificate, which are not safe.
Official records from AKPFlow and Google Play confirm that the developer used a trusted and verified digital signature. The downloadable file is original and it has not been modified in any way.
Why using SHA1 to check the identification of certificate is safe?
That’s a cryptography problem. Please refer to the following authoritative information to check the reason.
How do we make sure the updated Apps are real and created by the respective developers?
1. All AKPFlow.com apps are verified prior to publishing.
2. We make sure that the cryptographic signatures for new versions of all previously published apps match the original ones, which means we know if the new version APKs were signed by the real devs or someone pretending to be them.
3. For new apps that have never been published on AKPFlow.com, we try to match the signatures to other existing apps by the same developer. If there’s a match, it means that the same key was used to sign a previously known legitimate app, therefore validating the new upload. If we’re unable to verify the legitimacy of a new APK, we will simply not publish it on AKPFlow.com.