During the API freeze some of the sub-interfaces of radio were frozen
without the latest change adding "@Javaderive(toString=true)".
Instead of creating V2 with these changes, we are updating V1 to include
these changes instead. The change will not break anyone downstream, and
any devices built with the previous V1 will continue to work. The hashes
of the original V1 interfaces are still included in the .hash files, so
VTS will allow both.
Steps taken:
m android.hardware.radio.config-freeze-api
rm aidl_api/android.hardware.radio.config/2/.hash
cp -r aidl_api/android.hardware.radio.config/2/*
aidl_api/android.hardware.radio.config/1/
rm -rf aidl_api/android.hardware.radio.config/2/
vim Android.bp # remove the newly created version 2
system/tools/aidl/build/hash_gen.sh aidl_api/android.hardware.radio.config/1/
latest-version aidl_api/android.hardware.radio.config/1/.hash
Test: atest hal_implementation_test
Bug: 225941299
Change-Id: Id14cfffd326bd664acb678f15f4129d85ce251b2
Merged-In: Id14cfffd326bd664acb678f15f4129d85ce251b2
Test IRadioNetwork.setSignalStrengthReportingCriteria should
support multiple RANs per request.
Bug: 206857183
Test: atest VtsHalRadioTargetTest
Change-Id: I9d48029b4c2f5c36c7f48c9712c17dbdcf890dc4
All TCs store RadioResponseInfo in a shared variable and
read it to verify the result. So there is race condition
problem if we don't wait for responses.
Bug: 228593077
Test: run vts -m VtsHalRadioTargetTest
Change-Id: I45e60f324926588c55abd0a719fd55352767a3eb
If we set the SIM slots mapping arbitrarily on single SIM enabled
device, the SIM state could become absent and cause other TCs fail.
Bug: 227693614
Test: run vts -m VtsHalRadioTargetTest
Change-Id: I2c8d3a162e1dca5a0bd6cfe93a1cc269f4c25188
* changes:
Implement getInterfaceHash/Version for SoundTrigger
Add -Wno-missing-permission-annotation for soundtrigger3
V3 is the latest version of keymaster HAL interface
Freeze AIDL APIs for TM
1. Add 6s delay after setSimSlotsMapping because modem needs time to
process SIM configuration change. The next TC could fail at
checking SIM status if there is no delay. The default SIM
configuration on my test device is that physical#0 maps to
logical#1 and physical#1 maps to logical#0. When running
setSimSlotsMapping, it then becomes physical#0 maps to logical#0
and physical#1 maps to logical#1.
2. Support DSDS case and TSTS case for setSimSlotsMapping. The
original code only set for 1 slot and it caused 2nd slot SIM
absent when testing with DSDS enabled.
3. Set slotStatus from corresponding physical slot for
setSimCardPower.
Bug: 227579281
Test: run vts -m VtsHalRadioTargetTest
Change-Id: I8c12cb1dbc439655f9de88b1e217b3f34e44ebeb
Merged-In: I8c12cb1dbc439655f9de88b1e217b3f34e44ebeb
To accomodate MEP, we have updated the setSimSlotMapping API in the HAL,
Writing the tescases to check functionality of the same.
Test: atest VtsHalRadioTargetTest
Bug: 217665559
Change-Id: Idbff19db2e536d3c2f7b80afbbf244575d8247d0
Merged-In: Idbff19db2e536d3c2f7b80afbbf244575d8247d0
1. Add 6s delay after setSimSlotsMapping because modem needs time to
process SIM configuration change. The next TC could fail at
checking SIM status if there is no delay. The default SIM
configuration on my test device is that physical#0 maps to
logical#1 and physical#1 maps to logical#0. When running
setSimSlotsMapping, it then becomes physical#0 maps to logical#0
and physical#1 maps to logical#1.
2. Support DSDS case and TSTS case for setSimSlotsMapping. The
original code only set for 1 slot and it caused 2nd slot SIM
absent when testing with DSDS enabled.
3. Set slotStatus from corresponding physical slot for
setSimCardPower.
Bug: 227579281
Test: run vts -m VtsHalRadioTargetTest
Change-Id: I8c12cb1dbc439655f9de88b1e217b3f34e44ebeb
Setup code was causing all tests to be ignored on devices with AIDL HAL.
Fix the setup code and increase GTEST timeout to prevent the test suite
from crashing.
Test: atest VtsHalRadioTargetTest
Bug: 225032427
Change-Id: Ice60f7fae313863e97e425994bee5ad1d703c807
Merged-In: Ice60f7fae313863e97e425994bee5ad1d703c807
Fix failing SIM tests so test suite can be enabled
Test: atest VtsHalRadioTargetTest passes
Bug: 217574863
Change-Id: Id7ac87ca6da799df4af983cd295a4234e75565d2
Merged-In: Id7ac87ca6da799df4af983cd295a4234e75565d2
aidl::AccessNetworks and hidl::RadioAccessNetworks has a different enum
Bug: 223770908
Test: manual
Change-Id: Idd20d77c0090567a4e88334061ecd44415500000
Setup code was causing all tests to be ignored on devices with AIDL HAL.
Fix the setup code and increase GTEST timeout to prevent the test suite
from crashing.
Test: atest VtsHalRadioTargetTest
Bug: 225032427
Change-Id: Ice60f7fae313863e97e425994bee5ad1d703c807
Remove network on all errors instead of only RADIO_NOT_AVAIALBLE.
Test: atest DataNetworkTest
Bug: 219998284
Change-Id: I9e36829c627c7fa1286174e536ef5ff561e8b142
To accomodate MEP, we have updated the setSimSlotMapping API in the HAL,
Writing the tescases to check functionality of the same.
Test: atest VtsHalRadioTargetTest
Bug: 217665559
Change-Id: Idbff19db2e536d3c2f7b80afbbf244575d8247d0
Merged-In: Idbff19db2e536d3c2f7b80afbbf244575d8247d0
(cherry picked from commit 2a01674368)
* Timed out runs do not show any warning messages.
* These test files cannot finish clang-tidy runs with
the following settings:
TIDY_TIMEOUT=90
WITH_TIDY=1
CLANG_ANALYZER_CHECKS=1
* When TIDY_TIMEOUT is set, in Android continuous builds,
tidy_timeout_srcs files will not be compiled by clang-tidy.
When developers build locally without TIDY_TIMEOUT,
tidy_timeout_srcs files will be compiled.
* Some of these test modules may be split into smaller ones,
or disable some time consuming checks, and then
enable clang-tidy to run within limited time.
Bug: 201099167
Test: make droid tidy-hardware-interfaces_subset
Change-Id: I1de28f1572fff368f67eab512fffec9f2e5c2a9b
Fix failing SIM tests so test suite can be enabled
Test: atest VtsHalRadioTargetTest passes
Bug: 217574863
Change-Id: Id7ac87ca6da799df4af983cd295a4234e75565d2
Bluetooth uses ISAP interfaces which are radio 1.0 HIDL implementation.
ISAP is not migrated to AIDL and would need to be migrated only if adding
any new interfaces to ISAP. Since the usage is only in 1.0 and 1.1 and 1.2
would be backward compatible, adding bluetooth apex only to radio 1.0.
Bug: 206121418
Test: Compile
Change-Id: I4f387fb0a36518cbef99084421a90a5d2f5c26c2
The final step of the RadioNewtorkTest#setUsageSetting
is to restore the original value to the modem in case it was
changed. After doing that, the locally cached value in the
VTS layer needs to be updated before comparing it with the
originally queried value to ensure that the modem was
restored to its initial state.
Bug: 211819471
Test: m VtsHalRadioTargetTest
Change-Id: Ibdd584d91b16bb779a0cefa2f45d2704cdcf7288
