Android P will put on restriction any app that sucks up too much battery. Let’s see how.
How Background Restrictions work
The simplicity of Background Restrictions is what makes it beautiful.
“If an app exhibits some of the bad behaviors described in Android vitals, the system prompts the user to restrict that app’s access to system resources. This is a new feature for Android P.”
Google initiative, Android vitals, has the aim to improve the stability and performance of Android phones. Even though this is not an easy task, when Android phones are tested it does not happen with any apps on them so they can’t know what specific application can do to the battery of a Pixel, ThinQ, or Galaxy phone.
What restrictions are placed on a “naughty” app?
These restrictions are decided by the developers of the software that your phone uses. Every model of phone has different limits from the others because Android runs on different hardware and no hardware is the same. For example, an entry-level phone and handle way less load than a Galaxy S9+. The only individual who knows what is too much to ask from a phone or what it can control is the company that produces it.
On Pixel and Pixel 2, Google uses a stock AOSP as a baseline which is built for phones that can run them officially. When the restricted apps are not actively being used for a certain goal, this is what they can’t do:
- It can’t run any job. That is a single unit of work that an app, part of the OS (which run things on schedule) or you assign to the operating system.
- It can’t fire any alarms. That is an event or alert that is sent from the app used to the operating system. It differs depending on the type of notification seen.
- It can’t use any network. Even if it is 3G, Wi-Fi or LTE, none of them can be used.