Tech Behind ThingsHow the ordinary machinery actually works

Devices

Why your phone slows down, and which explanation is actually true

Several real mechanisms get collapsed into one conspiracy. Separating them explains what you can fix and what you cannot.

Close-up of a smartphone mounted on a car dashboard showing home screen with apps.
Photograph by Mustafa ezz via Pexels
Editorial note. Independent reporting and analysis. Nothing here is sponsored or paid for. How we work.

Everything here earned its place by changing an outcome. Nothing about phone slowdown is included to round the number up.

What matters most

  • Battery ageing triggers deliberate performance limiting on some devices.
  • Software grows to use the headroom that newer hardware provides.
  • Storage nearly full degrades performance independently of anything else.

Battery ageing causes real throttling

A lithium-ion cell's internal resistance rises as it ages, which limits how much current it can deliver in a sudden peak. If the processor demands a spike the battery cannot supply, voltage sags and the device shuts down unexpectedly.

Manufacturers respond by capping peak performance on degraded batteries to prevent that, which is a genuine engineering trade-off and was badly communicated when it emerged publicly. The practical consequence is that a battery replacement can restore performance on an older device, which is often the cheapest useful upgrade available.

Software expands to fill available hardware

Applications and operating systems are developed and tested on current hardware, and they use the headroom that hardware provides. An app that was comfortable on a four-year-old phone at release is heavier three years later, because it has grown. This is not deliberate sabotage; it is the ordinary consequence of developing against the machines developers actually own.

In practice, security updates are the part that keeps arriving on old hardware, and they bring new frameworks and background services with them, so a device kept on an older major release often stays faster at the price of no longer receiving fixes.

Storage pressure is the underrated cause

Flash storage relies on free blocks for wear levelling and garbage collection, and performance degrades sharply when a drive is nearly full. A device with a few per cent free can be dramatically slower than the same device at half capacity. This is the single most common fixable cause and the one people check last.

Controllers also borrow part of the free area as a fast write buffer and fall back to a slower writing mode once it is exhausted, so a full drive loses its fast path as well as its spare blocks.

Thermal limits shape sustained performance

Phones have almost no thermal mass and no active cooling, so sustained load causes the processor to reduce clock speed within minutes. Benchmark figures describe short bursts; real sustained performance is a fraction of them.

In the datasheet, a worn case, a hot room or charging while gaming all make this substantially worse. Temperature sensors sit away from the hottest silicon and the controller works from an estimate, which is why performance drops noticeably before the case ever feels warm to hold.

What actually helps

Replacing the battery, freeing storage below about eighty per cent full, and removing apps that run background services address most real slowdowns. Factory resets help mainly by clearing accumulated storage and background services, not by any magic. Nothing restores a device to being current hardware, and that is the part no maintenance addresses.

Cleaning utilities that promise to free memory generally make things worse, because they evict caches the operating system deliberately kept and everything then has to be read back from storage.

This is the general case; a specific device may behave differently by design.

Some of the slowdown is not in the device

Slowdown is usually noticed shortly after handling a newer phone, which means the reference point moved rather than the device. Interface animations are tuned to cover loading time on current hardware, so on slower hardware they stop hiding anything and become visible waits added on top of the real delay. Reducing motion in accessibility settings shortens or removes those animations and changes how fast the device feels without changing anything measurable about it.

In practice, much of what a phone displays arrives over a network rather than being computed locally, so a congested connection is routinely diagnosed as a tired handset.

Everything above, in order of what to do first

  1. Battery ageing causes real throttling. A lithium-ion cell's internal resistance rises as it ages, which limits how much current it can deliver in a sudden peak.
  2. Software expands to fill available hardware. Applications and operating systems are developed and tested on current hardware, and they use the headroom that hardware provides.
  3. Storage pressure is the underrated cause. Flash storage relies on free blocks for wear levelling and garbage collection, and performance degrades sharply when a drive is nearly full.
  4. Thermal limits shape sustained performance. Phones have almost no thermal mass and no active cooling, so sustained load causes the processor to reduce clock speed within minutes.
  5. What actually helps. Replacing the battery, freeing storage below about eighty per cent full, and removing apps that run background services address most real slowdowns.
  6. Some of the slowdown is not in the device. Slowdown is usually noticed shortly after handling a newer phone, which means the reference point moved rather than the device.

The takeaway

Check storage first, battery second, and accept that the software grew.

Once you know what it is trading away, the design stops looking arbitrary.

Questions readers ask

Does replacing the battery really speed up an old phone?

On devices that throttle based on battery condition, yes, sometimes dramatically. On devices that do not, it restores runtime but not speed.

How much free storage should I keep?

Aim to stay below about eighty per cent full. Performance degradation becomes pronounced in the last ten per cent.

Devicesperformancephonesbatteriessoftware
Mikkel Aas
Editor, Tech Behind Things

Mikkel edits Tech Behind Things and has taken apart more devices than he has successfully reassembled.

Also by Mikkel Aas