epicmann24

OOSGMS-OPTIMISER

v1.0.8guide

Magisk module to optimise and remove trackers for GMS and OOS

★62 stars
•Performance & Kernel•by epicmann24•Proprietary•Updated Oct 12, 2025
Platforms:
✓ Magisk✓ KernelSU
Download v1.0.8Starting download...GitHub Source
OOSGMS-OPTIMISER.zip

Overview

Google Play Services (GMS) and OEM system skins like OnePlus’s OxygenOS (OOS) operate dozens of background diagnostic services, analytics reporters, and location-polling receivers. Over time, these background tasks frequently become stuck in loops, causing elevated battery drain and keeping the device from entering deep Linux kernel sleep states.

Created by epicmann24, OOSGMS-OPTIMISER is a targeted optimization module designed to disable invasive telemetry, tracking services, and unnecessary background wakelocks in both Google Play Services and OxygenOS.

Coverage & Targeted Packages

Beyond silencing core GMS analytics, the module applies component-level disable rules to common third-party apps known for heavy background telemetry:

  • Core Google Frameworks: com.google.android.gms, com.google.ar.core, com.google.android.projection.gearhead (Android Auto), com.google.android.play.games
  • Social & Media Apps: Instagram (com.instagram.android), TikTok (com.zhiliaoapp.musically), Facebook (com.facebook.katana), Reddit (com.reddit.frontpage), Telegram (org.telegram.messenger), and X (com.twitter.android)
  • Shopping & Miscellaneous: Temu (com.einnovation.temu), AliExpress (com.alibaba.aliexpresshd), eBay (com.ebay.mobile), and Coinbase (com.coinbase.android)

Installation & Safe Uninstallation

Installation

  1. Download OOSGMS-OPTIMISER.zip from GitHub releases.
  2. Install the archive via Magisk or KernelSU.
  3. Reboot your device.

Safe Uninstallation

Because the module disables individual Android component receivers via package manager hooks, uninstallation requires cleanly restoring those component flags first:

  1. In KernelSU (or using the MMRL manager app), tap the module to trigger the built-in restoration action.
  2. Once the action script confirms components have been restored, uninstall the module normally and reboot.