Not all modules are created equal. Some are universal, while others are chipset-specific. Here are the current top contenders.
There is no universal “overclocking Magisk module” – frequencies are device-specific. However, these modules help apply OC settings:
| Module Name | Purpose | Source | |-------------|---------|--------| | KernelTweaks | Applies user-defined CPU/GPU freqs at boot | Magisk repo (Deprecated) | | Advanced Kernel Tweaks (AKT) | Profiles (not raw OC, but governor tweaks) | GitHub | | CPUFreq Controller | Sets min/max via sysfs | XDA | | Franco Kernel Manager (App) | Not a module, but can apply OC after boot | Play Store | overclocking+magisk+module+top
Better approach: Create your own minimal Magisk module to execute an init.d startup script.
If you are serious about this, Kernel Adiutor (or similar apps like Franco Kernel Manager) is the dashboard. It acts as the user interface for the raw Linux commands running under the hood. Not all modules are created equal
When you slide the "Max Frequency" bar higher in Kernel Adiutor, you aren't just moving a pixel on a screen. You are sending a command to the kernel driver, usually located at /sys/devices/system/cpu/cpu*/cpufreq/scaling_max_freq.
However, stock kernels usually have a "thermal throttling" safety net. If you push the frequency too high, the phone shuts down to prevent damage. This is where the Overclocking Module comes in—it bypasses the stock thermal limits and injects new frequency voltage tables. If you are serious about this, Kernel Adiutor
You mentioned "TOP." In the overclocking community, this usually refers to Top Bin or Silicon Lottery.
Not all processors are created equal. A Snapdragon 845 in one phone might handle 2.8GHz perfectly at 1.1V, while the same chip in another phone might crash at that voltage and require 1.15V.