What Is ReVanced GmsCore?
GmsCore is a lightweight implementation of Google's framework APIs, maintained by the ReVanced project. The Vanced ecosystem called its equivalent "MicroG", and the two names still get used interchangeably. For non-root users it provides:
- Google account sign-in
- Push notifications
- Account sync (subscriptions, history)
- Authentication tokens
Mechanically, a patched YouTube app is no longer the app Google signed. Android's real Play Services will not hand credentials to an app whose signature does not match what it expects, so the patched build has nothing to authenticate against. GmsCore fills that gap: it implements enough of the Play Services interface for the patched app to talk to, and it holds the account itself. Your sign-in lives in GmsCore, and the patched app borrows it.
It is deliberately partial. GmsCore does not attempt to be a full Play Services replacement, and it does not carry the location, advertising, or device management services that the real thing includes. It covers accounts and push, which is what a patched video client actually needs. Our MicroG glossary entry covers the wider background if you want the history.
When Is ReVanced MicroG Needed?
Only for non-root installations. With root (Magisk), the patched app replaces the original and talks to the device's existing Google Play Services, so GmsCore stays out of the picture.
You can skip it entirely if you never sign in. A patched app without an account still blocks ads and plays in the background; what it loses is your subscription feed, watch history, playlists, and notifications. Plenty of people run it that way on purpose. If you are unsure which install type you have, the root versus non-root explainer makes the distinction clear.
Installing It in the Right Order
- Get ReVanced GmsCore from the project's own official repository. Nowhere else. This component holds your Google credentials, so provenance matters more here than for anything else in the setup.
- Install it before the patched app. The patched build checks for it at first launch, and installing it afterwards leaves the app convinced it is absent.
- Open GmsCore and sign in there. The account lives in this app, not in the patched one.
- Grant it the permissions it asks for, including notification access if you want push to work.
- Exclude it from battery optimisation in Android's settings before you test anything.
- Now install and launch the patched app, and sign in when prompted.
Common Issues
- Login failures: install or update GmsCore from the official ReVanced repository
- Battery drain: turn off battery optimization for GmsCore in device settings
- Missing notifications: allow GmsCore to run in the background
- Sign-in screen loops back to itself: almost always wrong install order, or a stale GmsCore build against a newer patched app
- Account signs itself out after a few days: an OEM power manager is killing GmsCore while the screen is off
Why these cluster the way they do: GmsCore is a background service holding a long-lived connection, and modern Android is designed to shut exactly that kind of thing down. Most reported failures are the operating system doing its job rather than a bug. Xiaomi, Samsung, Huawei, and Oppo devices are the frequent offenders because their power management is more aggressive than stock Android's.
Verifying It Works
Three checks, in order. Open GmsCore and confirm the account is listed and the self-check screen shows its services registered. Open the patched app and confirm your subscription feed is populated rather than empty. Then lock the phone for half an hour, unlock, and confirm you are still signed in. That last one catches the battery-optimisation problem, which looks fine immediately after setup and only shows up later.
Honest Status
ReVanced GmsCore is maintained alongside the rest of the project and generally keeps up with Google's authentication changes, but it is community software with no guarantees. Login has broken before and will break again when Google adjusts something on its side, and the fix arrives when a volunteer ships it. If your account access matters more than ad blocking does, that is worth weighing. The discontinued Vanced MicroG is the cautionary version of this story: it still installs, and its login has been unreliable for years with nobody left to repair it.
Frequently Asked Questions
For practical purposes on this site, yes. The ReVanced project ships a component called GmsCore that does the job Vanced MicroG used to do, and most people still search for it under the old name. The underlying upstream microG project is separate and older; the ReVanced build is a fork tailored to patched apps. Guides using either name are usually describing the same install step.
No. A rooted install mounts the patched app in place of the original and lets it use the real Google Play Services already on the device. GmsCore exists to stand in for Play Services when the patched app cannot use it, which is only the non-root case. Installing it anyway on a rooted device adds a component you do not need.
Ordering is the usual reason. The patched app checks for GmsCore at first launch, so installing GmsCore afterwards leaves the app in a state where it does not look again. Uninstall the patched app, confirm GmsCore is present and signed in, then reinstall. Battery optimisation killing GmsCore in the background is the second most common cause.
It can, though the reports vary a lot by device. GmsCore holds a background connection for push notifications, and some OEM power managers fight that connection repeatedly, which costs more battery than leaving it alone would. If you do not need notifications from the patched app, turning push off inside GmsCore usually settles the drain.
The component is open source and its releases come from the ReVanced project's own repository, which is the meaningful safeguard. The risk is not the design, it is provenance: a copy taken from a random APK mirror could be anything, and it would be holding your account credentials. Install it from the official source, and if the idea still makes you uneasy, use an account you do not mind losing.
Yes, but the patched app loses account access when you do. Subscriptions, history, and playlists stop syncing and the app falls back to signed-out behaviour. Nothing on Google's side is affected, so signing back in after reinstalling restores everything.