am skip reason: Merged-In I6f6d36d1e3c98b85b412189c3f97163c0945a7ab with SHA-1 3beaf4faca is already in history
Original change: https://android-review.googlesource.com/c/platform/hardware/interfaces/+/3115574
Change-Id: I56a90e1a6b1eba513b789829f83b4909e9235a95
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
The policy building library changes in aosp/3125493, accordingly change
the function call. This does not change the behaviour or test coverage
of VTS.
Test: atest VtsSecretkeeperTargetTest
Bug: 291245237
Change-Id: I21a7b0abe5bf186893ec9a68bb080b41778d3313
During VTS testing, when many sensors are quickly enabled, the load on the Sensorhub side will be too heavy, and then continue to send sensor enable instructions and Sensor Flush instructions. These instructions sent by the Kernel driver to the Sensorhub through inter-core communication cannot be responded to in a timely manner. After the Kernel side judges the timeout, it will determine that the enable fails; after the enable fails, it cannot continue to test the flush or return the expected flush data.
ten sensors is tested as a group
Bug: 339763843
Test: run vts -m VtsHalSensorsV2_0TargetTest
(cherry picked from https://android-review.googlesource.com/q/commit:09952885e441bcf0d8f0bf0834ff46608b07e0d0)
Change-Id: I6f6d36d1e3c98b85b412189c3f97163c0945a7ab
During VTS testing, when many sensors are quickly enabled, the load on the Sensorhub side will be too heavy, and then continue to send sensor enable instructions and Sensor Flush instructions. These instructions sent by the Kernel driver to the Sensorhub through inter-core communication cannot be responded to in a timely manner. After the Kernel side judges the timeout, it will determine that the enable fails; after the enable fails, it cannot continue to test the flush or return the expected flush data.
ten sensors is tested as a group
Bug: 339763843
Test: run vts -m VtsHalSensorsV2_0TargetTest
(cherry picked from https://android-review.googlesource.com/q/commit:09952885e441bcf0d8f0bf0834ff46608b07e0d0)
Merged-In: I6f6d36d1e3c98b85b412189c3f97163c0945a7ab
Change-Id: I6f6d36d1e3c98b85b412189c3f97163c0945a7ab
aosp/3106417 added extra tests with for device ID attestation, but
didn't include a version gate for attesting to the second IMEI value,
which is only present in KeyMint v3+.
Test: VtsAidlKeyMintTargetTest
Change-Id: I95f47942058781709efe96d38442e0518e39705d
Currently same connection id can be given to different connections if
they don't belong to the same bufferpool.
Ensure uniqueness of connection id for each connection.
Bug: 323793249
Change-Id: I350872e6d60736ea4525d473944c92b5fe3f5f84
Not all target device support high quality broadcast config.
Bug: 342672142
Test: atest VtsHalBluetoothAudioTargetTest
Change-Id: I87508c8deec994defb5653e51e75a00a8efcb873
am skip reason: Merged-In I3d81f7e59b6189fab1b146320263509f2694c11e with SHA-1 ca3ea117ef is already in history
Original change: https://android-review.googlesource.com/c/platform/hardware/interfaces/+/3083274
Change-Id: I4f25468d68aae0afba294c83b495460eb241b37b
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
am skip reason: Merged-In I3d81f7e59b6189fab1b146320263509f2694c11e with SHA-1 ca3ea117ef is already in history
Original change: https://android-review.googlesource.com/c/platform/hardware/interfaces/+/3083274
Change-Id: I9361dc8a42434bbefaf83ad10e91c486e85d0021
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
It's no longer used (now libc++fs is part of libc++), and it's
dangerously opting out of the global cpp_std default.
Bug: http://b/344590580
Change-Id: I17648b573600ff2ee1ab45383c7fda7d5bcfc7a2
Broadcast settings matching now base on context to
populate configurations
Bug: 306225778
Test: atest VtsHalBluetoothAudioTargetTest
Change-Id: I150754558ceb74f19888ef63210e2a42b3f00cd8
Revert submission 3102645-no_vndk_aidl
Reason for revert: Droidmonitor triggered revert due to build breakage in b/345063864. Will be verifying through ABTD before submission.
Reverted changes: /q/submissionid:3102645-no_vndk_aidl
Change-Id: Idc33bb7fbad72d18ac46a69639ac81bf554d469f
This fixes build failure with clang-r522817
Bug: 322868540
Change-Id: Ie5db4a32bebd137d1ba11213e0d642d85f1f7d1d
Test: m out/soong/.intermediates/hardware/interfaces/automotive/can/1.0/default/tests/fuzzer/automotiveCanV1.0_fuzzer/android_vendor_arm64_armv8-2a_cortex-a55_fuzzer/e560d7b19ebf7276b3e850d3d346dec8/obj/hardware/interfaces/automotive/can/1.0/default/CanBus.o
When we match with the remote capabilities, we don't filter by
preferred audio context, since they are suggestion.
Instead, we populate settings into 2 separated vector:
- Matched settings with matched preferred context,
- Matched settings,
We then filter by the first vector, then by the second vector.
Bug: 306225778
Test: atest VtsHalBluetoothAudioTargetTest
Change-Id: I03f322e8de509127d218a9de6b41dd39b2ebdcba
Vndk_use_version property is no longer in use with deprecation of VNDK.
Remove Vndk_use_version property and its usage.
Bug: 328994089
Test: AOSP CF build succeeded
Change-Id: I681cc850341a7dc47416dc81c1da21b687f87b1b
Merged-In: I681cc850341a7dc47416dc81c1da21b687f87b1b
Add a test that includes all of the device IDs for attestation, which
helps to check whether the emitted extension is including everything in
the correct order.
(This is already tested in CTS since aosp/2650044)
Also fix test of first API level to use `get_vsr_api_level` helper.
Test: VtsAidlKeyMintTargetTest
Test: with/without KeyMint hacked to emit tags in wrong order
Change-Id: Ic6e489aa99c773d794ad8cbddbe5153b1a145ea5
Compare energy values of auxiliary output for different parameters
Remove environmental reverb default implementation from the config file.
Bug: 305866207
Test: atest VtsHalEnvironmentalReverbTargetTest
Change-Id: I261c52ff25dd63d41213f0b40df8627dbb80a95d
