| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
| |
Test: Build
Bug: 135717625
Change-Id: I324cfd592ca53a12ebe1161f242ae3b9c7fc59a4
Merged-In: I324cfd592ca53a12ebe1161f242ae3b9c7fc59a4
(cherry picked from commit 1f4012f417831ae076bb3861e1ac3f4c14fe2d7c)
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| | |
To be consistent w/ hidl-gen output.
Bug: N/A
Test: N/A
Change-Id: Ic4bd68777e74e5cdfc222202398923d34125f2af
|
|/
|
|
|
|
|
|
|
|
| |
Convert VtsHalRadioConfigV1_*TargetTest to be parameterized test
and add it to vts-core
Bug: 142397658
Test: $atest VtsHalRadioConfigV1_1TargetTest
$atest VtsHalRadioConfigV1_2TargetTest
Change-Id: I4dfa140e7d500022fcf59fefe62fee45c185b534
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Convert VtsHalRadioConfigV1_0TargetTest to be parameterized test
and add it to vts-core
Bug: 142397658
Test: $atest VtsHalRadioConfigV1_0TargetTest
Change-Id: Ie9b62e8e655b17577e01aebb3a30e37a598c7bdd
|
| |
| |
| |
| |
| |
| |
| |
| | |
Bug: 141995149
Test: build
Change-Id: I260dfa2e57f1b8c7df5273e2d0b39cbc1d6a4571
Merged-In: I260dfa2e57f1b8c7df5273e2d0b39cbc1d6a4571
|
|/
|
|
|
|
|
|
|
| |
So that later people can add APIs and type definitions as needed.
Bug: 141995149
Test: build
Change-Id: Ib18f75fd391b94ffbd65d7feb4589ff82b3ac1d4
Merged-In: Ib18f75fd391b94ffbd65d7feb4589ff82b3ac1d4
|
|\
| |
| |
| |
| |
| | |
am: 3c8f624724
Change-Id: If856c76531d329e7beac3d0b4902ecf46a7c8b6d
|
| |\ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Add the initialization of the incrementalResultsPeriodicity and
maxSearchTime in the networkScan request.
The incrementalResultsPeriodicity and maxSearchTime are not
initialized in the networkScan request. So the default value is 0.
But the incrementalResultsPeriodicity and maxSearchTime
are required not to be 0 in subsequent tests.
CL ported from pag/1433565
Bug:140451434
Test: make vts && vts-tradefed run commandAndExit vts -m \
VtsHalRadioV1_2Target -t RadioHidlTest_v1_2#startNetworkScan
Change-Id: I1b4e512a37d3d85ebc905a64987a40af801bce53
(cherry picked from commit f7894eb4d8c395add7c70a20520336057ae2656f)
|
|\| |
| | |
| | |
| | |
| | |
| | | |
am: 111a10c44e
Change-Id: If37e587d604003ea2422938dfc994d2109ae359e
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Update the documentation of NetworkScanRequest to clarify
that the interval between scans is from the completion of
one scan to the start of another. This is the only possible
definition that doesn't possibly result in back-to-back
scans which never complete.
In the initial design of this API, the stated use case was
for scans where "interval" >> "scan duration". For that
use case, this clarification doesn't make a meaningful
difference; however, for the use case of long-duration
scans, the distinction prevents the issue stated above.
Bug: 139935383
Test: compilation (docstring-only change)
Change-Id: Ib8393110bfd3ea883045648ee7dac9c6e6a32d44
|
|\|
| |
| |
| |
| |
| | |
am: 9f50a49681
Change-Id: I4e2f90ce020f0522e4f8c7e09bb9356ee5c21b0b
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Currently tests that check for incremental scan interval
range-checking have incremental scans disabled.
This CL turns on incremental scans for tests where the
invalid interval range checks are being validated.
Set Incremental Results to true for InvalidPeriodicity
Tests in Radio 1.4. This is a spiritual cherry-pick of
the exact same test copied from HAL 1.2.
Related Change-Id: I94874f538d2df70a72913b489d9298f8d1cf9b56
Related Sha: 81c811b895e2abb019598c77b9c73fc5c4770e23
Bug: 138317383
Test: atest RadioHidlTest_v1_4#startNetworkScan_InvalidPeriodicity1
Test: atest RadioHidlTest_v1_4#startNetworkScan_InvalidPeriodicity2
Change-Id: I20d6423c01dfc1c708514e798589c36666f2c0d4
|
|\ \
| |/
|/|
| |
| |
| | |
Bug: 135460123
Change-Id: Ia07db5c8afeed7fe22a2b18d867a38390f910a81
Merged-In: Ibbd540dbb5baee46360d3fe9469212cfd8f550ba
|
| |\
| | |
| | |
| | |
| | |
| | | |
am: 1f12b5323a
Change-Id: I6279a0da6ebf1f5c6e78e0c43d4d0ce4dc9a566a
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
After disconnect calls, we want to verify there are no more current calls
by calling IRadio.getCurrenctCalls
Test: run vts
Bug: 138413412
Change-Id: Iacca49abff11fbdfb4ae6dd060a5f150e9e4a74d
|
| |\|
| | |
| | |
| | |
| | |
| | | |
am: d005bbeb53
Change-Id: Ibcd1ae9af41a1330a1e5094ce2a34bee94dbae2d
|
| | |
| | |
| | |
| | |
| | |
| | | |
Test: VTS
Bug: 137298570
Change-Id: I0afacd413d467c3e25585d6d5431278fd61a1562
|
| |\|
| | |
| | |
| | |
| | |
| | | |
am: 53861e16c3
Change-Id: I05e4a0d99c92e1ae790e183b121e8dba30feae91
|
| | |\ |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Providing non-dds exemption for HAL 1.2 network scan due to some devices
only perform network scan on preferred data sim. Since logical modem
id(0/1) and physical sim slot id(0/1) are intuitively aligned. Set
first sim as dds sim, and skip the network scan on the second one
(non-dds).
Test: Vts
Bug: 135243177
Change-Id: I58b89473714dc6d3ce6567ba1809baad6cd6d799
|
| |\| |
| | | |
| | | |
| | | |
| | | |
| | | | |
am: c69700441e
Change-Id: Ie19296bfdea3a23986741e5e41813b51330b5009
|
| | |\ \ |
|
| | | |/
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Network scan tests with parameters are disabled because of vendors
failed to fully implement startNetworkScan in HAL 1.4, and GSM rat scan
with parameters will get REQUEST_NOT_SUPPORTED error from modem.
Test: VTS
Bug: 137298570
Change-Id: I99df8495c5f654cb1420b7da36d7f5128ce14dbc
|
| |\| |
| | | |
| | | |
| | | |
| | | |
| | | | |
am: fb1616eb94
Change-Id: I9d8de8a97e23b2321640615d14d33c997b45bbe3
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Change stopNetworkScan from 1_1 to 1_2 when testing VtsHalRadioV1_2Target.
Symptom:
When vts process slot2 "startnetworkscan", it will call "stopnetworkscan()" when startnetworkscan
success. But from current design it will set stopnetworkscan to slot1(wrong slot, expect is slot2)
as bwlow log.
CTS fail log:
hardware/interfaces/radio/1.2/vts/functional/radio_hidl_hal_test.cpp:111
//Device request NwScan on 2nd Sim
06-28 11:30:22.770 radio 873 1213 F RILQ : RIL[1][Log.cpp: 48] [DispatcherModul(873,1213)]
d: [DispatcherModule]: Handling msg = RIL_REQUEST_START_NETWORK_SCAN
//But Device want to abort on Primary Sim
06-28 11:30:22.776 radio 923 1205 F RILQ : RIL[0][Log.cpp: 48] [DispatcherModul(923,1205)]
d: [NasModule]: Handling msg = RIL_REQUEST_STOP_NETWORK_SCAN[Context: IRadio(1681692777)]
Bug: 135982495
Test: Build pass. Local test VTS pass.
Change-Id: Ic53c24ab2a670e806b4ac7f192e6eb81252ade84
(cherry picked from commit 5cef297cb2ed70bcf70abf911dc4bd14c343cbc6)
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Since these were combined into libhidlbase.
Bug: 135686713
Test: build only (libhwbinder/libhidltransport are empty)
Change-Id: I075670b64eebbbbd6a6ae0e84ad51bf1c6f5ba36
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
am: f0796fd497
Change-Id: I6c5748081b255d2b38e51aa285f60a786d72383a
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
It's reasonable to update the global variable "currentCalls" before
notifying the reader thread. Otherwise this can cause some issues such
as null pointer dereference in other modem.
Bug: 139264227
Test: Don't have devices that uses the corresponding modem that reports
this issues. This is verified according to a partner CL:
https://partner-android-review.googlesource.com/c/platform/hardware/interfaces/+/1422356
Change-Id: Iee9e18149397c39b7c84ec1dc570b9bac7142eb6
Merged-In: Iee9e18149397c39b7c84ec1dc570b9bac7142eb6
(cherry picked from commit fcd55caafdb83b664d1069a6ca96b40fd6cdf452)
|
|\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Bug: 139893257
Change-Id: I7e48b5477b2edda72c940e05531782dd28a2f784
|
| | |_|/ /
| |/| | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Providing non-dds exemption for HAL 1.2 network scan due to some devices
only perform network scan on preferred data sim. Since logical modem
id(0/1) and physical sim slot id(0/1) are intuitively aligned. Set
first sim as dds sim, and skip the network scan on the second one
(non-dds).
Test: Vts
Bug: 135243177
Change-Id: I58b89473714dc6d3ce6567ba1809baad6cd6d799
(cherry picked from commit fc85e8fa50ccae2cd0e538260ccb9e62c109b181)
|
| | |_|/
| |/| |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The whole test case run emergencyDial.RadioHidlTest_v1_4 first and then
come after startNetworkScan.RadioHidlTest_v1_4 test case immediately
(within ~3 secs) the NWscan failure is device in emergency call in
progress/connected while doing emergencyDial.RadioHidlTest_v1_4 test
Although emergencyDial.RadioHidlTest_v1_4 only care about command/response
is successful or not and don't care call is established or not, modem do
care about call condition is in idle/progress/connected state before it
can do NWscan
When there's dedicated channel established, modem can not perform AP
request NWscan in parallel as we are single HW modem restriction.
Test: run vts
Bug: 135595082
Change-Id: Iecba54b93b96d33b57bc59e00f082ff133d2e57b
Merged-In: Iecba54b93b96d33b57bc59e00f082ff133d2e57b
|
|\ \ \ \
| | |/ /
| |/| /
| |_|/
|/| |
| | | |
am: c8a08c1816
Change-Id: I3209c206b8299b2ecb7f6ec5df69dee2f643c743
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
After disconnect calls, we want to verify there are no more current calls
by calling IRadio.getCurrenctCalls
Test: run vts
Bug: 138413412
Change-Id: Iacca49abff11fbdfb4ae6dd060a5f150e9e4a74d
Merged-In: Iacca49abff11fbdfb4ae6dd060a5f150e9e4a74d
(cherry picked from commit 5f68117e87f4761948ce287d239c38b7c33081c0)
|
| |\ \
| | | |
| | | |
| | | |
| | | | |
Bug: 136196576
Change-Id: I58505f104075c7c210612eda8e266df9e3ecfeda
|
|\| | |
| | | |
| | | |
| | | |
| | | |
| | | | |
am: 98d0f4d52c
Change-Id: Ie6cfbacd523c4b09f77bee3369ec8e88b3fa0419
|
| |\ \ \ |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Signed-off-by: Felix <google@ix5.org>
Change-Id: I6d70bbdb66c3dce280bf6908c3750316a6f6cf70
|
| |\ \ \ \ |
|
| | |/ / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Bug: 122730535
Test: run vts -m VtsHalRadioConfigV1_2Target
Change-Id: Ib4fc17ea9f76caaf0cb0d4a2914595b7cfb7b041
Merged-In: Ib4fc17ea9f76caaf0cb0d4a2914595b7cfb7b041
|
|\| | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
am: 8c9947de8d
Change-Id: Ieeb5e62c4709c4288ebf956631851124caf90867
|
| |/ / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The whole test case run emergencyDial.RadioHidlTest_v1_4 first and then
come after startNetworkScan.RadioHidlTest_v1_4 test case immediately
(within ~3 secs) the NWscan failure is device in emergency call in
progress/connected while doing emergencyDial.RadioHidlTest_v1_4 test
Although emergencyDial.RadioHidlTest_v1_4 only care about command/response
is successful or not and don't care call is established or not, modem do
care about call condition is in idle/progress/connected state before it
can do NWscan
When there's dedicated channel established, modem can not perform AP
request NWscan in parallel as we are single HW modem restriction.
Test: run vts
Bug: 135595082
Change-Id: Iecba54b93b96d33b57bc59e00f082ff133d2e57b
Merged-In: Iecba54b93b96d33b57bc59e00f082ff133d2e57b
(cherry picked from commit 07a53471c45c53c00ca0fbe1d83b23a3f2c2ba76)
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Currently tests that check for incremental scan interval
range-checking have incremental scans disabled.
This CL turns on incremental scans for tests where the
invalid interval range checks are being validated.
Bug: 112486807
Test: atest RadioHidlTest_v1_2#startNetworkScan_InvalidPeriodicity1;
atest RadioHidlTest_v1_2#startNetworkScan_InvalidPeriodicity2;
Merged-In: I94874f538d2df70a72913b489d9298f8d1cf9b56
Change-Id: I94874f538d2df70a72913b489d9298f8d1cf9b56
(cherry picked from commit f56b9a41dd68e0d3cc7d2a506b26ce7d0fac2a12)
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
When incremental results are disabled for network scans,
update the API documentation to allow implementations to
ignore range checking for the incremental scan interval.
Bug: 112486807
Test: compilation - docstring-only change
Merged-In: I901335550b4b8c2cf75f91b39fd031f03ffae982
Change-Id: I901335550b4b8c2cf75f91b39fd031f03ffae982
(cherry picked from commit 944efca78d9717e1b17109b28c0da26a4cd9f790)
|
| |\ \ \
| | | | |
| | | | |
| | | | | |
available"
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
available
Bug: b/132818184
Test: VTS
Change-Id: I2b57ab99a376bcab26012d08f00284d65f915bc3
Merged-In: I2b57ab99a376bcab26012d08f00284d65f915bc3
(cherry picked from commit 52b35030640e960b6ff6ba98ca2c68eb7cb8b6a7)
|
| |\ \ \ \
| | |/ / /
| |/| | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Use the same resolution as 1.0 to check for invalid mnc and mcc values.
Bug: 130206359
Test: Vts
Change-Id: Iff766014ecfbe2d77db6771eda04fd4d9c84df14
|