Module

Universal GMS Doze: what it changes and how to use it

Universal GMS Doze is a Magisk module that removes Google Play services from Android's battery-optimization exemptions, so Doze can restrict it like any other app. It works, but the original is no longer maintained, it does more than its name suggests, and some of its changes stay until you remove it properly. Read what it changes before you install it.

Last updated 10 sourcesHow we check pages

The original module has not been updated since November 2024

Universal GMS Doze 1.9.2 (November 28, 2024) is the last release, and its changelog claims Android 15 support at most. A request for Android 16 support, opened in April 2026, has no reply, and the README now labels its downloads “Archive”. A community fork by MarsPatrick (1.9.11) says the original appears unmaintained and lists Android 14 to 16 devices it was tried on.

Status checked .

Setting up Universal GMS Doze: the whole job

  1. Step 1 · 2 minutesPick the original or the fork
  2. Step 2 · 2 minutesInstall the module
  3. Step 3 · 5 minutesExempt the apps that must stay instant
Each stage links to its full instructions below.

Why Google Play services is normally exempt

Android's Doze mode delays background work, network access and alarms when the phone is idle. System configuration files can list apps that Doze leaves alone, and phones ship with Google Play services (com.google.android.gms) on that list so that push notifications, location and account sync keep working. You can see the result under Settings → Battery → Battery optimization, where Play services usually cannot be optimized. The module takes it off the list. How much battery that saves depends on your phone and apps; neither the module nor this site publishes figures.

What the module actually changes

Reading the module's install and boot scripts shows five changes, not one:

WhenWhat it doesUndone when
InstallCopies the system XML files that exempt Play services into the module, minus the allow-in-power-save and allow-in-data-usage-save lines, so the originals stay untouched.Module disabled or removed
InstallDeletes every file with gms in its name under /data/data, clearing old Play services data. The script comment says “first install”, but the code runs it on every install.Not reversible
Install and every bootEdits the same lines out of other modules' XML files in /data/adb. At boot it also strips Play services' allow-unthrottled-location and allow-ignore-location-settings entries.Module removed
Every bootDisables Play services' device-admin receivers (auth.managed.admin.DeviceAdminReceiver and mdm.receivers.MdmDeviceAdminReceiver) for every user. This turns off Find My Device, which the README calls optional.Only when the module is removed, by its uninstall script
Every bootRuns dumpsys deviceidle whitelist -com.google.android.gms to drop the runtime exemption.Only when the module is removed

Because two changes are only reversed by the uninstall script, switching the module off leaves Find My Device disabled. Remove it instead.

Before you start

You will need

  • Magisk (or KernelSU) installed. On KernelSU 3.x, modules are only mounted once a metamodule such as meta-overlayfs is installed. The module cannot be installed from a custom recovery.
  • A decision about the version: the original gloeyisk/universal-gms-doze 1.9.2, or the maintained MarsPatrick fork, which adds a Find My Device toggle.
  • A list of apps whose notifications matter (messengers, banking one-time codes). You may need to exempt them afterwards.

Know the limits

  • Find My Device stops working while the original module is installed.
  • Late notifications. The README's own fix is to set affected apps to Not optimized battery usage.
  • Play services data is cleared on install, so you may be signed out of some Google features briefly.
  • Problems after removal. An open issue reports push notifications still missing after uninstalling; older reports fixed it by reinstalling Google Play services updates.
  • Conflicts with other modules that change the same XML files, reported as Play services crashes.

Install Universal GMS Doze

Each step has a Done box so you can keep your place. Your progress is saved in this browser only.

  1. Pick the original or the fork

    2 minutes

    On Android 15 or older, the original 1.9.2 still installs as before. On Android 16 or if you want to keep Find My Device, use the MarsPatrick fork, which says it was tried on Android 14 to 16 and lets you choose whether Find My Device is disabled. Its notes say it cannot modify Play services on OxygenOS 16.

  2. Install the module

    2 minutes

    Download the zip from the project's GitHub releases. In the Magisk app tap Modules → Install from storage, pick it and reboot.

  3. Exempt the apps that must stay instant

    5 minutes

    Open Settings → Apps, choose a messaging or banking app, and set its battery usage to Not optimized (or Unrestricted). Repeat for every app whose notifications arrive late.

Check that it worked

The module ships a checker, gmsc, which reads Android's Doze allowlist and prints Optimized or Not Optimized for Play services. You can also read the list yourself: com.google.android.gms should no longer appear under “Whitelist (except idle) system apps”. In Settings, Google Play services should now show as optimized under Battery optimization.

Check from a root shell
$su -c gmsc # or read Android's Doze state directly $su -c dumpsys deviceidle

To see Doze in action, Android's documentation lets you force the idle state while the phone is unplugged: adb shell dumpsys deviceidle force-idle, then return to normal with adb shell dumpsys deviceidle unforce and adb shell dumpsys battery reset.

Errors and fixes

Notifications arrive late

Expected for some apps once Play services is optimized. The README's advice: clear stale Play services data, and if it persists, set the affected app to Not optimized battery usage.

Find My Device says it is off

The original module disables Play services' device-admin receivers on every boot. Remove the module (not just disable it) so its uninstall script re-enables them, or use the MarsPatrick fork with its Find My Device toggle.

Notifications still broken after removing the module

An open issue (#66) reports this. Earlier reports were fixed by uninstalling Google Play services updates and updating it again from the Play Store, then rebooting.

Google Play services keeps crashing

Another module probably edits the same system XML files (issue #62). Disable other modules one at a time to find the conflict.

gmsc says Not Optimized

Make sure you rebooted after installing. On Android 16 the original is unsupported; try the fork. On KernelSU 3.x, check that a metamodule is installed so the module is mounted at all.

“Installation from recovery is NOT supported”

The module refuses to install from TWRP or another recovery. Install it from the Magisk app.

Questions people ask

Does Universal GMS Doze work on Android 16?

Not officially: the last release claims Android 15, and an Android 16 request is unanswered. The MarsPatrick fork lists Android 16 devices it was tried on.

Is Universal GMS Doze still maintained?

The original has had no release since 1.9.2 on November 28, 2024. The MarsPatrick fork (1.9.11) is the active continuation.

How much battery does it save?

There are no published measurements, from the module or anyone we could find. Results depend on your phone and apps.

Does it work with KernelSU?

The README says yes. On KernelSU 3.x, modules are only mounted once a metamodule such as meta-overlayfs is installed.

Why did Find My Device stop working?

The module disables Play services' device-admin receivers at every boot. Removing the module re-enables them.

How do I undo it completely?

Remove the module on Magisk's Modules screen and reboot. That runs its uninstall script, which re-enables the receivers and restores Play services' Doze exemption. Disabling it is not enough.

Sources

This page is written from the sources below. If anything here disagrees with them, the upstream source is correct.

Found a mistake or something out of date? Tell us and we will check it against the source and fix the page. Confirmed corrections are listed in the corrections log.

Report a problem with this page