Skip to Content
Platform.Ontology

Foreground service types (Android 14)

Every foreground service must declare a purpose and hold the matching permission.

Works without askingNotifications and backgroundAndroid background limitsAndroid and iPhoneIn the backgroundWhile you use it

In one line

Can run long Android background tasks, but only for a declared purpose with a notification

Every foreground service must declare a purpose and hold the matching permission.

Forces apps to state why they keep running (location, camera, media, phone call). The type decides which hardware and permissions the service can use, so it shows purpose to reviewers.

What it can and can't do

What the user does: You start something long, like playing music, tracking a run, or syncing a big file

It can

  • Keep playing audio, tracking location or syncing data while the screen is off
  • Show you a notification that says the work is running
  • Use the camera, microphone or location in the background, but only after you allowed each one

It cannot

  • Start a background service from nowhere without a notification
  • Use the microphone, camera or location without their own permission
  • Pick any purpose it likes; Android 14 makes each service declare one type and checks it
  • Match this on iPhone, where background modes need an Apple approved setting instead

How it differs between platforms: Android uses service types with a visible notification. iPhone uses background modes set up in Xcode.

On Android and iPhone

AndroidiPhone
StatusSupportedPartial
First versionAndroid 14 (API 34)iOS 4.0
Permission or entitlementFOREGROUND_SERVICE_<TYPE> permissions such as _LOCATION, _CAMERA, _MICROPHONE, _DATA_SYNC, _MEDIA_PLAYBACK, _CONNECTED_DEVICE, _PHONE_CALL, _SPECIAL_USEUIBackgroundModes
Protection levelnormalentitlement
How access is grantedinstallentitlement
What the user seesNotification required; microphone, camera, location need their own runtime grant while in useNone
How long it lastsWhile the service runsPer mode; app suspended when work ends
How to take it backTask managerRemove capability
Store policyPlay: FGS type declaration form for apps targeting 34App Review 2.5.4
APIandroid:foregroundServiceType, startForeground(id, notification, type)UIBackgroundModes: audio, location, voip, bluetooth-central, bluetooth-peripheral, fetch, remote-notification, processing, external-accessory, nearby-interaction
NotesTypes: camera, connectedDevice, dataSync, health, location, mediaPlayback, mediaProjection, microphone, phoneCall, remoteMessaging, shortService, specialUse, systemExempted; mediaProcessing added in 15See mob.bg.ios-modes

Data you get

What comes back: Service type
Shape: enum
How often: Per service

FieldTypeUnitRangePrecision
typeenumNoneabout 14 typesNot listed

Technical limits

  • Type must match actual use
  • Play review for sensitive types

The story

What it is

Android makes every always-running app task state its purpose, like navigation or music.

For you

You see this as a persistent notification, such as a music player or a navigation arrow. It tells you an app is allowed to keep working while you do something else.

For makers

Makers must pick the right label and get the matching permission. Google and reviewers use the label to check an app is not hiding battery heavy work behind a vague reason.

Where you see it

TypeExampleApps
mapsA navigation app keeps turn by turn guidance running with the screen off using the location type.Google Maps, Waze
musicA streaming app keeps playing with the phone locked using the media playback type.Spotify, YouTube Music
rideshareA driver app keeps sharing live position during a trip while you check messages in another app.Uber, Lyft
fitnessA cycling app records your route and heart rate through the whole ride using location and health types.Strava, Komoot
messagingA calling app keeps your microphone live during a voice call after you leave the app.WhatsApp, Signal
gamesA cloud gaming or remote play app keeps its stream alive while you answer a text.Xbox Cloud Gaming

Risks

  • Apps can misuse loose labels like special use
  • Always-on notification can be ignored

Android and iPhone in short

  • Android: Required from Android 14. Each type needs its own permission, and camera, mic and location still need your tap.
  • iPhone: iOS uses background modes in Xcode instead, which are reviewed by Apple.

What the platform says

Good uses and abuse

Legitimate uses

  • Navigation
  • Media

Known abuse

  • Using a loose type like specialUse to stay alive

Scores

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

History

  • 2023-10, Android 14 (API 34): Foreground service type and matching permission mandatory
  • 2024-10, Android 15 (API 35): mediaProcessing type added; BOOT_COMPLETED receivers cannot start dataSync, camera, mediaPlayback, phoneCall, mediaProjection or microphone FGS

Sources

How well checked: Based on official documentation.

On this page