There is this gesture we repeat dozens of times a day, almost mechanically: swiping up on the screen to close an app, convinced that it will extinguish as if we were blowing out a candle. The reasoning seems airtight. The app is no longer on screen, so it does nothing, so it won’t drain either the battery or the data plan. Yet this intuition, as reassuring as it may be, runs up against a far subtler technical reality. On Android, some apps continue to run quietly behind the scenes, even as you think you’ve shut them down. The mastermind behind this sleight of hand bears a name little known to the general public: the foreground service, a discreet status capable of keeping an app awake where the system should have silenced it.
The Myth of the “Closed” App That Sleeps for Good
Let’s start by debunking a stubborn belief. Closing an app from the task manager does not guarantee that it stops all activity. For several years now, Google has tightened the screws. With the arrival of Android 8.0, the system imposed real limits on background execution. The idea was simple and virtuous: prevent apps from running indefinitely in the shadows, from discreetly probing your location or pulling data back in without a valid reason, all at the expense of your battery life.
But there is a backdoor, perfectly legal and provided by the system itself. The famous restrictions hit classic background services, those that run when you are no longer interacting with the app. Yet they do not apply in the same way to foreground services. This is where the nuance lies: an app can claim activity deemed “visible” to the user, and thus benefit from favorable treatment. The system regards it as useful, almost indispensable, and gives it free rein.
How a Simple Status Allows an App to Stay Awake
The principle of the foreground service rests on one trade-off: to keep running, the app must display a permanently visible notification. You are surely familiar with those small icons that remain stuck in the status bar, such as a music player, ongoing GPS navigation, or an audio recording. This notification is the toll. It signals to the system, and to you, that something is still functioning. In exchange for this displayed transparency, Android allows the service to partially bypass the background execution limits.
Google has nonetheless continued to tighten the grip with each version. With Android 12, an app can no longer start a foreground service from the background, except in carefully bounded special cases. Only certain types, such as location or remote messaging, escape the rule without visible activity; the others must display their notification within ten seconds. There are exemptions: an app may act freely if it has just transitioned from a visible state, if it receives a high-priority message, or if you yourself have disabled battery optimization for it. With Android 15, the noose tightens further, in some cases requiring a specific permission and a real overlay window.
Battery, Data, Memory: What This Mechanism Really Costs
The burning question: is this a big deal? It depends on what that background service is doing behind the scenes. Some tasks are particularly demanding. A location service that repeatedly queries GPS, a media-processing service that encodes a video, or a health app that monitors your heart rate can drain a battery in plain sight if they linger too long. Added to that is mobile data consumption, invisible but real, when the app constantly syncs.
Since Android 11, an app launching such a background service can access your location only if you have granted background location permission, a requirement that was further strengthened by Android 14 for precise location. The message is clear: the system seeks a balance between user comfort and protecting your autonomy. In parallel, tools like WorkManager now allow developers to schedule short, high-priority tasks, such as sending a message or uploading a photo, without keeping a wakeful service running unnecessarily.
Take Back Control: Spotting and Limiting Apps That Never Sleep
Good news: you are not entirely defenseless. The first reflex is to monitor the persistent notifications. Each of them betrays an app that is active. Then head to your device’s battery settings, where a ranking reveals the most power-hungry applications, including those running in the background.
- Consult the Battery section to identify power-hungry apps
- Enable battery optimization for those that have no reason to run constantly
- Remove background location permissions from apps that do not need them
- Uninstall suspicious apps that display an unjustified persistent notification
One word of caution, however: not all these active apps are rogue passengers. Your music player must continue playing with the screen off, and your GPS must guide you even when you check a message. The foreground service is a legitimate tool before it becomes a nuisance.
In the end, this little technical mystery reminds us of one thing: our smartphones are much more alive than we imagine, even when we think we’ve put them to sleep. Closing an app is only an illusion of control if we ignore the mechanisms that keep it awake. So, next time a discreet notification lingers in your status bar, you’ll know to see it not as a bug, but as a sign of an app that keeps running, patiently. And why not take the opportunity to prune the list of those that don’t deserve this privilege?
