The smartphones of some Android OEM manufacturers frequently kill background applications, and may even violate Google’s policy. Google now wants to know who these OEMs are. kill background applications, and may even violate Google’s policy. Google now wants to know who these OEMs are.
Most Android apps may not always need to run in the background, but there is also a class of apps that do. For example, some health-centric applications may need to run all the time, but the system may not always let these applications run.
Of course, the application that has been running in the background is not without cost, which generally affects battery life. This is why platforms including Android have set rules and restrictions on which applications can always run in the background.
Google has also established rules for OEMs to make it transparent about the apps that are killed in the background. However, some OEM manufacturers implement their own anti-backend policies based on the Android system, but they usually do not let developers or users know this.
Simply put, some applications, such as sleep monitoring and exercise tracking applications, can work normally on one brand of mobile phone, but may not work properly on another brand, because the latter will frequently kill applications running in the background.
Some OEM manufacturers also set up a whitelist to allow apps like Facebook and WhatsApp to run without restrictions, putting small app developers at a disadvantage. Google is very aware of these inferior practices, although it has not taken decisive action, it is now inviting developers to provide feedback to find possible solutions.
As early as 2018, the AOSP bug tracker created a problem that explained in detail how some Chinese OEMs abused Android’s core features to prohibit third-party applications from running in the background. This question is full of responses from hundreds of application developers, echoing similar experiences, urging Google to prevent OEMs from violating Android system compliance and implementing such a radical back-office policy.
On June 8, a user commented that OEM manufacturers such as Xiaomi and OnePlus even killed AccessibilityService. In response, a Google employee recently commented that they will research this issue and invite application developers to submit their feedback.
Google requires developers to provide the following details:
- The name of the affected application
- The name of the OEM and device model they observed the problem
- Android operating system version
- Steps to reproduce the problem, as well as expected and observed results
- Affected API
- Can they reproduce the same problem on Pixel devices (or other devices running the same Android version)?
Considering that this situation has been going on for many years, this investigation is really long overdue. As they said, it’s better to be late than never.
If you like our news and you want to see such news even further, then follow RealMi Central on Google News, Telegram (RealMi Central, Xiaomi, Apple, Realme, Samsung, Microsoft, OnePlus, Huawei/Honor, Android 12), Twitter, Facebook (Page) (Group) & Instagram.