Android Not Working After Update? 12 Fixes (2026)

Quick answer: If Android is not working after an update, restart, clear the affected app cache/data, then repair Google Play services + WebView/Chrome; for boot or system-wide issues, use Safe Mode and (if available) wipe the cache partition.

Most “android not working after update after update problem” cases are caused by corrupted caches, Play services/WebView conflicts, or a stuck post-update optimization—use the checklist below to match your symptom to the fastest fix.

Quick Fix Checklist

• Phone is slow / freezing: Restart once, then wait 10–20 minutes on Wi‑Fi (post-update optimization can spike CPU). If it continues, go to Settings > Storage and ensure you have 5–10 GB free.
• One app broken: Settings > Apps > (app) > Storage > Clear cache (then Clear data if needed) > update/reinstall the app.
• Many apps crash at launch: Fix Android System WebView and Chrome (clear cache, uninstall updates if available, then update again).
• Play Store won’t download / Google login fails / notifications missing: Clear data for Google Play services, Google Play Store, Google Services Framework, then remove/re-add your Google account.
• Battery drain / overheating after update: Settings > Battery > Battery usage > identify the top app/process > restrict background + remove “always” permissions (location, mic, camera).
• Wi‑Fi/mobile data/Bluetooth not working: Reset Wi‑Fi, mobile & Bluetooth (network reset), then forget/re-pair and verify APN/carrier settings.
• Stuck on logo / boot loop / endless “Optimizing apps”: Boot Safe Mode and uninstall recent apps; if recovery offers it, wipe cache partition.
• Storage suddenly full after update: Remove large app caches, delete downloaded update leftovers (where OEM allows), and clear Downloads + messaging media folders.

Causes (realistic, not generic)

• Corrupted app cache after OS migration: Apps may crash until their cache/databases are rebuilt under the new framework.
• Google Play services token mismatch: After a major update, account tokens and Play services components can desync, breaking sign-in, Play Store installs, and push notifications.
• WebView/Chrome rendering conflict: A bad WebView/Chrome build can crash multiple unrelated apps that embed web content (banking, email, shopping, social).
• Stuck ART optimization / indexing: “Optimizing apps,” media indexing, and Play Protect scans can loop if storage is tight or a package is corrupted.
• Network stack config corruption: VPN profiles, private DNS, APN changes, or carrier config updates can break Wi‑Fi/mobile data until reset.
• OEM background limits changed: Updates can tighten battery rules, silently blocking notifications, background sync, and alarms.
• Permission model changes: New Android versions can reset permissions (notifications, nearby devices, background location), making apps appear “broken.”

Cause	What it looks like	Fix that works
App cache/database corruption	One app crashes, freezes, won’t open	Clear app cache/data; update or reinstall; check permissions
WebView/Chrome conflict	Multiple apps crash instantly	Clear cache; uninstall updates for WebView/Chrome; update again; switch WebView implementation
Play services/account token mismatch	Play Store stuck, login errors, missing notifications	Clear data for Play services/Store/Framework; remove & re-add Google account
Post-update optimization loop	Hot phone, lag, “optimizing apps” repeats	Free storage; reboot; Safe Mode; wipe cache partition (if available)
Network config corruption	No data, Wi‑Fi drops, Bluetooth pairing fails	Reset Wi‑Fi/mobile/Bluetooth; verify APN; disable VPN/private DNS temporarily

Step-by-Step Fix

1) Confirm what’s actually broken (saves time)

• Only one app fails: Fix that app (cache/data, permissions, update/reinstall).
• Many apps fail: Prioritize WebView/Chrome + Google components.
• System-level failure: Use Safe Mode/recovery steps before wiping data.

2) Do the “post-update stabilization” steps (often enough)

1. Restart the phone once.
2. Plug into power and connect to Wi‑Fi for 15–30 minutes (lets optimization finish).
3. Check free space: Settings > Storage. If under 5 GB, delete large files/apps first (low storage can cause crashes and boot issues).

3) Fix a single app that’s not working after the update

1. Settings > Apps > select the problem app.
2. Tap Force stop (if available).
3. Storage > Clear cache > reopen the app.
4. If still broken: Storage > Clear data (you may need to sign in again).
5. Update the app in Play Store. If the issue started after an app update, try Uninstall then reinstall.
6. Non-obvious check: Settings > Apps > (app) > Permissions and re-enable anything the update may have reset (especially Notifications, Nearby devices, Photos and videos, Background location).

4) Repair Google Play services / Play Store (fixes downloads, login, notifications)

Use this when Play Store won’t update apps, Google sign-in loops, or notifications stop after the update.

1. Go to Settings > Apps > See all apps.
2. Open each item below and do Storage > Clear cache, then Clear data:
   • Google Play services
   • Google Play Store
   • Google Services Framework (may be hidden: 3-dot menu > Show system)
3. Restart the phone.
4. Go to Settings > Passwords & accounts (or Accounts) > Google > Remove account.
5. Add the Google account back, open Play Store, and leave it open for 2–5 minutes to resync.

5) Advanced fix: WebView/Chrome crash chain (multiple apps crash)

This is one of the most common reasons Android “suddenly” stops working after an update because many apps rely on embedded web rendering.

1. Go to Settings > Apps > find Android System WebView and Google Chrome.
2. For both: Storage > Clear cache.
3. If available: open each app page and tap Uninstall updates (or Disable), then reboot.
4. Update WebView/Chrome again from Play Store.
5. Non-obvious option (when crashes persist): Enable Developer options (Settings > About phone > tap Build number 7 times) > Developer options > WebView implementation > switch between WebView/Chrome and retest.

6) Fix battery drain and overheating after update (find the offender)

1. Go to Settings > Battery > Battery usage.
2. Tap the top 1–3 items and apply:
   • Set battery mode to Optimized (or Restricted for obvious offenders).
   • Turn off Allow background activity (if present).
   • Change location to While in use and disable Precise location unless needed.
3. If Android System or Google Play services stays at the top for hours: run the Play services repair (Step 4), then reassess after 30–60 minutes.
4. Advanced check: Temporarily disable Always-on VPN, Private DNS, and third-party security apps—these can cause constant network retries after updates.

7) Fix Wi‑Fi, mobile data, or Bluetooth not working after update

1. Reset network stack: Settings > System (or General management) > Reset options > Reset Wi‑Fi, mobile & Bluetooth.
2. Wi‑Fi: forget the network and reconnect; if it still drops, toggle MAC randomization (device-specific) and test again.
3. Mobile data: Settings > Network & internet > SIMs > confirm the correct SIM is selected for data; verify APN matches your carrier (major Android updates can reset APNs).
4. Bluetooth: remove the paired device and pair again; if audio stutters, disable HD audio for that device to test codec compatibility.
5. Non-obvious check: Disable Private DNS (set to Automatic/Off) and remove any VPN profile to rule out DNS/VPN breakage after the update.

8) Boot loop, stuck on logo, or endless “Optimizing apps”

These steps avoid data loss first.

• Safe Mode (tests if a third-party app is the trigger):
  • Press and hold the power button.
  • Press and hold Power off > confirm Safe mode (wording varies by OEM).
  • If the phone works in Safe Mode, uninstall the last 3–5 apps you installed/updated before the issue.
• Recovery cache wipe (advanced, often effective):
  • Power off.
  • Enter recovery (commonly Power + Volume Up, but OEM-specific).
  • Select Wipe cache partition (if present) > confirm.
  • Reboot system.
• If recovery shows “Repair apps” / “Apps optimization”: run it once, then reboot.

9) Last resort: factory reset (do it in a way that actually isolates the cause)

Use this only if system-level issues persist after the steps above.

• Back up: photos, authenticator codes, offline files, and any app data not synced.
• Reset: Settings > System > Reset options > Erase all data (factory reset).
• Critical: After reset, test stability for 30–60 minutes before restoring everything. Restore apps in batches to identify the app that reintroduces the problem.

Still Not Working

• Check for a hotfix (common after major updates): Settings > System > System update and also update apps in Play Store (especially WebView/Chrome).
• Rule out “hidden” blockers introduced by the update:
  • Private DNS: set to Automatic/Off (can break sign-in, Play Store, and some Wi‑Fi networks).
  • VPN / Always-on VPN: disable temporarily (can cause no-internet loops after updates).
  • Date & time: set to Automatic (wrong time breaks TLS certificates and logins).
  • Notification permission reset: Settings > Notifications > ensure the app is allowed (updates can toggle this off).
• If only calls/SMS/data are broken: reseat the SIM, toggle airplane mode, then ask your carrier to re-provision the line (carrier config updates can fail during OS upgrades).
• If the phone reboots randomly after the update: uninstall recently updated “device admin” apps (security, VPN, parental control), and check Settings > Security for admin apps that may be incompatible.
• Collect evidence for real support (saves days):
  • Note: phone model, Android version, build number, and exact time the issue occurs.
  • Enable Developer options (tap Build number 7 times) and, if you have a computer, capture logs with adb logcat while reproducing the issue.
• Suspect storage/hardware corruption: repeated “app corrupted” messages, failed installs, or “can’t load Android system” can indicate failing storage. Run OEM diagnostics (if available) and consider service.
• If you’re on a beta: opt out and install the stable build (beta updates frequently cause post-update instability).

If you share your phone model, Android version, and the exact symptom (crash message, boot loop, battery drain, no network), you can map to the shortest fix path without wiping data.

Fixes for Android

On Android, this kind of issue is often caused by corrupted cache, battery restrictions, or background network controls that affect the app.

Why this happens

Android devices often keep cached app state longer than expected, and some manufacturers add aggressive battery or security settings that interrupt normal app behavior.

How to fix it

1. Force stop the app, then reopen it and test again.
2. Clear the app cache before clearing full storage.
3. Test on Wi-Fi and then on mobile data to isolate network-specific failures.
4. Disable VPN, ad-block DNS, firewall apps, or battery saver temporarily.
5. If needed, clear app storage or reinstall the app to reset broken local data.

Important notes

• If clearing cache helps, that usually confirms the problem was local to the device.
• If the app fails only when battery saver is enabled, background restrictions may be the real cause.

If the Problem Started After an Update

If the problem started right after an update, the timing strongly suggests a compatibility or local data issue.

Why this happens

Updates can change permissions, invalidate saved sessions, or leave behind temporary cached data that no longer matches the latest app or system version.

How to fix it

1. Restart the device first to clear temporary glitches triggered by the update.
2. Check whether a follow-up patch is already available for the app or system.
3. Sign out and sign back in if the app still opens but a specific function fails.
4. Clear cache or reinstall the app if the issue appears tied to corrupted local data.
5. Look for reports from other users to confirm whether the update introduced a wider bug.

Important notes

• If many users report the same issue after the same update, a vendor-side patch may be required.
• Do not reset the whole device too early if simpler update-related fixes have not been tested yet.

How to Check for a Temporary Outage

Before changing device settings, confirm that the problem is not caused by a temporary outage.

Why this happens

Service interruptions can make normal accounts, apps, and networks appear broken even when nothing is wrong locally.

How to fix it

1. Try the web version to see whether the same action fails outside the app.
2. Check official status pages or recent outage discussions if available.
3. Avoid repeated retries if the platform appears unstable.
4. Wait a few minutes and test again from the same trusted network.

Important notes

• If both the app and browser fail in the same way, the issue is much more likely to be service-side.
• Changing passwords or reinstalling apps will not help during a real outage.

Frequently Asked Questions