COPG is a Zygisk module that supplies selected Android apps with alternative device and CPU identity data. Its WebUI assigns profiles per package and also manages optional locale, refresh-rate, privacy, identifier, network, location, and comfort tweaks, with some capabilities reserved for COPG Pro.
Per-App Identity Profiles
COPG changes what a targeted process reports about the device; it does not physically upgrade the display, GPU, CPU, modem, or DRM hardware.
Device and CPU Profiles
Overrides selected build fields, model identity, fingerprint, serial data, baseband, or CPU identity for explicitly assigned packages.
On-Device WebUI
Searches installed apps, assigns reusable profiles, controls individual hooks, shows system information, and backs up the configuration.
Optional App Tweaks
Can apply per-app DND, screen-on, auto-brightness, logging, DPI, locale, timezone, refresh-rate, and privacy-related settings.
Requirements
| Component | Requirement |
|---|---|
| Android | Android 9 or newer |
| Magisk | Version 24+ with Zygisk Next, ReZygisk, or NeoZygisk |
| KernelSU | Version 0.6.6+ with one of the supported external Zygisk implementations |
| APatch | Version 0.10+ with one of the supported external Zygisk implementations |
Profiles, Hooks, and Pro Features
The free profile system covers core device and CPU spoofing, custom refresh-rate reporting, timezone/language selection, selected system-level unlocks, VPN hiding, developer-option hiding, and comfort controls. The project's current documentation labels GPU, Android ID, advertising ID, App Set ID, DRM, IMEI, SIM/carrier, per-app proxy, GPS, fake uptime, WebView user agent, and several other hooks as Pro or partially Pro.
Some options use resident hooks and are explicitly marked by upstream as higher risk. Others change device-wide behavior, such as disabling FLAG_SECURE or globally overriding an identifier. Read each WebUI warning and enable only the narrowest option needed for a specific package.
What to Expect
A game may expose a higher frame-rate or graphics menu when it recognizes a supported flagship identity. The physical panel refresh rate, thermal limits, graphics driver, and SoC performance still determine whether that mode works well. A spoofed Widevine value likewise cannot create hardware-backed DRM capability.
On KernelSU and APatch, open the WebUI from the manager. Magisk users need a compatible KSU WebUI host application. After changing a profile, test the targeted app and remove unnecessary hooks rather than enabling every available field.