These products have warnings about overriding build commands, which
means that there are multiple instructions on how to build a file, and
we've just picked one of them. Which one we pick is usually stable, but
it can change.
Bug: 77611511
Test: turn default to false, walleye still uses a warning
Change-Id: I11d194863b313f64b19291f65219682b169d9ced
This daemon doesn't exist on the device and causes init errors during
boot.
init: /vendor/etc/init/hw/init.walleye.rc: 745: Unable to decode GID
for 'qcom_diag': getpwnam failed: No such file or directory
init: Could not start service 'vendor.qmuxd' as part of class 'main':
Cannot find '/vendor/bin/qmuxd': No such file or directory
Test: tree-hugger passes
Merged-In: Ib2bc1739cac088af3e9ef2e0482f2536dad8fb8c
Change-Id: Ib2bc1739cac088af3e9ef2e0482f2536dad8fb8c
This daemon doesn't exist on the device and causes init errors during
boot.
init: /vendor/etc/init/hw/init.walleye.rc: 745: Unable to decode GID
for 'qcom_diag': getpwnam failed: No such file or directory
init: Could not start service 'vendor.qmuxd' as part of class 'main':
Cannot find '/vendor/bin/qmuxd': No such file or directory
Test: tree-hugger passes
Merged-In: Ib2bc1739cac088af3e9ef2e0482f2536dad8fb8c
Change-Id: Ib2bc1739cac088af3e9ef2e0482f2536dad8fb8c
This daemon doesn't exist on the device and causes init errors during
boot.
init: /vendor/etc/init/hw/init.walleye.rc: 745: Unable to decode GID
for 'qcom_diag': getpwnam failed: No such file or directory
init: Could not start service 'vendor.qmuxd' as part of class 'main':
Cannot find '/vendor/bin/qmuxd': No such file or directory
Test: tree-hugger passes
Change-Id: Ib2bc1739cac088af3e9ef2e0482f2536dad8fb8c
ro.vendor.graphics.memory and vendor.debug.rs.* are used by Render
script (one of same-process HALs).
So they should be public-readable because Render script can be loaded
from almost everywhere.
Bug: 109653662
Test: succeeded building and tested with taimen
Change-Id: I5c6d6dd2f2406feaec60c965a763215c4a064f52
Before it had permissions to use hal_power_hwservice,
but it didn't declare itself to be an hal_power_client.
Bug: 80319537
Test: boot + sanity
Change-Id: I7d82dd2d5692aa1efe75146beb567d166d3b4824
Before it had permissions to use hal_graphics_allocator_hwservice,
but it didn't declare itself to be an allocator_client.
Bug: 80319537
Test: boot + sanity
Change-Id: I93a23cd3db270491e82b378507f3cb55063561e8
system properties must not be used as a communication channel in between
system and vendor processes. However, there has been no enforcement on
this: system process could write system properties that are owned and
read by vendor processes and vice versa. Such communication should be
done over hwbinder and should be formally specified in HIDL.
Until we finish migrating the existing use cases of sysprops to HIDL,
whitelisting them in system_writes_vendor_properties_violators so that
the violators are clearly tracked.
These violators are allowed only for P, but not for Q.
Bug: 78598545
Test: m -j selinux_policy
Merged-In: I60b12f1232c77ad997c8c87e6d91baa14c626e94
Change-Id: I60b12f1232c77ad997c8c87e6d91baa14c626e94
(cherry picked from commit 3ee4e77674)
