フォアグラウンド サービス タイプは必須

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.

フォアグラウンド サービス タイプを使用する新しい権限を宣言する

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.

Caution: If you call startForeground() without declaring the appropriate foreground service type permission, the system throws a SecurityException.

実行時にフォアグラウンド サービス タイプを含める

The best practice for applications starting foreground services is to use the ServiceCompat version of startForeground() (available in androidx-core 1.12 and higher) 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.

ServiceCompat.startForeground(0, notification, FOREGROUND_SERVICE_TYPE_LOCATION)

If the foreground service type is not specified in the call, the type defaults to the values defined in the manifest. If you didn't specify the service type in the manifest, the system throws MissingForegroundServiceTypeException.

If the foreground service needs new permissions after you launch it, you should call startForeground() again and add the new service types. For example, suppose a fitness app runs a running-tracker service that always needs location information, but might or might not need media permissions. You would need to declare both location and mediaPlayback in the manifest. If a user starts a run and just wants their location tracked, your app should call startForeground() and pass just the location service type. Then, if the user wants to start playing audio, call startForeground() again and pass location|mediaPlayback.

システムによるランタイム チェック

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.

Caution: If your app doesn't fulfill all of the runtime requirements for starting a foreground service, the system throws a SecurityException after you call startForeground() for that service. This prevents the foreground service from starting, might cause a running foreground service to be removed from the foreground process state, and might cause your app to crash.

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.

各フォアグラウンド サービス タイプの対象ユースケースと適用

为了使用给定的前台服务类型，您必须在清单文件中声明特定权限，必须满足特定的运行时要求，并且应用必须满足该类型的其中一组预期用例。以下部分介绍了您必须声明的权限、运行时前提条件以及每种类型的预期用例。

カメラ

Foreground service type to declare in manifest under android:foregroundServiceType

camera

Permission to declare in your manifest

FOREGROUND_SERVICE_CAMERA

Constant to pass to startForeground()

FOREGROUND_SERVICE_TYPE_CAMERA

Runtime prerequisites

Request and be granted the CAMERA runtime permission

Note: The CAMERA runtime permission is subject to while-in-use restrictions. For this reason, you cannot create a camera foreground service while your app is in the background, with a few exceptions. For more information, see Restrictions on starting foreground services that need while-in-use permissions.

Description

Continue to access the camera from the background, such as video chat apps that allow for multitasking.

接続されたデバイス

要在清单中的以下位置声明的前台服务类型

android:foregroundServiceType

connectedDevice

在清单中声明的权限

FOREGROUND_SERVICE_CONNECTED_DEVICE

要传递给 startForeground() 的常量

FOREGROUND_SERVICE_TYPE_CONNECTED_DEVICE

运行时前提条件

必须至少满足以下其中一个条件：

• 在清单中至少声明以下其中一项权限：

  • CHANGE_NETWORK_STATE
  • CHANGE_WIFI_STATE
  • CHANGE_WIFI_MULTICAST_STATE
  • NFC
  • TRANSMIT_IR

• 至少请求并被授予以下其中一项运行时权限：

  • BLUETOOTH_CONNECT
  • BLUETOOTH_ADVERTISE
  • BLUETOOTH_SCAN
  • UWB_RANGING

• 调用 UsbManager.requestPermission()

说明

与需要蓝牙、NFC、IR、USB 或网络连接的外部设备进行互动。

注意 ：如果您的应用执行投影或远程消息传递操作，请改用相应的媒体投影或远程消息传递类型。

替代方案

如果您的应用需要向外部设备持续传输数据，请考虑改用配套设备管理器。使用配套设备感知 API，可帮助您的应用在配套设备在范围内时保持运行。

如果您的应用需要扫描蓝牙设备，请考虑改用 Bluetooth Scan API。

データの同期

要在清单中的以下位置声明的前台服务类型

android:foregroundServiceType

dataSync

在清单中声明的权限

FOREGROUND_SERVICE_DATA_SYNC

要传递给 startForeground() 的常量

FOREGROUND_SERVICE_TYPE_DATA_SYNC

运行时前提条件

无

说明

数据传输操作，例如：

• 数据上传或下载
• 备份和恢复操作
• 导入或导出操作
• 获取数据
• 本地文件处理
• 通过网络在设备和云端之间传输数据

替代方案

如需了解详情，请参阅数据同步前台服务的替代方案。

健康

マニフェストで宣言するフォアグラウンド サービス タイプ

android:foregroundServiceType

health

マニフェストで宣言する権限

FOREGROUND_SERVICE_HEALTH

startForeground() に渡す定数

FOREGROUND_SERVICE_TYPE_HEALTH

ランタイムの前提条件

次の条件の少なくとも 1 つを満たす必要があります。

• マニフェストで HIGH_SAMPLING_RATE_SENSORS 権限を宣言します。

• 次の実行時の権限を少なくとも 1 つリクエストし、付与されていること。

  • BODY_SENSORS（API レベル 35 以前）
  • READ_HEART_RATE
  • READ_SKIN_TEMPERATURE
  • READ_OXYGEN_SATURATION
  • ACTIVITY_RECOGNITION

注: BODY_SENSORS とセンサーベースの READ ランタイム権限には、使用中の制限が適用されます。そのため、アプリがバックグラウンドにあるときにボディセンサーを使用する health フォアグラウンド サービスを作成するには、BODY_SENSORS_BACKGROUND（API レベル 33 ～ 35）または READ_HEALTH_DATA_IN_BACKGROUND（API レベル 36 以上）の権限が付与されている必要があります。詳細については、使用中の権限が必要なフォアグラウンド サービスの開始に関する制限をご覧ください。

説明

フィットネス カテゴリのアプリ（エクササイズ トラッカーなど）をサポートする、長時間にわたるユースケース。

位置情報

要在清单中的以下位置声明的前台服务类型

android:foregroundServiceType

location

在清单中声明的权限

FOREGROUND_SERVICE_LOCATION

要传递给 startForeground() 的常量

FOREGROUND_SERVICE_TYPE_LOCATION

运行时前提条件

用户必须已启用位置信息服务，并且应用必须至少获得以下一项运行时权限：

• ACCESS_COARSE_LOCATION
• ACCESS_FINE_LOCATION

注意：如需检查用户是否已启用位置信息服务以及是否已授予对运行时权限的访问权限，请使用 PermissionChecker#checkSelfPermission()

注意：位置信息运行时权限受“使用期间”限制。因此，除非您已获得 ACCESS_BACKGROUND_LOCATION 运行时权限，否则无法在应用在后台运行时创建 location 前台服务。如需了解详情，请参阅与启动需要“使用时”权限的前台服务相关的限制。

说明

需要位置信息使用权的长时间运行的用例，例如导航和位置信息分享。

替代方案

如果您的应用需要在用户到达特定位置时触发，请考虑改用 Geofence API。

メディア

Foreground service type to declare in manifest under

android:foregroundServiceType

mediaPlayback

Permission to declare in your manifest

FOREGROUND_SERVICE_MEDIA_PLAYBACK

Constant to pass to startForeground()

FOREGROUND_SERVICE_TYPE_MEDIA_PLAYBACK

Runtime prerequisites

None

Description

Continue audio or video playback from the background. Support Digital Video Recording (DVR) functionality on Android TV.

Alternatives

If you're showing picture-in-picture video, use Picture-in-Picture mode.

メディア プロジェクション

要在清单中的以下位置声明的前台服务类型

android:foregroundServiceType

mediaProjection

在清单中声明的权限

FOREGROUND_SERVICE_MEDIA_PROJECTION

要传递给 startForeground() 的常量

FOREGROUND_SERVICE_TYPE_MEDIA_PROJECTION

运行时前提条件

在启动前台服务之前调用 createScreenCaptureIntent() 方法。这样做会向用户显示权限通知；用户必须先授予权限，您才能创建服务。

创建前台服务后，您可以调用 MediaProjectionManager.getMediaProjection()。

说明

使用 MediaProjection API 将内容投影到非主要显示屏或外部设备。这些内容不必全都为媒体内容。

替代方案

如需将媒体流式传输到其他设备，请使用 Google Cast SDK。

マイク

マニフェストの

android:foregroundServiceType

microphone

マニフェストで宣言する権限

FOREGROUND_SERVICE_MICROPHONE

startForeground() に渡す定数

FOREGROUND_SERVICE_TYPE_MICROPHONE

ランタイムの前提条件

RECORD_AUDIO の実行時の権限をリクエストして付与される。

注: RECORD_AUDIO 実行時の権限には、使用中の制限が適用されます。そのため、少数の例外を除き、アプリがバックグラウンドにあるときに microphone フォアグラウンド サービスを作成することはできません。詳細については、使用中の権限が必要なフォアグラウンド サービスの開始に関する制限をご覧ください。

説明

ボイス レコーダーや通信アプリなど、バックグラウンドからマイクのキャプチャを続行します。

電話

マニフェストで宣言するフォアグラウンド サービス タイプ

android:foregroundServiceType

phoneCall

マニフェストで宣言する権限

FOREGROUND_SERVICE_PHONE_CALL

startForeground() に渡す定数

FOREGROUND_SERVICE_TYPE_PHONE_CALL

ランタイムの前提条件

次の条件の少なくとも 1 つを満たす必要があります。

• アプリがマニフェスト ファイルで MANAGE_OWN_CALLS 権限を宣言している。

• アプリが ROLE_DIALER ロールを介してデフォルトのダイヤルアプリである。

説明

ConnectionService API を使用して、現在の呼び出しを続行します。

代替

電話、ビデオ、VoIP 通話を行う必要がある場合は、android.telecom ライブラリの使用を検討してください。

CallScreeningService を使用して通話をスクリーニングすることを検討してください。

リモート メッセージ

要在清单中的以下位置声明的前台服务类型

android:foregroundServiceType

remoteMessaging

在清单中声明的权限

FOREGROUND_SERVICE_REMOTE_MESSAGING

要传递给 startForeground() 的常量

FOREGROUND_SERVICE_TYPE_REMOTE_MESSAGING

运行时前提条件

无

说明

将短信从一台设备转移到另一台设备。在用户切换设备时，帮助确保用户消息任务的连续性。

ショート サービス

Foreground service type to declare in manifest under

android:foregroundServiceType

shortService

Permission to declare in your manifest

None

Constant to pass to startForeground()

FOREGROUND_SERVICE_TYPE_SHORT_SERVICE

Runtime prerequisites

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 shortService can only change to another service type if the app is currently eligible to start a new foreground service.
• A foreground service can change its type to shortService at any time, at which point the timeout period begins.

The timeout for shortService begins from the moment that Service.startForeground() is called. The app is expected to call Service.stopSelf() or Service.stopForeground() before the timeout occurs. Otherwise, the new Service.onTimeout() is called, giving apps a brief opportunity to call stopSelf() or stopForeground() 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 mentions FOREGROUND_SERVICE_TYPE_SHORT_SERVICE. For these reasons, it's considered best practice to implement the Service.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 the Service.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 the FOREGROUND_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 a ForegroundServiceStartNotAllowedException.

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 the shortService type declaration. However, the service must still adhere to the prerequisites of the other declared types. For more information, see the Foreground services documentation.

特殊用途

Foreground service type to declare in manifest under

android:foregroundServiceType

specialUse

Permission to declare in your manifest

FOREGROUND_SERVICE_SPECIAL_USE

Constant to pass to startForeground()

FOREGROUND_SERVICE_TYPE_SPECIAL_USE

Runtime prerequisites

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. The use cases you provide are free-form, and you should make sure to provide enough information to let the reviewer see why you need to use the specialUse type.

<service android:name="fooService" android:foregroundServiceType="specialUse">
  <property android:name="android.app.PROPERTY_SPECIAL_USE_FGS_SUBTYPE"
      android:value="explanation_for_special_use"/>
</service>

除外されたシステム

Foreground service type to declare in manifest under

android:foregroundServiceType

systemExempted

Permission to declare in your manifest

FOREGROUND_SERVICE_SYSTEM_EXEMPTED

Constant to pass to startForeground()

FOREGROUND_SERVICE_TYPE_SYSTEM_EXEMPTED

Runtime prerequisites

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 or USE_EXACT_ALARM permission and are using Foreground Service to continue alarms in the background, including haptics-only alarms.

• VPN apps (configured using Settings > Network & Internet > VPN)

  Otherwise, declaring this type causes the system to throw a ForegroundServiceTypeNotAllowedException.

フォアグラウンド サービス タイプの使用に対する Google Play ポリシーの適用

Android 14 以降をターゲットとするアプリの場合は、Google Play Console の [アプリのコンテンツ] ページ（[ポリシー] > [アプリのコンテンツ]）で、アプリのフォアグラウンド サービスのタイプを申告する必要があります。Google Play Console でフォアグラウンド サービスのタイプを申告する方法について詳しくは、フォアグラウンド サービスと全画面インテントの要件についてをご覧ください。