Android was born as an open system, but the Android we use on our phones has little to do with that pure open-source project. On top of the AOSP released by Google, a whole layer of... Google's proprietary services, APIs, and applications These are the things that really make "everything work" as we expect... and also the things that turn the system into a sieve of data towards the company's servers.
For those who want to continue using Android without giving up (almost) any apps but avoiding Google as much as possible, a key name emerges: MicroG, a free alternative to Google Mobile ServicesThis project attempts to replicate much of the behavior of Google services, but in an open, more controllable way, without depending on the company's official layer.
What is MicroG and what problem does it want to solve?
When we talk about Google services on Android, we're not just referring to Gmail, Maps, or YouTube, but to a whole range of APIs, libraries, and background processes (Google Play Services / GMS) These APIs, used by thousands of applications, allow for the integration of maps, push notifications, enhanced location services, advertisements, health data synchronization, backups, login, and more, without requiring each developer to reinvent the wheel in their own app.
The trouble starts when the device It does not have Google Play Services installed or is not certified by GoogleThis is what happens with many alternative ROMs without GApps, with Recent Huawei phones without certification or those who have decided to erase all traces of Google from their phones. Under these conditions, not only do Google's own apps stop working, but also a good number of third-party applications that depend entirely on that framework.
Huawei, for example, reacted by creating its own Huawei Mobile Services (HMS) As an alternative to GMS, MicroG expected developers to adapt their apps to use one system or the other depending on the mobile device. MicroG proposes another approach: instead of requiring changes to all apps, It mimics the interface of Google services so that applications "believe" they are still talking to Google., when in reality they are relying on an open-source replacement.
Put simply, MicroG is a set of components that masquerades as Google Play Services. using replacement APIs (“fake” but compatible) that expose the same basic structure. Thus, an app that requires GMS to display a map, receive notifications, or check location can continue to function on a phone that doesn't have a single official Google app installed.
Main components of MicroG and what it replaces
Google's services are very complex and cover many areas, so MicroG doesn't replace them 100%, but it does cover some of the bases. an important part of the components that are most used on a daily basisAmong the most relevant modules are:
- Service Core (GmsCore)This is the heart of the project. It provides much of the functionality needed for applications that depend on Google Play Services to start up and offers compatibility with the Google Maps Android API v2Basically, it acts as the "service layer" that most apps using GMS expect to find.
- Services Framework (alternative Google Services Framework)This module allows applications to interact with the cloud-based messaging system traditionally offered by Google (C2DM/FCM). Thanks to this module, Push notifications can still work without having the official framework installed.
- Unified location providerIt is a library that provides advanced location using Wi-Fi and cell phone towerswithout relying solely on GPS. With it, apps can obtain a location faster and more efficiently, similar to what they would get using Google services.
- Maps API: includes support for the Google Maps API version 1.0This is useful for older applications that still use it. Combined with GmsCore, MicroG covers various scenarios where maps need to be displayed within other apps.
- Store (under development)The project includes a proprietary store application that allow access to Google Play apps without depending on the official store, although this part continues to evolve and is not the main pillar of the ecosystem today.
Although the support isn't perfect, Many applications that refuse to start without GMS manage to work thanks to MicroGSome Google apps like Google Maps are also usable, which is already a significant achievement considering the system is not certified.
MicroG, Android AOSP and alternative ROMs
It's important not to confuse concepts: Android as such is an open source system (AOSP), while The "commercial" Android that comes on most mobile phones includes Google Play Services by default. and the entire proprietary ecosystem. Just because a phone uses Android AOSP doesn't automatically mean it runs GMS; in fact, many Chinese devices or projects like pure LineageOS are distributed without Google's interface.
In these cases, MicroG comes into play as alternative framework compatible with applications that expect to find Google Play ServicesIt is a particularly interesting piece in:
- ROMs like LineageOS, /e/OS, Replicant or AospExtended that, by philosophy, They are offered without Google apps pre-installed.
- Mobile devices without certification where the official GMS suite cannot be installed as standard.
- Advanced users who want an Android that is as free as possible from Google trackingbut they also don't want to give up apps that depend on the company's framework.
One of the key advantages of MicroG over flashing GApps is that It does not necessarily require a complex flashing process or an unlocked bootloader in all scenariosHowever, in classic ROMs without stock support, it is usually necessary to delve into that more technical area.
microG GmsCore: the “free Google Play Services”
Within the MicroG universe, the most talked-about component is microG GmsCoreYou can think of him as a framework to replace Google Play Services It is installed on phones without official services and acts as a bridge between apps and the system.
On a typical Android phone, Google Play Services are almost essential for many functions to work smoothly: the Play Store itselfGoogle Maps, the push notification system, account synchronization, and many other system layers are all part of the system. Therefore, when a device is sold without GMS, problems arise with countless applications that depend on it.
In those scenarios, microG GmsCore allows you to "hook" most apps that depend on Google Play Services without installing the official framework. It is widely used on Chinese brand phones without factory-installed GMS and on AOSP-based ROMs to prevent users from having to give up their usual app catalog.
Technical requirements: ROM without Google and signature spoofing
Installing MicroG isn't just a matter of randomly flashing an APK. For it to work properly, the ROM has to meet certain requirements. two basic technical conditions:
- ROM without Google packagesThe system must not have official Google apps and services installed. If they come pre-installed in /system, you must use a "clean" ROM (for example, LineageOS without GApps) or remove the Google components one by one, usually requiring root access and some technical skill.
- Support for signature spoofing: is a mechanism by which the ROM allows an application (MicroG) simulate the digital signature of another app (Google services)Without this "controlled deception," many apps would not accept MicroG acting as a substitute for GMS.
Some ROMs already include factory-integrated signature spoofingThis is the case with specific LineageOS builds with MicroG pre-installed or projects like AospExtended, where it can be enabled from the advanced application settings. On other systems, additional patches are required using root access, Xposed, or tools like Needle or Haystack.
In summary, a pre-configured ROM will suffice to Install and configure MicroG just like any other app.With a "closed" ROM and Google pre-installed, the process usually involves rooting, manually removing Google apps from /system/app and /system/priv-app, and applying a signature spoofing patch, which is not exactly suitable for those who don't want to complicate things.
How to install MicroG on custom ROMs
Each device and ROM has its nuances, but the general scheme for using MicroG on a "classic" Android without Google usually follows these logical steps:
- Choose or install a ROM without GAppsFor example, a LineageOS build without the Google packages, /e/OS, Replicant, or another ROM where you can do without installing GApps.
- Guarantee signature spoofing supportIf the ROM already includes it (as is the case with LineageOS using MicroG or AOSP Extended with the option in settings), simply activate it. Otherwise, you'll usually need to install modules like FakeGApps via Xposed or apply patches using tools like Needle or Haystack.
- Flash or install MicroG: from recovery (TWRP or other) if you use prepared ZIP packages, or by installing the official MicroG APKs and their components downloaded from GitHub or the project's official website.
- Configure permissions and perform self-checksWithin the MicroG app there is a "self-check" section that allows you to verify which services are working and which permissions are missing.
- Set up an alternative store: such as F-Droid for free apps, Aurora Store or Yalp Store to download APKs directly from Google Play without using the official store.
It is important to be clear that Entering this world always involves risk.From strange behavior to a possible bricked device if something goes wrong during flashing, the usual recommendation is to start by testing on a second device and thoroughly read forums and guides specific to your model before proceeding.
MicroG versus not using any Google services
Among advanced users, the question often arises as to whether it is better to use MicroG or going to the extreme of not having a single service compatible with GoogleIn a completely free ROM without GMS or substitutes, applications that require these services simply will not work or will do so in a very limited way (for example, without push notifications or without being able to log in).
With MicroG, on the other hand, a balance is achieved: A fairly high level of compatibility is maintained with the Android app ecosystem.But it significantly reduces dependence on Google and offers more control over which permissions are granted and what data is shared. It's a personal choice: maximum freedom and fewer apps running, or a middle ground with MicroG as an alternative layer.
Regarding resource consumption, MicroG is designed to be Lighter than official Google Services, both in RAM and battery usageIt doesn't work miracles, but many users notice fewer intrusive background processes. However, if you completely eliminate any such services, battery life can improve even further… at the cost of losing key features like instant notifications or "smart" location tracking in many apps.
MicroG in the Huawei ecosystem: EMUI, HarmonyOS and AppGallery
The Huawei case deserves its own chapter. After the US ban, the brand was left without Google Play certification and without official access to GMSDespite continuing to use Android AOSP as its base (and later HarmonyOS as a convergence system), its phones stopped including the Play Store and Google Play Services, which greatly complicated their use in Europe and other regions where those services are almost standard.
To survive, Huawei boosted its own ecosystem with HarmonyOS, Huawei Mobile Services (HMS), and the AppGallery storeThe problem is that many key applications were still expected to find GMS and the famous Google Services Framework, so the experience wasn't quite identical to that of a "classic" Android.
For a time, solutions like GBox acted as containers for Google-dependent apps (YouTube, YouTube Music, Gmail, Drive…). But these were still just workarounds, with their limitations and performance cost overruns. This is where MicroG's arrival in the Huawei ecosystem marks a turning point.
MicroG presents itself in this context as A free software project that fills the gap left by GMS on uncertified devices.It includes its own GmsCore and the necessary components so that a phone or tablet with EMUI or HarmonyOS can behave, in the eyes of many apps, as if it had Google services, but without installing the official packages.
Installing MicroG and Aurora Store on Huawei mobiles and tablets
Modern MicroG integration in Huawei is much more user-friendly than in the world of "raw" ROMs. In recent versions of EMUI (from 14/14.2 onwards) and HarmonyOS 4MicroG is offered directly through AppGallery, the official store, and the usual way is to search and install “microG Service” like any other app.
On a Huawei smartphone with EMUI 14, the typical workflow would look something like this:
- OPEN Open AppGallery and search for “microG Service”, installing the application like any other.
- Allow the process itself to also install “microG Companion”, an auxiliary app needed to complete the integration.
- Download from AppGallery Aurora Store, which is a free client for the Google Play Store.
- Open the MicroG app and use the section of “Self-check” to verify that all required services are active.
- Grant the necessary permissions in the section of EMUI “Permissions granted” (network, storage, account access, etc.) for the services to function properly.
- Link your Google account both on MicroG and, if you prefer, on Aurora Store to be able to use apps that require Google login.
Tablets with HarmonyOS 4 have a similar approach, although in some cases it touches Visit the official MicroG website to download the APKs and then install them manually. Content creators and video tutorials make this process much easier for less technical users.
Once operational, Aurora Store acts as an unofficial Google Play clientThis allows you to access the Google Play Store's catalog of apps and games, sign in with an account, download, and even update applications. It's not the Play Store itself, but it connects to Google's servers as a client and allows you to download free apps and paid apps already associated with your account.
What can MicroG do on Huawei and what limitations does it have?
With MicroG and Aurora Store integrated, a Huawei with EMUI 14 or HarmonyOS becomes much more usable and closer to the experience of a classic AndroidThe user can install applications like these without much trouble:
- Snapchat, TikTok, WhatsApp, Instagram, Spotify, Outlook and other popular third-party apps.
- Google Maps, YouTube, Gmail, Drive, Google Photos, Google Keep, Calendar and a large part of Google's own ecosystem.
In addition, MicroG makes it possible to use features such as Android Auto via cable In many vehicles, this is something highly demanded by those who spend the day on the go and want to continue projecting their mobile phone onto the car's screen.
Not everything is perfect, though. As of February 2025, for example, still unable to natively link watches with Wear OS In these environments, it's a limitation to consider. Huawei partially compensates for this lack with its own range of smartwatches, which generally offer much better battery life, but it's still a point to take into account.
In the field of mobile payments, Google Pay does not work on this type of configurationJust as it's not available on iOS, the alternative involves solutions like Cornerswhich allow you to pay with your mobile phone using its own layer, independent of Google Pay and relatively easy to migrate to other devices in the future.
Security, institutional support, and alternative stores
MicroG is not a “shady” invention without backing: it is a open source project supported by the /e/ Foundation, several European public administrations (such as the German Federal Ministry of Education) and even highly rated by European Union institutions in terms of privacy and transparency.
Their philosophy centers on give the user more control over what is shared and with whomBecause it's not a Google product, MicroG reduces data monitoring directed at the company and more clearly discloses what permissions it uses, which APIs it emulates, and for what purpose. This is why it has been well received in government and academic circles concerned with digital sovereignty.
In parallel, when opting out of the official Play Store, it is common to rely on alternative stores and secure repositories to complete the application ecosystem. Among the most used in combination with MicroG are:
- F-DroidA catalog focused on free software applications, highly valued in privacy and development environments.
- Aurora Store: an open-source client for Google Play that allows you to download, update, and search for apps from the official catalog without having the Play Store installed.
- Yalp Store: veteran tool for extracting APKs directly from Google Play, used mainly in older configurations.
- Other stores like XDA Labs, Aptoide, or the Amazon Appstore, which fill specific gaps or applications that do not appear in the previous repositories.
Final considerations
As always when you leave the official Google store, you have to Carefully monitor the origin of APKs and check the signatures. To avoid malware or manipulated packages, downloading from the project's official website or from reputable repositories is almost mandatory.
Ultimately, MicroG has become a key component for those who want a freer and more controlled Android experience without being left behind when it comes to applications: from advanced ROMs like LineageOS to Huawei phones with EMUI and HarmonyOS, this open-source framework allows the ecosystem of apps that depend on GMS to remain alive, reducing Google's weight on the system, improving privacy, and maintaining a very high degree of compatibility with everyday use. Share the information so that more users can learn about the topic.
