Last updated: May 9, 2026
Gemini has had a rough few months. Between the May 5 outage that knocked the model offline for hours, the recurring "Something went wrong (5)" error on Android, and a Google app update that's been breaking the Gemini app specifically on Xiaomi and some Samsung devices, there's a lot more going on than the usual "clear your cache" advice covers.
This page focuses on the things that are actually breaking Gemini in 2026 — the real failure modes — and walks through what to do for each. If you only have two minutes, the single most useful thing to know is that the Android app and the web version (gemini.google.com) fail independently. When the app is broken, the web is often fine, and vice versa. Switching between them is the fastest workaround for almost any Gemini issue.
"Something went wrong" with no number → Likely a server-side issue. Try the web version first, then check status. See section below.
"Something went wrong (5)" on Android → Google app/Gemini sync issue. Roll back the Google app.
App opens then crashes within seconds → Almost certainly the buggy Google app update. Same fix as above.
Web version returns 503 → The model variant you're on is overloaded. Switch from 2.5 Pro to 2.5 Flash, or wait.
Response generates partially then stops → Token limit or network drop, not an outage. Ask it to continue.
Mic/voice input doesn't work → Permissions or browser issue. Check the address bar lock icon.
Most older troubleshooting articles treat "Gemini not working" as one problem. It's not. The web version at gemini.google.com makes API calls directly to Google's AI infrastructure. The Android Gemini app, by contrast, routes through the regular Google app's services layer — the same one that powers Assistant. That's why a Google app update can crash Gemini while leaving the web version completely untouched.
Practical implication: before troubleshooting anything, open the other surface and see if it works. If the web works but the app doesn't, you have an Android-side problem and the fixes below apply. If the app works but the web doesn't, your problem is a browser/extension issue or a server-side incident affecting the web tier.
This is the generic error and it's the hardest to diagnose because it covers everything from a hiccup in your connection to a full-blown Google outage. Work through these in order — it takes about 90 seconds total.
This is the one that sends most people to Google Search. The numbered variant of the error appears specifically on Android, and through 2026 it's been correlated with Google app updates that change how the Gemini integration handshake works. Affected users have reported it heavily on Xiaomi devices, then Realme, then progressively on Samsung Galaxy S24 and S25 lines after specific updates.
The fix is to roll back the Google app to its previous version:
Re-enable auto-update only after Google has shipped a known-stable Google app version — usually you'll see this confirmed on the Gemini Apps Community forum.
503 errors mean the Gemini model variant you requested is temporarily over capacity on Google's end. This happens most often during peak US business hours and around new model launches when traffic spikes.
503 UNAVAILABLE on a specific model (e.g. gemini-3.1-flash-lite-preview), preview models have lower SLA priority — switch to the GA version of the same family for production work.Different from "something went wrong." Here the response starts generating, gets a few paragraphs in, and just stops — no error, no spinning indicator, just an incomplete answer. Two real causes:
Each Gemini response has a maximum length. For very long generations (long stories, big code dumps, deep research), the model runs out of room before it's finished its thought. The fix is simple: just type "continue from where you stopped" and Gemini will pick up from the last sentence. This isn't a bug — it's expected behavior.
Gemini streams responses token by token. A connection blip of even half a second can sever the stream and Gemini won't auto-resume. Re-issuing the same prompt usually works. If this happens repeatedly, switch from Wi-Fi to mobile data (or wired Ethernet on desktop) as a test — if cutoffs stop on the more stable connection, your network is the problem, not Gemini.
If the Gemini app launches and immediately closes, or crashes the moment you tap to send a message, the order of operations is:
Voice input has its own failure surface because it depends on the Google app's speech recognition pipeline being healthy — the same pipeline Assistant uses. If voice input has stopped working after you switched from Assistant to Gemini as your default, this is almost always why.
Q: What does "Something went wrong (5)" mean in Gemini?
A: The numbered variants of this error (1, 2, 5) are internal Google codes — 5 specifically tends to appear on Android when the Gemini app and the underlying Google app are out of sync after an update. The fastest fix is to roll back the Google app: Settings > Apps > Google > three-dot menu > Uninstall updates. Gemini routes through the Google app on Android, so a buggy Google update silently breaks Gemini even when the Gemini app itself is fine.
Q: Why does Gemini work on the website but crash in the Android app?
A: The web version (gemini.google.com) talks to Google's servers directly, while the Android app routes through the Google app's services layer. If a recent Google app update is buggy — which has happened repeatedly on Xiaomi, Realme, and some Samsung devices in 2026 — the app crashes while the web version stays fine. Use the web version short-term and roll back Google app updates for a longer fix.
Q: Is Gemini down right now?
A: Check status.cloud.google.com for the official Google AI services status, or Downdetector for crowdsourced reports. Gemini has had several public outages in 2026, including a notable one on May 5 where "something went wrong" was triggered for hours across both web and app. If reports are spiking, the only real fix is to wait — Google typically resolves these in 1–4 hours.
Q: Why does Gemini just stop typing mid-response?
A: Two main causes. The first is a model-side timeout — long, complex prompts can exceed Gemini's per-response generation limit, and the response just halts without an error. Ask Gemini to "continue from where you stopped" to resume. The second is your network: Gemini streams responses, so a brief connection blip cuts the stream off without showing an error. Try the same prompt with a stable connection or in incognito mode to confirm.
Q: Can I fix Gemini being slow, or is that always a server issue?
A: Mostly server-side, but not always. Slow responses on Gemini Advanced (paid tier) usually mean the underlying model is under load — try switching from 2.5 Pro to 2.5 Flash for the next prompt. On the free tier, slowness can also come from the device: the Gemini Android app keeps a local context cache that bloats over time, and clearing the app cache (not data) often returns response speed to normal.
If you've gone through the fixes above and Gemini still won't behave, the Gemini Apps Community at support.google.com/gemini/community is the most useful next stop — Google product team members reply to threads there directly, and you'll often see a fresh outage acknowledged within a few hours of it starting. Include your device model and the exact error string in any post.