Android Feels Slow After a System Update
Short answer
Give it 48 hours before changing anything. After an update Android recompiles every installed app and rebuilds the media index, which costs real CPU and battery in the background. If it is still slow on day three, clear the system interface cache, check for an app that has not been updated for the new release, and look at free storage — a phone under 10% free is slow for a different reason entirely.
On this page
Your phone was fine on Tuesday. It updated on Tuesday night, and since then apps take a beat too long to open, the keyboard lags behind your thumbs and scrolling stutters in places it never did.
The frustrating part is that a good share of this is real, expected, temporary, and nothing you can speed up. The rest is fixable. Working out which half you are in takes about two days of patience and ten minutes of checking.
The reindexing window is genuine
An Android update does not just swap out the operating system. It invalidates a large amount of precomputed state, and the phone has to rebuild all of it before performance returns to baseline.
| What rebuilds | Why the update broke it | Rough duration |
|---|---|---|
| App compiled code (ART) | New runtime, old binaries invalid | Hours to 2 days |
| Media index | Database schema and scan rules change | 20 min to a few hours |
| App caches | Cleared or invalidated by the install | Days, as you use apps |
| Launcher and icon caches | Rebuilt on first draw | Minutes |
| Play Services state | Re-registers push and sync | Hours |
The heaviest of these is the first. Android compiles app code ahead of time so it runs fast, and it profiles how you actually use each app to decide what to optimise. An update throws that away. Every app you open for the first time after the update runs partly interpreted, which is slower, and the system re-optimises in the background during idle and charging periods.
That is why the phone is noticeably better on day three than day one without you doing anything, and why heavy users with a hundred and fifty apps installed wait longer than someone with thirty.
Plug the phone in overnight and leave it alone. Android deliberately schedules this work for when the device is charging and idle, so a phone that spends two nights on a charger finishes substantially sooner than one that is used all day and dies at bedtime.
Decide which problem you have
After 48 hours of normal use, the free pass expires. Use this to work out where to look.
| What you see | Most likely cause |
|---|---|
| Slow everywhere, improving daily | Still reindexing. Wait. |
| Slow everywhere, no improvement after 3 days | Storage pressure or a stuck service |
| One or two apps slow, rest fine | App not yet updated for the new release |
| Lag plus heat plus fast battery drain | A process stuck in a loop |
| Animations choppy, apps open fine | Developer options or a UI cache issue |
| Phone 4+ years old, each update worse | Hardware ageing into heavier software |
Those last two are the ones people most often misdiagnose, in opposite directions. Choppy animations with otherwise normal app launches is a rendering problem, not a performance one. A four-year-old phone getting slower with every annual release is not a fault at all, and no amount of cache clearing changes it.
Check free storage first
This is the single most common non-update cause, and updates make it worse because they leave staged install files behind.
Open Settings → Storage. Flash storage slows down dramatically as it fills, because the controller has fewer free blocks to write into and has to shuffle existing data first. Under about 10% free, a phone becomes sluggish in a way that looks exactly like post-update slowness.
If you are tight, the fastest wins are offline media in streaming apps and trash folders rather than photos — storage full with nothing on the phone walks through where it actually hides, and freeing up Android storage covers the rest.
Also check whether a further update is pending. A downloaded-but-not-installed package sits on disk doing nothing useful, sometimes several gigabytes of it.
Clear the caches that are safe to clear
Two caches commonly survive an update in a stale state and cause visible lag.
The system interface cache. Go to Settings → Apps, show system apps from the three-dot menu, and find System UI on stock Android or One UI Home and System UI on Samsung. Open Storage and cache → Clear cache. This affects the launcher, notification shade and quick settings.
The Play Store and Play Services caches. Both get into odd states across version jumps, and Play Services misbehaving produces background load that feels like general slowness. Same path: Storage and cache → Clear cache.
Do not tap Clear storage on any of these. On Play Services in particular it resets device registration and can log you out of accounts and break push notifications until it re-registers. Cache is safe, storage is not — the difference between the two buttons is worth understanding before you touch either.
Restart the phone afterwards. A full restart also clears the ART interpreter state and any service that got stuck mid-migration.
Find the app that did not survive the jump
If only some apps are slow, the update changed something they depend on and they have not been rebuilt for it. Major Android releases regularly tighten background execution, change storage access or alter permission behaviour, and an app that has not shipped an update since will fall back to slower paths or retry things that now fail.
Open the Play Store → your profile icon → Manage apps and device and update everything pending. Then check the problem app’s listing: a last-updated date more than a year old on a major release transition is a poor sign, and there is nothing you can do about it from your side.
Reinstalling the specific app is worth one attempt. It forces a fresh compile and a clean data directory, which occasionally clears a migration that half failed.
Rule out a stuck process
Lag combined with the phone being warm and the battery falling faster than usual is not reindexing. Reindexing is bursty and happens when you are not using the phone; a stuck wakelock or sync loop runs constantly.
Open Settings → Battery → Battery usage and switch to the full device view from the three-dot menu. An app with high consumption and almost no foreground time is your candidate, and identifying the app draining your battery covers how to read that screen properly and what to do with the answer.
The classic post-update version of this is an account that failed to re- authenticate after the upgrade and now retries its sync every few minutes forever. Removing and re-adding the account fixes it in a minute.
Speed up the animations
This changes nothing about actual performance and makes the phone feel substantially faster, which is a fair trade.
Enable developer options by tapping Settings → About phone → Build number seven times. Then in Settings → System → Developer options, set Window animation scale, Transition animation scale and Animator duration scale to 0.5x.
Every screen transition now takes half as long. Setting them to “off” entirely works but makes the interface feel abrupt, and on some Samsung builds it causes odd redraw glitches in the recents view.
What does not help
- Cleaner and booster apps. They cannot speed up ART compilation, which is the actual bottleneck, and they consume resources themselves. Several also kill background processes that Android then restarts at a net cost.
- Wiping the cache partition from recovery. Most phones no longer have that partition, so the menu entry is simply missing. Where it survives, it clears far less than the forums imply.
- Closing all apps from Recents. Cold-starting an app costs more than leaving it cached, and after an update cold starts are the expensive ones.
- Turning off Adaptive Battery. It is part of how the system schedules the background optimisation work. Disabling it during this window is actively counterproductive.
- Rolling back. There is no supported path, and anti-rollback protection on most devices turns an attempt into a dead phone.
Realistic expectations
Most phones feel normal again by day three without intervention. Clearing the System UI and Play Services caches plus a restart is worth ten minutes if you are impatient, and freeing storage genuinely helps on a phone that was already near full.
If it is still slow after a week, with storage healthy and no app dominating battery, the honest answer is often that the phone has aged into software written for newer hardware. A factory reset will give you a clean baseline and tell you definitively — if a freshly reset phone is still slow, nothing you install was the problem. That is a weekend’s work to learn one fact, which is why it belongs last.