Prevent OOM-killing

Prevent OOM-kills by the kernel by setting the oom_score_adj to its minimum.
We need to do this periodically, because android also changes this value on certain evens, eg assigning a lower score when the app is open and a higher score when the app is in the background.

Author: programminghoch10

README.md

@@ -54,7 +54,9 @@ It contains many useability enhancements and all the major fixes needed to run `
   `ViPER4Android 2.7` comes with `Crashlytics bug report metrics` enabled by default. Personally I don't like to send bug reports, so I always disable it. I think Opt-in is the way to go here. 
   This is why in this module `Crashlytics` is disabled by default and you may enable if it you wish to.
 * **Keep the vibes alive** \
-  `ViPER4Android` will automatically be restarted if it gets killed. This may be of great convenience on low ram devices, where the OOM-killer is very aggressive, even towards foreground services.
+  Measures have been put in place to ensure `ViPER4Android` doesn't get killed by the OOM-killer. 
+  Though should `ViPER4Android` stop working anyways, will automatically be restarted.  
+  This may be of great convenience on low ram devices, where the OOM-killer is very aggressive, even towards foreground services.
 
 ## Install
 

magiskmodule/service.sh

@@ -6,18 +6,21 @@ waitUntilBootCompleted() {
   done
 }
 
+VIPERFXPACKAGE="com.pittvandewitt.viperfx"
+
 (
   waitUntilBootCompleted
   sleep 10
-  VIPERFXPACKAGE="com.pittvandewitt.viperfx"
   [ -n "$(pm list packages -d | grep $VIPERFXPACKAGE)" ] && pm enable $VIPERFXPACKAGE
 ) &
 
 (
   waitUntilBootCompleted
   sleep 60
   while true; do
-    ps -A -w -o ARGS=CMD | grep -v grep | grep -q com.pittvandewitt.viperfx || am broadcast -a android.intent.action.BOOT_COMPLETED -p com.pittvandewitt.viperfx
+    PID=$(pidof $VIPERFXPACKAGE)
+    [ -z "$PID" ] && am broadcast -a android.intent.action.BOOT_COMPLETED -p $VIPERFXPACKAGE
+    [ -n "$PID" ] && echo -1000 > /proc/$PID/oom_score_adj
     sleep 15
   done
 ) &