Open your recent apps screen and you’ll likely see far more apps listed than you actually used in the last hour. Most of these are sitting in a suspended state, using minimal resources.
A genuine subset are actively running processes in the background, checking for updates, syncing data, or tracking your location. These are the ones actually worth your attention.
Stopping unnecessary background activity is one of the more effective things you can do for both battery life and overall performance, but it’s worth doing selectively. Restrict the wrong apps and you’ll notice missed notifications; restrict nothing and you’re leaving real battery and performance on the table.
Understand What “Running in the Background” Actually Means
Not every app shown in your recent apps list is genuinely active. Android suspends most apps almost immediately after you leave them, keeping them cached in memory so they reopen instantly, but not consuming processing power or battery while suspended.
True background activity is different: an app actively checking a server, tracking location, or playing audio while you’re using something else. This is what actually costs battery and performance, not simply having many apps listed in your recent apps screen.
This distinction matters because swiping away every app from recent apps doesn’t meaningfully help battery life for apps that were already properly suspended, and can actually hurt it slightly, since relaunching from scratch uses more power than resuming a cached app.
Find Out Which Apps Are Actually Running in the Background
Rather than guessing, check what’s genuinely active right now.
- Go to Settings, then Battery, then Battery Usage.
- Look at the breakdown showing screen time versus background time for each app.
- Apps with high background time relative to how little you actually open them are your real targets.
This is a far more useful starting point than restricting apps based on assumption, since it shows you exactly which apps are consuming resources while closed, rather than which apps you simply have installed.
Restrict Background Activity Per App
Once you’ve identified specific apps worth restricting, the process is straightforward.
- Go to Settings, Apps, select the specific app.
- Tap Battery, or Battery Usage.
- Set it to Restricted.
A restricted app still works normally when you open it directly. It simply can’t run background processes or receive push updates between uses, which for many apps, shopping apps, games, news apps you check manually, has no real downside.
Avoid restricting messaging apps, delivery or ride-share apps, or anything you specifically rely on for time-sensitive notifications, since restriction will genuinely delay those.
Check Manufacturer-Specific Background App Managers
Stock Android’s restriction setting is only part of the picture on many phones. Manufacturers frequently layer their own, often more aggressive, background management system on top.
- Samsung has a separate Sleeping Apps and Deep Sleeping Apps list under Battery and Device Care, distinct from stock Android’s restriction setting.
- Xiaomi’s MIUI includes Autostart permissions and its own Battery Saver per app, both under the Security app, that can override stock Android settings entirely.
- OnePlus, Oppo, and Vivo include similar aggressive app management layers requiring separate configuration from stock settings.
If your phone is from one of these manufacturers, checking only stock Android’s settings won’t give you the full picture.
Using Adaptive Battery Instead of Manual Restriction
Rather than manually restricting every app individually, Android’s Adaptive Battery feature automatically learns which apps you use regularly and restricts the rest based on actual usage patterns, using on-device machine learning.
Check Settings, Battery, Adaptive Battery, and confirm it’s enabled. For most people, letting this run alongside a few manual restrictions for known problem apps is more practical than manually managing every single installed app individually.
Reviewing Auto-Start Permissions Separately From Background Restriction
Background restriction controls whether an app can run once it’s already been launched at least once. A separate setting, Auto-Start, controls whether an app can launch itself automatically after your phone boots up or after being force-closed, without you opening it manually first.
This is a more aggressive form of background activity, worth reviewing separately, particularly on phones with a dedicated Auto-Start permissions screen, commonly found on Xiaomi, Oppo, Vivo, and some Huawei devices under their respective Security or Phone Manager apps.
Understanding the Trade-Off With Widgets
Live-updating widgets on your home screen, weather, stock prices, sports scores, require the underlying app to periodically wake and refresh, even if you’ve restricted its general background activity through the app settings covered above.
If you’ve restricted an app but still have its widget on your home screen, the widget may not update as expected, or may continue draining some battery despite the restriction, depending on how that specific app implements its widget. Removing widgets for apps you’ve restricted avoids this inconsistency.
Reviewing Location Permissions Alongside Background Restriction
Background restriction and location permissions are separate settings that compound each other. An app with both unrestricted background access and “Allow all the time” location permission is genuinely one of the more resource-intensive combinations a phone can have running.
Check Settings, Location, App Permissions, alongside battery restriction settings for the same apps. Setting location to “Allow only while using the app” for anything you’ve also restricted in the background covers both angles of the same underlying problem.
What Happens on Phones With Very Limited RAM
On budget phones with 3GB of RAM or less, background app management matters more than on a flagship with 8GB or 12GB, since limited memory means Android has to more aggressively decide which apps to keep cached versus fully close.
Restricting background activity for apps you rarely use frees up memory for apps you do use to stay properly cached rather than being killed and needing a full relaunch each time you switch back to them.
Checking Data Usage as a Secondary Signal
Beyond the Battery Usage screen, checking Settings, Network & Internet, Data Usage, sorted by app, gives a complementary view of background activity, specifically for apps using meaningful background data even if their battery impact seems modest.
An app using significant background data without a corresponding reason you can identify is worth investigating and likely restricting, even if it didn’t stand out clearly on the battery screen alone.
Reserving Full Background Freedom for a Genuinely Small List
It’s worth being intentional about which apps get to keep full, unrestricted background access, rather than defaulting to leaving everything unrestricted out of caution. A genuinely short list, your primary messaging app, email if you need real-time delivery, and perhaps navigation, covers most people’s actual needs.
Everything else benefits from restriction without meaningful downside, and treating unrestricted access as something to grant deliberately, rather than the default state, keeps this list from growing back over time.
Do gaming apps need special treatment compared to other background restriction candidates?
Games you play actively benefit from staying unrestricted, since many use background time to preload assets or sync progress to the cloud between sessions, and restricting this can cause slower loading or lost progress syncs. Games you’ve stopped playing but haven’t uninstalled are safe, often high-value, restriction candidates.
Comparing Restriction to Uninstalling Rarely Used Apps Entirely
For apps you genuinely haven’t opened in months and don’t have a clear plan to use again, it’s worth asking whether restriction is even the right tool compared to simply uninstalling the app entirely. Restriction still leaves the app taking up storage and occasionally still checking in during Doze maintenance windows, however minimally.
A quick review of your full app list, sorted by last used date if your phone’s app drawer or Settings screen offers that view, often reveals several apps that would be better candidates for uninstalling outright rather than just restricting, freeing up storage as a side benefit alongside the battery and performance gains from removing background activity entirely.
Does clearing an app’s cache reset its background restriction setting?
No, clearing cache only removes temporary stored files and doesn’t touch permission or battery restriction settings, which are stored separately. Only clearing the app’s full Data, or uninstalling it entirely, resets restriction status back to default.
Can I set a schedule so restrictions only apply at certain times, like overnight?
Stock Android doesn’t offer time-based scheduling for background restrictions directly, it’s an always-on or always-restricted setting per app. Some manufacturer battery management tools include a scheduled power-saving mode that indirectly achieves something similar by applying broader restrictions during set hours.
What Happens When You Reinstall a Previously Restricted App
If you uninstall and later reinstall an app you’d previously restricted, it comes back with Android’s default background behavior rather than remembering your prior restriction setting, since uninstalling removes all app-specific settings along with the app itself.
This is worth knowing if you’re troubleshooting an app by reinstalling it, don’t assume your previous restriction is still in place afterward, and it’s a good moment to reconsider the restriction, since some issues that prompted an original restriction may have been fixed by an app update in the meantime.
Frequently Asked Questions
Does force-stopping an app achieve the same thing as restricting its background activity?
Not quite. Force-stopping fully terminates the app immediately, but it can restart itself the next time you open it or, for some apps, automatically restart in the background unless auto-start is also disabled. Restriction is a more permanent, ongoing setting rather than a one-time action.
Will restricting background apps break push notifications entirely?
For apps using Google’s standard push notification system, Firebase Cloud Messaging, restriction generally doesn’t block notifications, since these are delivered through a system-level channel rather than the app’s own background process. Apps using older polling-based notification methods are more likely to see delayed notifications after restriction.
Is there a way to restrict multiple apps at once instead of one at a time?
Some manufacturer battery management tools, Samsung’s Battery and Device Care in particular, let you bulk-select multiple apps and apply Sleep or Deep Sleep status to all of them simultaneously, which is faster than stock Android’s one-app-at-a-time approach.
Checking Whether Doze Mode Already Handles This Automatically
It’s worth understanding that Doze Mode, covered in more depth in guides about delayed notifications, already restricts background activity system-wide once your phone has been stationary with the screen off for a while, independent of any manual restriction you apply.
This means manual restriction and Doze work together, not against each other. Manual restriction is most valuable for the window when your phone is actively in use but the app itself is in the background, since Doze doesn’t apply while you’re actively using the phone for something else.
How This Differs When Your Phone Is Connected to Android Auto or a Smartwatch
Apps restricted from background activity can behave differently when your phone is connected to Android Auto or paired with a smartwatch that relies on that app for notifications or data, since these connected experiences sometimes need background access specifically to function correctly.
If you’ve restricted an app and notice it’s not showing up properly on your smartwatch or through Android Auto anymore, checking whether that specific app needs an exception for connected device functionality, separate from general phone notifications, is worth testing before assuming something else broke.
Setting Up a Recurring Review Rather Than a One-Time Cleanup
New apps you install don’t inherit restrictions from apps you’ve already configured, each starts with Android’s default battery behavior until you review it individually. A quick check of Battery Usage every few months, rather than treating this as a single one-time task, catches new apps that have started accumulating unnecessary background activity since your last pass.
This is a much smaller task than the initial cleanup, usually just reviewing whatever’s changed since your last check, and it keeps the benefits from this guide from eroding gradually as your app list changes over time.
Frequently Asked Questions, Continued
Does restricting an app affect its ability to receive calls if it’s a calling app?
For your default Phone app specifically, this is generally protected by Android’s system-level design and not something you can meaningfully restrict, since incoming calls need to work regardless. For a secondary VoIP calling app, restriction can genuinely delay incoming call notifications, so avoid restricting any app you rely on for calls.
Why do some apps ask me to manually re-enable background access after every update?
This can happen if an app’s update changes its package signature or requests a new permission tied to background behavior, which sometimes resets certain settings depending on your specific Android version’s update handling. It’s an occasional annoyance rather than a sign anything is wrong.
What Happens to Music and Media Apps When Restricted
Restricting background activity for a music or podcast app you actively use for playback causes real, immediate problems, since these apps fundamentally need to keep running while your screen is off to continue playing audio. Never restrict an app you use for active media playback.
This is worth stating explicitly, since it’s an easy mistake when working through a list of apps quickly without considering each one’s actual function. Media apps are a clear exception to general background restriction advice.
Checking Whether an App’s Background Activity Is Actually the App’s Fault
Sometimes what looks like one app misbehaving in the background is actually a shared library or SDK, like an advertising or analytics framework, embedded within several different apps you have installed, each contributing a small amount of background activity that adds up.
This is genuinely difficult to identify directly from Android’s settings alone, but if you notice multiple, seemingly unrelated apps all showing surprisingly high background activity around the same time, this shared-component pattern is worth suspecting, and restricting the apps individually remains the practical fix even without pinpointing the exact shared cause.
How This Interacts With Digital Wellbeing’s App Timers
Digital Wellbeing’s app timers, which limit how long you can actively use an app per day, are a separate feature from background restriction entirely, and don’t affect background activity at all. An app can be fully restricted from background activity while having no usage timer, or have a strict usage timer while still running freely in the background between your active sessions.
If your goal is reducing overall phone usage generally rather than specifically saving battery, Digital Wellbeing’s timers, covered in more detail in dedicated guides about that feature, are the more relevant tool, separate from anything covered in this guide about background restriction specifically.
Conclusion
Stopping unnecessary background activity is genuinely worth doing, but selectively, based on actual usage data rather than restricting everything indiscriminately.
Checking Battery Usage first to identify real offenders, then restricting those specific apps while leaving Adaptive Battery to handle the rest automatically, gets most people meaningfully better battery life without breaking notifications they actually rely on.
A short recurring review every few months, rather than a single one-time cleanup, keeps this from quietly eroding as new apps get installed and start accumulating their own unnecessary background habits over time.
If you think there’s been a mistake here, please do let us know by commenting on this post or Contact Us. And a member of our Content Integrity Team will review this decision with you.
