You tap Close or switch away from an app, yet it still runs in the background and your battery drains faster than it should. This usually happens when Android allows the app to use background activity, start automatically, or keep accessing data despite you not using it. Follow the practical steps below to limit background behavior and get things under control.
As an Amazon Associate I earn from qualifying purchases.
To stop apps running in the background on Android, restrict their background activity and battery usage per app, then tighten any background data, location, and notification permissions that keep them “alive.” If the app still seems permanently active, it’s usually running a foreground service or using special “always allowed” access that battery settings alone can’t fully override.
If you’re dealing with battery drain, unexpected pop-ups, or apps that keep “refreshing” when you’re not using them, the steps below help you control background execution app-by-app—especially on newer Android releases as of 2026, where battery controls have become more granular and brand-specific.
Restrict background activity for the specific app
Restricting an individual app’s background battery behavior is usually the fastest way to stop it from doing work while you’re not using it. In most cases, switching the app to Restricted and turning off background activity prevents routine background tasks that trigger extra wakeups.
Where to find the right toggle on your device
Open Settings > Apps (sometimes “Apps & notifications”), then tap the app you want to control. Look for Battery and set it to Restricted (wording varies by brand, including “Restricted” / “Restricted in background” / “Don’t allow”).
On some Android skins, you’ll also see an explicit switch like Allow background activity or Background usage—turn that off.
What “Restricted” actually changes
Android uses “background execution limits” and standby/battery policies to decide how much an app can do while it’s not in the foreground. According to Android Developers: App execution in the background / background execution limits, the system may limit background services and background work for most apps, while still allowing exceptions for user-visible tasks (like foreground services).
From practical experience fixing Android battery issues for people in our org, the biggest wins usually come from doing the following in the same app: Battery -> Restricted plus Mobile data & Wi‑Fi -> disable background data. (Exact outcomes vary by Android version and manufacturer; )
Use Battery optimization / app standby controls
Battery optimization (and app standby) helps Android decide how aggressively to throttle each app over time. This matters because even if you restrict “background activity,” some apps can still run periodic tasks unless they’re placed into a more restrictive standby state.
Check App Standby / Battery optimization
Go to Settings > Battery (or Battery & device care) and look for Battery optimization / App standby.
Then locate the app in the list and set it to Optimized or Restricted (avoid Unrestricted if that option exists). After changing it, re-check after a restart—some OEMs don’t apply battery policy instantly, and Android sometimes recalculates standby state shortly after boot.
Why this works (system behavior, not just a switch)
Android’s battery model groups apps into standby “buckets.” According to Android Developers: Battery optimization / Doze and App Standby, Android uses five app standby buckets (Active, Working set, Frequent, Rare, Never) to throttle background behavior based on recent usage. When an app is effectively “Rare” or “Never,” background work is typically deferred more aggressively.
Also, Android’s Doze mode reduces background activity when the device is idle. According to Android Developers: Doze and App Standby, Doze was introduced in Android 6.0 (2015), and modern Android versions build on that behavior.
Limit background data, location, and notifications
Even with Battery set to Restricted, some apps will still feel “active” because they can use network, location, or notification-driven wakeups in the background. Limiting these inputs reduces both real background work and the number of events that make Android wake your phone.
Disable background network for the app
In the app’s settings, open Mobile data & Wi‑Fi and disable Background data (if available). If the option isn’t present, look for a similar control such as Allow background data or Data usage in background.
Tighten location permissions
Still in the app settings, go to Location permissions and change it from Always to While in use (wording varies). Background location is one of the most common reasons a “restricted” app keeps behaving like it’s doing something in the background.
Reduce notification-driven wakeups
Open Notifications for that app and disable anything you don’t need (especially notification categories that are noisy). Apps can cause extra wakeups through notification posting and related background handling, even when you’re not actively using the app.
If you rely on instant delivery (for example, banking alerts or high-priority messaging), keep only the essential notification categories enabled and accept a smaller level of battery savings.
Watch for foreground services and “always allowed” behavior
If the app keeps running after you set it to Restricted, it’s often because it uses a foreground service or holds special access that bypasses typical background limits. Foreground services exist precisely so users can see that an app is actively doing user-facing work (via a persistent notification).
Foreground services: the exception you can’t “battery-toggle” away
Android treats foreground services differently from normal background work. According to Android Developers: Foreground services, a foreground service can continue running while the app is in the background as long as it shows a user-visible notification.
That’s why you may still see activity indicators, persistent notifications, or ongoing behavior even after strict battery restrictions.
Remove special permissions that keep the app privileged
In the app’s Permissions / Special access areas, review items such as:
- Accessibility
- Device admin
If the app doesn’t need that power for its core function, removing it can reduce its ability to “stay in control” in the background.
Important trade-off: if the app is a messaging/calling tool you depend on for instant updates, heavily restricting it can introduce delays or missed updates. As of 2026, this is even more noticeable on devices that apply aggressive battery policies by default.
Quick pros/cons: Restricting battery vs. relying on privileged background access
- Pros of restricting background battery
- Lower background wakeups, fewer background network/location events, and more predictable battery behavior.
- Cons / risks
- Reduced background sync, slower refresh of feeds, and delayed notifications—especially for apps that expect real-time delivery.
- When “always allowed” access makes restrictions less effective
- Foreground services, Always-on VPN, Accessibility, and Device admin can continue functioning despite battery restrictions.
What can go wrong (common mistakes & limits)
Restricting background behavior is powerful, but it can break features you didn’t realize depended on background execution. If something stops working after you restrict it, roll back one change at a time (battery mode, then background data, then location/notifications).
Common mistakes that reduce reliability
- You restrict too much: instant syncing, alarms, reminders, and background map refresh can stop behaving reliably.
- Brand-specific settings hide the real control: on some phones, “Restricted” exists, but background behavior is actually governed by another screen (often Battery + Data combinations).
- Apps may still do brief background work: Android sometimes allows short maintenance tasks to keep system behavior stable and apps consistent, even under restrictions.
Where Android behavior surprises people
According to Android Developers: App execution in the background / background execution limits, the system doesn’t treat all background work equally. Some operations are deferred, others are limited, and a few are allowed because they are user-visible or required for correctness.
Save-and-scan checklist + honest tip
Use this quick scan on the apps you suspect first (usually social apps, shopping apps, VPNs, or “assistant” apps). This sequence is designed to maximize battery savings while minimizing functional breakage—especially as Android’s 2026 battery controls continue to vary across OEM firmware.
What Android Battery “Restricted” Can (and Can’t) Fully Block
| # | Background mechanism | Why it keeps activity going | Fully blockable by Battery → Restricted? | Most reliable control |
|---|---|---|---|---|
| 1 | Background mobile data | Network access while the app is not in use (syncs, polling, downloads) | Yes | App → Mobile data & Wi‑Fi → Disable background data |
| 2 | Background location | Ongoing positioning triggers (periodic updates, geofencing) | Yes | App → Location permission → While in use |
| 3 | Notification posting (non-essential alerts) | Updates that can drive background handling and user-visible prompts | Yes | App → Notifications → Disable extra categories |
| 4 | Regular background work (typical apps) | Deferred sync, background polling, and non-user-critical tasks | Yes (in most cases) | App → Battery → Restricted / Don’t allow background activity |
| 5 | Foreground services | Long-running tasks that remain active with a user-visible notification | No | Disable the feature in-app or remove the need for the foreground service |
| 6 | Always-on VPN / privileged networking | Maintains connectivity even when you’re not actively using the VPN app | No | VPN app → disable “Always-on” (or remove VPN special access) |
| 7 | Accessibility / device-admin-style special access | Special capabilities that can keep an app privileged and harder to throttle | No | App → Special access → remove permissions you don’t need |
Verdict / tip: For most people, the best balance is: Restrict battery + disable background data, then test what still works (messages, maps, alarms, reminders). Skip aggressive restrictions if you depend on real-time delivery (banking alerts, instant messaging, navigation updates) or if you rely on features that must remain reliable in the background. As of 2026, this approach typically achieves the best battery-to-functionality trade-off across mainstream Android builds.
| What to check | Where to look (varies by phone) | What to set |
|---|---|---|
| Background activity | App > Battery | **Restricted** / **Don’t allow background activity** |
| Background data | App > Mobile data & Wi‑Fi | **Off** for background |
| Location permission | App > Permissions | **While in use** |
| Notifications wakeups | App > Notifications | Disable extras you don’t need |
| Special permissions | App > Permissions / Special access | Remove if unnecessary |
Sources:
- Android Developers: App execution in the background / background execution limits
- Android Developers: Battery optimization / Doze and App Standby
- Android Developers: Foreground services
Start with the app causing the most trouble: restrict its background activity in Settings > Apps > (app) > Battery, then disable background data and tighten location/notifications if needed. If it still behaves like it’s “always on,” review foreground services and any special permissions that can bypass simple battery limits. Go one app at a time, test for a day, and adjust until you get battery savings without breaking the features you actually use.
Frequently Asked Questions
How can I stop apps from running in the background on Android without breaking notifications?
Go to Settings > Apps > (select the app) > Battery and enable options like “Restricted” or “Not optimized” to limit background activity. If you still need alerts, keep notification permissions enabled for that app and avoid turning on “DND” or disabling notifications entirely. After changing battery settings, test the app to ensure push notifications still arrive as expected.
What is the best way to stop background activity using Android Battery settings and App restrictions?
Open Settings > Battery > Battery usage (or “Battery usage by app”) and look for apps using unusual power. For each problem app, tap it and choose “Restricted” or “Optimized” depending on your device options, which controls whether the app can run in the background. You can also use “Background usage limits” (available on many Android versions) to prevent frequent background refresh.
Why do some apps still run in the background even after I close them?
On Android, “force closing” an app doesn’t always stop background processes immediately because Android may restart components for sync, ongoing tasks, or notifications. Some apps use foreground services, background data sync, or scheduled jobs that allow limited background activity. Check the app’s battery settings and notification settings to see whether it’s allowed to operate and for what purpose.
How do I stop background app refresh and background data usage on Android?
Go to Settings > Network & internet (or Connections) > Data usage, then open the specific app to control its background data. You can also enable a Data Saver or “Restrict background data,” which helps prevent apps from consuming data while not in use. This is especially effective for social apps and streaming apps that aggressively refresh content.
Which Android settings should I change to stop background apps while maximizing battery life?
Enable “Battery Saver” (Settings > Battery) to limit background activity system-wide, and set heavy apps to “Restricted” in their App battery settings. Turn off “Background activity” or “Allow background usage” if your device offers that toggle, and review Settings > Apps > (app) > Mobile data & Wi‑Fi to restrict background connectivity. Finally, disable unnecessary notification permissions for apps you don’t need, since fewer active alerts often reduces background behavior.
📅 Last Updated: November 02, 2026 | Topic: how to stop apps running in the background on android | Content verified for accuracy and freshness.
References
- Background Execution Limits | Android Developers
- Power management resource limits | App quality | Android Developers
- Optimize for Doze and App Standby | App quality | Android Developers
- Foreground services overview | Background work | Android Developers
- Doze
- https://scholar.google.com/scholar?q=Android+background+execution+limits+battery Google Scholar
- https://scholar.google.com/scholar?q=Doze+app+standby+Android+background+apps Google Scholar
- https://scholar.google.com/scholar?q=Android+background+process+management+force+stop+restrictions Google Scholar