[Detail]
data_between_core_and_vendor_violators is used temporarily. We should
follow Android P SELinux rule to write sepolicy.
[Solution]
Remove data_between_core_and_vendor_violators from files which already
fix SELinux build errors
MTK-Commit-Id: 6a75842a96d8997bca10caf6ca4d5b4e7e8f68a4
Change-Id: I5e840fdf6b61d44860429a7e5c7e24c9a48a9c75
CR-Id: ALPS03800946
Feature: Treble
[Solution]
There are some build errors in factory.te, so fix
MTK-Commit-Id: db2e842e2fa353e987baa282d5c2026ae8395a61
Change-Id: I07d3906e8a934ae0e36b7c384208f2cfc8506a23
CR-Id: ALPS03788916
Feature: Factory Mode
Restore the policies accessing files labeled
as proc_xxx or sysfs_xxx, but there are some
exceptions for coredomain process, such as
meta_tst,dump_state,kpoc_charger
MTK-Commit-Id: 7953b5203bb3cac099c3326d330643b4cd73746d
Change-Id: I4b16c09c352891783e837bea370c264966ca6d13
CR-Id: ALPS03825066
Feature: [Android Default] SELinux, SEAndroid, and SE-MTK