A callback should be executed every time the NFC interface is opened,
even in OpenAfterOpen scenarios. If a callback is not executed, a
crash may occur where the NfcService hangs while waiting for an
OPEN_CPLT event.
Bug: 327582461
Merged-In: Idd78c0dae944e3d39a6828b43db5a608adbaf1d9
Change-Id: Idd78c0dae944e3d39a6828b43db5a608adbaf1d9
Signed-off-by: Bruno Carneiro <bccunha@motorola.com>
(cherry picked from commit 056aa140ca)
The tuner vts will read the system property
ro.vendor.vts_tuner_configuration_variant as the suffix of the config
file to read. Vendor who wants to support multiple region for a single
SoC need to put all VTS config with different suffix as
/vendor/etc/tuner_vts_config_aidl_V1.{suffix}.xml on device.
Bug: 322899156
Test: atest VtsHalTvTunerTargetTest
Change-Id: I1f76d700671c07bc90965fba94f96b8be47198d7
For devices not in LTE service, the vts test returns MODEM_ERR is an expected result
Bug:317314512
Test:
VtsHalRadioTargetTest
PerInstance/RadioNetworkTest#setNetworkSelectionModeManual/0_android_hardware_radio_network_IRadioNetwork_slot1
PerInstance/RadioNetworkTest#setNetworkSelectionModeManual/1_android_hardware_radio_network_IRadioNetwork_slot2
Merged-In: I75414ba18be93707310cace21b52508edfc33a20
Change-Id: I75414ba18be93707310cace21b52508edfc33a20
Signed-off-by: liuxiangjun <liuxiangjun3@xiaomi.com>
The invalid value used for the second IMEI attestation test is
potentially wrong in two ways:
- It doesn't match the provisioned value.
- It's not a valid IMEI, not least because it is longer than 16 bytes.
Make the test value shorter so the second failure doesn't apply and
the test can reliably expect CANNOT_ATTEST_IDS.
Bug: 292959871
Bug: 327123694
Test: VtsAidlKeyMintTargetTest
Change-Id: If8c6b9e08b48e6caf5c767578e1ac43964214619
(cherry picked from commit 0215cb3d3e)
This change updates the VTS to exempt TV devices that consume <= 2W of
standby power from APF requirements. This update aligns with latest GTVS
policy.
Bug: 306587099
Test: TH
(cherry picked from https://android-review.googlesource.com/q/commit:9f215110bf524e3bf1d2fb591a724623e11423bc)
Merged-In: Ifec617520db20d1ef61f1eca63b7160d9191f446
Change-Id: Ifec617520db20d1ef61f1eca63b7160d9191f446
am skip reason: Merged-In I8199e5c7570b10b71f127c7439b889c0b3327865 with SHA-1 981c9c2236 is already in history
Original change: https://android-review.googlesource.com/c/platform/hardware/interfaces/+/2665235
Change-Id: I30cc99967587e979d36f8b6b1de76bfb4c0964fd
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
am skip reason: Merged-In I4a5b2a41172c15ae29efb5b177eb86cea5527b4e with SHA-1 b7d44a2eef is already in history
Original change: https://android-review.googlesource.com/c/platform/hardware/interfaces/+/2665195
Change-Id: I241187d84b542beb5a44df2c867056d2ba6d7426
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
am skip reason: Merged-In I8199e5c7570b10b71f127c7439b889c0b3327865 with SHA-1 981c9c2236 is already in history
Original change: https://android-review.googlesource.com/c/platform/hardware/interfaces/+/2665235
Change-Id: If4d6d688d8e7d0373e3e1edd740ae0c78605134e
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
am skip reason: Merged-In I4a5b2a41172c15ae29efb5b177eb86cea5527b4e with SHA-1 b7d44a2eef is already in history
Original change: https://android-review.googlesource.com/c/platform/hardware/interfaces/+/2665195
Change-Id: I3bab88ae6c301fb8ced89c251e84a21e0e35ec59
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
There are no mandatory stream combinations for RAW_SENSOR streams that
do not involve the CROPPED_RAW stream use case. So we don't need to test
stream non CROPPED_RAW stream use cases with the RAW_SENSOR format,
since we don't have a definite answer to whether they will be supported or not.
Bug: 317773720
Test: Camera VTS on cf
Test: Vendor testing
Merged-In: I0870e90ae68a5e35196f0ba0afaa6b8bf7fbfbd8
Change-Id: I0870e90ae68a5e35196f0ba0afaa6b8bf7fbfbd8
Signed-off-by: Jayant Chowdhary <jchowdhary@google.com>
(cherry picked from commit 6847115a00)
am skip reason: Merged-In If9349a097a92c51101c7b5f4bf807b610ab2cb0b with SHA-1 1837df06c2 is already in history
Original change: https://android-review.googlesource.com/c/platform/hardware/interfaces/+/2927410
Change-Id: I6d6ea305b270b7fe524f4d980531577cc1a794d5
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
Set property operation is async so getting the property value
immediately after setting the property might not return the new
value. This CL adds the logic to retry when we do not get the
expected values back.
This CL also skips the test case if getting property or setting
property returns unavailable.
Test: atest VtsHalAutomotiveVehicle_TargetTest
Bug: 322070490
Change-Id: If9349a097a92c51101c7b5f4bf807b610ab2cb0b
Merged-In: If9349a097a92c51101c7b5f4bf807b610ab2cb0b
Set property operation is async so getting the property value
immediately after setting the property might not return the new
value. This CL adds the logic to retry when we do not get the
expected values back.
This CL also skips the test case if getting property or setting
property returns unavailable.
Test: atest VtsHalAutomotiveVehicle_TargetTest
Bug: 322070490
Change-Id: If9349a097a92c51101c7b5f4bf807b610ab2cb0b
Merged-In: If9349a097a92c51101c7b5f4bf807b610ab2cb0b
The Thread HAL VTS test is built from the staging folder on the
android14-tests-dev branch. And the HAL interface doesn't have
@VintfStability which means it is unstable interface. Thread HAL
interface has been removed from the staging folder and added the
@VintfStability on main branch. It reports following errors when
runing the VTS that froms android14-tests-dev branch on main branch.
`BpBinder: Cannot do a user transaction on a system stability
binder in a vendor stability context`
This CL bypasses the `SendSpinelFrame` test case of the Thread
VTS tests on TV devices.
Bug: b/322731574
Test: Run `run vts -m VtsHalThreadNetworkTargetTest` on the TV device
Change-Id: Ibf7fe96aafa58cee7ae55a0ef613f0be67548a80
setProp test, sets READ_WRITE property and reads prop value immediately,
without considering the time delay Vehicle HAL service required to process
the set request.
This is handled by a retry and timeout mechanism, where the read trials
will happen in 500 milliseconds for a timeout of 2 seconds.
Bug: 312265787
Test: VtsHalAutomotiveVehicleV2_0TargetTest
Change-Id: I5db6d724710033f271064ac81c5178f0dec74b26
One case was missed in the previous fix.
This is an update.
Bug: 312911587
Test: no regressions
Change-Id: I7fefa92d5a66581431288ec902a56ed61e9cf310
(cherry picked from commit 46d9630125)
