Empty memory is wasted memory
The habit of opening the recents view and swiping everything away comes from desktop computers, where a running program really does consume resources continuously. Android works differently: an app in the background is usually frozen rather than running, and keeping it in memory is what makes it reappear instantly. Free memory does nothing for you, which is why the system deliberately does not leave much of it.
What is actually happening
When you leave an app, Android normally stops it executing and keeps its state in memory. It costs nothing while it sits there, and returning to it is nearly free. When memory runs short, the system evicts whatever it judges least useful, entirely on its own, and it is better at that judgement than a person swiping cards.
Swipe the card away and you throw that cached state out. The next time you open the app it is a cold start: reading from storage, rebuilding the interface, reconnecting, re-authenticating. That costs both time and battery, which is the opposite of the intended effect. Worse, some apps treat being killed as a reason to restart themselves, so the card reappears and the cycle repeats.
Advertisement
What actually helps
- Find the app that is genuinely misbehaving Battery settings list what has used power in the background. One offender is the usual story, not thirty innocent cards.
- Restrict that one app's background activity Per-app battery settings let you restrict a single app without touching anything else. This is the targeted version of what swiping attempts.
- Uninstall what you do not use An app that is not installed cannot wake up, sync, or hold the microphone. This is the only real way to stop background work.
- Leave a few gigabytes of storage free A nearly full phone slows down measurably, because the filesystem and the app cache both need room to work.
- Restart the phone occasionally Genuinely stuck processes and leaks are cleared by a reboot, which is the honest version of what people hope swiping does.
- Do not disable background activity for the apps you rely on Restricting a messaging or alarm app is how notifications arrive hours late, and it is the most common self-inflicted Android complaint.
| Symptom | Common real cause | What to do |
|---|---|---|
| Phone feels slow generally | Storage nearly full, or an old animation setting | Free several gigabytes; check developer options |
| One app is always slow to open | It was swiped away and cold starts every time | Leave it in recents and see whether it improves |
| Battery drains overnight | One app syncing or holding a wake lock | Read battery usage, restrict that single app |
| Notifications arrive late | Aggressive battery saving or a restricted app | Remove the restriction for that app |
| Games stutter after a while | Heat, and the phone throttling itself | Take the case off; do not blame memory |
| Free memory is always low | Normal, intended behaviour | Nothing; this is the system working |
Tools worth having, and what to use them for
DevCheck: live memory, processor and battery figures, and a clear list of what is actually running. The app to answer 'is something really using this phone' with a number.
AccuBattery: measures real discharge and attributes it to what was awake. The most useful thing on this list for finding a genuine background offender.
Ampere: shows actual charge and discharge current, which is how to tell whether an overnight drain is an app or a failing battery.
AIDA64: a full hardware and system report, including memory layout and thermal sensors, when you want the whole picture rather than a summary.
CPU-Z: about 5 MB and shows clock speeds and temperature live, which is how to confirm that a stutter is thermal throttling rather than memory.
Device Info HW: small, detailed and offline, with the component-level view that general monitors skip.
Files by Google: finds the large and duplicated files that are the actual cause of a slow, full phone. Unglamorous and effective.
Material Files: an open source file manager with no advertising, for the same clear-out when you would rather not use a Google app.
Greenify: included as history rather than a recommendation. Its hibernation approach mattered on Android 4 to 6 and modern versions handle this themselves, so most people no longer need it.
- Reading battery usage to find one bad app
- Restricting that specific app
- Keeping several gigabytes of storage free
- Rebooting when something is genuinely stuck
- Swiping every card away out of habit
- Installing a memory cleaner or booster
- Restricting background work for messaging apps
- Judging the phone by how much memory is free
Stop swiping. Find the one app draining the battery, restrict it, free some storage, and let the system manage memory.
Frequently asked questions
Should I never close an app?
Close one that has visibly broken: frozen, stuck playing audio, or refusing to reconnect. That is what the recents view is for. Clearing all of them as routine maintenance is the part that achieves nothing.
Why does my phone show so little free memory?
Because unused memory is wasted memory. Android fills it with cached apps and reclaims what it needs, when it needs it. A low free figure on a responsive phone is the system doing its job.
Do memory cleaner apps ever help?
Very rarely, and they cost battery to run. If a specific app misbehaves, restrict or uninstall that app. A tool that kills processes indiscriminately fights the platform's own scheduling.
Read next
Nothing has infected your phone. Something you installed has permission, and the fix is a list in settings.
A phone will happily run a keyboard, a mouse and a memory stick. It will not power a desktop hard drive.
Hard and fast are different things. Almost every game confuses them, and these do not.
