From bdfe592a878b3142426a8c39010a0b039d374363 Mon Sep 17 00:00:00 2001 From: Artem Borisov Date: Tue, 28 May 2019 01:32:30 +0530 Subject: [PATCH] sdm660-common: Disable ALMK on all targets * No matter how hard QC tried to improve these features, they still suffer from stability issues, mainly due to the unpredictable nature of vmpressure they rely on. Change-Id: Icd14c79298a3c268abffa06ed17a79dececf423a Signed-off-by: PIPIPIG233666 <2212848813@qq.com> --- rootdir/bin/init.qcom.post_boot.sh | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/rootdir/bin/init.qcom.post_boot.sh b/rootdir/bin/init.qcom.post_boot.sh index 53784840..e31e8856 100755 --- a/rootdir/bin/init.qcom.post_boot.sh +++ b/rootdir/bin/init.qcom.post_boot.sh @@ -395,7 +395,7 @@ else # Enable adaptive LMK for all targets & # use Google default LMK series for all 64-bit targets >=2GB. - echo 1 > /sys/module/lowmemorykiller/parameters/enable_adaptive_lmk + echo 0 > /sys/module/lowmemorykiller/parameters/enable_adaptive_lmk # Enable oom_reaper if [ -f /sys/module/lowmemorykiller/parameters/oom_reaper ]; then