MicroG Push Notifications Not Working? FCM/GCM Fix Guide
Delayed notifications are the single most common complaint about MicroG — and also one of the most fixable. Messages arrive twenty minutes late, or everything floods in the moment you unlock your phone, or one important app never notifies you at all while everything else works fine. Each of those patterns points to a different cause, which is why random toggling rarely fixes anything.
This MicroG push notifications fix guide works in the right order: check the connection status screen first, then work through the fixes that solve most cases — battery whitelisting, registration order, and OEM background killers.
How does push actually work through MicroG?
On a normal Android phone, apps do not stay awake waiting for messages. Instead, each app registers with Firebase Cloud Messaging — FCM, the modern name for the older Google Cloud Messaging, or GCM. The app’s server sends a message to Google’s cloud, Google passes it down one persistent, always-on connection to the phone, and the system wakes the right app to show your notification.
MicroG provides that same service. Apps register with MicroG’s Cloud Messaging component, MicroG holds the persistent connection, and messages are delivered through it. That design is efficient, but it creates three failure points you should keep in mind: the app must have registered, the connection must be alive, and Android must not kill MicroG in the background. Almost every push problem is one of those three — and our MicroG settings explained guide covers where each related toggle lives.
MicroG Push Notifications Fix #1: Check the Cloud Messaging Status First
Do not change a single setting until you have looked at the status screen. Open MicroG Settings, then Cloud Messaging. This screen tells you two things that decide everything else: whether Cloud Messaging is connected, and which apps are registered for push.
If it shows as disconnected, your problem is the connection itself — and no MicroG push notifications fix further down this page will help until it is live. Work through the battery and registration fixes below. If it shows connected but your problem app is missing from the registered list, the app never registered, and no amount of battery tweaking will help until it does. If the app is listed and the connection is live, the problem is almost certainly the phone killing something in the background. Ten seconds on this screen saves an hour of guessing.
Is Cloud Messaging and device registration switched on?
It sounds basic, yet it catches people out — especially after a fresh install or an update that reset preferences. In MicroG Settings, make sure device registration is enabled and Cloud Messaging is turned on. Device registration gives your phone the identity that apps register against; with it off, apps have nothing to connect to, and push silently does nothing.
While you are in the settings, open the Cloud Messaging advanced and status screens to confirm the connection state after you change anything. If you toggle these options, give the phone a minute, check the status shows connected, and then test with a real message from another device or a friend — not just by waiting and hoping. This confirmation belongs in every MicroG push notifications fix, because a toggle that leaves the status screen disconnected has not solved the underlying problem.
Is battery optimization killing MicroG?
This is the number one cause of microg notifications not working and delayed messages, and it is not really MicroG’s fault. Android’s battery optimization puts background apps to sleep, and a sleeping MicroG cannot hold its persistent connection — so messages queue up until the phone wakes for another reason, then arrive all at once.
The MicroG push notifications fix is to whitelist MicroG. Go to your phone’s battery or app settings, find MicroG Services, and set it to unrestricted, or exclude it from battery optimization. Then re-check this after system updates and MicroG updates, because both can quietly reset it. Also consider the apps themselves: if MicroG is awake but a specific messaging app is heavily restricted, its notifications can still lag. If MicroG also keeps stopping entirely, fix that first — push cannot survive a service that is crashing.
Was the app installed before MicroG existed?
Here is the trap behind microg notifications not working that frustrates people most, because everything looks correct. Apps register for push when they are installed or first run — they look for a Cloud Messaging service and register with it. If the app was installed before MicroG was on the phone, there was no service to register with, so it never did. MicroG can be perfectly set up and that app will still never receive push.
The fix is to force a fresh registration. The gentler option is clearing the app’s data in its app info screen, then opening it and signing in again — it will register as if newly installed. The stronger option is uninstalling and reinstalling the app now that MicroG exists. Either way, confirm the result on the Cloud Messaging status screen: the app should now appear in the registered list. Do this for your essential apps — messaging, email, banking alerts — rather than every app on the phone.
Is your phone brand killing apps in the background?
On top of standard Android battery optimization, many manufacturers add their own aggressive background management. Xiaomi, Oppo, Vivo, Samsung, and Huawei devices are all known for extra app-killing behaviour under names like autostart management, app launch control, or protected apps. These systems can stop MicroG — or your messaging apps — from starting, staying alive, or using the network in the background, even when standard battery settings look generous.
Work through your brand’s controls: allow MicroG to autostart, set its app launch or background behaviour to manual and fully allowed, and lock it in the recent-apps screen if your launcher offers that option. Apply the same treatment to the one or two apps whose notifications matter most. If you have tried everything here and problems persist across many apps, our broader MicroG not working fixes guide is the next step.
One honest warning: you will find old forum posts suggesting dialer codes and heartbeat tricks. Treat them with suspicion — the reliable controls are the ones visible in MicroG’s own Cloud Messaging status and advanced screens and your phone’s battery settings, not secret codes that vary by device and often do nothing. In practice, a MicroG push notifications fix should start with evidence from the status screen, not a code copied from an old thread.
Which apps will never push properly on MicroG?
Finally, the honest limit. Some apps tie themselves tightly to Google’s own integrity checks — Play Integrity — or expect behaviour MicroG deliberately does not reproduce. Certain banking and payment apps, some work and security apps, and occasional high-profile apps fall into this group. Their notifications may never arrive reliably, or the apps may refuse to run properly at all, no matter how perfect your settings are.
That is not a failure on your part, and no setting will change it. Your options are to accept in-app checking for those services, use their web versions, or keep those accounts on a device with official Play Services. Everything else should push correctly once registration, connection, and battery are sorted — the three steps behind almost every successful MicroG push notifications fix. If yours still do not, revisit the guides on the homepage and confirm MicroG is current via the download page.
Frequently Asked Questions
Why are my microg notifications not working until I open the app?
That pattern usually means MicroG or the app is being put to sleep by battery optimization. Whitelist MicroG in your battery settings, check the OEM background restrictions for your phone brand, and confirm Cloud Messaging shows as connected in MicroG Settings.
How can I tell if an app is registered for push with MicroG?
Open MicroG Settings, then Cloud Messaging. The status screen shows the connection state and lists the apps that have registered for push. If your app is missing from that list, it never registered — clear its data or reinstall it now that MicroG is installed.
Do apps need to be installed after MicroG to get notifications?
The MicroG push notifications fix here is registration order: apps need to register after MicroG exists. An app installed before MicroG often never registered, because there was no Cloud Messaging service to register with at install time. Clearing the app’s data or reinstalling it forces a fresh registration.
Why do some apps have microg notifications not working no matter what?
Some apps depend on hard Play Integrity checks or proprietary Google behaviour that MicroG cannot reproduce. Banking, payment, and a few high-security apps are the common examples. For those, delayed or missing push is a limitation, not a setting you missed.
Should I turn on device registration in MicroG?
Yes, if you want push notifications. Open MicroG Settings and make sure both device registration and Cloud Messaging are enabled. Without registration, apps cannot create the push identity MicroG needs to deliver their messages.
Get MicroG
Running an old build can cause push problems all by itself, so before any other MicroG push notifications fix, make sure you are current: visit the homepage for the latest guides, check the download page for the newest build, or install it directly: Download MicroG APK. Then check the Cloud Messaging status screen once more — with a live connection and your apps registered, your notifications should finally behave.