Diversity is Android’s greatest virtue and flaw. There are not only significant differences in the version of the operating system, but also in the layers of customization. Google wants to improve detection of issues with apps in personalization layers, and do the aggressive battery restrictions of any of these layers affect application performance.
From today, developers have a new way to report issues in apps, indicating in which layer of personalization this happened and, oddly enough, they are asked to try and reproduce the problem on a Google Pixel.
If there is a defect in a layer and not in a pixel, the layer may be the culprit.
Google has opened a new questionnaire in which it invites developers to report bugs in applications. The funny thing about the news is that finally Google is focusing on the battery restrictions of the personalization layers, a historical problem that Android has been dragging along for a long time.
There are many layers of customization that, by saving battery, end up preventing apps from working.
Some time ago we told you about Dont Kill My App, a reference to classify manufacturers doing the worst by shutting down background apps. Among them, Samsung, Xiaomi or OnePlus. Many of these manufacturers program restrictions so that apps don’t consume as much battery in the background, but that ends up causing issues with operation.
As we read in XDA Developers, Google is starting to investigate which apps are causing issues in certain layers and is asking developers to try and reproduce these errors on a Google Pixel. If an app fails in MIUI, EMUI, etc., but not in a Pixel, something is wrong with the layers.
