for the Wifi VTS tests.
Main method is getBridgedWifiApIface_1_6, which
allows us to configure the chip based on the
Bridged AP IfaceConcurrencyType, rather than
the AP IfaceType like in getBridgedWifiApIface_1_5.
Implementations were largely copied from
wifi_hidl_test_utils and wifi_hidl_test_utils_1_5.
Bug: 283402709
Test: atest VtsHalHostapdTargetTest
# tested on a Bluejay device that supports
# the AddAccessPointWithDualBandConfig test
Change-Id: I2571876149fc14c8de02e1cec9934dd052cada5c
Merged-In: I2571876149fc14c8de02e1cec9934dd052cada5c
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.
Bug: 259674407
Test: atest VtsHalRadioTargetTest
Change-Id: Ic7188f9d8ccfcd90d844b45e3b370a3be3c515d6
Merged-In: Ic7188f9d8ccfcd90d844b45e3b370a3be3c515d6
(cherry picked from commit ddaea2e5a4)
We check SIM card status is PRESENT before running any VTS tests, so
ensure that it's enforced in the configs as well.
Test: atest VtsHalRadioTargetTest
Bug: 249143796
Change-Id: I1b2c317e21db118e4b957804feb76f266d887b20
Merged-In: I1b2c317e21db118e4b957804feb76f266d887b20
(cherry picked from commit 658fdaaa2a)
The code currently uses 'dsds' to detect dual-SIM configurations,
but it misses 'dsda' configurations, resulting in test failures.
Should use the detection mechanism by adding handling for 'dsda',
ensuring accurate detection of all dual-SIM configurations.
Bug: 277705768
Test: vts -m VtsHalRadioTargetTest -t PerInstance/RadioConfigTest#checkPortInfoExistsAndPortActive/0_android_hardware_radio_config_IRadioConfig_default
Change-Id: Ie73a958ff14e86f440831e18291b6599b6eac30b
Signed-off-by: Jia Jia <jia.jia@zte.com.cn>
If CEC DUT is a TV device type,we should reset logical address to tv,
and then set message.initiator to tv.
Bug: 277715429
Test: run VTS
Change-Id: If7f7b9ddce182e5de80c91a30c4ec18294459fbf
Signed-off-by: caijq <callen.cai@rock-chips.com>
am skip reason: Merged-In Id581e290740a3c00ba3719a339c9bc47d730f35c with SHA-1 afff851110 is already in history
Original change: https://android-review.googlesource.com/c/platform/hardware/interfaces/+/2544670
Change-Id: I7cc328378f38bb1918d6751797865a3b99de459e
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
am skip reason: Merged-In Id581e290740a3c00ba3719a339c9bc47d730f35c with SHA-1 afff851110 is already in history
Original change: https://android-review.googlesource.com/c/platform/hardware/interfaces/+/2544670
Change-Id: I50d081a0fbafc3e91a93cd1d36578a2b1b0693a7
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
There was a proposal for a backward-compatible XML schema change
(https://android-review.googlesource.com/q/I1bf31c6bf6c57c9b79f0d5751601aa77780f1f80)
which had a mistake. Express the change correctly to match
the implementation.
Bug: 231929160
Test: atest VtsHalAudioPolicyV1_0TargetTest
Change-Id: Id581e290740a3c00ba3719a339c9bc47d730f35c
Merged-In: Id581e290740a3c00ba3719a339c9bc47d730f35c
(cherry picked from commit e01186e117)
Fence fd is closed when processCaptureResult returns. In order to
wait for the release fence *after* processCaptureResult returns,
the fence fd needs to be duped.
Test: Vendor testing
Bug: 241281568
Change-Id: Ib74f9bb141802713b476a2ef48a2252125a7915d
If the device is depth-only, use threshold with Y16 format rather than
IMPLEMENTATION_DEFINED.
This fixes the regression introduced by the fix for b/265984260.
Bug: 276957901
Test: atest VtsAidlHalCameraProvider_TargetTest
Change-Id: If9023f1ed17bb761abbb9be36e567264f8bf0689
The camera HAL may signal release fence after processCaptureResult.
If the VTS test waits for the release fence in the context of the
capture result, there is possibility of deadlock.
Rather, we should wait for the releaseFence in a different thread
context to really emulate the real application behavior.
Test: atest VtsAidlHalCameraProvider_TargetTest
Bug: 241281568
Change-Id: Id1d92e901aae1cab084846d252ef090fcda182d7
Bad safe_union access is raised by calling the GET method of
eutranBands(), because in default ctor of safe_union RadioAccessSpecifier::Bands
hidl_d is assigned with hidl_discriminator::geranBands, which conflicts
with hidl_discriminator::eutranBands, and leads to crash.
Should use the SET method of eutranBands(&) for assignment purpose.
Fix: 275077563
Bug: 271642958
Change-Id: Ie241e8968eb7f9a1297203be2ab4e0a1bf738dea
Signed-off-by: Jia Jia <jia.jia@zte.com.cn>
Bug: 264597734
Test: atest VtsHalGnssTargetTest
(cherry picked from https://googleplex-android-review.googlesource.com/q/commit:dbab0de442246a78c42acf5ca7c4f7c94fd82651)
Merged-In: I1064807adf3264f13c1ef6678df37cff350503c5
Change-Id: I1064807adf3264f13c1ef6678df37cff350503c5
NOTE FOR REVIEWERS - original patch and result patch are not identical.
PLEASE REVIEW CAREFULLY.
Diffs between the patches:
47,6 +447,7 @@
const int numMeasurementEvents,
const int timeoutSeconds,
std::vector<int>& deltasMs) {
+ callback->gnss_data_cbq_.reset(); // throw away the initial measurements if any
int64_t lastElapsedRealtimeMillis = 0;
for (int i = 0; i < numMeasurementEvents; i++) {
GnssData lastGnssData;
Original patch:
From dbab0de442 Mon Sep 17 00:00:00 2001
From: Yu-Han Yang <yuhany@google.com>
Date: Tue, 07 Feb 2023 19:01:56 +0000
Subject: [PATCH] Throw away initial measurements before interval tests
Bug: 264597734
Test: atest VtsHalGnssTargetTest
Change-Id: I1064807adf3264f13c1ef6678df37cff350503c5
---
Test with LTE bands, which are supported by every device
in the world.
Bug: 271642958
Test: atest VtsHalRadioTargetTest
Change-Id: Ibc71a69b1a9aeec506a35fac9f64ecad80371155
Function assertTypeMatchStringType does not match the sensor type
HINGE_ANGLE that only exists on folding screen phones. When testing the
VtsAidlHalSensorsTargetTest on a folding screen mobile phone,
it will fail.
So we need add CHECK_TYPE_STRING_FOR_SENSOR_TYPE(HINGE_ANGLE) to
the function assertTypeMatchStringType.
Bug: 270831199
Change-Id: Ib82a1168ff90d851eee6ce025464b11bcda7d5ca
Sensor event never occur on DUT that has no sensor.
So, skip this test case on DUT that has no sensor.
Test: run vts -m VtsHalSensorsV2_0TargetTest
Bug: 273383821
Change-Id: I657b74ca3c67c105e40e58a7e4c700370a9db3e3
Signed-off-by: AOYAGI Takako <aoyagi.takako@jp.panasonic.com>
am skip reason: Merged-In Iedb9caad933b0df2b190915f5cc7177e507f15b5 with SHA-1 a6fc69d339 is already in history
Original change: https://android-review.googlesource.com/c/platform/hardware/interfaces/+/2489995
Change-Id: I102eb9702ba55f190cd59c46afabd3f8f9eac738
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
ATSC configuration isn't supported in current config reader.
Add it in this CL.
Bug: 271933206
Test: manual
Change-Id: I7a1f5356c33d6576d6ae6c71fd4af171b5ad30ac
For those devices which does not support GSM, returning is not
supported or invalid arguments are the expected behavior.
Bug: 271642958
Test: atest VtsHalRadioTargetTest
Merged-In: I3ac7407fdee82348411db99d340613e62f36a277
Change-Id: I3ac7407fdee82348411db99d340613e62f36a277
Signed-off-by: Jia Jia <jia.jia@zte.com.cn>
(cherry picked from commit 5bf6d5777a)
