Handle user-initiated stopping of apps running foreground services
Stay organized with collections
Save and categorize content based on your preferences.
Starting in Android 13 (API level 33), users can complete a workflow from the
notification drawer
to stop an app that has an ongoing foreground services, regardless of that app's
target SDK version. This affordance, called the
Task Manager, shows a list of apps that are
currently running a foreground service.
Figure 1. Task Manager workflow on devices that
run Android 13 or higher.
This list is labeled Active apps.
Next to each app is a Stop button. Figure 1 illustrates the
Task Manager workflow on a device that runs
Android 13.
When the user presses the Stop button next to your app in the
Task Manager, then the following actions occur:
The system removes your app from memory. Therefore, your entire app stops,
not just the running foreground service.
The system removes your app's activity back stack.
Any media playback stops.
The notification associated with the foreground service is removed.
Your app remains in history.
Scheduled jobs execute at their scheduled time.
Alarms go off at their scheduled time or time window.
To test that your app behaves as expected while and after a user stops your
app, run the following ADB command in a terminal window:
adbshellcmdactivitystop-appPACKAGE_NAME
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-08-26 UTC.
[null,null,["Last updated 2025-08-26 UTC."],[],[],null,["Starting in Android 13 (API level 33), users can complete a workflow from the\n[notification drawer](/develop/ui/views/notifications#bar-and-drawer)\nto stop an app that has an ongoing foreground services, regardless of that app's\ntarget SDK version. This affordance, called the\n*Task Manager*, shows a list of apps that are\ncurrently running a foreground service. \n**Figure 1.** Task Manager workflow on devices that run Android 13 or higher.\n\nThis list is labeled **Active apps** .\nNext to each app is a **Stop** button. Figure 1 illustrates the\nTask Manager workflow on a device that runs\nAndroid 13.\n\nWhen the user presses the **Stop** button next to your app in the\nTask Manager, then the following actions occur:\n\n- The system removes your app from memory. Therefore, your **entire app stops**, not just the running foreground service.\n- The system removes your app's activity back stack.\n- Any media playback stops.\n- The notification associated with the foreground service is removed.\n- Your app remains in history.\n- Scheduled jobs execute at their scheduled time.\n- Alarms go off at their scheduled time or time window.\n\n| **Note:** The system doesn't send your app any callbacks when the user taps the **Stop** button. When your app starts back up, it's helpful to check for the [`REASON_USER_REQUESTED`](/reference/android/app/ApplicationExitInfo#REASON_USER_REQUESTED) reason that's part of the `ApplicationExitInfo` API.\n\nTo test that your app behaves as expected while and after a user stops your\napp, run the following ADB command in a terminal window: \n\n```bash\nadb shell cmd activity stop-app PACKAGE_NAME\n```"]]
