The core SEPolicy for vendor_init is being restricted to the proper
Treble restrictions. Since this is a legacy device, it is tagged as a
data_between_core_and_vendor_violators and the needed permissions are
added to its device specific vendor_init.te
Bug: 62875318
Test: boot walleye without audits
Change-Id: I13aaa2278e71092d740216d3978dc720afafe8ea
Signed-off-by: Subhajeet Muhuri <kenny3fcb@gmail.com>
* Fixes the bug in dual SIM device where preferred data selection didn't stick after reboot
Co-authored-by: federicobenedetti <fede.benedetti9@gmail.com>
* Given the fact that the bootloader allows bootable images with
arbitrary signatures to boot, one can relock the bootloader after
installing a signed custom recovery. After that, custom ROMs can be
installed from recovery as usual, as long as the boot.img's are
signed.
* This is NOT a security vulnerability because unlocked bootloader is
still prerequisite to access fastboot boot/flash, in contrast it's a
feature suggested by Google.
* To make it feasible with Lineage, sign the img with AOSP verity key
which is publicly available.
* OnePlus happens to use the same key to sign their own images and
bootloader, so as a bonus there's even no 5s warning indicating a
custom boot.img is in use on boot.
* This doesn't mean using custom ROMs with locked bootloader is
suggested.
Change-Id: I178e9588e1dde96400dcb2178a027597d05949bd
* VNDK runtime isolation is kept disabled for now because that's
also how Xiaomi is shipping P on their devices.
Change-Id: I43140442ab33f3e9633bb4f347e2bee9be97b447
* Move vendor android.hidl.base@1.0 to EXTRA_VENDOR_LIBRARIES as well
to make code cleaner.
* Remove android.hidl.manager@1.0-java from product packages as it's
built by default.
Change-Id: Ia95e09b21ce42137cac9a1dd22f208fd9de9bf20
Move persist entry to fstab and mount at /mnt/vendor/persist
Apply required user, group and permissions once persist
folder is created through __mount and parititon is mounted.
Run restorecon on /mnt/vendor/persist.
Change-Id: I20a16f3669bc7abf9844525c6ba0db1521a5a8e2
core_ctl's enable & disable nodes are differnt on different
kernel versions. Fix Disabling of core_ctl for msm8917.
CRs-Fixed: 2366575
Change-Id: Ide7fc5384b34e9e686fe686f9fd70aaaaffcc278
Currently if targets support ESOC there would almost certainly
only be a single instance of an external modem. Hence we can
simplify the esoc_link check accordingly without needing to do
a loop and grep. Choosing the external modem composition simply
depends on whether esoc_name is present.
Change-Id: Ib47e34fd31c3745a0c7b3568968f6f36681c98e7
Those values seem off. CAF maybe messed them up as those values look possibly wrong.
Those values are used as powerhint values on pixel 2 and 3.
Signed-off-by: Dusan Uveric <dusan.uveric9@gmail.com>
* 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>
