# What are background apps on Android, and why do they run? — Adinand Auto File Sorter

Last reviewed: October 29, 2026. HTML version: https://adinandsorter.com/answers/what-are-background-apps-on-android

Android's developer documentation draws the line precisely: "An app is running in the background if none of its activities are visible to the user, and the app isn't running any foreground services" ([*Background tasks overview*, Android Developers](https://developer.android.com/develop/background-work/background-tasks?hl=en), read 29 October 2026). In plain terms, a background app is one you have left, or never opened today, that is still allowed to do something. Most of the time that something is small and deliberate: checking for new mail, uploading a photo, counting steps.

## The three kinds of work you are actually seeing <p>The same guide sorts an app's off-screen work into three categories, and each looks different from the outside.</p> <ul> <li>**Scheduled work.** Jobs an app hands to the system to run later, which "need to continue even if the user leaves the app". Google's examples are "Fetching data from server periodically", "Fetching sensor data (for example, step counter data)", periodic location, and "Uploading content based on a content trigger, such as photos created by the camera". The guide recommends WorkManager for most of these.</li> <li>**Foreground services.** Work that "ought not to be interrupted", which Android only allows if the user can see it: "a foreground service has to be noticeable to the user". Google's foreground-service page gives "A music player app that plays music in a foreground service" and a fitness app recording a run as examples, each with a status bar notification ([*Foreground services overview*, Android Developers](https://developer.android.com/develop/background-work/services/fgs?hl=en), read 29 October 2026). By the definition above, an app doing this is not technically "in the background" at all, which is why it has to show you a notification.</li> <li>**Short tasks that end when you leave.** The guide calls this asynchronous work and is blunt about its limit: it "is not guaranteed to finish if the app stops being in a valid lifecycle stage (for example, if the app leaves the foreground)".</li> </ul>

## Why the system does not simply let them run <p>Every one of these costs battery, so Android rations them. The background-tasks guide says that "If an app is running in the background, the system puts a number of restrictions on it", and Android's power guide adds that "The system prioritizes apps' requests for resources based on the device state, app state and the app's standby bucket" ([*Power management resource limits*, Android Developers](https://developer.android.com/topic/performance/power/power-details?hl=en), read 29 October 2026). The states and buckets themselves have their own pages here: [Doze](https://adinandsorter.com/answers/what-is-doze-mode-on-android) and [the standby buckets](https://adinandsorter.com/answers/android-app-standby-buckets). The practical result is that a schedule is a request, and the phone decides when it is granted.</p>

## Your three settings for any one app <p>Android's developer guide describes the per-app choice on the Battery usage page of system settings:</p>

| Setting | Google's description |
|---|---|
| Unrestricted | "Allow all background work, which might consume more battery." |
| Optimized (default) | "Optimize an app's ability to perform background work, based on how the user interacts with the app." |
| Restricted | "Fully prevents an app from running in the background. Apps may not work as expected." |

([*Background optimization*, Android Developers](https://developer.android.com/topic/performance/background-optimization?hl=en), read 29 October 2026.) On stock Android, Google lists what Restricted blocks for an app in the background: it "Can't launch foreground services", "Alarms aren't triggered" and "Jobs aren't executed", though the same page notes that "The precise restrictions imposed are determined by the device manufacturer". Opening a restricted app lifts it for as long as you use it. Phone makers add their own lists on top; Samsung's, for one, are covered on [our Samsung page](https://adinandsorter.com/answers/check-background-running-apps-on-samsung).

## Should you worry about them? <p>Our view: rarely. Background work is how a messaging app tells you a message arrived. The ones worth a look are apps you do not recognise near the top of your battery usage, and for those, Optimized or Restricted is the lever. The reverse problem, an app that should run in the background and does not, is on [the page about allowing it](https://adinandsorter.com/answers/allow-apps-to-work-in-background).</p>

## Adinand Auto File Sorter as a background app <p>The app is an example of the first kind. Its automatic sorting, a Pro feature, is a WorkManager job that runs on the interval you pick, from every 15 minutes to once a day, without the app being open. Because Android can delay or stop that job, the interval is not a guarantee, and the app does not ask for a battery exemption. A health indicator shows when the phone has not let it run. If you set the app to Restricted, by Google's description above its jobs are not executed, so background sorting stops; Sort Now, which is free, still works whenever you open it.</p>

Related: [Why background apps stop on Android](https://adinandsorter.com/answers/why-background-apps-stop-on-android) · [Allowing apps to work in the background](https://adinandsorter.com/answers/allow-apps-to-work-in-background) · [Seeing what runs in the background on a Samsung](https://adinandsorter.com/answers/check-background-running-apps-on-samsung) · [What battery optimization is on Android](https://adinandsorter.com/answers/what-is-battery-optimization-on-android)