此页面由 Cloud Translation API 翻译。

前台服务类型

从 Android 14（API 级别 34）开始，您必须为每个前台服务声明适当的服务类型。这意味着，您必须在应用清单中声明服务类型，并且除了请求 FOREGROUND_SERVICE 权限之外，还必须为该类型请求适当的前台服务权限。此外，根据前台服务类型，您可能需要在启动服务之前请求运行时权限。

摄像头

要在清单中的 android:foregroundServiceType 下声明的前台服务类型

camera

在清单中声明的权限

FOREGROUND_SERVICE_CAMERA

要传递给 startForeground() 的常量

FOREGROUND_SERVICE_TYPE_CAMERA

运行时前提条件

请求并获得 CAMERA 运行时权限

注意：CAMERA 运行时权限受使用时限制。因此，当您的应用位于后台时，您无法创建 camera 前台服务，但存在一些例外情况。如需了解详情，请参阅有关启动需要运行时权限的前台服务的限制。

说明

继续在后台访问摄像头，例如支持多任务的视频聊天应用。

连接的设备

要在其清单中声明的前台服务类型

android:foregroundServiceType

connectedDevice

在清单中声明的权限

FOREGROUND_SERVICE_CONNECTED_DEVICE

要传递给 startForeground() 的常量

FOREGROUND_SERVICE_TYPE_CONNECTED_DEVICE

运行时前提条件

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

在清单中至少声明以下其中一项权限：
请求并获得以下至少一项运行时权限：
调用 UsbManager.requestPermission()

说明

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

替代方案

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

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

数据同步

Foreground service type to declare in manifest under

android:foregroundServiceType

dataSync

Permission to declare in your manifest

FOREGROUND_SERVICE_DATA_SYNC

Constant to pass to startForeground()

FOREGROUND_SERVICE_TYPE_DATA_SYNC

Runtime prerequisites

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

Alternatives

See Alternatives to data sync foreground services for detailed information.

健康

Foreground service type to declare in manifest under

android:foregroundServiceType

health

Permission to declare in your manifest

FOREGROUND_SERVICE_HEALTH

Constant to pass to startForeground()

FOREGROUND_SERVICE_TYPE_HEALTH

Runtime prerequisites

At least one of the following conditions must be true:

Declare the HIGH_SAMPLING_RATE_SENSORS permission in your manifest.
Request and be granted at least one of the following runtime permissions:
- BODY_SENSORS
- ACTIVITY_RECOGNITION

Note: The BODY_SENSORS runtime permission is subject to while-in-use restrictions. For this reason, you cannot create a health foreground service that uses body sensors 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

Any long-running use cases to support apps in the fitness category such as exercise trackers.

位置

Foreground service type to declare in manifest under

android:foregroundServiceType

location

Permission to declare in your manifest

FOREGROUND_SERVICE_LOCATION

Constant to pass to startForeground()

FOREGROUND_SERVICE_TYPE_LOCATION

Runtime prerequisites

The user must have enabled location services and the app must be granted at least one of the following runtime permissions:

Note: In order to check that the user has enabled location services as well as granted access to the runtime permissions, use PermissionChecker#checkSelfPermission()

Note: The location runtime permissions are subject to while-in-use restrictions. For this reason, you cannot create a location foreground service while your app is in the background, unless you've been granted the ACCESS_BACKGROUND_LOCATION runtime permission. For more information, see Restrictions on starting foreground services that need while-in-use permissions.

Description

Long-running use cases that require location access, such as navigation and location sharing.

Alternatives

If your app needs to be triggered when the user reaches specific locations, consider using the geofence API instead.

媒体

要在其清单中声明的前台服务类型
android:foregroundServiceType: mediaPlayback
在清单中声明的权限: FOREGROUND_SERVICE_MEDIA_PLAYBACK
要传递给 startForeground() 的常量: FOREGROUND_SERVICE_TYPE_MEDIA_PLAYBACK
运行时前提条件: 无
说明: 在后台继续播放音频或视频。在 Android TV 上支持数字视频录制 (DVR) 功能。
替代方案: 如果您显示的是画中画视频，请使用画中画模式。

媒体投影

要在其清单中声明的前台服务类型
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 前台服务，但存在一些例外情况。如需了解详情，请参阅有关启动需要运行时权限的前台服务的限制。

说明

在后台继续捕获麦克风内容，例如录音器或通信应用。

致电

Foreground service type to declare in manifest under

android:foregroundServiceType

phoneCall

Permission to declare in your manifest

FOREGROUND_SERVICE_PHONE_CALL

Constant to pass to startForeground()

FOREGROUND_SERVICE_TYPE_PHONE_CALL

Runtime prerequisites

At least one of these conditions must be true:

App has declared the MANAGE_OWN_CALLS permission in its manifest file.

App is the default dialer app through the ROLE_DIALER role.

Description

Continue an ongoing call using the ConnectionService APIs.

Alternatives

If you need to make phone, video, or VoIP calls, consider using the android.telecom library.

Consider using CallScreeningService to screen calls.

远程消息传递

要在其清单中声明的前台服务类型
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.

特殊用途

要在其清单中声明的前台服务类型

android:foregroundServiceType

specialUse

在清单中声明的权限

FOREGROUND_SERVICE_SPECIAL_USE

要传递给 startForeground() 的常量

FOREGROUND_SERVICE_TYPE_SPECIAL_USE

运行时前提条件

无

说明

涵盖其他前台服务类型未涵盖的所有有效前台服务用例。

除了声明 FOREGROUND_SERVICE_TYPE_SPECIAL_USE 前台服务类型之外，开发者还应在清单中声明用例。为此，他们会在 <service> 元素内指定 <property> 元素。当您在 Google Play 管理中心内提交应用时，我们会审核这些值和相应的用例。您提供的用例是自由形式的，您应确保提供足够的信息，让审核人员了解您为何需要使用 specialUse 类型。

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

系统豁免

要在其清单中声明的前台服务类型

android:foregroundServiceType

systemExempted

在清单中声明的权限

FOREGROUND_SERVICE_SYSTEM_EXEMPTED

要传递给 startForeground() 的常量

FOREGROUND_SERVICE_TYPE_SYSTEM_EXEMPTED

运行时前提条件

无

说明

为系统应用和特定系统集成预留，以便继续使用前台服务。

如需使用此类型，应用必须至少满足以下条件之一：

设备处于演示模式状态
应用是设备所有者
应用是性能分析器所有者
属于具有 ROLE_EMERGENCY 角色的安全应用
属于设备管理应用
具有 SCHEDULE_EXACT_ALARM 或 USE_EXACT_ALARM 权限的应用
VPN 应用（通过设置 > 网络和互联网 > VPN 进行配置）

否则，声明此类型会导致系统抛出 ForegroundServiceTypeNotAllowedException。

使用前台服务类型时强制执行的 Google Play 政策

如果您的应用以 Android 14 或更高版本为目标平台，您需要在 Play 管理中心的应用内容页面（政策 > 应用内容）中声明应用的前台服务类型。如需详细了解如何在 Play 管理中心内声明前台服务类型，请参阅了解前台服务和全屏 intent 要求。