Unlock 120-144 FPS

Unlock FPS / High Refresh Rate — Per-Game Auto Edition 🔥

Unlocks the real maximum screen refresh rate and enables it automatically — by itself, without your involvement during gameplay. 🧠

WHAT IT DOES
— Unlocks FPS to the real panel maximum (not a made-up number — determined during installation via dumpsys display; if that fails, you choose manually with volume buttons).
— Turns itself ON and OFF during gameplay: a background daemon monitors which app is in the foreground and applies tweaks only while a game from your list is running — reverts immediately after you exit.
— You add the game list yourself via the module's WebUI — without this, the daemon does nothing, it's not a global "always on" toggle.
— Full control from WebUI: target Hz, game list, daemon status (running/stopped, pid, uid), manual override (force overclock regardless of what's on screen until you turn it off), live log, RU/EN toggle.

WHAT ELSE IT DOES
— Besides the refresh rate itself — tweaks HWUI/SurfaceFlinger/RenderEngine (buffers, VSync phase offset, layer cache) for smoother rendering at high Hz.
— Contains Qualcomm and MIUI/HyperOS specific property blocks for cross-platform coverage — on chips/firmwares where a particular key doesn't fit, it's simply harmlessly ignored.
— Device spoofing (model, brand, build fingerprint) to a known high-refresh-rate flagship — increases the chance that the game/launcher accepts the overclock if they have their own device whitelist. Requires true root (resetprop); without it, this part simply doesn't work, the FPS unlock itself is unaffected. Original values are read from disk (build.prop), not via live getprop which might have been already altered by a previous installation — and are fully restored when you exit the game, disable, or remove the module.

HOW IT WORKS
The daemon and WebUI store everything in /data/local/tmp/fps_unlock/ — not in the module's own folder. This is a deliberate decision: not all managers reliably report all module files during updates, so the daemon, hook script, and WebUI depend only on this single persistent directory. The daemon polls the foreground app every 3.5 seconds; when you exit a game, it waits 4 seconds (debounce protection for fast app switching) before reverting. When manual override is enabled, the daemon completely skips its automatic logic until the override is turned off. The daemon always starts at boot — there is no separate autostart toggle anymore; if the game list is empty, it simply does nothing.

WHAT IT DOES NOT DO
— Cannot exceed the physical panel maximum — if detection shows 90 Hz, the ceiling is 90, not 144.
— Does not touch game binaries — no interaction with anti-cheat beyond what any legitimate overclock/game mode tool does.
— Does not disable thermal throttling — sustained high-frequency operation under load still depends on device cooling.

SAFETY
Reversible, with no bootloop risk: everything boils down to setprop / settings put / resetprop, applied and reverted from the daemon/service/action script — does not touch partitions, boot images, or files needed to boot Android. Disabling or removing the module restores all values to factory, including device identity. However — not a "zero effect": sustainably higher refresh rate increases heat and GPU/screen power consumption compared to the stock limit — that's the whole point of the module, for long sessions active cooling is recommended. Identity spoofing is real substitution while active: apps that check ro.product.model/build fingerprint (banking apps, some anti-cheats, Play Integrity) will see the spoofed profile, not the actual device, for as long as the tweaks are applied — keep this in mind if you plan to switch to anything identity-sensitive right in the middle of a gaming session.

REQUIREMENTS
Magisk, KernelSU, APatch or AxManager (install via the manager app, not through TWRP — the installer needs a live system for frequency detection and, for manual selection, for reading volume buttons). A panel that supports a frequency higher than the stock firmware limit. Also remove the old module before installing the new one.

COMPATIBILITY
Built and tested on a Qualcomm/HyperOS (MIUI) device. Qualcomm and MIUI specific keys are included; effect on other chips/firmwares (Samsung One UI, MediaTek, OxygenOS, etc.) is not yet confirmed — it is expected that those keys will simply be harmlessly ignored rather than break anything, but actual FPS unlock on them has not yet been verified. If you have a different chip/firmware and it doesn't work — send the getprop output for your device's refresh rate keys, and we'll add support.

Author: @TosikV02
Support: t.me/opensourcemagiskmodule