Background start restrictions
Apps in the background cannot freely start foreground services or open screens.
In one line
Can't freely start work or open screens from the background
Apps in the background cannot freely start foreground services or open screens.
Stops hidden activity from popping up or starting long tasks while the person is elsewhere. iOS goes further: apps can only launch for a few triggers, like location or push.
What it can and can't do
What the user does: Nothing. It happens when an app tries to start a service or screen while hidden
It can
- Start a foreground service from the background only in listed exemptions on Android 12 and newer
- Open a screen from the background with a special display permission or a notification tap
- Wake on events on iPhone, such as push or location
It cannot
- Start foreground services from the background at will on Android 12 and newer
- Pop up screens over other apps with no exemption
- Run on iPhone with an equivalent start call; it has none
- Skip tighter rules in Android 17
How it differs between platforms: Android 12 blocks background starts and Android 17 tightens it. iPhone has no start call, only event wake ups.
On Android and iPhone
| Android | iPhone | |
|---|---|---|
| Status | Supported | Partial |
| First version | Android 8.0 (API 26) | iOS 4.0 |
| Permission or entitlement | SYSTEM_ALERT_WINDOW (special exemption) | Not listed |
| Protection level | normal | none |
| How access is granted | none | none |
| What the user sees | None | None |
| How long it lasts | Exemptions: visible activity, high priority FCM message, exact alarm, active notification interaction, device owner | iOS wakes apps only for specific events (push, location, BLE, geofence, background tasks) |
| How to take it back | n/a | Force quit stops all |
| Store policy | None listed | None listed |
| API | ForegroundServiceStartNotAllowedException (API 31), BAL via PendingIntent | Background modes |
| Notes | Android 12 blocks FGS starts from background except listed exemptions; Android 17 hardens IntentSender BAL | iOS has no equivalent start API; wake only on events |
Data you get
What comes back: Allowed triggers
Shape: list
How often: Static
| Field | Type | Unit | Range | Precision |
|---|---|---|---|---|
android_exemptions | list | None | FCM high, exact alarm, visible activity | Not listed |
Technical limits
- Exemptions are narrow and change by version
The story
What it is
The phone stops apps in the background from suddenly starting visible services or opening screens.
For you
You notice it as fewer pop ups and less hidden work. An app you are not using cannot suddenly open a screen over your game or start a long task. That keeps the phone calm.
For makers
Makers must start long work from a screen you are using or a clear event, like a tap or a push. Some tricks to start hidden work are blocked. Allowed exceptions are small and listed.
Where you see it
| Type | Example | Apps |
|---|---|---|
| games | A game cannot throw an ad screen over your video call from the background. | None named |
| messaging | A chat app starts a call screen only through a high priority message you trigger. | |
| maps | A navigation app starts when you tap Start, not from the background. | Google Maps |
| fitness | A workout app starts tracking after a tap or an approved trigger. | None named |
| security | A bad app tried to pop up fake login screens from the background, which the rules stop. | None named |
| rideshare | A driver app uses an allowed exemption while you are on a trip. | Uber Driver |
Risks
- Exemptions misused
- Features may break
Android and iPhone in short
- Android: Android limits when background apps can start foreground services and open screens, with a list of exceptions.
- iPhone: iPhone goes further and lets apps wake only for a few triggers, like location or push.
What the platform says
- Google: Background start restrictions. Android limits when apps in the background can start foreground services, to stop surprise activity.
Good uses and abuse
Legitimate uses
- Preventing nuisance
Known abuse
- Using exemptions for covert wakeups
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
- 2017-08, Android 8.0 (API 26): Background execution limits, no background services
- 2021-10, Android 12 (API 31): FGS start from background blocked except exemptions
- 2026-06, Android 17 (API 37): Background activity launch hardened for IntentSender
Related capabilities
Related
- Foreground service types (Android 14). Can run long Android background tasks, but only for a declared purpose with a notification
- Alarms and reminders. Can set alarms at an exact time on Android, if you allow Alarms and reminders
Same idea on the web
- Service worker lifetime. Can keep a background helper script for a site that stays after you close the tab
Sources
How well checked: Based on official documentation.