Android will say goodbye to one of its endemic evils: aggressive background app restrictions

One of the most persistent issues when using certain caped Androids is background app restriction. The system understands that an app is consuming more resources than it should (even if it is necessary to do so, for example, to receive notifications), and closes it without notifying the user.

With Android 13, manufacturers will have a harder time applying these “battery optimizations”. In the CDD (Compatibility Definition Document) of this version, the document that establishes the bases of how Android manufacturers must implement to have access to the Google servicesit is detailed the end of such restrictions.

If you want to restrict apps, you must notify the user

It makes sense that if an app demands a lot of resources, the customization layer restricts some of its functions to save power. The problem is that these restrictions, in some layers, were indiscriminateand they could leave us without notifications (something common in Asian layers).

The other big problem is that there was no way to control these automatic optimizationssomething that is about to change with upcoming updates to Android 13 and all the customization layers that are based on this version.

With Android 13 there are new requirements for app restriction levels. The system will have to report that an app is optimized, so the user will know if there are going to be changes or not. Similarly, the layer itself you will need to create a publicly accessible documentexplaining whether or not restrictions apply, how they apply if they do, and how an app can bypass them.

In addition, the user you will have access to a list of restricted applications, to disable this feature in case you don’t want layered apps. A big change that will be applied as devices are updated to Android 12.

Via | AndroidPolice