To help developers be more intentional with defining user-facing foreground
services, Android 10 introduced the android:foregroundServiceType
attribute within the <service>
element.
If your app targets Android 14, it must specify appropriate foreground service types. As in previous versions of Android, multiple types can be combined. This list shows the foreground service types to choose from:
camera
connectedDevice
dataSync
health
location
mediaPlayback
mediaProjection
microphone
phoneCall
remoteMessaging
shortService
specialUse
systemExempted
If a use case in your app isn't associated with any of these types, we strongly recommend that you migrate your logic to use WorkManager or user-initiated data transfer jobs.
The health, remoteMessaging, shortService, specialUse
, and systemExempted
types are new in Android 14.
The following code snippet provides an example of a foreground service type declaration in the manifest:
<manifest ...>
<uses-permission android:name="android.permission.FOREGROUND_SERVICE" />
<uses-permission android:name="android.permission.FOREGROUND_SERVICE_MEDIA_PLAYBACK" />
<application ...>
<service
android:name=".MyMediaPlaybackService"
android:foregroundServiceType="mediaPlayback"
android:exported="false">
</service>
</application>
</manifest>
If an app that targets Android 14 doesn't define types for a given service in
the manifest, then the system will raise MissingForegroundServiceTypeException
upon calling startForeground()
for that service.
Mendeklarasikan izin baru untuk menggunakan jenis layanan latar depan
If apps that target Android 14 use a foreground service, they must declare a specific permission, based on the foreground service type, that Android 14 introduces. These permissions appear in the sections labeled "permission that you must declare in your manifest file" in the intended use cases and enforcement for each foreground service type section on this page.
All of the permissions are defined as normal permissions and are granted by default. Users cannot revoke these permissions.
Menyertakan jenis layanan latar depan saat runtime
The best practice for applications starting foreground services is to use the
overloaded version of startForeground()
where you pass in a bitwise
integer of foreground service types. You can choose to pass one or more type
values.
Usually, you should declare only the types required for a particular use case. This makes it easier to meet the system's expectations for each foreground service type. In cases where a foreground service is started with multiple types, then the foreground service must adhere to the platform enforcement requirements of all types.
If you start a foreground service that uses any of the
following types, however, you should always include the types each time you call
startForeground()
for that service:
Service.startForeground(0, notification, FOREGROUND_SERVICE_TYPE_LOCATION)
If the foreground service type is not specified in the call, it will default to the values defined in the manifest.
Pemeriksaan runtime sistem
The system checks for proper use of foreground service types and confirms that
the app has requested the proper runtime permissions or uses the required APIs.
For instance, the system expects apps that use the foreground service type
FOREGROUND_SERVICE_TYPE_LOCATION
type to request either
ACCESS_COARSE_LOCATION
or ACCESS_FINE_LOCATION
.
This implies that apps must follow a very specific
order of operations when requesting permissions from the user and starting
foreground services. Permissions must be requested and granted before the
app attempts to call startForeground()
. Apps that request the appropriate
permissions after the foreground service has been started must change this order
of operations and request the permission before starting the foreground service.
The specifics of platform enforcement appear in the sections labeled "runtime requirements" in the intended use cases and enforcement for each foreground service type section on this page.
Kasus penggunaan dan penerapan yang ditargetkan untuk setiap jenis layanan latar depan
In order to use a given foreground service type, you must declare a particular permission in your manifest file, you must fulfill specific runtime requirements, and your app must fulfill one of the intended sets of use cases for that type. The following sections explain the permission that you must declare, the runtime requirements, and the intended use cases for each type.
Kamera
- Permission that you must declare in your manifest file
FOREGROUND_SERVICE_CAMERA
- Runtime requirements
- Request the
CAMERA
runtime permission - Description
- Continue to access the camera from the background, such as video chat apps that allow for multi-tasking.
Perangkat yang terhubung
- Permission that you must declare in your manifest file
FOREGROUND_SERVICE_CONNECTED_DEVICE
- Runtime requirements
At least one of the following conditions must be true:
Declare at least one of the following permissions in your manifest:
Request at least one of the following runtime permissions:
- Description
Interactions with external devices that require a Bluetooth, NFC, IR, USB, or network connection.
Sinkronisasi data
- Permission that you must declare in your manifest file
FOREGROUND_SERVICE_DATA_SYNC
- Runtime requirements
- None
- Description
Data transfer operations, such as the following:
- Data upload or download
- Backup-and-restore operations
- Import or export operations
- Fetch data
- Local file processing
- Transfer data between a device and the cloud over a network
Kesehatan
- Permission that you must declare in your manifest file
FOREGROUND_SERVICE_HEALTH
- Runtime requirements
At least one of the following conditions must be true:
Declare the
HIGH_SAMPLING_RATE_SENSORS
permission in your manifest.Request at least one of the following runtime permissions:
- Description
Any long-running use cases to support apps in the fitness category such as exercise trackers.
Lokasi
- Permission that you must declare in your manifest file
FOREGROUND_SERVICE_LOCATION
- Runtime requirements
Request at least one of the following runtime permissions:
- Description
Long-running use cases that require location access, such as navigation and location sharing.
Media
- Izin yang harus Anda deklarasikan dalam file manifes
FOREGROUND_SERVICE_MEDIA_PLAYBACK
- Persyaratan runtime
- Tidak ada
- Deskripsi
- Melanjutkan pemutaran audio atau video dari latar belakang. Mendukung fungsi Perekaman Video Digital (DVR) di Android TV.
Proyeksi media
- Permission that you must declare in your manifest file
FOREGROUND_SERVICE_MEDIA_PROJECTION
- Runtime requirements
- Call the
createScreenCaptureIntent()
method before starting the foreground service. - Description
- Project content to non-primary display or external device using the
MediaProjection
APIs. This content doesn't have to be exclusively media content. Excludes Cast SDK.
Mikrofon
- Permission that you must declare in your manifest file
FOREGROUND_SERVICE_MICROPHONE
- Runtime requirements
- Request the
RECORD_AUDIO
runtime permission. - Description
- Continue microphone capture from the background, such as voice recorders or communication apps.
Panggilan telepon
- Permission that you must declare in your manifest file
FOREGROUND_SERVICE_PHONE_CALL
- Runtime requirements
At least one of the following:
- Declare the
MANAGE_OWN_CALLS
permission in your manifest file. - Hold the
ROLE_DIALER
role.
- Declare the
- Description
Continue an ongoing call using the
ConnectionService
APIs.
Pengiriman pesan jarak jauh
- Permission that you must declare in your manifest file
FOREGROUND_SERVICE_REMOTE_MESSAGING
- Runtime requirements
- None
- Description
- Transfer text messages from one device to another. Assists with continuity of a user's messaging tasks when they switch devices.
Layanan singkat
- Permission that you must declare in your manifest file
- None
- Runtime requirements
- None
- Description
Quickly finish critical work that cannot be interrupted or postponed.
This type has some unique characteristics:
- Can only run for a short period of time (about 3 minutes).
- No support for sticky foreground services.
- Cannot start other foreground services.
- Doesn't require a type-specific permission, though it still
requires the
FOREGROUND_SERVICE
permission. - A running foreground service cannot change to or from
shortService
type.
The timeout for shortService begins from the moment that
Service.startForeground()
is called. The app is expected to callService.stopSelf()
orService.stopForeground()
before the timeout occurs. Otherwise, the newService.onTimeout()
is called, giving apps a brief opportunity to callstopSelf()
orstopForeground()
to stop their service.A short time after
Service.onTimeout()
is called, the app enters a cached state and is no longer considered to be in the foreground, unless the user is actively interacting with the app. A short time after the app is cached and the service has not stopped, the app receives an ANR. The ANR message mentionsFOREGROUND_SERVICE_TYPE_SHORT_SERVICE
. For these reasons, it's considered best practice to implement theService.onTimeout()
callback.The
Service.onTimeout()
callback doesn't exist on Android 13 and lower. If the same service runs on such devices, it doesn't receive a timeout, nor does it ANR. Make sure that your service stops as soon as it finishes the processing task, even if it hasn't received theService.onTimeout()
callback yet.It's important to note that if the timeout of the
shortService
is not respected, the app will ANR even if it has other valid foreground services or other app lifecycle processes running.If an app is visible to the user or satisfies one of the exemptions that allow foreground services to be started from the background, calling
Service.StartForeground()
again with theFOREGROUND_SERVICE_TYPE_SHORT_SERVICE
parameter extends the timeout by another 3 minutes. If the app isn't visible to the user and doesn't satisfy one of the exemptions, any attempt to start another foreground service, regardless of type, causes aForegroundServiceStartNotAllowedException
.If a user disables battery optimization for your app, it's still affected by the timeout of shortService FGS.
If you start a foreground service that includes the
shortService
type and another foreground service type, the system ignores theshortService
type declaration. However, the service must still adhere to the requirements of the other declared types.
Penggunaan khusus
- Permission that you must declare in your manifest file
FOREGROUND_SERVICE_SPECIAL_USE
- Runtime requirements
- None
- Description
Covers any valid foreground service use cases that aren't covered by the other foreground service types.
In addition to declaring the
FOREGROUND_SERVICE_TYPE_SPECIAL_USE
foreground service type, developers should declare use cases in the manifest. To do so, they specify the<property>
element within the<service>
element. These values and corresponding use cases are reviewed when you submit your app in the Google Play Console.<service android:name="fooService" android:foregroundServiceType="specialUse"> <property android:name="android.app.PROPERTY_SPECIAL_USE_FGS_SUBTYPE" android:value="foo"/> </service>
Sistem dikecualikan
- Permission that you must declare in your manifest file
FOREGROUND_SERVICE_SYSTEM_EXEMPTED
- Runtime requirements
- None
- Description
Reserved for system applications and specific system integrations, to continue to use foreground services.
To use this type, an app must meet at least one of the following criteria:
- Device is in demo mode state
- App is a Device Owner
- App is a Profiler Owner
- Safety Apps that have the
ROLE_EMERGENCY
role - Device Admin apps
- Apps holding
SCHEDULE_EXACT_ALARM
orUSE_EXACT_ALARM
permission. - VPN apps using the
VpnService
(apps usingPlatformVpnProfile
are not eligible)
Otherwise, declaring this type causes the system to throw a
ForegroundServiceTypeNotAllowedException
.
Penegakan kebijakan Google Play untuk menggunakan jenis layanan latar depan
The April 2023 Google Play policy updates includes changes to the Device
and Network Abuse policy. These new policies restrict when and how your app
can declare the FOREGROUND_SERVICE
permission, especially if
the corresponding types don't match the system expectations.