포그라운드 서비스 유형

Android 14 (API 수준 34)부터는 각 포그라운드 서비스에 적절한 서비스 유형을 선언해야 합니다. 즉, 앱 매니페스트에서 서비스 유형을 선언하고 해당 유형에 적합한 포그라운드 서비스 권한을 요청해야 합니다 (FOREGROUND_SERVICE 권한 요청 외에). 또한 포그라운드 서비스 유형에 따라 서비스를 실행하기 전에 런타임 권한을 요청해야 할 수도 있습니다.

카메라

android:foregroundServiceType 아래 매니페스트에서 선언할 포그라운드 서비스 유형: camera
매니페스트에서 선언할 권한: FOREGROUND_SERVICE_CAMERA
startForeground()에 전달할 상수: FOREGROUND_SERVICE_TYPE_CAMERA
런타임 기본 요건: CAMERA 런타임 권한을 요청하고 부여받음

참고: CAMERA 런타임 권한에는 사용 중 제한이 적용됩니다. 따라서 앱이 백그라운드에 있는 동안 camera 포그라운드 서비스를 만들 수 없으며 BOOT_COMPLETED 리시버에서 camera 포그라운드 서비스를 실행할 수 없습니다(일부 예외 있음). 자세한 내용은 사용 중 권한이 필요한 포그라운드 서비스 시작에 관한 제한사항을 참고하세요.
설명: 멀티태스킹을 허용하는 영상 채팅 앱과 같이 백그라운드에서 카메라에 계속 액세스합니다.

연결된 기기

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

android:foregroundServiceType

connectedDevice

在清单中声明的权限

FOREGROUND_SERVICE_CONNECTED_DEVICE

要传递给 startForeground() 的常量

FOREGROUND_SERVICE_TYPE_CONNECTED_DEVICE

运行时前提条件

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

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

说明

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

替代方案

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

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

데이터 동기화

매니페스트에서

android:foregroundServiceType

dataSync

매니페스트에서 선언할 권한

FOREGROUND_SERVICE_DATA_SYNC

startForeground()에 전달할 상수

FOREGROUND_SERVICE_TYPE_DATA_SYNC

런타임 기본 요건

없음

설명

다음과 같은 데이터 전송 작업입니다.

데이터 업로드 또는 다운로드
백업 및 복원 작업
가져오기 또는 내보내기 작업
데이터 가져오기
로컬 파일 처리
네트워크를 통해 기기와 클라우드 간에 데이터 전송

대안

자세한 내용은 데이터 동기화 포그라운드 서비스의 대안을 참고하세요.

Health

매니페스트에서 선언할 포그라운드 서비스 유형

android:foregroundServiceType

health

매니페스트에서 선언할 권한

FOREGROUND_SERVICE_HEALTH

startForeground()에 전달할 상수

FOREGROUND_SERVICE_TYPE_HEALTH

런타임 기본 요건

다음 조건 중 하나 이상에 해당해야 합니다.

매니페스트에서 HIGH_SAMPLING_RATE_SENSORS 권한을 선언합니다.
다음 런타임 권한 중 하나 이상을 요청하고 부여받습니다.
- BODY_SENSORS(API 35 이하)
- READ_HEART_RATE
- READ_SKIN_TEMPERATURE
- READ_OXYGEN_SATURATION
- ACTIVITY_RECOGNITION

설명

운동 추적기 등 피트니스 카테고리의 앱을 지원하기 위한 장기 실행 사용 사례입니다.

위치

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:

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 15 或更高版本为目标平台的应用不得从 BOOT_COMPLETED 广播接收器启动媒体播放前台服务。如需了解详情，请参阅与 BOOT_COMPLETED 广播接收器启动前台服务相关的限制。
替代方案: 如果您要显示画中画视频，请使用画中画模式。

미디어 처리 중

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

android:foregroundServiceType

mediaProcessing

在清单中声明的权限

FOREGROUND_SERVICE_MEDIA_PROCESSING

要传递给 startForeground() 的常量

FOREGROUND_SERVICE_TYPE_MEDIA_PROCESSING

运行时前提条件

无

说明

用于对媒体资源执行耗时的操作（例如将媒体转换为其他格式）的服务。系统允许此服务运行的时间有限；在正常情况下，此时限为每天 24 小时中的 6 小时。（此限制由应用的所有 mediaProcessing 前台服务共享。）

在以下情况下，您的应用应手动停止媒体处理服务：

当转码操作完成或达到失败状态时，让服务调用 Service.stopForeground() 和 Service.stopSelf() 以完全停止服务。

如果超时期限已到，系统会调用服务的 Service.onTimeout(int, int) 方法。此时，该服务有几秒钟的时间来调用 Service.stopSelf()。如果服务未调用 Service.stopSelf()，则会发生 ANR，并显示以下错误消息：“<fgs_type> 的前台服务未在超时时间内停止：<component_name>”。

注意：Service.onTimeout(int, int) 不适用于 Android 14 或更低版本。在搭载这些版本的设备上，如果媒体处理服务达到超时期限，系统会立即缓存应用。因此，您的应用不应等待收到超时通知。相反，它应在适当情况下尽快终止前台服务或将其更改为后台服务。

미디어 프로젝션

Foreground service type to declare in manifest under
android:foregroundServiceType: mediaProjection
Permission to declare in your manifest: FOREGROUND_SERVICE_MEDIA_PROJECTION
Constant to pass to startForeground(): FOREGROUND_SERVICE_TYPE_MEDIA_PROJECTION
Runtime prerequisites: Call the createScreenCaptureIntent() method before starting the foreground service. Doing so shows a permission notification to the user; the user must grant the permission before you can create the service.; After you have created the foreground service, you can call MediaProjectionManager.getMediaProjection().
Description: Project content to non-primary display or external device using the MediaProjection APIs. This content doesn't have to be exclusively media content.

Note: Apps that target Android 15 or higher are not allowed to launch a media projection foreground service from a BOOT_COMPLETED broadcast receiver. For more information, see Restrictions on BOOT_COMPLETED broadcast receivers launching foreground services.
Alternatives: To stream media to another device, use the Google Cast SDK.

마이크

要在清单中声明的前台服务类型，位于
android:foregroundServiceType: microphone
要在清单中声明的权限: FOREGROUND_SERVICE_MICROPHONE
要传递给 startForeground() 的常量: FOREGROUND_SERVICE_TYPE_MICROPHONE
运行时前提条件: 请求并被授予 RECORD_AUDIO 运行时权限。

注意： RECORD_AUDIO 运行时权限受“使用时”限制。因此，当应用在后台运行时，您无法创建 microphone 前台服务，也无法从 BOOT_COMPLETED 接收器启动 microphone 前台服务，但有少数例外情况。如需了解详情，请参阅与启动需要“使用时”权限的前台服务相关的限制。
说明: 在后台继续捕获麦克风内容，例如录音器或通信应用。

전화 통화

要在清单中声明的前台服务类型，位于

android:foregroundServiceType

phoneCall

要在清单中声明的权限

FOREGROUND_SERVICE_PHONE_CALL

要传递给 startForeground() 的常量

FOREGROUND_SERVICE_TYPE_PHONE_CALL

运行时前提条件

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

应用已在其清单文件中声明 MANAGE_OWN_CALLS 权限。

应用通过 ROLE_DIALER 角色成为默认的拨号器应用。

说明

使用 ConnectionService API 继续当前通话。

替代方案

如果您需要拨打手机、视频或 VoIP 通话，不妨考虑使用 android.telecom 库。

考虑使用 CallScreeningService 来过滤来电。

원격 메시지

Foreground service type to declare in manifest under
android:foregroundServiceType: remoteMessaging
Permission to declare in your manifest: FOREGROUND_SERVICE_REMOTE_MESSAGING
Constant to pass to startForeground(): FOREGROUND_SERVICE_TYPE_REMOTE_MESSAGING
Runtime prerequisites: None
Description: Transfer text messages from one device to another. Assists with continuity of a user's messaging tasks when they switch devices.

짧은 서비스

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> 元素。这些值和相应的应用场景。用途您提供的案例均为自由形式，因此，您应确保提供足够的相关信息，让审核人员了解您为何需要使用 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。