- add sRGB and DisplayP3 layers in HWC, if mixedColorSpaces is
supported, only DPU composition happens.
Bug: 311252937
Test: this
Change-Id: I400a6dd18a05bbdf69e249907e13a4fa7eafbf01
CarEvsService shares state changes of its service types via this new
VHAL property.
Bug: 325317031
Test: atest VtsHalAutomotiveVehicle_TargetTest
Change-Id: I50f8523aea6a2b5ccb55db9ca620e64e1cada8ee
Added unit tests for methods related to config flag in the default AIDL
broadcast radio HAL implementation.
Bug: 316630344
Test: atest DefaultBroadcastRadioHalTestCase
Change-Id: Id42915613f931ebcd40ca05d9534dc087e479461
It's not supposed to be sign-extended as that blocks off the entire
28-64 bit range instead of the 28-31 bit range as indicated in the
comment
As this value is correct in HIDL and in the docs, do a history
re-write of the AIDL value to match the intended (and previous)
values.
Test: make
Bug: 323484008
Change-Id: I0b373576a366c853c87109a9b24ec9f8d9cbdb4d
This CL is created as a best effort to migrate test targets
to the new android ownership model. If you find incorrect or unnecessary
attribution in this CL, please create a separate CL to fix that.
For more details please refer to the link below,
<add g3 doc link>
Bug: 304529413
Test: N/A
Change-Id: Ia656d4d37c9219c4ef25fb6739c7410a0ded216b
In newer versions of libc++, std::char_traits<T> is no longer defined
for non-character types, and a result, std::basic_string_view<uint8_t>
is also no longer defined. See
https://discourse.llvm.org/t/deprecating-std-string-t-for-non-character-t/66779.
Bug: 175635923
Test: libkeymint_remote_prov_support_test
Change-Id: Ic373e0a3c081b996d4c81a9783103ae6406833f7
In newer versions of libc++, std::char_traits<T> is no longer defined
for non-character types, and a result, std::basic_string<uint8_t> is
also no longer defined. See
https://discourse.llvm.org/t/deprecating-std-string-t-for-non-character-t/66779.
Bug: 175635923
Test: make checkbuild
Change-Id: Icb3937d8b1ff6dbe7e35e62f2e6cc1e2eb789121
Added unit tests for methods related to program list updates
in the default AIDL broadcast radio HAL implementation and the
corresponding mock tuner callback methods.
Bug: 316630344
Test: atest DefaultBroadcastRadioHalTestCase
Change-Id: I0bde2b9cc376315320521a1d13ec521781a77cca
Fuzzer is breaking due to fatal log for host. Downgrade it to error.
Test: m android.hardware.neuralnetworks-service.example_fuzzer &&
out/host/linux-x86/fuzz/x86_64/android.hardware.neuralnetworks-service.example_fuzzer/android.hardware.neuralnetworks-service.example_fuzzer
Bug: 312902296
Change-Id: I7013ed14f6644d0459929380202de45f92575cf9
This implementation of the HAL is used by pixel devices.
The implementation of GetProviderInfo is test only
Bug: 324570010
Test: TreeHugger
Change-Id: I67d17fb07c1288317290a0b1c4b07cd3be1e48c6
Make vibrator VTS tests deterministic by removing all uses of
std::rand() from HAL input values used in test. Rely on max supported
values instead.
Fix: 324840028
Test: atest VtsHalVibratorTargetTest
Change-Id: Id40fb5a86238226feec9affff631bab37383f26b
Add TearDown method to reset the vibrator state between tests to avoid
illegal state errors caused by unrelated tests.
Add calls to vibrator->off between vibrator->compose invocations within
the same test, so calls are tested individually.
Test runs with this change on failing targets:
Bug: 323087313
Test: atest VtsHalVibratorTargetTest
Change-Id: I1e9aa243da07040b33df2474977fc8becac440a5
Fixes an issue with the benchmarks, where they would skip unsupported
situations by early returning without reaching the measure loop and
without notifying the framework.
The framework would then retry the exact same scenario indefinitely.
To fix, makes sure every early return also calls SkipWithMessage.
Fixes: 302845046
Test: adb shell /tmp/foobar/VibratorHalIntegrationBenchmark --v=2
Change-Id: Ib52b8c4d94755a0961bcfb40d508482e5c49cb52