AIDL deprecation checks are only implemented in U,
so the existing V2 requirement on the T matrix
did not take effect on T branches. Hence, we
shouldn't add requirements retroactively.
Test: TH
Bug: 298318354
(cherry picked from https://android-review.googlesource.com/q/commit:7e2962f03a649dd4eb34c86c0eb93c98a3bc93b4)
Merged-In: Iaf38c6d6270f4aa9c7163540a396045be9d7865a
Change-Id: Iaf38c6d6270f4aa9c7163540a396045be9d7865a
AIDL deprecation checks are only implemented in U,
so the existing V2 requirement on the T matrix
did not take effect on T branches. Hence, we
shouldn't add requirements retroactively.
Test: TH
Bug: 298318354
Change-Id: Iaf38c6d6270f4aa9c7163540a396045be9d7865a
am skip reason: Merged-In Id5baa0f599d11a3563780aae15ff3cea0407060c with SHA-1 284883f847 is already in history
Original change: https://android-review.googlesource.com/c/platform/hardware/interfaces/+/2743883
Change-Id: I0894217fa9396955f249959889c25ff2ad832db7
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
am skip reason: Merged-In Id5baa0f599d11a3563780aae15ff3cea0407060c with SHA-1 284883f847 is already in history
Original change: https://android-review.googlesource.com/c/platform/hardware/interfaces/+/2743883
Change-Id: I80093fabbd1fc1068c17a22e8aa29c306e14e465
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
am skip reason: Merged-In Id5baa0f599d11a3563780aae15ff3cea0407060c with SHA-1 284883f847 is already in history
Original change: https://android-review.googlesource.com/c/platform/hardware/interfaces/+/2743883
Change-Id: I746f74b9d36dd3909e4869d419c16b6483b93911
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
am skip reason: Merged-In Id5baa0f599d11a3563780aae15ff3cea0407060c with SHA-1 284883f847 is already in history
Original change: https://android-review.googlesource.com/c/platform/hardware/interfaces/+/2743883
Change-Id: I3fb4c958ca058603e670bdf449e66395c24241b1
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
am skip reason: Merged-In Id5baa0f599d11a3563780aae15ff3cea0407060c with SHA-1 284883f847 is already in history
Original change: https://android-review.googlesource.com/c/platform/hardware/interfaces/+/2743883
Change-Id: Icde5cac14c9255b1e1db6253c9c01b54747bb291
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
am skip reason: Merged-In Id5baa0f599d11a3563780aae15ff3cea0407060c with SHA-1 284883f847 is already in history
Original change: https://android-review.googlesource.com/c/platform/hardware/interfaces/+/2743883
Change-Id: Ic0e8428c99962d9ba000675dde5f5e18b2625df3
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
am skip reason: Merged-In Id5baa0f599d11a3563780aae15ff3cea0407060c with SHA-1 284883f847 is already in history
Original change: https://android-review.googlesource.com/c/platform/hardware/interfaces/+/2743883
Change-Id: I443dbbe1c07ca458d30c66490f5819c85e5da30e
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
After adding ag/21179155, auto join flag is
not set for every p2p connect command. The tests
are passing an unknown peer MAC address to connect(). To
pass the tests, the connect should trigger a scan and
try to find this unknown mac address. So set join flag
to true to run the same scan logic.
Bug: 298310537
Bug: 268236829
Bug: 218608010
Test: atest VtsHalWifiSupplicantP2pIfaceTargetTest
Change-Id: Id5baa0f599d11a3563780aae15ff3cea0407060c
Merged-In: Id5baa0f599d11a3563780aae15ff3cea0407060c
It turns out we had a bug (b/263844771) in how RKP support was
detected, and that was fixed. However, due to this bug, some S chipests
shipped without RKP support which is now required by the tests.
This change drops the RKP requirement from S chipsets. There should be
no new S chipsets, so this effectively grandfathers in the previous
ones that were skipped by the RKP VTS tests.
T+ tests (both VTS and other suites) will verify that RKP support is
there, so there is no gap introduced by this change.
Bug: 297139913
Test: VtsAidlKeyMintTargetTest
(cherry picked from https://android-review.googlesource.com/q/commit:8be875e0d0c18b8de67744c8b9629f2ff518dd60)
Merged-In: I387e5f058ada698747aac103c1745682291f2d1c
Change-Id: I387e5f058ada698747aac103c1745682291f2d1c
- Added API to check wifi chip supports AP interface
- Check AP support as a precondition for AP related TCs
Bug: 284925541
Test: atest VtsHalWifiApV1_5TargetTest
Change-Id: I1121d7b787ed972980bab0e05a52f3ca2f3d0a24
Use "AServiceManager_waitForService" instead of
"AServiceManager_getService" to wait for any camera
providers that might be using the lazy mechanism and
are not running all the time.
Bug: 297965980
Test: atest VtsAidlHalCameraProvider_TargetTest
Change-Id: I6374dc768cd1068885668f927f902dcee44a7a42
the Hostapd AIDL VTS tests.
At the beginning of each test, we now:
1. Disable the Wifi framework, Hostapd, and Vendor HAL.
2. Enable the Hostapd and Vendor HAL.
At the end of each test, we now:
1. Disable the Hostapd and Vendor HAL.
2. Enable the Wifi framework.
Bug: 283402709
Test: atest VtsHalHostapdTargetTest --iterations 10
# Tested on both an Android T and U device.
# All tests passed in both cases.
Change-Id: I8b5e24ad44d13fad09d84f1b212e60ca8df3aa7e
Hostapd AIDL VTS tests.
Main purpose will be to enable/disable the
HALs and Wifi framework before and after
each test.
Bug: 283402709
Test: atest VtsHalHostapdTargetTest
Change-Id: Ib3ceca4ad25f472e1b75fa95661235c880a489fd
