--HAL requires 64 bit usage flags to support more feature
--Re-used one of the reserved locations to read 64bit usage flags
and override format
CRs-fixed: 2264577
Change-Id: I9a4cbb80b1c2d82ec4af3941f0d98b67ecfd59ef
Define two new tags for FBE Key Management.
FBE_ICE: This is a boolean which specifies if new key
management is used.
KEY_TYPE: Specifies if it is a DE_USER or a CE_USER key.
CRs-Fixed: 2288316
Change-Id: Id9468d1fab0b0517a0a96734cdfe5612855fd2d9
The test may run on older devices and it is possbile that the
android::hardware::isHidlSupported is not available.
So statically link libhidlbase.
Bug: 352683715
Bug: 352486655
Bug: 346693391
Test: cameraservice VTS
(cherry picked from https://android-review.googlesource.com/q/commit:ca6839888e8f82b6f3a1d9f5c42571a72550637b)
Merged-In: I5bad6363fba4ebe3285c64cbaaf722e8da5cafdf
Change-Id: I5bad6363fba4ebe3285c64cbaaf722e8da5cafdf
am skip reason: Merged-In I6f6d36d1e3c98b85b412189c3f97163c0945a7ab with SHA-1 8659a96281 is already in history
Original change: https://android-review.googlesource.com/c/platform/hardware/interfaces/+/3115574
Change-Id: Iaad73d8763d06e4e0e4e2c4a54b7f356bddc5696
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
am skip reason: Merged-In I6f6d36d1e3c98b85b412189c3f97163c0945a7ab with SHA-1 8659a96281 is already in history
Original change: https://android-review.googlesource.com/c/platform/hardware/interfaces/+/3115574
Change-Id: I9073c68731740e2f5b25496eae8dceed87be67d4
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
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: Ic0620cc4c544665768435f24c328c75f08aa8ac0
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
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: I7060c448400a79db08b823100cf9b710761fea88
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
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
I'm no longer on the team, so make sure any place I'm an explicit owner points
to the generic owners file.
Bug: 346974431
Change-Id: Icbcb3b2024f8adb9980c6128022965e8f9a87918
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
In the original code, vector::erase() would invalidate iterators so we
should move the thread object into the std::async() for the blocking
operation.
Bug: 344250967
Test: atest VtsHalGnssTargetTest
Change-Id: I4cc82131bb070a37cb6ed9dbe9d7cccc7ab5ee89
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
This reverts commit 439e897d10.
Reason for revert: Seahawk now uses v3 lib, which should not be affected
Change-Id: Ia04c9a2c28829778c4d9d24b4a1138b615ac9377
