~ MamakTalk ~: Google Wants To Do Something About OEMs Killing Background Apps

2021年6月14日星期一

Google Wants To Do Something About OEMs Killing Background Apps

Stock Android, as we see in Google’s Pixel lineup, has a lot going for it but most smartphone manufacturers prefer to offer their own features and design tweaks on top of it. While that’s not necessarily a bad thing, OEMs often make aggressive changes to some out-the-box Android features that ruin the user experience. For example, many companies go the extra mile to implement additional power-saving measures for the sake of extended battery life. However, it comes at the cost of apps being killed unexpectedly in the background.

To that end, Google is now seeking feedback from app developers on how custom Android skins are interfering with their apps. The company wants to know which OEM device is preventing apps from functioning properly in the background, which Android version are the issues most prevalent in, whether the issues can be reproduced on devices from other manufacturers, and several other details from third-party app developers.

It’s unclear what Google will do with this data. Perhaps it wants to take decisive action on these shoddy practices of OEMs. Nonetheless, if you’re an Android app developer and have faced the wrath of customers because of your apps not working properly in the background, you could provide the company with some valuable insights on this issue (link to the feedback form below).

Google is seeking developer feedback on how OEMs are killing background apps

Android has fairly capable power-saving features. Over the past few years, Google has made tons of optimizations that have improved the platform’s handling of background apps. It has also introduced new features that help allocate system resources to apps adequately so they run smoothly in the background. However, the unexpected killing of background apps is still one of the most common problems that Android users encounter.

But, to be fair, Google isn’t to blame here. The tweaks made by other smartphone OEMs are causing the issues. In particular, additional power-saving measures the companies implement in their custom Android skins are restricting the background activity of apps. As we saw in a report earlier this year, Stock Android is the best at handling background apps. On the other hand, Samsung’s One UI is the worst offender. OnePlus’ OxygenOS, as well as custom Android skins offered by many other OEMs, were also found killing background apps aggressively.

Moreover, some OEMs reportedly allow apps like Facebook and WhatsApp to run unrestricted while restricting the background activity of other smaller apps. This often prevents apps from functioning properly. And it’s developers who have to hear about it, though they can’t really do anything about it. Thankfully, Google is now coming to their rescue.

Google finally seems to be taking this issue seriously

This issue exists for years. Over the years, hundreds of developers have written to Google complaining about OEMs aggressively killing apps in the background. Some OEMs have even been accused of abusing the core functionality of Android, completely preventing third-party apps from running in the background. Most recently, a user complained that companies like Xiaomi and OnePlus are killing AccessibilityService.

While Google hasn’t done anything about this issue yet, it finally seems to be getting a bit serious about it. The company recently said that it would look into the matter. It is now gathering feedback from more developers on how OEM Android skins are interfering with their apps. If you’re an affected Android app developer, you can submit your feedback by filling this Google Docs form.

The post Google Wants To Do Something About OEMs Killing Background Apps appeared first on Android Headlines.