Should fix intermittent failures of SELinuxUncheckedDenialBootTest.
Bug: 192485697
Test: build, checked for denials in logcat
Change-Id: I3b9cafd99f9ff343e5ab5c67f5f268e5eb4382d6
This is to enable clearing of secure element during a master reset.
Bug: 182508814
Test: master reset on device with keys; verified no keys after reset
Signed-off-by: Jeffrey Carlyle <jcarlyle@google.com>
Change-Id: I9bb569e09f8cd6f5640757bd0d10a14ef32946ff
Revert "add gs101-specific recovery library"
Revert "recovery: enable support for device-specific WipeSe impl..."
Revert "clear secure element of Digital Car Keys during factory ..."
Revert submission 14983788-clear_keys
Reason for revert: b/192373955
Reverted Changes:
Ia8fc29e6c:add gs101-specific recovery library
Icc1eabfd4:clear secure element of Digital Car Keys during fa...
I943d97b26:recovery: enable support for device-specific WipeS...
I15c7fbd7f:allow recovery and fastboot to access secure elmen...
Change-Id: Ic576b40641171298ad840bedbd4a9f7b67052d95
This mirrors the same sepolicy line in previous Pixel devices.
Bug: 189493387
Test: fastboot flash vendor_boot on r4
Change-Id: Ie15c8e6e5c01b249e1e5e244666c461253279f0b
major changes:
1. This change is to allow rlsservice to read the status of
display status file. Similar method was employed in previous
pixels.
Bug: 191122203
Test: p21 camera test checklist
Change-Id: I09483881294fd6dde46d4d0b7283311a2d20c404
This is to enable clearing of secure element during a master reset.
Bug: 182508814
Test: master reset on device with keys; verified no keys after reset
Signed-off-by: Jeffrey Carlyle <jcarlyle@google.com>
Change-Id: I15c7fbd7f2c4fb34dcad0ae4f5cee3238f526fa5
This change removes direct access to the LHBM sysfs node from SystemUI,
but allows SystemUI to make binder calls to the hardware composer (HWC),
which can be used to enable or disable LHBM.
Bug: 191132545
Bug: 190563896
Bug: 184768835
Test: no avc denials
Change-Id: I5417377ff096e869ad772e4fd2fb23f8c1fd4f1e
These properties cannot be resolved after product sepolicy is replaced.
vendor_persist_config_default_prop
vendor_rild_prop
Test: The device can boot to home after replacing with GSI
Bug: 191236468
Change-Id: Ib797601a44306987e5a85897c7b6cd7827ad91b2
Provide necessary sepolicy for bugreport dump to access cma metric
information under /sys/kernel/pixel_stat/*
Test: Run "adb bugreport <zip>" and verify it contains the output
from dumpstate_board.txt
Bug: 191904985
Signed-off-by: Minchan Kim <minchan@google.com>
Change-Id: Iaa92006eeb5158a0962652427d1af061fe1cf03d
Bug: 187386527
Test: Boot and confirm HAL is up
Signed-off-by: Michael Ayoubi <mayoubi@google.com>
Change-Id: Ia9f3f90fba6981762fe375aa37c81f8474ad9c53
For sched nodes, "proc_vendor_sched" and "sysfs_vendor_sched",
their type definition is in product sepolicy,
while genfs_contexts is in vendor sepolicy.
In this case, genfs_contexts cannot be resolved after product sepolicy
is replaced by Dynamic System Update.
Need to keep the type definition and genfs_contexts in the same partition.
Now move genfs_contexts because the type definition has to be in product for now
since other private domains are accessing these sched nodes.
Test: $ make selinux_policy
The device can boot to home after replacing with GSI.
Bug: 191236468
Change-Id: I02ea78b04dfcade4ceb426ff6ebf498daa81ac32
