OEM background killers
Many Android makers add extra killers that stop apps beyond what Google's rules allow.
In one line
Can't count on running in the background on some Android phones, since brands add extra killers
Many Android makers add extra killers that stop apps beyond what Google's rules allow.
Explains why push and alarms fail on some phones: aggressive task killers, autostart lists and battery managers. Developers ask users to whitelist; no API can force it.
What it can and can't do
What the user does: Nothing. The phone's maker stops the app on its own after you leave it
It can
- Run normally while you have the app open
- Ask you to switch on autostart or remove battery limits in the phone's own settings
- Keep working in the background if you turn off the maker's limits for it
It cannot
- Check from inside the app whether the maker's killer is on; there is no common way
- Turn off the maker's battery limits by itself
- Behave the same on every Android phone; each brand differs
- Face this on iPhone, which has one background rule for everyone
How it differs between platforms: Many Android brands stop apps beyond Google's rules. iPhone has a single consistent background policy.
On Android and iPhone
| Android | iPhone | |
|---|---|---|
| Status | Not supported | Not supported |
| First version | Android 6.0 (API 23) | Not available |
| Permission or entitlement | REQUEST_IGNORE_BATTERY_OPTIMIZATIONS (Play-restricted) | Not listed |
| Protection level | normal | none |
| How access is granted | not-exposed | not-exposed |
| What the user sees | Vendor specific settings: autostart, protected apps, battery manager | Not listed |
| How long it lasts | Until the user changes it | Not listed |
| How to take it back | Vendor settings app | Not listed |
| Store policy | Play: battery opt-out prompts limited | None listed |
| API | dontkillmyapp.com lists vendors (Xiaomi, Huawei, Oppo, Vivo, Samsung and others) | Not listed |
| Notes | Behavior varies by vendor; no portable detection | iOS has one consistent background policy; no OEM variation |
Data you get
What comes back: Vendor behavior
Shape: none
How often: n/a
No individual data fields. The signal is the access itself.
Technical limits
- No API; vendor specific
- Google CTS does not cover vendor killers
The story
What it is
Some Android phone makers add extra app killers that stop apps beyond Google's rules.
For you
You may miss alarms, chat alerts or fitness tracking on some brands, even with every setting on. You may be told to dig through battery menus and allow the app to autostart.
For makers
Makers lose reliable alerts and reminders on these phones and cannot detect or fix it with code. They write help pages and in app guides that ask people to whitelist the app.
Where you see it
| Type | Example | Apps |
|---|---|---|
| messaging | A chat app on some phones stops delivering message alerts after the screen is off, so the app shows a guide to turn off the battery manager. | WhatsApp, Telegram |
| health | A medication reminder app fails to ring at night because the phone maker killed it, so it asks to be put on a protected list. | None named |
| fitness | A run tracker on certain phones stops recording mid run, so the app links to a help page for that brand. | Strava |
| smart-home | A security camera app misses a motion alert because the phone maker shut the app down. | None named |
| games | A game that sends a timer alert for a finished build gets silenced, so players miss the reminder. | None named |
| developer | Developers check a public list of phone brands to see which ones kill apps and adjust their guide. | Don't kill my app |
Risks
- Missed alerts and alarms
- Hard for apps to detect or fix
Android and iPhone in short
- Android: This is Android only. It depends on the phone brand and has no standard way to check.
- iPhone: iOS has one background policy for every iPhone, so this problem does not exist.
Good uses and abuse
Legitimate uses
- Reliable reminders
Known abuse
- None
Scores
| Score | Value | Meaning |
|---|---|---|
| Sensitivity | 1 of 5 | How revealing the data is |
| Utility | 3 of 5 | How useful it is to honest apps |
| Friction | 0 of 5 | How much the user has to do |
| Fingerprint bits | Not rated | Rough identifying entropy, when known |
History
- 2015-10, Android 6.0 (API 23): Doze gave vendors a template; vendor killers grew after
Related capabilities
Related
- Restricted bucket and battery restriction settings. Can only run in the background as much as your battery setting allows
- Doze and idle mode. Can't force the phone to stay awake; Doze delays jobs, alarms and network
Sources
How well checked: Based on official documentation.