- CameraStreamBuffering test is modified to use the minimum number of
frame buffers that is required to run a camera pipeline for a single
client instead of using an arbitrarily chosen number, which may not
work for certain device implementations.
- Fix a name of v1.0 EvsManager implementation in
VtsHalEvsV1_0TargetTest.cpp
Bug: 305642713
Test: atest VtsHalEvsV1_0TargetTest and
atest VtsHalEvsV1_1TargetTest
Change-Id: Ieec986dbdf947311e0bc86871432da8a988d37ad
(cherry picked from commit 2d8834dc96)
- Removes a requirement of the landscape aspect ratio of the captured
frames because the Extended View System now allows the video streams
in any aspect ratio
- Increases the maximum latency of the video stream start request from
500 ms to 1 second to accommodate the camera system design with the
additional processing units outside of the head unit
- Reduces a number of additional buffers to allocate from 6 to 2 in
CameraStreamBuffering test, to be consistent with comments
Bug: 204835095
Bug: 305642713
Test: atest VtsHalEvsV1_0TargetTest and
atest VtsHalEvsV1_1TargetTest
Change-Id: Id41bde10964b650f78e76d4f97a4588367f7c7fc
Merged-In: Id41bde10964b650f78e76d4f97a4588367f7c7fc
(cherry picked from commit 7bc98ce6ed)
Allow CDD required properties not to be supported in VHAL VTS since
this is already covered in CTS. We also need to consider special
cases where one VHAL instance does not support all required
properties.
Test: atest VtsHalAutomotiveVehicle_TargetTest
Bug: 301577794
Merged-In: I93020e7e024760601bc5a8edf9997cc356a568c6
Change-Id: I93020e7e024760601bc5a8edf9997cc356a568c6
Allow CDD required properties not to be supported in VHAL VTS since
this is already covered in CTS. We also need to consider special
cases where one VHAL instance does not support all required
properties.
Test: atest VtsHalAutomotiveVehicle_TargetTest
Bug: 301577794
Change-Id: I93020e7e024760601bc5a8edf9997cc356a568c6
(Cherry-picked from commit b84f6f3c68fcd7f613146146821130eb354865c1)
Allow CDD required properties not to be supported in VHAL VTS since
this is already covered in CTS. We also need to consider special
cases where one VHAL instance does not support all required
properties.
Test: atest VtsHalAutomotiveVehicleV2_0TargetTest
Bug: 301577794
Merged-In: I93020e7e024760601bc5a8edf9997cc356a568c6
Change-Id: I1c95625d45f5199328c4e157ebaa05f480d9e1cc
The nit information was used when we set exact nit values rather than a
relative brightness per layer. But we only need nit values for the
renderengine interface, which isn't tied to any hwc or panel
capabilities.
Bug: 301261125
Test: VtsHalGraphicsComposer3_TargetTest
(cherry picked from https://googleplex-android-review.googlesource.com/q/commit:712b3d9880b6aff51ab17d539bfcbdf3785cc6ca)
Merged-In: I770dc5620648df2eab608e030c5e76cf190f315d
Change-Id: I770dc5620648df2eab608e030c5e76cf190f315d
When VTS case kills supplicant in SetUp, Wi-Fi framework will trigger
recovery process and causes races between VTS and Wi-Fi framework.
Disable Wi-Fi framework using 'cmd wifi' in SetUp.
Bug: 297820612
Test: run vts -m VtsHalWifiHostapdV1_0TargetTest with new case
(cherry picked from https://android-review.googlesource.com/q/commit:46538346af90bf93dcafa36206fc2ea5c545dd93)
Merged-In: I5ea7f00cfebf79021185f66766454d053c973b31
Change-Id: I5ea7f00cfebf79021185f66766454d053c973b31
The transmit without openning a channel passes on some platforms,
because a basic channel can be opened by external applications
and the state is maintained in the HAL.
Bug: 300502872
Test: run vts -m VtsHalSecureElementTargetTest
(cherry picked from https://android-review.googlesource.com/q/commit:d0ed43bb7eeb8c2cdc23d23d0d926e083322b7f3)
Merged-In: If727c613e8575802b99604f7242e16cf85fc97a0
Change-Id: If727c613e8575802b99604f7242e16cf85fc97a0
Introduce a field to the configuration descriptor that provides a
standard semantically-defined version number rather than the
vendor-defined component version which acts more like a build ID.
Test: n/a
Bug: 298580435
Bug: 282205139
(cherry picked from https://android-review.googlesource.com/q/commit:0d520e8e1751fde5a3207c6f27be88a8bbc245dc)
Merged-In: Idb0c991ab12ae75687236f2489e639e4422a0225
Change-Id: Idb0c991ab12ae75687236f2489e639e4422a0225
These tests were created for IRadio 1.2 when all devices supported GSM,
and REQUEST_NOT_SUPPORTED was valid for devices that didn't support GSM. Change the VTS logic to test EUTRAN instead of GERAN.
Remove REQUEST_NOT_SUPPORTED for tests now without GERAN and add REQUEST_NOT_SUPPORTED for all GERAN-specific tests.
Test: atest VtsHalRadioTargetTest
Bug: 294965245
Change-Id: Ib36b171e33451bf0c9adc0b065a4c74df357e77e
Merged-In: Ib36b171e33451bf0c9adc0b065a4c74df357e77e
1. nvResetConfig takes some time to reset the modem, causing subsequent
tests to fail with a timeout since the modem is unavailabe.
Add a timeout after nvResetConfig to allow the modem to be up again
before running the next test.
2. Remove invalid errors for start/stopKeepalive. These tests should
fail due to invalid arguments, so remove NONE as a possible error.
RADIO_NOT_AVAILABLE should also be removed.
3. Fix incorrect startNetworkScan_InvalidInterval tests, since we only
check the interval when the scan type is PERIODIC.
4. Save and reset the previous allowed network type bitmap after the
test. Combine get/set into one test that tests both behaviors.
5. Fix checks for MCC/MNC in getDataRegistrationState
Bug: 277626718
Bug: 240953393
Bug: 264913330
Bug: 259674407
Bug: 242801688
Test: atest VtsHalRadioTargetTest
Change-Id: Ic7188f9d8ccfcd90d844b45e3b370a3be3c515d6
Merged-In: Ic7188f9d8ccfcd90d844b45e3b370a3be3c515d6
(cherry picked from commit ddaea2e5a4)
These tests were created for IRadio 1.2 when all devices supported GSM,
and REQUEST_NOT_SUPPORTED was valid for devices that didn't support GSM. Change the VTS logic to test EUTRAN instead of GERAN.
Remove REQUEST_NOT_SUPPORTED for tests now without GERAN and add REQUEST_NOT_SUPPORTED for all GERAN-specific tests.
Test: atest VtsHalRadioTargetTest
Bug: 294965245
Change-Id: Ib36b171e33451bf0c9adc0b065a4c74df357e77e
AIDL test utils in order to avoid having
an ambigous function call.
aosp/2728874 adds a method of the same
name, which is causing pre-submit issues.
Bug: 297820612
Test: atest VtsHalHostapdTargetTest
Change-Id: Ie4da0a0037e7411e7908401f021b48246ea227bd
Merged-In: Ie4da0a0037e7411e7908401f021b48246ea227bd
(cherry picked from commit 94950dc20d)
The original change to add this test didn't make it into the Android 13
version of the VTS test, so the version gate needs to be updated to be
v3+
Bug: 292318194
Test: VtsAidlKeyMintTargetTest --gtest_filter="*EcdsaMissingCurve*"
(cherry picked from https://android-review.googlesource.com/q/commit:9ed7d2c5bfa3958ef399567e12d84a3f67f0cb80)
Merged-In: I94bf816688e57c7c04893a23cf0399129de94229
Change-Id: I94bf816688e57c7c04893a23cf0399129de94229
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
