CPU & GPU Governors
Set governors, min/max frequency per CPU cluster, plus Qualcomm (KGSL) and MediaTek GPU control. Includes sched boost & uclamp.
Zuan Kernel Manager Next brings CPU & GPU governors, ZRAM, UFS devfreq, kernel flashing, root terminal, and SetEdit together in a single Material 3 interface. Open source under GPL-3.0 — for those who want advanced system customization.
ZKM NextBuilt for power users: automatic node detection, unsupported controls hidden, and a consistent interface across all ROMs.
Set governors, min/max frequency per CPU cluster, plus Qualcomm (KGSL) and MediaTek GPU control. Includes sched boost & uclamp.
Monitor UFS health, manage host controller clock gating, and configure devfreq nodes (DDR/DVFSRC, LLCC) on supported devices.
Configure ZRAM size, compression algorithm, swappiness, dirty ratio, and cache pressure — complete with RAM, swap, and PSI monitoring.
You don't always need root. Monitoring and basic features work via Shizuku or Axeron; full kernel actions require Root mode.
Flash kernel images with a careful workflow, including boot image backup & restore utilities so you always have a way back.
Material 3 with Haze blur, app-controlled Light/Dark mode, custom colors, and custom backgrounds — not forced into system Dynamic Color.
Edit the Android settings database (SetEdit) and system properties, run commands in the built-in root terminal, and execute custom shell scripts for tuning automation — all without leaving the app.
Game overlay panel, per-cluster Custom Mode, Root Tools, plus a preset library: Battery Saver, Daily Balanced, Performance Ultra, Thermal Chiller.
Every device is different. A feature appearing in the UI doesn't guarantee its node exists on your device — ZKM detects paths and hides unsupported controls.
List of the main paths read or written by ZKM Next. RW = writable by the app (requires root), RO = read-only for monitoring.
/sys/devices/system/cpu/cpufreq/policyN/Governor and frequency limits per cluster. Clusters (policies) are auto-detected — 2, 3, or 4 tiers.
/sys/devices/system/cpu/cpuN/cpufreq/Real-time frequency of each core for the dashboard and monitors.
/proc/sys/kernel/Scheduler parameters for performance/power-saving profiles.
/sys/devices/system/cpu/qcom_lpm/parameters/Qualcomm CPU low-power mode control (if exposed by the kernel).
/sys/class/kgsl/kgsl-3d0/Clock, load, and behavior of the Qualcomm Adreno GPU.
/sys/class/devfreq/*Governor and frequency limits for each detected devfreq device, including UFS/DDR on supported SoCs.
/sys/block/zram0/Size and compression algorithm of the compressed swap. Resizing requires resetting the ZRAM device.
/proc/sys/vm/Kernel memory management tuning.
/proc/meminfo · /proc/pressure/Monitor RAM, swap, and pressure stall information (cpu, memory).
/sys/devices/platform/soc/<addr>.ufshc/Clock gating settings on the UFS host controller. Node names and addresses vary between SoCs.
/sys/block/<dev>/queue/ · /proc/diskstatsI/O scheduler, read-ahead, and live I/O statistics for the Storage screen.
/sys/class/thermal/Temperature readings from thermal zones; some devices also expose thermal profiles.
/sys/class/power_supply/battery/Battery & charging statistics for monitoring and Charge Stats. Advanced charging control depends on vendor nodes.
/sys/class/leds/Standard Android nodes for LED and brightness. Part of the sysfs interface reference; ZKM doesn't rely on them for core features and their availability depends heavily on the device.
/proc/ppm/ · /proc/cpufreq/CPU power policy control on MediaTek SoCs (Helio / Dimensity) that expose these nodes.
/proc/gpufreq/ · /proc/gpufreqv2/ · /sys/kernel/ged/ · /proc/mali/Frequency and DVFS for Mali/MediaTek GPUs.
No matching paths.
# Read first — don't write values you don't understand
su -c 'cat /sys/devices/system/cpu/cpufreq/policy0/scaling_governor'
su -c 'cat /sys/devices/system/cpu/cpufreq/policy0/scaling_available_governors'
ZKM Next performs privileged operations. Wrong values can cause instability, boot issues, overheating, or data loss.
Kernel and thermal tuning have real hardware consequences. Don't blindly copy values from other devices.
Disabling thermal throttling or forcing maximum frequencies for extended periods can trigger overheating.
What you need before installing and fully using ZKM Next.
Required for full kernel control. Compatible with:
suThe bootloader generally must be unlocked to gain root and to flash kernels/boot images. The unlock process may wipe data and varies by vendor.
Some nodes depend on SELinux policy. If access is denied, the related feature won't work on that device.
| Architecture | Status |
|---|---|
arm64-v8a | ✅ Primary |
armeabi-v7a | ✅ Supported when available |
x86_64 | ⚠️ Depends on device / build |
Minimum supported Android version. Without root, some monitoring features can run through Shizuku or Axeron.
Can't find the answer? Open a discussion or report an issue directly in the repository.
Include your device model, SoC, Android version, root manager, and logs when filing an issue.
Open GitHub IssuesYes, there is — especially if you change kernel parameters to extremes, disable thermal controls, or flash an image that doesn't match your device.
Yes, both are handled. On Snapdragon, ZKM reads nodes such as /sys/class/kgsl/kgsl-3d0/ and qcom_lpm. On MediaTek, nodes such as /proc/ppm, /proc/gpufreq, and /sys/kernel/ged are available. Other platforms (Exynos, Tensor, etc.) work as far as generic nodes like cpufreq and devfreq are available.
Feature availability depends on the kernel and vendor — ZKM hides controls whose nodes aren't found.
Partly. Through Shizuku or Axeron, monitoring features and some basic actions can run without root. Actions that write to kernel nodes (governor, ZRAM, flasher) require Root mode.
su -c getenforce. Strict policy can deny writes to certain nodes.Use the Language Pack: export a JSON file containing all strings, edit the translations, then import it back. Keep placeholders like %1$s and %1$d exactly as they are.
You need Android Studio, the Android SDK, JDK 21, and the Android NDK for native components.
git clone https://github.com/zuanvfx02/zuan-kernel-manager-next.git
cd zuan-kernel-manager-next
./gradlew :app:assembleDebug
The only official source for the APK is the Releases page in the GitHub repository. Avoid third-party mirrors.

com.zuan.kernelmanager.next
The official SHA-256 value is listed in each release's notes. Match it before installing:
sha256sum ZKM-Next.apk
Free to study, modify, and redistribute under the terms of GPL-3.0. Third-party components follow their respective licenses.