Why Does My Phone Slow Down After Two Years?
Short answer
Four separate things change over two years: storage fills up and slows writes, the battery degrades to the point some phones reduce peak performance, apps grow heavier with each update, and OS updates add features the original hardware was not specified for. Start by checking free storage — keep at least 10–15% free — because it is the most common single cause and the easiest to fix.
On this page
The belief that manufacturers deliberately cripple old phones is widespread, and the reason it persists is that the experience is real. Phones genuinely do get slower, often fairly abruptly around the two-year mark, and the timing feels suspicious.
The explanation is less dramatic and more annoying: four separate things degrade at once, each modestly, and they compound. None of them requires a conspiracy, and three of them are at least partly fixable.
It is worth dealing with the planned obsolescence question directly, though, because one part of it is true.
The four causes, and which is yours
| Symptom | Likely cause | Fixable? |
|---|---|---|
| Everything slow, especially saving and installing | Storage nearly full | Yes, substantially |
| Slow only when the battery is low; shutdowns above 20% | Battery degradation and throttling | Yes, by replacing the cell |
| Specific apps slow, the phone itself fine | App bloat | Partly |
| Slowed noticeably right after a major update | OS weight on older hardware | Partly |
| Fast for a minute, then slows and the phone is warm | Thermal throttling | Sometimes |
Start with storage. It is the most common and the cheapest to address.
Storage, the cause people underestimate
Phone storage is flash memory, and flash does not behave like a drawer that you can fill to the brim.
Data is written in pages but erased in much larger blocks. To change part of a block, the controller has to read it, modify it and write it somewhere else, then eventually erase the original. When there is plenty of free space the controller has spare blocks ready and this happens invisibly. When the drive is nearly full it has to shuffle existing data to free a block before every write, and write performance falls sharply.
Everything that writes to storage then gets slower: installing updates, saving photos, app databases, and the system’s own logging and caching. Which is most of what a phone does.
Check Settings → Storage. Aim to keep at least 10–15% of total capacity free. On a 128GB phone that is a comfortable margin; on a 32GB phone it is genuinely difficult, which is one reason budget phones with small storage age so badly.
Clearing space is more involved than deleting a few photos, because much of what fills a phone is invisible app data and cache. How to free up Android storage covers the order to work through, and what the Other category actually contains explains the portion you cannot reclaim.
Messaging apps are usually the largest culprit, because they save every image and video anyone sends you — why WhatsApp takes so much storage is the single biggest win on most phones.
The battery, and the throttling question
This is where the planned obsolescence argument has its one genuine basis, so it is worth being precise.
A lithium-ion cell loses capacity with age, and it also loses its ability to supply high current. When a processor demands a burst of power, a worn cell’s voltage sags. If it sags far enough, the phone shuts down abruptly — which is why an old phone dies at 30% in cold weather.
Some manufacturers respond by limiting peak processor performance on phones with degraded batteries, trading speed for the phone staying on. Apple did this and did not disclose it initially, which led to the “batterygate” controversy and a settlement. Since then Apple shows battery health and lets you turn the management off, and the practice is openly documented.
The important distinction: that was throttling triggered by battery condition, not by the phone’s age or by a new model launching. A phone with a healthy battery was not affected. It was poorly communicated and it was not an attempt to force upgrades, though it is entirely reasonable that people concluded otherwise.
How to tell whether this is your problem:
- Check battery health. Settings → Battery → Battery health on Android 14 and later and on Samsung via Samsung Members; Settings → Battery → Battery Health on iPhone.
- Test the pattern. Does the phone feel faster when fully charged and plugged in than at 30%? If so, the battery is involved. If performance is identical regardless of charge, it is not.
- Watch for shutdowns above 20%, which is the clearest sign of a cell that can no longer supply peak current.
If the battery is the cause, replacing it restores performance as well as runtime, and whether that is worth doing on your phone depends mostly on how long the phone has left in software support.
Apps grow, and the hardware does not
This is the cause nobody can fix and everybody experiences.
Applications get updated continuously, and almost every update adds something: new features, higher-resolution assets for newer screens, more analytics, more background services, larger local databases. Developers test against current hardware, which gets faster every year, so there is persistent pressure for software to expand into whatever is available.
A social media app on a phone bought two years ago is doing considerably more work than the version that shipped with it. The hardware is identical. The experience degrades without anything breaking.
Two sub-effects make it worse over time:
- Accumulated local data. Chat histories, cached media, offline content and app databases grow steadily, and a large database is slower to query than a small one.
- Background activity. Every app installed adds some background work — syncing, checking for notifications, uploading usage data. Thirty apps is thirty small background costs.
What helps: uninstall what you no longer use rather than leaving it dormant; clear app cache for the heaviest offenders, which is safe and distinct from clearing storage; the difference between the two is worth knowing before you tap the wrong one. Lite versions of heavy apps, or using the mobile website instead, genuinely helps on older hardware.
OS updates add weight
Each Android or iOS release adds features, visual effects and background services. Manufacturers test on current hardware and on supported older models, but “supported” means it runs, not that it runs as well as it did.
The effect is usually modest and occasionally pronounced, particularly on devices at the bottom of the supported range or with limited RAM. A phone with 3GB or 4GB of RAM running a current OS plus a modern browser is constantly evicting apps from memory, which is why switching back to an app reloads it from scratch instead of resuming.
Skipping updates is a poor trade. Security patches are the reason to install them, and running unpatched software to recover some responsiveness is not a good exchange. What is worth doing is a factory reset after a major OS upgrade if the phone clearly degraded, since an in-place upgrade carries forward years of accumulated state.
The quick fixes, in order of yield
Work down this list and stop when the phone feels acceptable.
- Free up storage to at least 10–15% of capacity. Largest and most reliable improvement on most phones.
- Restart the phone. Clears memory fragmentation and stops runaway background processes. On a phone that has not been restarted in weeks the difference is real.
- Uninstall what you do not use. Each app removed is background work removed. Check Settings → Apps sorted by last used.
- Clear cache on the heaviest apps. Safe, reversible, and it recovers both space and database performance.
- Turn off animations. Developer options → Window, Transition and Animator duration scale → 0.5x. This does not make the phone faster, it makes it feel faster by removing waiting. That is a legitimate improvement.
- Check for a misbehaving app. One app waking the phone constantly looks exactly like general slowness — identifying the culprit takes a few minutes.
- Factory reset, after backing up. The most effective single step and the most disruptive. Expect a clear improvement that fades somewhat as you reinstall things.
So is it planned obsolescence?
Deliberate slowdowns to drive sales have not been demonstrated, and they would be a strange strategy given how visible the code would be. What exists is considerably more mundane and in some ways harder to defend.
Phones are built to a cost with storage and RAM sized for their launch year, not for five years later. Batteries are sealed in and awkward to replace, which turns a cheap repair into a decision about the whole device. Software support windows end, and the one that matters is security updates. And the software ecosystem expands continuously to fill whatever hardware is current, which quietly pushes older devices below the threshold.
The outcome resembles designed obsolescence closely enough that the suspicion is understandable. The mechanism is a set of commercial decisions about component cost and serviceability rather than a switch anyone flips at the two-year mark.
The practical consequence is that the fixable parts are worth fixing: storage, battery, and the apps you no longer use. The parts that are not fixable — RAM, processor, the support window — are what eventually decide when the phone is finished, and no amount of cleaning changes them.
What to expect after the fixes
Clearing storage back to a healthy margin and removing unused apps typically takes a phone from frustrating to usable, and the storage element alone is frequently most of it. A factory reset goes further and takes an evening.
If the phone is still slow with ample free storage, a healthy battery and a clean install, you have reached the hardware. A two-year-old flagship normally still has years of useful life; a two-year-old budget phone with 3GB of RAM and 32GB of storage is close to the limit of what it was ever going to do.