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

With Android 13, manufacturers will have a hard time implementing these “battery optimizations”. The CDD (Compatibility Description Document) for this release details the document that lays the foundations for how Android manufacturers should implement it to access Google Services. end of such restrictions.

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

If an application is very resource-intensive, it makes sense for the customization layer to restrict some of its functions to save power. The problem is these constraints were haphazard in some layersand they may leave us without notice (something common in Asian strata).

The other big problem is there was no way to check for these automatic optimizationsThat’s about to change with the upcoming updates to Android 13 and all the customization layers based on that version.

Current levels in app restrictions.

With Android 13, there are new requirements for app restriction levels. system will have to report that an app is optimized, so the user will know if there will be changes. Similarly, the layer itself you will need to create a document that anyone can accessexplains whether restrictions apply, how to apply if any, and how an application can bypass them.

Also, the user you will be able to access the restricted apps list, to disable this feature if you don’t want layered apps. A big change that will be implemented when devices are updated to Android 12.

via | AndroidPolice