LMK Controller by feerd gives you robust, boot-persistent control over Android's Low Memory Killer through a clean WebUI. Auto-detects kernel types effortlessly.
Select the configuration that matches your device usage via the MMRL WebUI.
Disables LMK thresholds completely. Allocates maximum RAM for the foreground application. Ideal for heavy gaming sessions.
Provides balanced multitasking capabilities. Keeps apps in memory longer without system freezing. Recommended for daily use.
Reverts memory management to near AOSP stock behavior. Safe fallback if you experience any system instability.
Engineered for reliability, from boot to runtime.
Fully manageable through a clean web interface accessible directly via MMRL or compatible module managers.
Guaranteed execution on every reboot utilizing /data/adb/service.d/. Your settings survive system restarts.
Automatically detects your kernel architecture—seamlessly switching logic between Classic LMK and LMKD daemon.
Full support for modern userspace LMKD utilizing magisk resetprop --file alongside HUP signaling.
Logs all boot execution data to /data/adb/modules/lmk_controller_feerd/boot.log for easy troubleshooting.
Leaves zero trace. Removes all boot services and properties automatically upon module uninstallation.
Older Android kernels used an in-kernel driver called Classic LMK (manipulating a sysfs node). Modern Android uses LMKD, a userspace daemon responding to Android properties. LMK Controller supports both out of the box.
Get up and running in minutes.
Added robust LMKD support using magisk resetprop --file and HUP signal execution. Improved automatic kernel detection.
Introduced the clean WebUI accessible via MMRL. Added boot persistence logic utilizing /data/adb/service.d/.
Initial release. Full control over Classic LMK kernel nodes with 3 distinct operational modes.
Special thanks to George Machen for beta testing the LMKD implementation on the Pixel 4a (5G).