Starting March 27, 2025, we recommend using android-latest-release instead of aosp-main to build and contribute to AOSP. For more information, see Changes to AOSP.
Stay organized with collections
Save and categorize content based on your preferences.
In Android 13, a new System UI affordance called the
Task Manager
notifies the user about the state and resources being used by the foreground
services on background apps and enables the user to stop these apps.
With the introduction of notification permissions
in Android 13, users have control over turning off
notifications from background apps that run foreground services
for location, media playback and projection, data sync, video and voice calls,
and connected devices. When such notifications are turned off, required
notifications from foreground services that indicate their state and resource
usage to the user aren't displayed. The Task Manager adds an information bar
on the Quick Settings display to inform users of the apps running in the
background and their usage of phone resources such as memory and battery. With
this interface, users are notified if an app is running a foreground service for
a long time and can choose to stop an app. The affordance is placed on the
display in a subtle way so it doesn't obstruct important notifications. See
Task Manager
for more information.
Implement Task Manager for background apps
Although a reference AOSP implementation
for this feature is available, Android-powered device implementers can customize and
modify this System UI.
The stop affordance in the Task Manager mustn't be displayed for apps which are
core to the functionality of the device, such as Dialer and Camera.
The AOSP implementation uses a new internal callback API
between the System UI
and System Server. This API lets the System Server notify the System UI when new
foreground services are started. The API also notifies the System Server to
stop certain apps, when requested by the user.
Validate Task Manager for background apps notifications
For manual testing, validate the Task Manager feature against apps that are
running in the background.
For unit testing, use unit tests
available in AOSP.
Content and code samples on this page are subject to the licenses described in the Content License. Java and OpenJDK are trademarks or registered trademarks of Oracle and/or its affiliates.
Last updated 2025-06-26 UTC.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-06-26 UTC."],[],[],null,["# Task Manager\n\nIn Android 13, a new System UI affordance called the\n[Task Manager](https://developer.android.com/about/versions/13/changes/fgs-manager)\nnotifies the user about the state and resources being used by the foreground\nservices on background apps and enables the user to stop these apps.\n\nWith the introduction of [notification permissions](https://developer.android.com/about/versions/13/changes/notification-permission)\nin Android 13, users have control over turning off\nnotifications from background apps that run [foreground services](https://developer.android.com/guide/components/foreground-services)\nfor location, media playback and projection, data sync, video and voice calls,\nand connected devices. When such notifications are turned off, required\nnotifications from foreground services that indicate their state and resource\nusage to the user aren't displayed. The Task Manager adds an information bar\non the Quick Settings display to inform users of the apps running in the\nbackground and their usage of phone resources such as memory and battery. With\nthis interface, users are notified if an app is running a foreground service for\na long time and can choose to stop an app. The affordance is placed on the\ndisplay in a subtle way so it doesn't obstruct important notifications. See\n[Task Manager](https://developer.android.com/about/versions/13/changes/fgs-manager)\nfor more information.\n\nImplement Task Manager for background apps\n------------------------------------------\n\nAlthough a [reference AOSP implementation](https://cs.android.com/android/platform/superproject/+/android-latest-release:frameworks/base/packages/SystemUI/src/com/android/systemui/qs/FgsManagerController.kt)\nfor this feature is available, Android-powered device implementers can customize and\nmodify this System UI.\nThe stop affordance in the Task Manager mustn't be displayed for apps which are\ncore to the functionality of the device, such as Dialer and Camera.\n\nThe AOSP implementation uses a new internal [callback API](https://cs.android.com/android/platform/superproject/+/android-latest-release:frameworks/base/core/java/android/app/IForegroundServiceObserver.aidl)\nbetween the [System UI](https://cs.android.com/android/platform/superproject/+/android-latest-release:frameworks/base/packages/SystemUI)\nand [System Server](https://cs.android.com/android/platform/superproject/+/android-latest-release:frameworks/base/services/core/java/com/android/server). This API lets the System Server notify the System UI when new\nforeground services are started. The API also notifies the System Server to\nstop certain apps, when requested by the user.\n| **Note:** This feature can't be turned off.\n\nValidate Task Manager for background apps notifications\n-------------------------------------------------------\n\nFor manual testing, validate the Task Manager feature against apps that are\nrunning in the background.\n\nFor unit testing, use [unit tests](https://cs.android.com/android/platform/superproject/+/android-latest-release:frameworks/base/packages/SystemUI/multivalentTests/src/com/android/systemui/qs/FgsManagerControllerTest.java)\navailable in AOSP."]]
