I pulled up my phone’s battery stats last week and noticed something odd. Apps I hadn’t opened since morning were still listed as active in the background. No notifications, nothing visible on screen, yet they were burning battery anyway. I started digging into how Android handles apps once you leave them. Turns out, a single setting inside a hidden menu puts a hard cap on how many processes your phone keeps alive.
What closing an app actually does
Swiping away doesn’t mean gone
Whenever you press Home or switch to another app, the one you left behind doesn’t close. Android keeps that process loaded in memory as a cached state, ready to resume if you return to it. The apps you actually swipe away from your recent apps screen do get killed, but the apps you leave during a normal day never get swiped. You just move on, and Android holds onto them. The system treats empty memory as wasted space, so it fills it with whatever you used recently.
Before long, your phone may be holding onto a dozen or more cached processes at any given time, all from apps you finished using hours ago. On top of that, many apps register scheduled tasks through Android’s background frameworks that run independently of the cached process. These tasks wake your processor to sync data, refresh content, or upload analytics, and swiping the card away doesn’t stop them.
And if you’ve tried fixing this with a RAM booster or cleaner app, you may have made it worse. When a cleaner force-kills an active background service, Android notices the service is gone and relaunches it automatically. That restart loop ends up burning more battery than leaving the app alone would have. The cached process pile-up is the part you can fix with a single setting. Scheduled tasks need a different approach, and both solutions live in menus Android keeps tucked out of sight.
How to stop Android from caching old apps
Fewer cached apps, less wasted memory
The setting you need is Background Process Limit, tucked inside Developer Options. To unlock that menu, open Settings, go to About Phone, and tap Build Number seven times. You’ll need to enter your PIN or password to confirm. Once Developer Options appears in your main settings list, open it and scroll down to the Apps section. Background Process Limit is in there, set to Standard limit by default.
That default mode lets Android decide how many cached processes to keep on its own. Tap the setting, and you’ll see options ranging from four processes down to none at all. Setting it to two or three is the practical sweet spot. Your notifications and messaging apps will keep working because system-level services handle them independently of any cached process. Spotify won’t stop mid-song and Google Maps won’t cut out during navigation either, since both run as foreground services that this cap never touches.
Going all the way to No Background Processes sounds appealing, but it creates problems you’ll notice fast. If you leave a banking app to grab a two-factor code from your messages, your session gets killed before you return. Every app switch becomes a full reload. Some phones also reset this cap after a reboot, so check whether the limit reverts to standard if your battery drain suddenly returns.
Restricting apps individually instead
Not every app deserves background access
Capping cached processes doesn’t stop apps from running scheduled background tasks. Those need to be handled on a per-app basis. Long-press any app icon on your home screen, tap the small info button, then open the Battery menu. Switching that control from Optimized to Restricted cuts off that app’s ability to run background jobs entirely.
Once locked down, an app can’t sync data, check your location, or ping remote servers while you aren’t using it. Everything stays completely frozen until you open it. Shopping apps, food delivery services, and games that run tasks overnight make great candidates. I went through my app list and restricted about fifteen apps I only open once or twice a month. The drop in overnight standby drain showed up within a single day.
If you aren’t sure which apps to target first, check your Battery Usage screen to see what ran while you were asleep. Samsung users can also drop several apps at once into the Deep Sleeping Apps list inside Battery settings. Unlike the developer setting, these individual restrictions survive every reboot, so you only need to set them once.
What to check before restricting everything
Between the process limit and per-app restrictions, you get two layers of background control that Android never turns on for you. Both take less than a minute to set up, and using them together stops unwanted activity from every angle. Just make sure your alarm, messaging, and email apps stay on their default settings. Saving a few percent of battery overnight isn’t worth sleeping through a morning alarm or missing an urgent text.