Last updated: October 2026 · 7 min read

MicroG Keeps Stopping? Here’s How to Fix It

“MicroG keeps stopping” is one of those Android errors that tells you almost nothing and interrupts you constantly. The popup appears, you dismiss it, and twenty minutes later it’s back — along with missed notifications and an app or two refusing to sign in. Here’s what’s actually happening, why it almost certainly isn’t anything sinister, and the fix sequence that stops it for good, in the order you should try it.

What Does “MicroG Keeps Stopping” Actually Mean?

MicroG isn’t an app you open and use directly most of the time. Its main component, GmsCore, is a background service that other apps call when they need Play Services APIs. The “keeps stopping” message means that background service has crashed, or — just as often — your phone’s system has killed it and Android is reporting the death as a crash.

Either way, the effect is the same: while MicroG is down, apps that depend on it lose sign-in, maps, location or push notifications until it restarts. The fix, then, is mostly about stopping the system from killing it and clearing out whatever makes it crash when it does start.

What Are the Most Common Causes?

Four causes account for the overwhelming majority of cases. First, battery optimisation and OEM background killers — this is the big one, detailed below. Second, a corrupted update: MicroG, an app, or your ROM updated and left incompatible cached data behind. Third, missing permissions after a ROM or system update quietly revoked something MicroG needs.

Fourth, the wrong variant: a standard build where a ReVanced-specific one is required, two variants installed at once, or a very old build on a new version of Android. If our broader list of MicroG not working fixes describes your wider symptoms, work through that too — the crash popup is often just the loudest symptom.

How Do You Fix It, Step by Step?

Start simple. Restart the phone — a genuine restart, not just dismissing the popup — then open MicroG Settings and run Self-Check. Note anything unticked. Next, whitelist MicroG from battery optimisation: Settings > Apps > MicroG > Battery > Unrestricted. Then clear the cache via Settings > Apps > MicroG > Storage > Clear cache, and use your phone normally for an hour. If the popup hasn’t returned, you were in the majority — it was the battery manager or stale cache.

If it does return, reinstall cleanly:

1. Uninstall MicroG completely from Settings > Apps, including any duplicate MicroG or Vanced MicroG entries you find.
2. Restart the phone. Don’t skip this — it clears the old service registration.
3. Download a fresh copy from the download page — the latest version available on this site, not an old APK from your files.
4. Install it and open MicroG Settings straight away.
5. Run Self-Check and grant every permission it flags, then set battery use to Unrestricted before you open any other app.
6. Test after a sleep cycle — lock the phone for fifteen minutes, then check your dependent apps and notifications.

Finally, double-check you installed the right build for your use case. ReVanced users in particular need the variant ReVanced points them to; mixing builds is a guaranteed crash loop. Our guide to MicroG settings explained helps you confirm each switch afterwards.

Does Your Phone Brand Make It Worse?

Often, yes. Samsung’s Device Care, Xiaomi’s MIUI battery saver and Huawei’s EMUI power management are all notably aggressive with background services, and each buries its controls in a different place.

On any brand, if there’s an option to lock MicroG in your recent apps screen, use it. And after every major system update, revisit these settings — OEM updates love resetting them to defaults, which is why a phone that behaved for months suddenly starts throwing the error again.

How Do You Stop It Happening Again?

Keep MicroG current: when crashes begin out of nowhere, an outdated build struggling with newer apps is a frequent culprit, so follow our notes on how to update MicroG rather than sitting on an old version. Keep exactly one MicroG variant installed. Re-check the battery whitelist after system updates. And keep an eye on Self-Check every few weeks — thirty seconds there catches permission resets before they turn into crash loops. Return to the homepage anytime for the current download and the rest of our guides.

One honest boundary: if MicroG runs cleanly but a specific banking or Play Integrity-heavy app still won’t work, that isn’t this error and no reinstall will change it. That’s a known limit of a non-Google services layer, separate from the crashing problem this page fixes.

What Should You Check if the Popup Returns Weeks Later?

A crash that comes back after weeks of calm is rarely a new problem — it’s usually an old setting quietly undone. Work through a short checklist before you reinstall anything. Has your phone had a system update since the fix? If so, re-check the battery whitelist and MicroG’s permissions, because both are commonly reset. Have you installed a battery-saver, cleaner or antivirus app recently? Those tools pride themselves on stopping background services, and MicroG is exactly the sort of service they target — whitelist MicroG inside them or remove them.

Have you installed a second app that bundles its own MicroG variant, such as another patched YouTube build? Duplicate variants fighting each other is a slow-motion crash loop. Finally, open Self-Check again and compare it with how it looked when things worked. If everything there is still ticked, the battery settings are intact and only one variant is installed, then — and only then — is a fresh clean reinstall worth your time.

Frequently Asked Questions

Get MicroG

For a clean reinstall, start from the homepage or go straight to the download page for the current build, then set the battery whitelist before you do anything else — it is the best prevention against microg keeps stopping. Download MicroG APK