Universal GMS Doze

gloeyisk

Magisk KernelSU APatch
1.9.2
Version
14.82 KB
Size
Nov 28, 2024
Updated

Module Info

  • Contributors gloeyisk
  • Source Code View Repository
  • Tags
    #Universal GMS Doze #Doze #Battery Optimization #Google Play Services #GMS #Android Battery #Root Module

About this module

Universal GMS Doze makes Google Play services eligible for Android's battery-optimization and Doze policies, trading unrestricted background activity for potentially lower idle power use.

Doze Policy for Google Services

A systemless policy change for Android 6.0 and later, with a command-line utility for status and maintenance.

Doze Eligibility

Removes the usual exemption that keeps Google Play services outside normal idle optimization.

Maintenance Console

Provides the root command gmsc for module controls and diagnostic information.

Observable Trade-Offs

Idle restrictions can delay cloud messaging, account synchronization, location reporting, and other background work.

How the Module Changes GMS

Google Play services normally receives special treatment that permits substantial background activity. Universal GMS Doze patches the relevant application and service policy so the package can be optimized by Android's device-idle framework.

The module targets Android API level 23 and later and is packaged for Magisk, KernelSU, and APatch-style root environments. It does not replace Android's Doze implementation or impose a universal sleep schedule; the ROM still decides when the device enters idle states.

Verification and Control

Open a terminal, enter a root shell, and start the supplied console. Android's device-idle service can also be inspected directly.

$ su
# gmsc
# dumpsys deviceidle

In the upstream verification method, com.google.android.gms should no longer appear in the ordinary device-idle whitelist. Test notification delivery and synchronization over several real idle periods rather than judging the change immediately after reboot.

Notification and Service Impact

Apps that depend on Firebase Cloud Messaging can receive notifications later while the device is idle. Location History, Find My Device, account sync, wearable integrations, and vendor services may also rely on unrestricted GMS activity. Results differ by ROM, app priority, network state, and notification implementation.

If a required feature becomes unreliable, revert the module before clearing Google Play services data. Data cleanup is disruptive, can remove account-related state, and should be attempted only with a backup and a clear reason.

Battery savings are workload-dependentThe module changes eligibility for optimization; it does not guarantee a particular screen-off drain reduction. Measure idle behavior on the same network and usage pattern, and prioritize reliable notifications where they are operationally important.