Skip to Content
Platform.Ontology

OEM background killers

Many Android makers add extra killers that stop apps beyond what Google's rules allow.

Blocked for appsNotifications and backgroundPlatform quirksAndroid and iPhoneIn the background

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

AndroidiPhone
StatusNot supportedNot supported
First versionAndroid 6.0 (API 23)Not available
Permission or entitlementREQUEST_IGNORE_BATTERY_OPTIMIZATIONS (Play-restricted)Not listed
Protection levelnormalnone
How access is grantednot-exposednot-exposed
What the user seesVendor specific settings: autostart, protected apps, battery managerNot listed
How long it lastsUntil the user changes itNot listed
How to take it backVendor settings appNot listed
Store policyPlay: battery opt-out prompts limitedNone listed
APIdontkillmyapp.com lists vendors (Xiaomi, Huawei, Oppo, Vivo, Samsung and others)Not listed
NotesBehavior varies by vendor; no portable detectioniOS 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

TypeExampleApps
messagingA 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
healthA 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
fitnessA run tracker on certain phones stops recording mid run, so the app links to a help page for that brand.Strava
smart-homeA security camera app misses a motion alert because the phone maker shut the app down.None named
gamesA game that sends a timer alert for a finished build gets silenced, so players miss the reminder.None named
developerDevelopers 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

ScoreValueMeaning
Sensitivity1 of 5How revealing the data is
Utility3 of 5How useful it is to honest apps
Friction0 of 5How much the user has to do
Fingerprint bitsNot ratedRough identifying entropy, when known

History

  • 2015-10, Android 6.0 (API 23): Doze gave vendors a template; vendor killers grew after

Sources

How well checked: Based on official documentation.

On this page