Skip attestation key tests if the feature
FEATURE_KEYSTORE_APP_ATTEST_KEY is disabled on device,
as done in KeyMint CTS.
Bug: 244460948
Bug: 265740739
Test: VtsAidlKeyMintTargetTest
Change-Id: I8199e5c7570b10b71f127c7439b889c0b3327865
In case we have a camera device that doesn't support the
Hal buffer management mode, services are required to use
the frame number and stream id to deduce the specific
buffer id and Hals are not mandated to return valid
buffer ids as part of the capture result.
Bug: 265092659
Test:adb shell
/data/nativetest64/VtsAidlHalCameraProvider_TargetTest/VtsAidlHalCameraProvider_TargetTest
--gtest_filter=PerInstance/CameraAidlTest.process10BitDynamicRangeRequest/0_android_hardware_camera_provider_ICameraProvider_internal_0
Change-Id: I3b10e91d38a13afcca45f26712cc5d5c241c2a32
am skip reason: Merged-In If47154adf9d48f9c1b8390b4bee090d8bf40ff3b with SHA-1 308f4ac906 is already in history
Original change: https://android-review.googlesource.com/c/platform/hardware/interfaces/+/2315559
Change-Id: Id1f46ca50a167b3a9df97cd898cedc4a6f83b6a3
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
"physicalCameraDeviceStatusChange" returns a default
ScopedAStatus that will not include a valid AStatus instance.
This will result in binder instabilities once the status
is being parceled.
Return "ScopedAStatus::ok" instead.
Bug: 253993253
Test: adb shell VtsAidlHalCameraProvider_TargetTest
Change-Id: I219f608a04aaec0631e3de58a7e0d47a30294e52
Dimension was initialized to the size of the last config that is in the config list.
VTS didn't change the dimension in the readback test and allocated buffer
for the readback with the dimension size.
However it was different with actual display size.
This change initializes display dimension to the actual display size.
Bug: 259155172
Change-Id: I64fec02f5386eb6ca1f41ab376be193231810b93
Merged-In: I64fec02f5386eb6ca1f41ab376be193231810b93
Signed-off-by: HyunKyoung <hk310.kim@samsung.com>
Root Cause: Even when proper DAB signals are available, the test-case
"BroadcastradioHalTest.DabTune" always fails. This is because the Pro
-gramSelector created as part of the test-case is not valid according
to the AOSP documentation; it passes only DAB_FREQUENCY as the Primar
-yId, but according to the AOSP documentation, DAB_FREQUENCY is not p
-art of proper acceptable PrimaryIds in a ProgramSelector
Fix: The test-case is modified to retrieve the station list before pe
-rforming any tune in the test-case; there are three possible outcome
-s:
- If there are no stations in the station list, the test-case shall b
-e skipped
- If there are stations in the station list, but there are no dab sta
-ions being transmitted/received, the test-case shall be skipped
- If there are stations in the station list, and if there are DAB ser
-vices, extract one service from the list, and create a ProgramSele
-ctor, and send a tune-request
Test: run "VtsHalBroadcastradioV2_0TargetTest from VTS; run the test-
case - "BroadcastradioHalTest.DabTune"
Bug: 208477956
Change-Id: I874d36f9eeb460fabadd06fe1e138a35b13a5816
(cherry picked from commit e1863a9ce4)
DAB frequency 178352kHz hardcoded in the test is used in EU region
(channel 5C) but it is not valid in others (e.g. Korea and China).
Therefore DabTune test was modified to use one of supported
frequencies reported via getDabRegionConfig method.
Test: run VtsHalBroadcastradioV2_0TargetTest on hardware units
configured for Europe, China and Korea DAB tuner regions.
Bug: b/190136847
Change-Id: Icd71e42a9242528465ac1358465d8b6d6d4896bf
(cherry picked from commit 7aa628d4de)
Root Cause: Even when proper DAB signals are available, the test-case
"BroadcastradioHalTest.DabTune" always fails. This is because the Pro
-gramSelector created as part of the test-case is not valid according
to the AOSP documentation; it passes only DAB_FREQUENCY as the Primar
-yId, but according to the AOSP documentation, DAB_FREQUENCY is not p
-art of proper acceptable PrimaryIds in a ProgramSelector
Fix: The test-case is modified to retrieve the station list before pe
-rforming any tune in the test-case; there are three possible outcome
-s:
- If there are no stations in the station list, the test-case shall b
-e skipped
- If there are stations in the station list, but there are no dab sta
-ions being transmitted/received, the test-case shall be skipped
- If there are stations in the station list, and if there are DAB ser
-vices, extract one service from the list, and create a ProgramSele
-ctor, and send a tune-request
Test: run "VtsHalBroadcastradioV2_0TargetTest from VTS; run the test-
case - "BroadcastradioHalTest.DabTune"
Bug: 208477956
Change-Id: I874d36f9eeb460fabadd06fe1e138a35b13a5816
Add mode not support check for setPreferredNetworkTypeBitmap.
Bug: 142369230
Test: run vts -m VtsHalRadioV1_4Target
Change-Id: I17b07f40b313f9b04e2f73d9b4a235ede891f8ea
(cherry picked from commit 16e7bf5ce3)
Bluetooth does not handle well conflicting message
Test: VtsHalBluetoothV1_0TargetTest
Test: VtsHalBluetoothV1_1TargetTest
Bug: 262645484
Bug: 262501652
Bug: 260064452
Change-Id: I0aca127fb5e5e33cc0086aaad19a8f1286fc83d6
(cherry picked from commit cd64ee13fb)
SM8550 doesn't support Keymint2.0, per the discussion in b/
add an exception in the test case when SM8550 is detected.
Bug: b/245649355
Test: VtsHalKeymasterV4_0TargetTest
Change-Id: I788a80c0f9b011f73aac9a8c4774e70e203ac3d6
The fix in https://r.android.com/2322475 modifies the device
address, which becomes 'IN_DEFAULT' for the telephony case.
As a result, tests that verify capture position were not
skipped, and they do fail on certain platforms when there is
no active telephone call. The fix is to use the initial device
type which was passed to the test as a parameter, not the adjusted
one.
Bug: 263305254
Test: atest VtsHalAudioV7_0TargetTest
Test: atest VtsHalAudioV7_1TargetTest
Change-Id: Ied7134a1bd97e70dcc2400e0827810f9d71a6438
(cherry picked from commit 7029707e34)
