Since negative values indicates network did not suggest
data retry timer, the type should be signed instead of
unsigned.
Test: Manual
Fix: 159672248
Change-Id: Ibda126c7db6b7e1fef9323d4b2aace37ca13ebc1
* Added modemReducedFeatureSet1 flag to HalDeviceCapabilities
* Applied flag to secondary link bandwidth getters in carrier bandwidth
Test: cts
Bug: 173806995
Change-Id: Icfca599607e02a6c3e258c11dc9eb7701b7afd3f
Revert "Add cuttilefish implementation for emergencyDial_1_6"
Revert submission 13164522-emergencyDial_1_6
Reason for revert: Potential culprit of b/176519828
Reverted Changes:
I3680b8d42:Add cuttilefish implementation for emergencyDial_1...
I94319ab34:Add emergencyDial_1_6 in the HAL to modify the mul...
Change-Id: I17e59676b6467b8b51dcb839497883a2c89ee50d
Update documentation for secondary bandwidth to indicate that
some modems do not support this feature
Test: build
Bug: 162373679
Change-Id: I03d4079e03817fe7c7b52eb18058c49e54302d6b
* Added support for S-NSSAI within HAL
* Created struct SliceInfo that represents a S-NSSAI as defined
in 3GPP TS 24.501.
* Added slice info to setupDataCall and SetupDataCallResult
Bug: 169960538
Test: made ims phone call
Change-Id: I8d2c55bece07c599cb7d1ac0d16ad85c0acdeae5
Update Hal IRadio, IRadioResponse, and IRadioIndiction
for the updated SignalSterength.
Move radio_responce#getSignalStrengthResponse_1_4 to the right block
Bug: 174775680
Test: atest VtsHalRadioV1_6TargetTest
Change-Id: If61ff4f72b44ac5482acd1823153633d5f9bfce9
As requested by Android Council review of API.
Test: vts
Change-Id: I1f633856c31623ef95f459b2195743f53b5d85fc
Merged-In: I1f633856c31623ef95f459b2195743f53b5d85fc
Define data structures for VoNR network feature support information,
and update RegStateResult to allow the information to be reported
through the response of getVoiceRegistrationStateResponse and
getDataRegistrationStateResponse.
Bug: 167991878
Test: make, VTS
Change-Id: I098bd1b6c86cd38be6fbc086b8ebd7b1bb2408fa
The pdu session id needs to be passed to setup data call on handover
(clean cherry-pick)
Test: Tested that handover still worked with logs. IWlan -> Cell + Cell -> IWlan
Bug: 161572859
Merged-In: I0e11c8997674cdaad4bb82491d818ca85ee197d1
Change-Id: I0e11c8997674cdaad4bb82491d818ca85ee197d1
The retry timer suggested by the network will persist
accross network requests. Also changed the retry timer
to a 64-bit value to be consistent with types used in
Android time APIs.
(clean cherry-pick)
Test: FrameworksTelephonytests
Fix: 159672248
Merged-In: I763afdf34378512c60c0838830cb84875b1c66f0
Change-Id: I763afdf34378512c60c0838830cb84875b1c66f0
* Asks the device what set of capabilities are supported on the device
with respect to the Radio Hal
* The capabilities struct is left empty and will be filled
in once the first set of radio hal capabilities are nailed down later
in Android S
Test: Added cts, ran cts, and std tests
Bug: 163085807
Change-Id: I867f26bc649005e89ebf7a0b74f6fbeb2f44ac93
The pdu session id needs to be passed to setup data call on handover
Test: Tested that handover still worked with logs. IWlan -> Cell + Cell -> IWlan
Bug: 161572859
Change-Id: I0e11c8997674cdaad4bb82491d818ca85ee197d1
Provide intrface to get secondary link capacity estimation
Bug: 162373679
Test: build
merged-In: I371f1f8ad820f8b20c972c3310ebe82b3790a577
Change-Id: I371f1f8ad820f8b20c972c3310ebe82b3790a577
There are currently two methods that cover the network family types:
setPreferredNetworkType and setPreferredNetworkTypeBitmap. They both
serve a similar purpose and have been previously interpreted as a
suggestion to the modem on the type of networks requested by the OS.
This change introduces a new method (setAllowedNetworkTypeBitmap) which
will coexist with these methods. This new method must be interpreted as
a strict set of Radio Access Technology (RAT) that should be accepted by
the modem.
For instance, one may first use setAllowedNetworkTypeBitmap to exclude
2G technology from the list of usable RAT. Then, they may use
setPreferredNetworkType to describe their preference for 4G.
Test: mm
Bug: 171791177
Change-Id: I7f5fdf9bf5a80c47e9ad838b740b2d6e40ffea60
Merged-In: I7f5fdf9bf5a80c47e9ad838b740b2d6e40ffea60
There are currently two methods that cover the network family types:
setPreferredNetworkType and setPreferredNetworkTypeBitmap. They both
serve a similar purpose and have been previously interpreted as a
suggestion to the modem on the type of networks requested by the OS.
This change introduces a new method (setAllowedNetworkTypeBitmap) which
will coexist with these methods. This new method must be interpreted as
a strict set of Radio Access Technology (RAT) that should be accepted by
the modem.
For instance, one may first use setAllowedNetworkTypeBitmap to exclude
2G technology from the list of usable RAT. Then, they may use
setPreferredNetworkType to describe their preference for 4G.
Test: mm
Bug: 171791177
Change-Id: I7f5fdf9bf5a80c47e9ad838b740b2d6e40ffea60
* Add in HAL support for AOSP allocating pdu session ids from modem
* Add in HAL support that notifies modem when a handover has begun and was cannceled
(clean cherry pick)
Test: N/A
Bug: 161572859
Change-Id: I2771b4773381ba68f482a80e743bdbb05a8e59d1
Merged-In: I2771b4773381ba68f482a80e743bdbb05a8e59d1
* Add in HAL support for AOSP allocating pdu session ids from modem
* Add in HAL support that notifies modem when a handover has begun and was cannceled
Test: N/A
Bug: 161572859
Change-Id: I2771b4773381ba68f482a80e743bdbb05a8e59d1
The retry timer suggested by the network will persist
accross network requests. Also changed the retry timer
to a 64-bit value to be consistent with types used in
Android time APIs.
Test: FrameworksTelephonytests
Fix: 159672248
Change-Id: I763afdf34378512c60c0838830cb84875b1c66f0
Support RadioError:RF_HARDWARE_ISSUE and RadioError:NO_RF_CALIBRATION_INFO for
setRadioPowerResponse_1_6().
Bug: 170938075
Test: build. VTS on Cuttlefish.
Change-Id: Iaf582c31f439810db34693c61e58ff1f4dfd19fd
On a handover request failure, the modem can now determine
whether or not to fallback. There is also the option to revert
to the legacy logic. Following the legacy logic is the default
behavior.
Test: FrameworkTelephonyTests
Bug: 161572465
Change-Id: Iad778e83ffc264ee25f57f54ff58532d6a8c5cbf
Merged-In: Iad778e83ffc264ee25f57f54ff58532d6a8c5cbf
On a handover request failure, the modem can now determine
whether or not to fallback. There is also the option to revert
to the legacy logic. Following the legacy logic is the default
behavior.
Test: FrameworkTelephonyTests
Bug: 161572465
Change-Id: Iad778e83ffc264ee25f57f54ff58532d6a8c5cbf
Add indication APIs to expose Quality Of Service (QOS) information
from LTE and NR default as well as dedicated bearers. The QOS is
added to the existing SetupDataCallResult structure so that the
baseband can notify whenever there is a change in QoS on a PDN.
The baseband vendor shall notify the {@link Qos} of the default
bearer at the time of setup data call success. The dedicated bearer
QOS shall be notified whenever network establishes or modfies a
dedicated bearer using dataCallListChanged() API. When network tears
down the dedicated bearer, vendor shall update the same with a empty
{@link QosSession} for the particular data call.
Bug: 158315614
Test: make, VTS
Change-Id: I58cd3fd2cf354de8916aeed1292cd7071e79e184
HIDL libs are not necessarily part of VNDK now. Because some are
used by VNDK libs, they are still VNDK. But rest are now just
vendor-available.
.hidl_for_test files are also removed because they are used to exclude
test-purpose hidl libs from VNDK libs.
Instead, .hidl_for_system_ext files are added to tests/lazy to
distinguish them from others which are installed /system.
Bug: 143933769
Test: update-makefiles.sh && m com.android.vndk.current
Merged-In: Ia81312dda340b6b5cbdd7a3c21e1d323bda39a4a
Change-Id: Ia81312dda340b6b5cbdd7a3c21e1d323bda39a4a
(cherry picked from commit b0907a6bb8)
HIDL libs are not necessarily part of VNDK now. Because some are
used by VNDK libs, they are still VNDK. But rest are now just
vendor-available.
.hidl_for_test files are also removed because they are used to exclude
test-purpose hidl libs from VNDK libs.
Instead, .hidl_for_system_ext files are added to tests/lazy to
distinguish them from others which are installed /system.
Bug: 143933769
Test: update-makefiles.sh && m com.android.vndk.current
Merged-In: Ia81312dda340b6b5cbdd7a3c21e1d323bda39a4a
Change-Id: Ia81312dda340b6b5cbdd7a3c21e1d323bda39a4a
(cherry picked from commit b0907a6bb8)
Note that this just increases the gtest time to match our
highest wait times. Each test still has wait times fitted for the
expected length of that test.
Bug: 159289514
Test: atest VtsHalRadioV1_0TargetTest
Change-Id: I0825305258bae20ea6e13e9b9a65ce30b7153611
Merged-In: I0825305258bae20ea6e13e9b9a65ce30b7153611
Note that this just increases the gtest time to match our
highest wait times. Each test still has wait times fitted for the
expected length of that test.
Bug: 159289514
Test: atest VtsHalRadioV1_0TargetTest
Change-Id: I0825305258bae20ea6e13e9b9a65ce30b7153611
Allow devices launching with IRadio 1.5 this year to
not support BarringInfo.
Bug: 159582898
Test: atest VtsHalRadioV1_5TargetTest -- -t getBarringInfo
Change-Id: I05b749fa3cfb3648148fd2666d7eb6f43f3c45d2
Sendcdmasexpectmoreresponse to the request sendcdmasexpectmore
did not accept the return parameter responseinfo, which caused
the VTS system to wait for a response until it exceeded 60 seconds,
and the VTS determined No test results.
so we can add parameters to receive the parameters of
sendcdmasexpectmoreresponse,and then make subsequent judgment.
Bug: 158542706
Test: run vts -m VtsHalRadioV1_5TargetTest
Change-Id: I1d6214f58850d707520b80634cb93d0e0cc712bb
Merged-In: I1d6214f58850d707520b80634cb93d0e0cc712bb
VtsHalRadioV1_5TargetTest.PerInstance/RadioHidlTest_v1_5#
sendCdmaSmsExpectMore/0_slot1
Sendcdmasexpectmoreresponse to the request sendcdmasexpectmore
did not accept the return parameter responseinfo, which caused
the VTS system to wait for a response until it exceeded 60 seconds,
and the VTS determined No test results.
so we can add parameters to receive the parameters of
sendcdmasexpectmoreresponse,and then make subsequent judgment.
Bug: 158542706
Test: run vts -m VtsHalRadioV1_5TargetTest
Change-Id: I1d6214f58850d707520b80634cb93d0e0cc712bb
The test doesn't need framework. It seems that the test can be flaky
when framework was stop/started earlier.
Bug: 154445273
Test: atest -a VtsHalBluetoothV1_0TargetTest \
VtsHalSapV1_0TargetTest \
VtsHalAudioV4_0TargetTest
Change-Id: I60f62923cfb826c5e33e9885ea08efdbe4c8f57e
These tests assumed that they were rooted before running, and due to
a combination of b/152655658 and b/154638140, these appeared to work
when a device already happened to be rooted and the test failures showed
up as problems with the test rather than as problems with the target
preparer.
This is the same workaround being used elsewhere.
Fixes: 154445273 # specifically about VtsHalSapV1_0TargetTest
Test: atest VtsHalSapV1_0TargetTest # passes 100%
The following tests, I confirm MultiSimTargetPreparer works, although my
test device has no SIM so I cannot get fully useful results.
Test: atest VtsHalRadioV1_0TargetTest # slot2 cases can now pass
Test: atest VtsHalRadioV1_1TargetTest # slot2 cases can now pass
Test: atest VtsHalRadioV1_2TargetTest # slot2 cases can now pass
Test: atest VtsHalRadioV1_3TargetTest # fully passes
Test: atest VtsHalRadioV1_4TargetTest # fully passes
Change-Id: Id62cb2e1b7a95552b560ab1d4ff2f63c0a7569a3
Bug: 151896491
Test: local build
Exempt-From-Owner-Approval: This CL update suite name vts-core to vts as
the suite name is updated. This CL won't change test logic or behavior.
Change-Id: I562b4dc50765e953800a814a8fd84a01c1b9352b
Merged-In: I562b4dc50765e953800a814a8fd84a01c1b9352b
Bug: 151896491
Test: local build
Exempt-From-Owner-Approval: This CL update suite name vts-core to vts as
the suite name is updated. This CL won't change test logic or behavior.
Change-Id: I562b4dc50765e953800a814a8fd84a01c1b9352b
Merged-In: I562b4dc50765e953800a814a8fd84a01c1b9352b
Due to modem issue, enableModem only works in dual-SIM mode.
And we only use that in dual-SIM mode. So skipping testing in
in single SIM mode.
Bug: 152557383
Test: vts
Change-Id: I41f200317eaf9be0613f92e5bff9a3ee8a98ef15
Merged-In: I41f200317eaf9be0613f92e5bff9a3ee8a98ef15
Due to modem issue, enableModem only works in dual-SIM mode.
And we only use that in dual-SIM mode. So skipping testing in
in single SIM mode.
Bug: 152557383
Test: vts
Change-Id: I41f200317eaf9be0613f92e5bff9a3ee8a98ef15
This HAL API was not enforced in IRadio 1.3. The vts was disabled.
Now we have new API setSystemSelectionChannels_1_5 in IRadio 1.5 and
corresponding vts test. We no longer need this old disabled vts.
Bug: 146062695
Test: vts
Change-Id: Ie81cb38c4848118318b9df5eef799469ff362f16
Merged-In: Ie81cb38c4848118318b9df5eef799469ff362f16
Bug: 148102466
Test: compilation for both cuttlefish and sargo
Merged-In: I8a8e734011909b038c0d735c2bfde7ea773b71e6
Change-Id: I8a8e734011909b038c0d735c2bfde7ea773b71e6
(cherry picked from commit 24c3416b4f)
Add a VTS that verifies polled BarringInfo
is sanely constructed.
Bug: 148646258
Test: make VtsHalRadioV1_5TargetTest
Merged-In: Idf8d110efe8fa2289fbcc8ed7f0959f0bd51999e
Change-Id: Idf8d110efe8fa2289fbcc8ed7f0959f0bd51999e
(cherry picked from commit 72083ba9cd)
Add CellIdentity to getBarringInfoResponse to make
the req/resp method match the existing indication.
The CellIdentity is used to prevent races where
barring is attributed to the wrong cell based on the
timing of separate polled or unsolicited inputs to
the framework.
Because the CellIdentity is already in IRadioIndication
the information to provide CID with BarringInfo is already
present and available. This just makes the unsol and the
polled APIs match.
Matching indication is IRadioIndication@1.5::barringInfoChanged
Bug: 148992393
Test: make && VtsHalRadioV1_5TargetTest
Merged-In: I74e6ab9ca9e0dd49846af774fd73773ff3737df7
Change-Id: I74e6ab9ca9e0dd49846af774fd73773ff3737df7
(cherry picked from commit 6894f89fd8)
There were some questions on how the new IRadio 1.5 setRadioPower
command should be implemented based on vendor feedback. This CL
clarifies this behavior.
Test: manual
Bug: 143683647
Change-Id: If08741f0ea156a5c2656a47e46f7e1f98bf54ec4
Merged-In: If08741f0ea156a5c2656a47e46f7e1f98bf54ec4
- IRadio.nvResetConfig:
IRadio.nvResetConfig with ResetNvType ERASE cause radio restart.
The subsuquent test cases fail with RADIO_NOT_AVAILABLE.
Fix to use ResetNvType FACTORY_RESET which does not restart the radio.
Test: run vts -m VtsHalRadioV1_0Target
Bug: 147831226
Change-Id: I45e5cbcf9144c3ace987ac8e047e40fbee403734
There were some questions on how the new IRadio 1.5 setRadioPower
command should be implemented based on vendor feedback. This CL
clarifies this behavior.
Test: manual
Bug: 143683674
Bug: 147496715
Merged-In: If08741f0ea156a5c2656a47e46f7e1f98bf54ec4
Change-Id: If08741f0ea156a5c2656a47e46f7e1f98bf54ec4
(cherry picked from commit 0eac27ccf3)
This reverts commit b071f8ae53.
Reason for revert: Change will not be supported by vendor, so HAL for RadioConfig is no longer necessary.
Change-Id: I33bf652c6aa2f8516ee6ec1c462a1a575d2a5d27
Merged-In: I2eb83fd2356134ef45a782d99174fdd65f8c5a13
This reverts commit e1d1b0b92c.
Reason for revert: Change not supported by vendor
Change-Id: I5e2cdf0797124e0a1d272ca4b0525d2425954c3f
Merged-In: I9b268f41614149b5cd55caf3d730b25bb1f885e9
This reverts commit f0cfc3ef60.
Reason for revert: Change not supported by vendor
Change-Id: Ie148208a890834b0cd05b0ae4d6190e1a0b5dede
Merged-In: Ief5c5325f51a9bb3921bd2eb6e0ea8c9e7111581
Add to IRadio, IRadioResponse, and VTS
Test: make cf_x86_phone-userdebug && mm
Bug: 149112073
Change-Id: I330d5be6bf531c93439f8f1d55718f71ec46c1c3
Merged-In: I330d5be6bf531c93439f8f1d55718f71ec46c1c3
This reverts commit 83e3ca82e6.
Reason for revert: Change will not be supported by modem, so HAL for RadioConfig is no longer necessary.
Change-Id: I2eb83fd2356134ef45a782d99174fdd65f8c5a13
Add a VTS that verifies polled BarringInfo
is sanely constructed.
Bug: 148646258
Test: make VtsHalRadioV1_5TargetTest
Change-Id: Idf8d110efe8fa2289fbcc8ed7f0959f0bd51999e
Add CellIdentity to getBarringInfoResponse to make
the req/resp method match the existing indication.
The CellIdentity is used to prevent races where
barring is attributed to the wrong cell based on the
timing of separate polled or unsolicited inputs to
the framework.
Because the CellIdentity is already in IRadioIndication
the information to provide CID with BarringInfo is already
present and available. This just makes the unsol and the
polled APIs match.
Matching indication is IRadioIndication@1.5::barringInfoChanged
Bug: 148992393
Test: make && VtsHalRadioV1_5TargetTest
Change-Id: I74e6ab9ca9e0dd49846af774fd73773ff3737df7
Removed unused import statements.
Consistent between internal and AOSP.
More accurate names for ModemFeatures.
Test: make
Change-Id: Icbfe35d472ab3f7fd6cd50b4888e3c478dd29fd2
Merged-In: Icbfe35d472ab3f7fd6cd50b4888e3c478dd29fd2
This HAL API was not enforced in IRadio 1.3. The vts was disabled.
Now we have new API setSystemSelectionChannels_1_5 in IRadio 1.5 and
corresponding vts test. We no longer need this old disabled vts.
Bug: 146062695
Test: vts
Change-Id: Ie81cb38c4848118318b9df5eef799469ff362f16
Removed unused import statements.
Consistent between internal and AOSP.
More accurate names for ModemFeatures.
Test: make
Change-Id: Icbfe35d472ab3f7fd6cd50b4888e3c478dd29fd2
1. Docomo, Softbank, KDDI, and another Japan Operator request this.
- During operation, the mobile device confirms the presence of the ICC and performs ICC outlier detection. If ICC disconnection is detected during operation, turn off the power within 5 seconds after detection, and perform power reset operation.
2. "setSimCardPower power down"
- After "setSimCardPower power down", SIM set power down. and ME is wating for "remove sim card" event, but phsically detect pin is still connected, so "remove" event never be sent, and ME can't reboot.
3. Japan model can not "setSimCardPower power up"
After "setSimCardPower power down", Japan model prepare for rebooting.
so so VTS requests "setSimCardPower power up", they can't do this.
Signed-off-by: Jicheol Shin <jicheol.shin@lge.com>
Test: VTS
Test: runc vts -m VtsHalRadioV1_1Target -t VtsHalRadioV1_1Target#RadioHidlTest_v1_1.setSimCardPower_1_1(slot1)_32bit
Test: runc vts -m VtsHalRadioV1_1Target -t VtsHalRadioV1_1Target#RadioHidlTest_v1_1.setSimCardPower_1_1(slot1)_64bit
Bug ID : 147969063
Change-Id: I524a16d04a7783f605913fd3ead15d3c1fbbc78b
Support updated API for setNetworkSelectionModeManual
Bug: 68116277
Test: atest FrameworksTelephonyTests
Change-Id: I7076da1734d2d020adef568188cb4f4b4914f379
Merged-In: I7076da1734d2d020adef568188cb4f4b4914f379
To match the API in LinkAddress.
Test: Telephony sanity tests
Bug: 135717900
Change-Id: I06559044c8015bc577d9e4ca489a4924f69093b2
Merged-In: I06559044c8015bc577d9e4ca489a4924f69093b2
One cell could have multiple bands assigned.
One frequency could be shared by multiple bands
because they have overlapping.
Test: Telephony sanity tests.
Bug: 131061889
Change-Id: I6018b9df8b8bd0745c3736df764f4569bea28baa
Merged-In: I6018b9df8b8bd0745c3736df764f4569bea28baa
Change mtu->mtuV4 and add mtuV6 for DataProfileInfo and
SetupDataCallResult
Test: mm and build
Bug: 146668814
Change-Id: I33320281730fdb91d2b07d11cd24a95d0834c9dd
Merged-In: I33320281730fdb91d2b07d11cd24a95d0834c9dd
Non-functional changes:
-Clarify that the MCC+MNC in the CellIdentity should be used to
report the Primary PLMN only; (this PLMN is globally unique, and
can be used to construct a CGI/ECGI whereas other PLMN-IDs cannot).
-Add clarification for the reporting of multi-PLMN 5G networks.
Functional changes:
-Add a list of PLMNs for MOCN Networks. This allows cells that are
shared by multiple operators to be properly reported.
-Add support for Closed Subscriber Group reporting to allow
identification of small-cell deployments.
Bug: 135921133
Test: make VtsHalRadioV1_5Target
&& make aosp_cf_x86_64_phone-userdebug
Change-Id: Ibb0682de8ae9c4421e79086773c977a4e76ac4f1
Merged-In: Ibb0682de8ae9c4421e79086773c977a4e76ac4f1
-Define RegistrationFailCause as an enum
-Combine voice and data reg state into a single struct
-Define a safe-union for AN-specific registration info
Bug: 73629308
Test: make && make VtsHalRadioV1_5TargetTest
&& make cf_x86_64_phone-userdebug
Change-Id: I43df3cffd4c55f2c5df8eaf0235772e5930dced5
Merged-In: I43df3cffd4c55f2c5df8eaf0235772e5930dced5
Change PhoneCapability structure to contain static capabilities for:
* the entire device
* each modem/radio
* each SIM slot
Created SimSlotCapability and SlotType to hold information about
device SIM slot capabilities (separate from SimSlotStatus).
Created ModemFeatures to express modem capabilities as a bitfield
of concurrently supportable modem features.
PhoneCapability has fields for UE categories, bands, access networks,
and modem switching linger time. It also contains a lists of logical
modem UUIDs, SIM slot capabilities, and all possible concurrently
supportable modem features.
TelephonyManager will have an API that returns
* the PhoneCapability for the device
* active set of ModemFeatures
Apps with CARRIER_PRIVILEGE can use these APIs to access all
capabilities of a device (eg. 5G capable, DSDS capable, etc.) and
use them to make decisions based on what the device can support.
Test: atest FrameworksTelephonyTests
Bug: 143238237
Bug: 143238191
Change-Id: I424ef176086d2308a4bf53b2c79407eabafb3178
Merged-In: I424ef176086d2308a4bf53b2c79407eabafb3178
Add new API in @1.5 IRadio and IRadioResponse interfaces
to send MO CDMA SMS with expectMore option
Bug: 72613248
Change-Id: I9aec3a58b531c17ec55db290d0e82bc7d34afa84
Merged-In: I9aec3a58b531c17ec55db290d0e82bc7d34afa84
Add new API in @1.5 IRadio and IRadioResponse interfaces
to send MO CDMA SMS with expectMore option
Test: make
Bug: 72613248
Change-Id: I9aec3a58b531c17ec55db290d0e82bc7d34afa84
