From 56e1c005758eea39028699edaff4a5d66be7cbf1 Mon Sep 17 00:00:00 2001
From: LuK1337 <priv.luk@gmail.com>
Date: Sat, 28 Mar 2020 16:53:53 +0100
Subject: [PATCH] sdm660-common: Don't set ro.alarm_boot

* We don't support alarm_boot anyway, also
  it's not getting set because of SELinux denial:
[    7.243347] selinux: avc:  denied  { set } for property=ro.alarm_boot pid=556 uid=0 gid=0 scontext=u:r:vendor_init:s0 tcontext=u:object_r:default_prop:s0 tclass=property_service permissive=0\x0a
[    7.243470] init: Unable to set property 'ro.alarm_boot' to 'false' from uid:0 gid:0 pid:556: SELinux permission check failed

Change-Id: Ia188bac2d2aa466c23dabd9dc50ee1f58e6ab7ee
---
 rootdir/etc/init.qcom.rc | 1 -
 1 file changed, 1 deletion(-)

diff --git a/rootdir/etc/init.qcom.rc b/rootdir/etc/init.qcom.rc
index f26eb09a..cdb8ed98 100755
--- a/rootdir/etc/init.qcom.rc
+++ b/rootdir/etc/init.qcom.rc
@@ -85,7 +85,6 @@ on early-boot
     write /sys/devices/virtual/npu/msm_npu/boot 1
     write /sys/kernel/boot_slpi/boot 1
     exec u:r:qti_init_shell:s0 -- /vendor/bin/init.qcom.early_boot.sh
-    setprop ro.alarm_boot false
 
     # SSR Setup
     write /sys/bus/msm_subsys/devices/subsys0/restart_level RELATED