फ़ोरग्राउंड सेवा के टाइप

Android 14 (एपीआई लेवल 34) से, आपको हर फ़ोरग्राउंड सेवा के लिए सही सेवा टाइप का एलान करना होगा. इसका मतलब है कि आपको अपने ऐप्लिकेशन मेनिफ़ेस्ट में, सेवा के टाइप की जानकारी देनी होगी. साथ ही, उस टाइप के लिए फ़ोरग्राउंड सेवा की सही अनुमति का अनुरोध करना होगा. इसके अलावा, आपको FOREGROUND_SERVICE अनुमति का अनुरोध भी करना होगा. इसके अलावा, फ़ोरग्राउंड सेवा के टाइप के आधार पर, सेवा को लॉन्च करने से पहले आपको रनटाइम की अनुमतियों का अनुरोध करना पड़ सकता है.

ध्यान दें: कई मामलों में, किसी खास तरह की फ़ोरग्राउंड सेवा बनाने के बजाय, काम के हिसाब से बनाए गए एपीआई का इस्तेमाल किया जा सकता है. जब खास मकसद के लिए बनाए गए एपीआई उपलब्ध होते हैं, तो आम तौर पर फ़ोरग्राउंड सेवा बनाने के बजाय, उन्हें इस्तेमाल करना बेहतर होता है. ये एपीआई, फ़ोरग्राउंड सेवा के सही टाइप के विकल्प सेक्शन में मौजूद होते हैं.

कैमरा

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

camera

要在清单中声明的权限

FOREGROUND_SERVICE_CAMERA

要传递给 startForeground() 的常量

FOREGROUND_SERVICE_TYPE_CAMERA

运行时前提条件

请求并被授予 CAMERA 运行时权限

注意： CAMERA 运行时权限受“使用时”限制。因此，当应用在后台运行时，您无法创建 camera 前台服务，也无法从 BOOT_COMPLETED 接收器启动 camera 前台服务，但有少数例外情况。如需了解详情，请参阅与启动需要“使用时”权限的前台服务相关的限制。

说明

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

कनेक्ट किया गया डिवाइस

Foreground service type to declare in manifest under

android:foregroundServiceType

connectedDevice

Permission to declare in your manifest

FOREGROUND_SERVICE_CONNECTED_DEVICE

Constant to pass to startForeground()

FOREGROUND_SERVICE_TYPE_CONNECTED_DEVICE

Runtime prerequisites

At least one of the following conditions must be true:

• Declare at least one of the following permissions in your manifest:

  • CHANGE_NETWORK_STATE
  • CHANGE_WIFI_STATE
  • CHANGE_WIFI_MULTICAST_STATE
  • NFC
  • TRANSMIT_IR

• Request and be granted at least one of the following runtime permissions:

  • BLUETOOTH_CONNECT
  • BLUETOOTH_ADVERTISE
  • BLUETOOTH_SCAN
  • UWB_RANGING

• Call UsbManager.requestPermission()

Description

Interactions with external devices that require a Bluetooth, NFC, IR, USB, or network connection.

Note: If your app performs a projection or remote messaging operation, use the corresponding media projection or remote messaging type instead.

Alternatives

If your app needs to do continuous data transfer to an external device, consider using the companion device manager instead. Use the companion device presence API to help your app stay running while the companion device is in range.

If your app needs to scan for bluetooth devices, consider using the Bluetooth scan API instead.

डेटा सिंक करना

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

Note: Apps that target Android 15 or higher are not allowed to launch a data sync foreground service from a BOOT_COMPLETED broadcast receiver. For more information, see Restrictions on BOOT_COMPLETED broadcast receivers launching foreground services.

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 on API 35 and lower
  • READ_HEART_RATE
  • READ_SKIN_TEMPERATURE
  • READ_OXYGEN_SATURATION
  • ACTIVITY_RECOGNITION

Note: The BODY_SENSORS and sensor-based READ runtime permissions are 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, unless you've been granted the BODY_SENSORS_BACKGROUND (between API level 33 and API level 35) or READ_HEALTH_DATA_IN_BACKGROUND (API level 36) permissions. 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:

• ACCESS_COARSE_LOCATION
• ACCESS_FINE_LOCATION

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 15 或更高版本为目标平台的应用不得从 BOOT_COMPLETED 广播接收器启动媒体播放前台服务。如需了解详情，请参阅与 BOOT_COMPLETED 广播接收器启动前台服务相关的限制。

替代方案

如果您要显示画中画视频，请使用画中画模式。

मीडिया प्रोसेस करना

Foreground service type to declare in manifest under

android:foregroundServiceType

mediaProcessing

Permission to declare in your manifest

FOREGROUND_SERVICE_MEDIA_PROCESSING

Constant to pass to startForeground()

FOREGROUND_SERVICE_TYPE_MEDIA_PROCESSING

Runtime prerequisites

None

Description

Service for performing time-consuming operations on media assets, like converting media to different formats. The system allows this service a limited time to run; under normal circumstances, this time limit would be 6 hours out of every 24. (This limit is shared by all of an app's mediaProcessing foreground services.)

Your app should manually stop the media processing service in the following scenario:

• When the transcoding operation finishes or reaches a failure state, have the service call Service.stopForeground() and Service.stopSelf() to stop the service completely.

If the timeout period is reached, the system calls the service's Service.onTimeout(int, int) method. At this time, the service has a few seconds to call Service.stopSelf(). If the service does not call Service.stopSelf(), an ANR will occur with this error message: "A foreground service of <fgs_type> did not stop within its timeout: <component_name>".

Note: Service.onTimeout(int, int) is not available on Android 14 or lower. On devices running those versions, if a media processing service reaches the timeout period, the system immediately caches the app. For this reason, your app shouldn't wait to get a timeout notification. Instead, it should terminate the foreground service or change it to a background service as soon as appropriate.

मीडिया प्रोजेक्शन

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 角色成为默认的拨号器应用。

注意： 以 Android 15 或更高版本为目标平台的应用不允许从 BOOT_COMPLETED 广播接收器启动电话前台服务。如需了解详情，请参阅与 BOOT_COMPLETED 广播接收器启动前台服务相关的限制。

说明

使用 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.

खास इस्तेमाल

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>

सिस्टम को छूट मिली

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

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 की नीति लागू करना

If your app targets Android 14 or higher, you'll need to declare your app's foreground service types in the Play Console's app content page (Policy > App content). For more information on how to declare your foreground service types in Play Console, see Understanding foreground service and full-screen intent requirements.