Background Activity, Battery and Privacy on Android

We've all been there: your phone starts getting warm in your pocket, or you notice your battery has dropped 15% in an hour while you weren't even using it. Usually, the culprit is an app running in the background. But beyond battery drain, background activity is a huge privacy concern. If an app is "awake" while your screen is off, it could be doing anything—tracking your location, listening for "trigger words," or syncing your personal data to a server when you aren't looking.

Why background activity is a privacy issue

Privacy isn't just about what an app can see; it's about when it sees it. When you have an app open on your screen, you’re aware it's running. But background activity happens in the shadows. I once found an old "deals" app on my phone that was checking my location every 5 minutes, 24 hours a day, just so it could send me a notification if I walked near a specific coffee shop. That is a massive amount of personal data being collected without any active interaction.

Furthermore, apps running in the background can "collaborate" with each other. If multiple apps from the same developer are running, they can share a profile of your day—when you woke up (based on when you first moved your phone), where you went, and how long you stayed there. Restricting background activity isn't just about making your phone last until bedtime; it's about putting a "DO NOT DISTURB" sign on your personal life when you aren't actively using your device.

Restricting background access per app

Android has generic battery "optimization" settings, but I prefer the surgical approach. You can tell a specific app to basically "die" the moment you swipe it away from your recent apps. Here’s how I do it on my Pixel (Android 14):

1. Long-press the app icon on your home screen and tap the "i" (App info) icon.
2. Tap on Battery.
3. Choose Restricted.

When you set an app to "Restricted," it won't be allowed to run in the background at all. This is perfect for apps you use rarely, like a flight-booking app or a specific store's app. The caveat here is that you might stop getting notifications from that app. For me, that's usually a feature, not a bug. If I'm not looking for a new pair of shoes right now, I don't need a background process running just to tell me about a 10% sale. However, don't do this for your alarm clock or your messaging apps, or you'll miss your wake-up call and your texts!

Samsung Sleeping Apps and Xiaomi MIUI

Samsung and Xiaomi are much more aggressive with background management than Google is. On a Samsung Galaxy, there's a feature called "Deep sleeping apps." These are apps that will never run in the background. Samsung's software is smart enough to suggest apps for this list if you haven't opened them in a while. I love this feature; I currently have about 45 apps in "Deep sleep," and it definitely helps with my S23's longevity.

Samsung path: Settings > Battery > Background usage limits > Deep sleeping apps.

Xiaomi's HyperOS (formerly MIUI) is "notoriously" aggressive. It often kills background apps so quickly that people complain they aren't getting emails. If you’re on a Xiaomi and you want an app to stay private but functional, you often have to go into the "Battery saver" settings for that specific app and select "No restrictions." It's a bit of a counter-intuitive dance, but it gives you total control over what's allowed to breathe when the screen is off.

Foreground service notifications

Have you ever seen a notification that says something like "[App Name] is running in the background" and you can't swipe it away? That is a "Foreground Service." Usually, these are things like a music player, a fitness tracker recording a run, or a VPN. Google requires apps to show this notification so they can't hide their activity from you.

This was an "honest" eye-opener for me: I once saw a "Flashlight" app showing a foreground service notification. Why would a flashlight need a background service? It turns out it was using that persistent connection to maintain a data link for ads. If you see a persistent notification from an app that shouldn't be active, it's a huge red flag. You can try to "Force Stop" it, but if it keeps coming back, that app is poorly behaved and should probably be uninstalled.

Auditing what's running

If you want to see exactly what's happening right now, you need to use the "Running Services" menu. This is hidden inside the Developer Options, which sounds scary but isn't. To enable it, go to Settings > About phone and tap "Build number" seven times. Now, go to Settings > System > Developer options > Running services.

Looking at this list is fascinating. You'll see things like "Google Play services" (normal) alongside random apps you haven't opened in days. Last time I checked mine, I found a "smart home" app taking up 120MB of RAM even though I haven't used it for a week. Seeing the numbers—like "Started 142 hours ago"—really puts into perspective how much junk is just sitting there in your phone's memory, potentially collecting data.

Force-stopping vs disabling

There’s a difference between "Force stopping" and "Disabling." When you hit Force stop, the app dies immediately, but it can be woken up again by the system or by another app. It's a temporary fix. I use this when an app is acting up or when I've finished using something I know is a battery hog (like Uber or a heavy 3D game).

Disabling (or "Uninstalling" for third-party apps) is the permanent solution. If you have "bloatware" on your phone that you can't delete—like a carrier-branded app—disabling it is your best bet. It removes the app from your drawer and prevents it from ever starting. It's not a perfect fix because it still takes up space in your storage, but from a privacy and battery perspective, it’s as good as gone. Just be careful not to disable anything related to "System" or "Google," or you might find your phone won't boot or your App Store stops working.