![\"\"](\"https:\/\/icrowdnewswire.com\/wp-content\/uploads\/2020\/06\/4001-logo.png\"){kind=logo}
<\/p>\n<\/p>\n
![\"Android](\"https:\/\/cdn57.androidauthority.net\/wp-content\/uploads\/2020\/06\/Android-11-logo-stock-photo-on-smartphone-16-1200x675.jpg\"){kind=logo}
<\/p>\n
<\/p>\n
Some Android<\/a> OEMs have a nasty habit of killing apps in the background in a bid to reclaim RAM, reign in rogue apps, or save device battery. But this process is more annoying than useful if those apps provide beneficial services to users. More, it makes lives hard for developers whose apps are affected.<\/p>\n During a Reddit AMA<\/a>, the Android engineering team revealed that Android 11<\/a> will introduce notifications to users when the OS culls an app. Users will also get a chance to override the OS’s decision. It’s possible that this system could mirror how Android 10 permission<\/a> alerts are issued on a per-app basis.<\/p>\n The team is also set to improve app developers’ lives. A new crash diagnostics API will provide more details surrounding app culls. This introduction will allow developers to better understand why some OEMs treat their apps as rogue or misbehaving.<\/p>\n See also<\/strong>: Here’s a list of Android 11 beta phones<\/a> | Android 11 release date<\/a><\/p>\n The engineering team will also forbid the use of whitelists that determine which top apps can run in the background. The team believes the move will introduce a level playing field for app developers. Right now, OEMs whitelist big apps like WhatsApp, making them immune from background killing, which is not fair to smaller developers.<\/p>\n While the engineering team does admit there’s a problem with app management on Android, it does see its necessity especially for controlling rogue apps. To that end, Android 11 will also introduce “extra measures to prevent abusive behavior by misbehaving apps,” though it’s not clear what this means.<\/p>\n The refreshed requirements don’t solve the issues but will go a long way to give developers and users a little more control over their apps and devices. It may also force OEMs to be more transparent about their practices too. Nokia<\/a>, OnePlus<\/a>, Xiaomi<\/a>, and Huawei<\/a> are among the worst offenders, according to DontKillMyApp<\/a>, a website that ranks OEMs based on aggressively they kill background apps.<\/p>\n Tags:<\/b> Andy Walker<\/p>\n<\/p><\/div>\n","protected":false},"excerpt":{"rendered":"See Campaign: <\/strong>https:\/\/www.androidauthority.com\/android-10-update-1023882\/<\/a>
Contact Information:<\/b>
Andy Walker<\/p>\n
<\/a>, Wire<\/a>, United States<\/a>, English<\/a><\/p>\n<\/div>\n
\nContact Information:<\/h3>\n
Google will introduce new requirements to limit Android manufacturers’ power over background apps. The new rules aim to address some OEMs’ aggressive management of useful background apps and services. Some Android OEMs have a nasty habit of killing apps in the background in a bid to reclaim RAM, reign in rogue apps, or save device battery. … Continue reading Here’s how Google plans to fight OEMs killing apps in the background<\/span><\/a> Continue Reading