* Adding XiaomiParts into whitelist to avoid it being killed by
doze. Also granting necessary permission to function properly.
* Required for Headphone & Mic Gain as it currently get killed
* This is manually ported by me from Lavender tree on Corvus-Devices
* Thanks @StyloGey for reviewing the java code and giving me a better solution
* Original repo: https://github.com/Corvus-Devices/device_xiaomi_lavender.git
To get it working, you need these two commits in your kernel:
> c04d6d6e61
> 8e25ac3318
Signed-off-by: OdSazib <odsazib@gmail.com>
Change-Id: I1bb48ced1f23728daa2e5170647ce08a04347110
Updating blobs to LA.UM.8.2.r1-06700-sdm660.0 was leading to RIL breaks and show following error-
* E AndroidRuntime: java.lang.NoSuchMethodError: No virtual method getEssentialRecordsLoaded()Z in class Lcom/android/internal/telephony/uicc/IccRecords; or its super classes (declaration of 'com.android.internal.telephony.uicc.IccRecords' appears in /system/framework/telephony-common.jar)
This reverts commit 4cd252e878983e8da8337525858a97f1b3aaac88.
breaks display turn on when notification comes in
Change-Id: I300853bfd806afffd55c6c3bc0c7dfde3e1cb0cb
b/71936484 has audio accessories failing to connect
when there's a transition to suspend when they're attempting
to enumerate.
Avoid this problem by increasing autosuspend delay
from the default 2s to 7s.
The longest I've seen a device take to enumerate after
vbus is ~3 seconds, this gives a 2x margin.
Test: booted on Walleye, saw no more messages:
[ 472.412555] c0 5675 msm-dwc3 a800000.ssusb: DWC3 in low power mode
between device connection and enumeration.
Bug: 71936484
Change-Id: Ic655f2ce6dec429510cc7c00452da4d49f2392b0
Adding com.skyhook.blp into whitelist to avoid it being killed by
doze. Also adding INTERACT_ACROSS_USERS permission to be able to
run as single user. Update for Q.
Change-Id: I245965c87e7a5029eb8a308af24484d64a3fcb87
CRs-Fixed: 2674734
Set USB default composition to 0x9091 having diag,serial_cdev,
rmnet,adb for 8909 with kernel 4.9.
Change-Id: I3066799d801bc9d8451b0d5a0bcd6d4055d1f735
* 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
* In favor of Low Memory Killer Daemon (lmkd).
* Adaptive LMK was also dropped quite sometime ago
making it useless to keep this script around.
Change-Id: Ie221d6f669d261bb871a77fed712b0df3f5ba248
Enable ro.lmk.use_minfree_levels flag to use minfree levels to decide
when lmkd should kill. This makes lmkd work the same way lowmemorykiller
kernel driver used to work.
Bug: 77299493
Bug: 75322373
Test: lmkd_unit_test
Change-Id: Ic29d7fd21af1cb6af3a7d2a175d210775a09987e
Signed-off-by: Suren Baghdasaryan <surenb@google.com>
Setting ro.lmk.medium to 800 to prevent important processes from being
killed at medium vmpressure levels.
Bug: 77299493
Test: lmkd_unit_test
Merged-In: I37e1651a0a2b148a852e5bde86501024d4f87bbf
Change-Id: I37e1651a0a2b148a852e5bde86501024d4f87bbf
Signed-off-by: Suren Baghdasaryan <surenb@google.com>
(cherry picked from commit c954ec2eb318518cfa5c6f64a688fd8c809e91c5)
* 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
