am skip reason: Merged-In I473ac38a5f7b1540aea0b4588bc358f6855ff4b3 with SHA-1 e871979054 is already in history
Original change: https://googleplex-android-review.googlesource.com/c/device/google/zuma/+/25973408
Change-Id: Ic02206928d9c7d418d4736972c4d1dc57df9abd6
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
c2.android.av1-dav1d.decoder performance has been improved with CL
"C2SoftDav1dDec: Fix performance issues in frame parallel multi-threading"
More detail in b/315828433
Bug: 315828433
Test: run cts -m CtsMediaDecoderTestCases -a arm64-v8a -t android.media.decoder.cts.VideoDecoderPerfTest --module-arg CtsMediaDecoderTestCases:instrumentation-arg:codec-prefix:=c2.android.av1-dav1d.decoder
Change-Id: I18b1179d9008ed2d2b35c8ead2606b252cf17f48
Previously, `Liboemservice_proxy` was included as a part of DMD, and so
didn't need to be included on its own. However, since these two have
been decoupled, we need to explicitly include the build target here for
it to execute on device.
Test: Build and check logs to ensure service starts up on boot
Bug: 321867236
Change-Id: I525b5f44c60c636302431733b3c311cdf4336d42
Refresh rate residency is not directly related to backlight state.
Relocate to a more appropriate location.
Bug: 315424658
Test: vts-tradefed run vts -m VtsHalPowerStatsTargetTest
Change-Id: Ib8d38e04aa6e76766bb05f11b50670094ae55347
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
