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
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)
am skip reason: Merged-In If106f81c0dd2bd81a48e156e1cc75dba4a885aca with SHA-1 dc330b5e88 is already in history
Original change: https://googleplex-android-review.googlesource.com/c/device/google/zuma/+/25704537
Change-Id: Icaf771cd1500a31df49dd844132f1f23687d77d1
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
am skip reason: Merged-In I688f2559698c7553a7f585cab2693d09d70731f4 with SHA-1 f08b6e4d84 is already in history
Original change: https://googleplex-android-review.googlesource.com/c/device/google/zuma/+/25689420
Change-Id: I9727815f1b677fb77c0403c4b0e35bd66dd994fe
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
Since LMKD introduced aggressive kill for cached apps, we can change the
swap_free_low_percentage back to 10.
Bug: 300660611
Change-Id: I688f2559698c7553a7f585cab2693d09d70731f4
Merged-In: I688f2559698c7553a7f585cab2693d09d70731f4
Signed-off-by: Minchan Kim <minchan@google.com>
ACPM has an issue b/315079424 that reports incorrect TPU DVFS
residency. So change the data source from ACPM to TPU kernel.
Bug: 310094590
Test: vts-tradefed run vts -m VtsHalPowerStatsTargetTest
Change-Id: If4bdaeea510b1a8e72d057a7fbb0dc03f6a6c665
Signed-off-by: Darren Hsu <darrenhsu@google.com>
