microg/GmsCore

What it does

microG Services is a FLOSS framework that lets apps written for Google Play Services run on Android systems where Play Services is not available. Instead of shipping Google's proprietary user-space components, it provides free implementations and stubs for the APIs those apps call: sign-in, push notifications, geolocation, maps and Firebase-related calls are among the listed topics. The practical target is custom ROMs and de-Googled devices that still need mainstream apps to launch and work.

Implementation is a mix. Some Play Services calls are replaced with fully free implementations, some are no-ops, and some are forwarded to Google's own remote endpoints, as described in the project discussion on Hacker News. Which category a given feature falls into determines how much data still leaves the device.

Getting started

The repository README does not contain installation steps; it directs users to the project wiki for downloads and instructions. Use that wiki as the authoritative entry point and follow the build for your Android version and ROM. The code itself is Java and can be built from source via the project's CI build workflow setup.

A typical path looks like this:

1. Check that your ROM supports the Play Services signature spoofing microG relies on (see constraints below).
2. Download the build recommended by the wiki for your Android version.
3. Install the microG services package and any companion components the wiki lists.
4. Grant the permissions the wiki requests, then test with an app that depends on Play Services sign-in or push notifications.

No supported version matrix, package order or command-level install steps are given in the provided material, so treat the wiki as required reading rather than guessing from the README.

Constraints

• Signature spoofing is required. Apps trust the Play Services package by signature, so the system must be patched to let microG impersonate it. Commenters note that this is narrowly scoped on LineageOS but still introduces risk in general in the discussion.
• Feature coverage is partial by design. Expect no-op stubs for some APIs and Google-server calls for others; an app may work on one ROM and fail on another. In the same thread, users report that app-store and payment integrations in third-party ROMs can come from companion apps rather than microG alone discussion.
• Licensing. The code is Apache-2.0, so reuse and redistribution are permitted under that license.

HotRepo's take

In the daily Java-language ranking for 2026-11-01, the project recorded 17 new stars and a best position of 13; it has no recorded placement on the all-language GitHub daily ranking. A Hacker News thread from 2026-10-20 drew 431 points and 132 comments thread, and the discussion shows the two sides of the project clearly: one commenter asks why apps like a French retailer's payment flow work under microG on /e/OS but not on plain LineageOS comment, and the answers point to companion apps such as App Lounge handling store and payment paths reply. Another thread of comments centers on signature spoofing as the unavoidable cost of using microG at all comment. The takeaway from the discussion is that microG is a compatibility layer with uneven coverage, not a drop-in Play Services equivalent, and evaluations should be per app and per ROM rather than per star count.