Android phone slow after update: 6 fixes that work

A phone that goes sluggish the same week Android updates is usually not broken. Nothing crashes, and then the animation arrives a beat late and the camera takes a second longer to open. That is the window this guide is built for, and it is a 72 hour triage rather than a bag of tricks.

Samsung says a phone that behaves oddly after a software update is usually dealing with temporary system glitches or leftover cache files, and needs time to settle and optimize its apps. Google's Android source explains what settling is: when the device is idle and charging, a compilation daemon runs to recompile your apps. A system module update also changes the boot classpath, which renders all dexpreopt files stale and unusable, so the phone redoes work it already did. Samsung adds a third job: the phone may take some time to index correctly after the update. That combination is the post-update optimization window, the 24 to 48 hours when the slowdown is expected. Work the six fixes in order and stop the moment the phone feels normal again.

Every path below is labelled by brand, and the HiOS menus were read on my Tecno Spark 40. See how we test, and check any path against your own build before you follow it.

Fix 1: Let the update finish, then restart

Start here, because it is free and matches every source. If the update did not fully install, the phone is finishing that job and the slowdown is partly that.

1. On stock Android 15, open Settings > System > Software update. If it does not read as up to date, let it download and install first.
2. Press and hold the power button, then tap Restart. A full restart is what makes a background install active.

On Samsung the path is Settings > Software update > Download and install > Install now. On my Spark 40, HiOS 15 places the menu under Settings > About phone > Software update, and TECNO publishes no troubleshooting page for it. You know it worked when the status reads as current and the phone has restarted fully at least once. Abandon if the update will not complete, but a retry is normal: Google says an unfinished download will try again over the next few days.

Fix 2: Give it idle and charging time

This is the one step where you do nothing except plug in and wait, and it is the heart of the window. AOSP is specific about the condition the recompiler needs: the device must be idle and charging. Fighting the phone keeps it busy, and busy is the opposite of idle. So plug it in, leave the screen off, and let it sit. Overnight is the natural version of this. You know it worked when responsiveness returns after that quiet, plugged-in time. Abandon if nothing changes after a genuine idle charging stretch. If the phone runs hot here, that is the same work making heat, and our guide to an Android phone overheating covers the cases where heat does not settle.

Fix 3: Restart again, then clear the leftover cache

Samsung's first line on post-update trouble is that it is usually temporary glitches or leftover cache files. Restart once more, then clear the cache the update left behind. The cache wipe comes after the phone has had its idle time. Stock Android 15 has no user-facing cache-partition wipe, so do not hunt for one. Google's route is per app: open Settings > Apps > See all apps, tap the app, then Storage & cache > Clear cache.

On Samsung, One UI gives a shallower route through Settings > Device care > Memory > Clean now. The deeper route is the recovery wipe: power off, hold Volume Up and Power, release at the Android Recovery screen, highlight Wipe cache partition with Volume Down, press Power, confirm Yes, then Reboot system now. Samsung states that wiping cache does not delete personal data.

On HiOS 15 the documented route is Settings > Storage > Cached data, which is where this setting sits on my Spark 40. TECNO does not document a cache-partition wipe from HiOS recovery, so do not enter an unverified key combination. If the update seems to have eaten space, our guide on what is actually filling your storage handles that separately. Abandon if the phone is unchanged. A cache clear is a one-shot, so do not run it in a loop.

Fix 4: Update the apps the new OS expects

An app that has not caught up with the new OS version is the most likely non-system cause of post-update slowness, and Google's ladder puts app updates right after the restart and the version check.

1. Open the Play Store, tap your profile icon, then Manage apps & devices > Updates available, and update everything.
2. For Play services itself, go to Settings, tap your profile picture, then All services > System services > Google Play services > Update.

One warning keeps people out of trouble here. Google says clearing the cache and data of Google Play services is not recommended unless you have tried all other troubleshooting options, because it can delete saved passwords and payment cards and force you to sign back in everywhere. So update Play services and leave its data alone. Re-indexing often finishes on its own here, because a freshly updated app rebuilds its own index. Abandon if the updates change nothing.

Fix 5: Check the permissions and battery profile

The sources do not say what most blog posts claim about permissions. No Google or Samsung page states that an update resets your app permissions. What Google does document is that Android revokes permissions and stops background activity for apps you have not used for a long time, and that background usage should stay set to Optimized. So the honest check is whether the update left an app in a state you did not choose.

1. Open Settings > Apps > Unused apps to see what Android has paused for you.
2. Open Settings > Apps, pick an app, check Permissions, then set App battery usage to Optimized.
3. Open Settings > Battery and confirm Adaptive Battery is on.

On Samsung this lives under Settings > Device care > Battery > Power mode, whose labels differ on One UI 2.5 and below. On HiOS 15 the documented areas are Settings > Battery and Settings > Apps > [app] > Permissions. If your phone is draining hard instead of just running slow, work our Android battery draining fast guide and the piece on improving battery life on Android devices separately.

Fix 6: Safe mode to separate the update from an app

This rung is diagnostic, and it is the only clean way to tell whether the update is the problem or an app broke after it landed. Google's help is direct: some apps you download can cause issues, and running slow is listed as a symptom. Here is the honest limit. Google says restarting in safe mode varies by phone and points you to your manufacturer's support site, and Samsung does not publish a safe-mode combination on the pages in our sources. So do not follow a key combination from a blog, including this one. Find your own device's method from its maker. If the phone is fine in safe mode, an app is the cause, and Google's sequence is to remove recently downloaded apps one at a time, restarting normally after each removal. If it is still slow in safe mode after the window has passed, the update or the hardware is the cause, and this ladder has run out of rungs.

The rung not to lead with: factory reset

A factory reset is the last resort, not a troubleshooting step, and both vendors say so. Google states that if you are resetting to fix an issue, you should first try other solutions, and a reset can take up to an hour. Samsung says a factory reset should only be used if the issue continues after the other steps. If you do reach it, back up first and know your Google Account password. On stock Android 15 the path is Settings > System > Reset options > Erase all data (factory reset), and on Samsung it is Settings > General management > Reset > Factory data reset. At that point, our guide on how to test a used phone tells you whether hardware, not software, is what you are fighting.

The bottom line

Almost every phone that feels slow in the days after an update is finishing work, not dying. Restart it, plug it in, and leave it alone long enough for Android to recompile and reindex. Then clear the leftover cache and update your apps. Hold the factory reset until every other rung has failed. For everything else on the same fault tree, start from our Android problems fix guide.

Frequently asked questions

Is my phone broken after the update?

Usually not. Samsung states that odd behaviour after a software update is usually due to temporary system glitches or leftover cache files. If the phone responds to the six fixes above, the update did not break it.

Will it fix itself if I just wait?

Often it will. Samsung says post-update trouble is usually temporary and resolves after system optimization. Google's source explains what the phone is waiting for: app recompilation only runs when the device is idle and charging. Neither source publishes a number of hours.

How long does the post-update window last?

The working frame is 24 to 48 hours, when Android recompiles apps, rebuilds caches, and reindexes files. No vendor document states an exact number of hours. If day two is no better than day one, stop waiting and work the ladder.

Should I factory reset to fix it?

Only as a last resort. Google states that if you are resetting to fix an issue, you should try other solutions first, and a factory reset erases all data and can take up to an hour. Samsung agrees it should only be used if the problem continues.

Should I clear the cache of everything, including Google Play services?

No, not casually. Google states that clearing Play services cache and data is not recommended unless you have tried all other options, because it can delete saved passwords and payment cards. Clear per-app caches instead.

The update will not install. Is that why it is slow?

Possibly. Google says that if an update starts downloading and does not finish, the device automatically tries again over the next few days, and it needs free space and a charge. So make space, plug in, and let the retry run.

What if the phone is fine in safe mode?

Then an app is likely the cause. Google's sequence is to remove recently downloaded apps one at a time, restart normally after each removal, and reinstall the innocent ones. If the phone is still slow in safe mode, the update or the hardware is at fault.