Dump flag value in the construtor for easier debugging. Feature flags
are not expected to change in runtime, dumping the value once should
be enough.
Bug: 296119135
Test: manual test
Change-Id: Ie5aca2dff23e59704fb306833cde0e592b9f430d
This is just a copy of the existing display_colordata_cal0.pb, which
will provide the same colordata for libdisplaycolor to use for external
display.
Bug: 288608645
Test: manual
Change-Id: I2e895c3f5eefc9626bb88b7b321ff92739b39e4f
4c7ea96e6b
Reverting to comply with the Allocator VTS for 24Q1, do not merge to main.
Bug: 310046460
Test: VtsHalGraphicsAllocatorAidl_TargetTest
Change-Id: Id8b721b05dc20032d13aed469327e8e996b0cffe
Fine tune the performance table since the change in CPU policy for
power saving cause some encoder performance results from the CTS
are not able to meet pass criteria from the original performance
measurement results.
Bug: 317441297
Test: run cts -m CtsVideoTestCases -t android.video.cts.VideoEncoderDecoderTest
Test: run cts -m CtsVideoTestCases -t android.video.cts.CodecDecoderPerformanceTest
Change-Id: Ib75d3f35c5ea2e2dc80ba192d738d54140a09d68
Fine tune the performance table since the change in CPU policy for
power saving cause some encoder performance results from the CTS
are not able to meet pass criteria from the original performance
measurement results.
Bug: 317441297
Test: run cts -m CtsVideoTestCases -t android.video.cts.VideoEncoderDecoderTest
Test: run cts -m CtsVideoTestCases -t android.video.cts.CodecDecoderPerformanceTest
Change-Id: Ib75d3f35c5ea2e2dc80ba192d738d54140a09d68
This reverts commit 4a1f9459e5.
The Chrome issue has been fixed upstread and this workaround is no
longer needed; in fact, it triggers another issue where conflicting MTE
mode settings make newer Chrome versions crash at startup.
Bug: 297266100
Bug: 305005339
Bug: https://crbug.com/1515053
Test: chrome still does not crash; debuggerd shows MTE is enabled (grep
for TCF_MTE)
Change-Id: Iee2b704c4ea39b5809193c1ceed3b8f41618dd40
Remove SELinux error from b/313804706 as the issue is solved now.
Bug: 313804706
Test: No selinux denial error from boot with husky-trunk_staging-userdebug build
Change-Id: I19c7fba663abac4d180b6a144f0aff5d108806f6
Bug: 299553227
Test: boot to home with test build b/299553227#comment8
Change-Id: I9ee23a9aa753d891d233e337908c2091d63f3834
Signed-off-by: Jasmine Cha <chajasmine@google.com>
With multiclient HAL, the socket server domain changes from chre to
hal_contexthub_default.
Bug: 248615564
Test: updated the sepolicies and observed that avc violation logs
disappears.
Change-Id: I4b2d27b436c9d81bd0d0cdc5b3c1540884c37fec
This is enabled on debuggable builds only, includes
- Grant mlstrustedsubject typeattribute to wm_trace_data_file
- Grant systemui_app the write access to
wm_trace_data_file
Bug: 251513116
Fix: 288049075
Test: make sepolicy
Change-Id: Ifa5a5281c6e8c7ecedcd601fc8cc58c4be6bdc3b
The state count requirement is very specific to the case where the
signal integrity is the culprit of flaky connection. However,
there could be other cases such as bad receptacles causing data pins
to disconnect randomly.
Remove the state count requirement to cover more cases.
Bug: 296119135
Test: manually trigger the warnings
Change-Id: Ic2ae376ad6062d9930614381503f44e4a5ac760f
(cherry picked from commit 5e14ba01be9acc31d3df0f506b4287eea0bf9583)
Support flagging enum failure and flaky connection in device mode,
flagging enum failure and missing data lines in host mode.
No warning would be flagged until 5 secs after the data session
starts to give ample time for the connection to stabilize, a timer
is added to support it.
Bug: 296119135
Test: manually trigger the warnings
Change-Id: I25f08657e328913946add192b5ecb9ee50c3a1a8
(cherry picked from commit 42020dc4585442bd7ca88f183ba29a18834af197)
