Optimize Google Mobile Services for better battery life, privacy, and performance
GhostGMS has now reached a saturation point: after months of refinements and optimizations, the module has been fully developed to maximize battery life, privacy, and performance for Google Mobile Services (GMS) without breaking Android functionality.
While development continues, this release may represent the final major feature expansion. Future releases will focus mainly on stability, minor improvements, or compatibility updates rather than adding new optimization features.
Starting with v3.0, the release includes two separate modules under the same release:
| Module | Description | Key Differences |
|---|---|---|
| GhostGMS 3.0 (Core) | Optimized for maximum safety and compatibility | Focuses on GMS optimizations without kernel modifications |
| GhostGMS 2.0 (Legacy) | Includes previous kernel tweaks and deeper system-level tweaks | May provide additional performance gains but could affect device stability if misused |
Users can choose whichever module works best for their device and needs.
- 🔋 Better Battery Life: Reduce GMS wake locks and background activity
- 🔒 Enhanced Privacy: Disable intrusive tracking and analytics services
- ⚡ Improved Performance: Lower RAM usage and CPU utilization
- 📱 Maintained Functionality: Essential Google services remain fully functional
⚠️ GhostGMS has reached the maximum safe optimization level. Adding further tweaks risks breaking Android or critical Google services.
🛑 Ads & Tracking
Disable advertising identifiers and tracking capabilities
📊 Analytics & Reporting
Reduce data collection and analytics services
🔄 Background & Update Services
Limit background operations and automatic updates
📍 Location & Geofence
Control location tracking and geofencing services
📡 Nearby & Discovery
Manage nearby device detection and casting
☁️ Sync & Cloud
Adjust account synchronization and cloud storage
💰 Wallet & Payment
Toggle payment and wallet-related services
⌚ Wear & Fitness
Control wearable and fitness tracking features
- Download the latest release from the Releases page
- Install via Magisk Manager
- Choose the preferred module (3.0 Core or 2.0 Legacy)
- Follow the on-screen prompts to select your optimizations
- Reboot your device
⚠️ Important: After installation, you may notice temporarily higher battery usage (Active/Idle drain) for the first 24–48 hours as Android adjusts to the new configuration. This is normal and will settle down after a couple of days, resulting in better battery life.
- ❌ Doesn't modify Android kernel (3.0 Core)
- ❌ Doesn't remove Google apps or break core functionality
- ❌ Doesn't change system memory management
- ❌ Doesn't affect OTA updates
The Legacy 2.0 module may include kernel tweaks, but users should proceed with caution.
- ✅ Enable all logging controls for maximum battery savings
- ✅ Disable only service categories you don’t actively use
- ✅ Run for at least 2–3 days to see the full benefits
- ✅ Check logs in
/data/adb/modules/GhostGMS/logs/for troubleshooting - ✅ Compare performance between 3.0 Core and 2.0 Legacy if desired
| Android Version | Status |
|---|---|
| Android 14 | ✅ Compatible |
| Android 13 | ✅ Compatible |
| Android 12/12L | ✅ Compatible |
| Android 11 | ✅ Compatible |
| Android 10 | ✅ Compatible |
| Android 9 | |
| Android 8.x |
Some Google apps show notifications about Google Play services
This is normal and safe to ignore. Essential functionality still works.
Battery drain seems worse initially
Wait 24–48 hours for Android to adjust. Initial reconfiguration may temporarily increase battery usage.
GCM push notifications delayed
Enable the "Sync" category during installation if you rely heavily on timely notifications.
- Original concept and development by Veloxine
- Additional improvements by MiguVT
This project is licensed under the MIT License - see the LICENSE file for details.
GhostGMS has reached the final stage of safe optimization. While there may be minor improvements in the future, v3.0 is likely the last major feature release.
Two modules are now provided so users can choose between maximum safety (3.0 Core) and legacy tweaks (2.0 Legacy) based on their needs.
