- This reverts commit e4163edba7 as it is incorrect.
- It causes sideload to fail with kPostinstallRunnerError on a msmsteppe device.
- UFS sysfs nodes are labeled properly in sepolicy_vndr as vendor_sysfs_scsi_target and should be left as is.
- Labeling it incorrectly in qcom/common essentially causes update_engine_sideload to get a SELinux denial;
- when trying to search the UFS sysfs nodes with vendor_sysfs_mmc_host.
- The correct fix is to revert this as it was not needed to begin with.
Test: Build, sideload and check whether kPostinstallRunnerError occurs.
Change-Id: Ic15740660f123eefce22515e5ddafb5959c1fb4d
Signed-off-by: Cyber Knight <cyberknight755@gmail.com>
Qualcomm labels all the DCVS/devfreq nodes in SoC policies. Instead of maintaining it every tag/SOC update, keep it in sepolicy_vndr to avoid conflicts and errors. This fixes high battery drain and performance issues by allowing the correct values to be set in init scripts. If SoC SEPolicies are broken, we can fix them rather than moving to common. These nodes differ a lot by platform, which makes common policies not particularly useful.
This reverts commit 9817d1f368.
Change-Id: Ifc22d9baaed8ed353987c95f79c87ec71d972bc5
[1] - Move partally bengal to sepolicy_vndr, keep 4.19 specifc nodes here
[2] - Keep kona here for now
[3] - Import msmsteppe from taro sepolicy_vndr
[4] - Use neuralnetworks on sepolicy_vndr
Change-Id: Icda5ebce28b97d45c8067f08be98d85313ab1474
Signed-off-by: chrisl7 <wandersonrodriguesf1@gmail.com>
Qualcomm removed them at
"removing some of the target dir from the component.", which
we reverted.
Change-Id: If2d407c03c112099b67bcd88d2ec4b31c0425642
This adds back SDM845, SM6125, SM8150, SM8250, SM8350,
and others.
This reverts commit 4346ce0d904984c5582d62cd9586a15abf2d62d5.
Change-Id: Idc0f96e28b4d47481d1281d34bf13859a45be1d8
Cyber Knight
Vishalcj17
chrisl7
Pulkit077
Jake Weinstein