Last updated: October 2026 · 7 min read

Table of Contents

How to Update MicroG to the Latest Version Safely

How to update MicroG sounds risky to a lot of people, mostly because nobody wants to break a setup that took an afternoon to get working. The good news is that a normal update is one of the simplest jobs in the whole MicroG world: you download the newer GmsCore APK and install it over the top of the old one. No uninstalling, no starting again, no re-adding your account.

This guide on how to update microg walks through the whole process safely — checking your current version first, doing the update, understanding the one error that actually causes trouble, and running a short checklist afterwards so push notifications and sign-in keep working exactly as before.

Why do MicroG updates actually matter?

Google changes its APIs constantly, and apps are built against the current version of Play Services. When your MicroG build falls too far behind, apps start complaining that Play Services is outdated, or quietly lose features. Updates also carry fixes for Firebase Cloud Messaging — the system behind push notifications — plus compatibility work for maps, location, and sign-in that apps lean on every day.

You do not need to update obsessively. But if notifications have become unreliable, an app has started warning about Play Services, or you have not updated in many months, a fresh build, following how to update microg properly, is often the quickest fix — and it is worth trying before the deeper troubleshooting in our MicroG not working fixes guide.

How do you check which version you have now?

Before you change anything, find out where you are starting from. Open MicroG Settings from your app drawer, then look in the About section. It shows the installed GmsCore version, so you can compare it with the latest version available on this site. While you are there, glance at the Self-Check screen too — if everything is ticked now, you have a healthy baseline, and any change after the update will be easy to spot.

Also note where your original install came from — this site, a ROM, or a fork. That matters for the signature issue below, as our how to install MicroG guide explains.

How to update MicroG safely, step by step

The update itself takes about two minutes. Work through these steps in order:

Download the new GmsCore APK from the download page on this site — the latest version available on this site — using the same source as your original install wherever possible.
Open the downloaded APK and tap Install. Android will recognise it as an update to the existing app, not a new app. Allow installation from your browser or file manager if Android asks.
Wait for the install to finish, then open MicroG Settings again. Confirm the version shown in About has changed to the new build.
Re-run Self-Check from MicroG Settings and make sure every item is still ticked, including signature spoofing and battery optimization status.
Open Settings, then Cloud Messaging, and confirm the connection status looks healthy and your important apps are still listed as registered for push.
Send yourself a test — ask a friend to message you, or trigger a notification from an app you rely on — and confirm it arrives promptly.

That is how to update microg in full: no restart is usually required, though a reboot does no harm if anything feels sluggish afterwards.

What does the signature-mismatch error mean?

This is the one update problem that stops people cold, so it deserves a plain explanation. Every Android app is signed with a developer key. Android will only install an update if the new APK carries the same signature as the version already on your phone. If the signatures differ, Android refuses the install — often with a vague message about a conflict with an existing package.

In practice, this happens when builds get mixed: your original MicroG came from one source, and the update came from another that signs its builds differently. Forks and variant builds, including the ones discussed in MicroG vs Vanced MicroG, are a common cause. Neither build is broken — they just cannot update each other.

Your two fixes are simple. Either go back to your original source and get its latest build, or uninstall the old version and do a clean install of the new one. A clean reinstall works, but understand the cost: you will need to add your account again and let your apps re-register for push, just like a first-time setup.

What survives an update — and what does not?

On a normal, same-signature update, almost everything survives. Your Google account added to MicroG stays signed in. Your settings — Cloud Messaging preferences, location options, device registration — stay as you left them. Apps registered for push stay registered, which is why a quick status check afterwards is normally all that is needed.

A backup is not usually needed for this kind of update, and most people never make one. Still, take two minutes to note your key settings and which account you used. That small note turns a rare worst-case — a forced clean reinstall — from a disaster into a ten-minute job. What does not survive is a clean reinstall: uninstalling wipes MicroG’s data, so accounts, settings, and registrations all need to be set up again.

What should you check after the update?

Run through this short post-update checklist before you declare victory:

Self-Check: every box ticked again in MicroG Settings, with no new warnings.
Battery whitelist: confirm MicroG is still excluded from battery optimization — updates and system changes can quietly reset this, and it is the top cause of delayed notifications.
Cloud Messaging: open the status screen and confirm the connection is live and your key apps still show as registered.
Your problem app: open the app that prompted the update and confirm its warning or error is gone.
Location and maps: if you use them, open a maps-based app briefly and check your position loads correctly.

If something on the list fails, it is usually one setting rather than a broken update. Toggle the relevant MicroG setting off and on, reboot once, and check again before assuming the worst.

When is a clean reinstall better than an update?

Sometimes, instead of following how to update microg, starting fresh is genuinely the smarter move. Choose a clean reinstall if you are switching sources or forks and hit the signature wall, if your install has survived several messy fixes and never quite worked right, or if Self-Check shows problems that a normal update does not clear. It is also the honest answer when your original install came from a source you no longer trust.

Plan it like a small project: note your settings, remove the old build, install the latest version available on this site, add your account, open your important apps once so they register for push, and re-check the battery whitelist. Done carefully, your phone will be in a cleaner state than any update could give you. And if you get stuck, start from the homepage — the guides there assume nothing and walk you through it from zero.

Frequently Asked Questions

Do I lose my accounts and settings when I update MicroG?

No, not on a normal same-signature update. Installing the newer GmsCore APK over the old one keeps your accounts, settings, and app registrations in place, because Android treats it as an update to the same app, not a new install.

Why does Android refuse to install my MicroG update?

The usual cause is a signature mismatch. The new APK was signed with a different key than the version already installed, often because the two builds came from different sources. Android refuses differently-signed updates to protect you, and the fix is to stick to one source or do a clean reinstall.

Do I need to back up before updating MicroG?

A backup is not usually needed for a straightforward update, and most people update without one. It is still worth noting your important settings and which account you used, so you can quickly restore your setup if you ever need a clean reinstall.

How often should I update MicroG?

Revisit how to update microg every month or two, and update sooner if push notifications break, an app starts complaining about an outdated Play Services version, or a new release mentions fixes for something you use. There is no need to chase every minor build the day it appears.

What should I check after updating MicroG?

Re-run the Self-Check in MicroG Settings so every box is ticked again, open Settings and then Cloud Messaging to confirm the connection is live and your apps are still registered, and confirm MicroG is still excluded from battery optimization.

Get MicroG

Ready to update? Read the version notes on the download page, start from the homepage if you want the full picture first, or grab the file directly: Download MicroG APK. Install it over your current build, run the checklist above, and you are done — that is how to update microg safely, start to finish.