Here at NearIT we constantly pay attention to UX, user permission requests and app background functionality. Mobile users can experience some issues caused by aggressive power management and app blocking policies imposed by smartphone vendors. Inspired by dontkillmyapp.com, we want to provide an Android library that checks and handles those strange scenarios by asking the user to whitelist or protect an app.

implementation 'it.near.sdk:pokeflute:prealpha-1'

If you are experiencing any issue with resource merging or support-library compatibility, try clean/build project or:

implementation('it.near.sdk:pokeflute:prealpha-1') {
    exclude group: 'com.android.support'
}

We provide these useful methods:

boolean potentiallyBlocked = Utils.isAppPotentiallyBlockedByManufacturer();

returns true if the manufacturer is known for using a non-standard background policy.

boolean appBlockerFound = Utils.checkForAppBlockersExplicitly(context);

returns true if one of the (in)famous app killer is installed on the device.

Once you found out that your app could be blocked, you can start our all-in-one activity that will handle many scenarios (including many vendors and os versions).

startActivity(SolutionActivity.createIntent(this));

• Missing Oppo instructions.
• Missing Vivo instructions.
• Lenovo P2 (and similar) not handled.
• Can't be aware of canDrawOverlay() on Oreo (8.0.0) devices (known Android bug https://issuetracker.google.com/issues?q=Settings.canDrawOverlays).
• English only localization
• Not sure about solution for OnePlus with Android version < P.

• Investigate and handle cleaner apps such as Clean Master or Security Manager.

This is not production-ready and we are still discussing a universal UX solution. Currently, we appreciate anyone testing the solution on various smartphones to increase the supported phones list. In the PR, please include screenshots or video of the testing results.