You put your phone down with 80 percent battery. Three hours later you pick it up and it is at 45 percent. You have not used it. The screen was off the entire time. Yet something consumed over a third of your battery while the phone sat on your desk.
This is background activity. Understanding how it actually works changes how you approach battery life entirely, and it starts with correcting one of the most persistent myths in tech.
The Myth of the Recent Apps Screen
Most people believe that swiping apps out of the recent apps screen saves battery. It almost never does, and in some cases makes things slightly worse.
When you switch away from an app on a modern phone, the operating system does not leave it running at full power. It suspends it. A suspended app is essentially frozen in place. It holds its position in memory so you can return quickly, but it executes no code and consumes almost no battery.
Swiping it away clears it from memory entirely. The next time you open it, your phone has to load it from scratch, which briefly uses more CPU than simply resuming a frozen app would.
The apps actually draining your battery in the background are not sitting in your recent apps list. They are the ones the operating system has explicitly permitted to keep running, or the ones that have found ways to keep themselves awake.
How Background Activity Actually Works
Both Android and iOS use a system of background modes that determine what an app can and cannot do when it is not on screen.
On iOS, the rules are strict. Apple allows apps to perform specific, declared background tasks: playing audio, tracking location, receiving push notifications, and completing downloads the user started. An app that has not declared a legitimate background mode gets suspended immediately when you leave it. It cannot run arbitrary code in the background. This is the main reason iPhones are known for strong battery management.
On Android, the rules have historically been looser. Google has tightened background restrictions significantly in recent versions, but enforcement varies across devices and manufacturers. Samsung, Xiaomi, and others layer their own battery policies on top of Android's baseline, which is why the same app can behave differently on different phones.
What Actually Keeps Apps Awake
The real drain comes from specific mechanisms that prevent apps from sleeping properly.
Wake Locks
A wake lock is a signal an app sends to the operating system asking it to keep the processor running even when the screen is off. Legitimate uses include music apps that need to decode audio, and navigation apps that need to keep tracking location.
The problem is that many apps hold wake locks for no good reason. A social media app might hold a wake lock while syncing your feed in the background, keeping the CPU running long after a simple push notification would have done the same job.
Google recently introduced consequences for this behaviour, defining excessive wake lock use as holding the processor awake for more than two hours on average while the screen is off in more than five percent of user sessions. Apps that cross this threshold now face Play Store penalties. It is a meaningful step, but apps already on your device may already be doing this.
Background Refresh and Polling
Some apps wake themselves up periodically to check for new content. A news app refreshing every fifteen minutes. A weather app checking conditions hourly. A social media app pre-loading your feed so it appears instant when you open it.
Each wake event costs battery even if the individual cost is small. Ten apps waking up four times per hour adds up to forty processor activations, forty radio wake events, and forty network requests per hour. None of them feel significant individually. Together they quietly drain your battery across the day.
Location Access
GPS is one of the most power-hungry components in any phone. An app accessing your location continuously in the background keeps the GPS or cell tower triangulation active at all times.
Navigation apps genuinely need this. A shopping app or a social media platform does not. Many apps request continuous location access beyond what their core function requires, and they keep it unless you specifically revoke it.
Push Notifications and Persistent Connections
Receiving a push notification itself is extremely battery-efficient. Both Apple and Google operate centralised notification servers so that all apps deliver notifications through a single shared connection rather than each app maintaining its own.
The drain comes when apps bypass this system. Some messaging apps, VOIP services, and social platforms maintain their own persistent connections to guarantee lower latency or support features the standard notification system does not offer. Each persistent connection keeps a radio active and adds a small but continuous power draw throughout the day.
Why Some Apps Are Worse Than Others
Not all apps drain battery equally. The difference comes down to design choices and business incentives.
Social media apps are consistently among the worst offenders. Facebook, Instagram, TikTok, and similar platforms have strong incentives to stay active in the background. The more they can preload content, monitor your behaviour between sessions, and track engagement patterns, the more effectively they can optimise advertising and retention. Their background activity serves their business model, not your battery.
Poorly optimised apps from smaller developers often drain battery through carelessness rather than intention. An app that forgets to release a wake lock, or that polls for updates far more frequently than necessary because no one tuned the interval, drains your battery just as effectively as a deliberately aggressive app. The outcome is identical even when the intent is not.
Well-optimised apps like Spotify, Google Maps, and Apple's own applications tend to use background resources efficiently. Spotify keeps audio playing without an excessive wake lock footprint. Google Maps tracks location efficiently using the platform's fused location provider rather than forcing continuous GPS. These apps are built by teams with dedicated platform engineers who understand Android and iOS internals.
Live service games are a mixed case. A game that truly suspends when you leave it costs nothing. A game that checks for daily rewards, sends engagement reminders, and pre-downloads content behaves more like a social media app in terms of background drain.
How Android and iOS Handle This Differently
iOS takes a gatekeeping approach. Apple decides which background modes exist, and developers must explicitly declare which ones their app uses. An undeclared background task simply does not run. The operating system enforces this at a technical level. This rigidity occasionally frustrates developers, but it explains why iPhones tend to manage background battery consistently well.
Android takes a permission-based approach that has tightened through recent versions. Android 13 and later include a power tracker that monitors background services and alerts users when an app has consumed more battery than expected. Google's Doze mode progressively restricts background activity the longer the phone sits unused. Apps can request exemption from Doze, which legitimate apps sometimes need, but the exemption is visible and can be revoked.
The difference shows up most clearly on budget Android devices, where manufacturers sometimes apply aggressive battery restrictions that break legitimate background functionality. A messaging app that stops delivering notifications when the screen is off is the most common example. Getting the balance right between restricting bad actors and preserving legitimate background activity is genuinely difficult, and different manufacturers handle it with varying success.
What You Can Actually Do
Understanding how background activity works makes the standard advice far more actionable.
Check battery usage stats rather than closing recent apps. On iOS, go to Settings, Battery, and review usage by app over the last week. On Android, go to Settings, Battery, Battery Usage. The apps at the top of that list are where your battery is actually going. Target those, not the frozen apps in your recent list.
Restrict location access to While Using only. On both platforms, changing location permission from Always to While Using cuts the single largest source of unnecessary background drain for most users. Review which apps have permanent location access and question whether each one genuinely needs it.
Disable Background App Refresh for non-essential apps on iOS. Go to Settings, General, Background App Refresh. News apps, social media, and shopping apps do not need to refresh while you are not using them. Turn the setting off for every app that you are comfortable checking manually when you open it.
Restrict background usage for aggressive apps on Android. Go to Settings, Apps, select the offending app, and look for Battery or App Battery Usage. Setting an app to Restricted prevents it from running background jobs. This is the right choice for apps you open intentionally rather than ones that need to deliver real-time content to you.
Let the adaptive battery features do their job. Both platforms have adaptive battery systems that learn your usage patterns and automatically restrict background activity for apps you rarely use. Whitelisting every app from battery optimisation defeats the purpose entirely. Leave the system to manage the apps you do not actively supervise.
The practical reality is straightforward. Most background battery drain comes from a small number of apps behaving badly. Identifying those apps through your battery usage settings and restricting their background access solves most of the problem without touching apps that genuinely need background activity to serve you well.
Discussion (0)
Be the first to comment.