Overclocking Magisk Module Better [top]

Have a "better" module we missed? Drop your custom build in the XDA forums and link it below.

The problem isn't overclocking itself; it's how you are implementing it. overclocking magisk module better

# Aggressive ramp up, immediate ramp down echo "0" > /sys/devices/system/cpu/cpufreq/interactive/above_hispeed_delay echo "99" > /sys/devices/system/cpu/cpufreq/interactive/go_hispeed_load Let’s compare a standard module (e.g., "Xtreme Performance X") vs. a "Better" module (custom-built). Have a "better" module we missed

#!/system/bin/sh Sets max freq only when screen is touched, otherwise saves battery Set max frequency for performance cores echo 2841600 > /sys/devices/system/cpu/cpu4/cpufreq/scaling_max_freq Set min frequency when idle to save heat echo 300000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq Dynamic governor tuning for "better" touch response echo "95" > /sys/devices/system/cpu/cpufreq/performance/governor_tunables/target_loads echo "40000" > /sys/devices/system/cpu/cpufreq/performance/governor_tunables/timer_rate GPU simple governor based on workload, not constant high speed echo "1" > /sys/class/kgsl/kgsl-3d0/popp Step 3: The "Race-to-Idle" Philosophy To be better , you must embrace logic. A phone that finishes a task in 0.2 seconds at 3.0 GHz uses less total energy than a phone that takes 0.5 seconds at 2.0 GHz. This is called race-to-idle . # Aggressive ramp up, immediate ramp down echo