MicroG: Open-Source Replacement for Google Play Services
GmsCore only works on ROMs that support signature spoofing, and it is only one piece of the stack. What to check before you commit to a microG-based setup.

An AOSP-based ROM such as LineageOS ships without Google Play Services. Any app that calls proprietary Google APIs, whether for location, push or maps, has nothing to talk to, and either degrades or refuses to run. That missing layer is a closed-source piece of Android user space, and it is what most people mean when they say 'GApps'.
microG GmsCore is a free software reimplementation of that layer. It answers the API calls apps make to Play Services, so those apps can run on a ROM that does not carry Google's binaries. This article covers what the project says it does, what it needs from your device, and where the model has limits you should know about before you build on it.
The scope here is deliberately narrow. It rests on the project's own wiki, which describes the design and requirements but not per-API coverage, so for anything specific to your app you will need to check the project's status page yourself.
What GmsCore replaces
GmsCore stands in for Google Play Services. Apps call the same Google APIs they always did, and GmsCore handles those calls instead of Google's proprietary package. The project describes itself as a free replacement for the non-free, proprietary Play Services, and the licence is Apache 2.0.
The wiki is candid about what this does and does not buy you. It is a tool to 'reclaim your privacy and freedom', but the apps you run that use it may still rely on proprietary libraries to communicate with microG, exactly as they do with the real Play Services. The replaced layer is open. The apps on top of it are whatever they were before.
The listed features include opt-in to Google services, which extends application support only where you choose it, and both on-line and off-line location. The project also claims it is easy on battery, memory and CPU and carries no bloatware. These are the project's own claims, and the wiki gives no benchmarks, so test them on your own hardware rather than taking them as measured.
Signature spoofing is the hard requirement
The system requirement is one line, and it decides whether you can use microG at all: your Android system must support signature spoofing. GmsCore uses it to pretend that the official Play Services exist, so applications calling Google APIs find what they expect.
In practice this means the ROM matters. Some ROMs support signature spoofing out of the box, and the wiki links to a page listing them and describing what you can do about the others. If you are picking a ROM for a managed fleet or a product, check this before anything else. A ROM without the capability is a dead end for GmsCore, whatever else it offers.
The wiki does not go into how each ROM provides the capability, and neither will this article. Follow the linked page and treat it as the authority for your device.
The pieces of a working setup
GmsCore on its own is not a complete setup. It includes the Unified Network Location Provider module, UnifiedNlp, which handles application calls to Google's network location provider. That is the part behind the network-based location feature.
For a fully working microG setup, the wiki says you must also install a Play Store replacement app, with microG Companion as the example it gives. The installation page covers the steps. The point to take from the overview is that you are assembling components: the core services, the location module, and a store replacement.
The project also says it works on real devices, test emulators and virtual mobile infrastructure. For a team that tests Android apps without Google's services, running the same stack in an emulator as on a handset is a practical advantage. The wiki does not say how emulator setups differ, so verify that part yourself.
Checking whether your app's APIs are covered
A reimplementation only helps for the APIs it implements. The project documents the current status of implemented APIs on a dedicated wiki page, and that page, not the overview, tells you whether the calls your app makes are handled.
Before you commit to a microG-based ROM, list the Google APIs your app or your users' key apps depend on and compare them against that status page. I would not infer coverage from the fact that an app 'runs'. An app may start and still fail when it reaches a call that GmsCore does not implement.
When something does misbehave, the wiki asks for specific information in bug reports:
- logs
- screenshots
- version numbers
- device information, depending on the issue you observed
It also asks you not to contact third-party app authors when a problem might be related to microG services, since they cannot fix it. If a logcat contains sensitive data, the project says you can send it as a private message rather than posting it publicly.
Where this does not fit
The first limit is the device. Without signature spoofing support, GmsCore cannot do its job, so a locked-down stock ROM is not a candidate. You are choosing a ROM and a stack, not installing an app.
The second is coverage. microG is a reimplementation, and the wiki frames API support as a status that changes over time, which it hands you to check. If your product depends on a Google API the project has not implemented, nothing in the overview promises a workaround.
The third is the privacy claim. Replacing Play Services with free software gets rid of the proprietary layer, but the wiki itself notes that apps may still use proprietary libraries to talk to microG. If your goal is a verified absence of proprietary code across the whole device, microG addresses one layer of that and no more. It also asks you to assemble the pieces yourself, including a store replacement, which is a real maintenance cost for anyone supporting more than a handful of devices.
- #Android user space
- #GmsCore
- #LineageOS
- #UnifiedNlp
- #microG
- #signature spoofing



Comments