Foreground service timeouts (Android 15)
Some foreground services now stop after 6 hours in 24, and can only restart after a user returns to the app.
In one line
Can keep some Android services running, but only about 6 hours in 24
Some foreground services now stop after 6 hours in 24, and can only restart after a user returns to the app.
A hard cap on long background syncs and media processing. It limits always-running services; Android 17 adds memory and audio limits on top.
What it can and can't do
What the user does: Nothing. It happens when an app runs a long sync or media job in the background
It can
- Keep a long sync or media job going for several hours at a stretch
- Restart a stopped service once you open the app again
- Use a short service for quick tasks, which gets about 3 minutes
It cannot
- Run a data sync service past the daily limit without you opening the app
- Keep working after the system calls time out; the app gets only a few seconds to stop
- Do this on iPhone, which has no foreground services and suspends apps as soon as work ends
How it differs between platforms: Android 15 caps some long services. iPhone has no such service type and simply suspends apps when work ends.
On Android and iPhone
| Android | iPhone | |
|---|---|---|
| Status | Supported | Not supported |
| First version | Android 15 (API 35) | Not available |
| Permission or entitlement | Not listed | Not listed |
| Protection level | none | none |
| How access is granted | none | not-exposed |
| What the user sees | None | Not listed |
| How long it lasts | dataSync and mediaProcessing get 6 hours total per 24 h; timer resets when the app is brought to the foreground | Not listed |
| How to take it back | n/a | Not listed |
| Store policy | None listed | None listed |
| API | Service.onTimeout(int, int); startForeground throws ForegroundServiceStartNotAllowedException when exhausted | Not listed |
| Notes | Service gets a few seconds after onTimeout to call stopSelf() or a RemoteServiceException is thrown; shortService limit about 3 min | iOS has no foreground service; background modes have no fixed daily cap but suspension is immediate once work ends |
Data you get
What comes back: Time budget
Shape: integer
How often: Per 24 h
| Field | Type | Unit | Range | Precision |
|---|---|---|---|---|
dataSync | integer | hours | 6 | Not listed |
mediaProcessing | integer | hours | 6 | tracked separately |
shortService | integer | minutes | about 3 | approx |
Technical limits
- Applies to apps targeting 35 and above
- Timer resets on foreground
The story
What it is
Android now stops some always-running background tasks after about 6 hours in a day.
For you
You never see it work. Your phone just stops apps from quietly running heavy tasks for hours, so your battery lasts longer. If an app was syncing a huge backup, it may pause until you open it again.
For makers
Makers must design long jobs to finish, save progress and resume. It forces them to move big uploads and media work to smarter tools instead of one endless service.
Where you see it
| Type | Example | Apps |
|---|---|---|
| media | A video editor exporting a long 4K clip keeps going in the background, then must pause and resume if the export runs past the daily limit. | CapCut, Google Photos |
| fitness | A running tracker that keeps a data sync service alive all day must now finish cleanly and restart when you next open it. | Strava |
| games | A big game download or patch in the background gets paused near the limit and resumes when you return to the game. | Genshin Impact |
| productivity | A cloud drive uploading thousands of photos overnight switches to scheduled jobs so it is not killed by the timeout. | Google Drive, Dropbox |
| health | A health app that copies sensor data from a watch all day has to batch the data instead of running nonstop. | None named |
| enterprise | A delivery company app that polled for new orders in the background now relies on push messages instead. | None named |
Risks
- Background jobs can stop mid task
- Sync may lag until you reopen the app
Android and iPhone in short
- Android: Applies from Android 15. The app gets a few seconds to wrap up when the timer fires, or it crashes.
- iPhone: iOS has no equivalent. Apps are simply put to sleep soon after their work ends.
What the platform says
- Google: Foreground service timeouts. Android 15 puts a time limit on certain long-running background services so apps cannot drain the battery all day.
Good uses and abuse
Legitimate uses
- Limiting battery drain
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
- 2024-10, Android 15 (API 35): 6 hour per 24 h timeout for dataSync and mediaProcessing (targetSdk 35)
Related capabilities
Related
- Foreground service types (Android 14). Can run long Android background tasks, but only for a declared purpose with a notification
- Expedited and user-initiated long jobs. Can run jobs soon or for a long time after you tap something, with daily limits
Sources
How well checked: Checked against real behavior.