Add API that indicates if the usage of multiple SIMs at the same time is
allowed or restricted in order to support requirements from carriers for
dual SIM devices
Bug: 123537730
Test: Verified with test application.
Change-Id: I5e3e5ff41927e43ead4a30988630cf9125d5a048
These were system API but we should expose them for apps with carrier
privileges.
Test: manual
Bug: 122974656
Change-Id: Ie60e4c580dfa9dd0d7d6fb6b94226661d0620dad
Add EMERGENCY_NUMBER_SOURCE_TEST_MODE
This also does not allow to send the service categories from database when
dialing.
Bug: 122840137
Test: Manual; Treehugger
Merged-in: I4ea3539e3b814b71e03e956d4a857ec20141fa8c
Change-Id: I4ea3539e3b814b71e03e956d4a857ec20141fa8c
(cherry picked from commit cb4bd3a30f)
Data profile should use the public defined types
instead of the internal defined data types.
1. Using integer instead of string for protocol type.
2. Using TelephonyManager.NetworkTypeBitMask instead of
the internal ServiceState.RIL_RADIO_TECHNOLOGY_XXX
in data profile.
Test: Telephony sanity tests
Bug: 73659459
Merged-In: I04b910f8e349e8b7819ff058bf37ad06c3fd9adc
Change-Id: I04b910f8e349e8b7819ff058bf37ad06c3fd9adc
(cherry picked from commit af6b47af54)
The ImsService can crash unexpectantly or not be available
for certain device configurations. Define a checked exception
ImsException to handle these cases instead of using
RuntimeExceptions.
Bug: 122480210
Test: atest FrameworksTelephonyTests
Change-Id: Ie3221d56a235c0e037d71e197f4972df31faa09b
When user selects a eSIM subscription, Settings app informs Telephony.
Telephony needs to take actions such as writting it into global
settings, switch profiles and notify registrants, for example
AlternativeNetworkAccessService.
Bug: 120945564
Test: unittest
Change-Id: I846d9444aac368d183e06744c9eb8aa0c08dfe6a
Adds two new carrier config options for UT:
1) Whether or not the carrier supports UT over IMS
2) Whether or not the carrier requires a carrier app to
provision the device to use UT over IMS.
Also adds new ITelephony AIDL for querying/setting
provisioning for MMTEL currently used for UT over
IMS only.
Bug: 119896853
Test: atest FrameworksTelephonyTests
Change-Id: I51260afed85b99cf6ed89374daf417c3a25c7fb9
Data profile should use the public defined types
instead of the internal defined data types.
1. Using integer instead of string for protocol type.
2. Using TelephonyManager.NetworkTypeBitMask instead of
the internal ServiceState.RIL_RADIO_TECHNOLOGY_XXX
in data profile.
Test: Telephony sanity tests
Bug: 73659459
Change-Id: I04b910f8e349e8b7819ff058bf37ad06c3fd9adc
There are a few non-OMADM specific configs that need to
be exposed in ProvisioningManager to handle cases
like turning on WFC "non-persistently" for provisioning
on certain networks. These should be well defined for
compatibility as well as ease of use.
Test: atest FrameworksTelephonyTests, turn on WFC
Change-Id: I79c9492664d4bf41b10639c0596d4f2697cd46f2
Design doc http://shortn/_GG690j15js
1. Modified SmsManager to send message thru Bluetooth if the subscription
is for a Remote-SIM.
2. Added new column 'subscriptionType' to SubscriptionInfo.
3. SubscriptionManager:
a. Added new constants for Local SIM and Remote SIM
b. Added hidden APIs to add/remove Remote SIM subscriptions
Bug: 112321331
Test: tested manually and w/ unittests
Change-Id: Ib15553a806691a258fc00f7aaf812b8a9d49c2e9
1. expose to system API
2. refactor to support passing subId instead of read from defaultSIM and
previously inserted SIM.
Bug: 122620985
Test: cts
Merged-In: I8f78ba00abf0ef74bd2b2147755596edaee156cf
Change-Id: I8f78ba00abf0ef74bd2b2147755596edaee156cf
1. expose to system API
2. refactor to support passing subId instead of read from defaultSIM and
previously inserted SIM.
Bug: 122620985
Test: cts
Change-Id: I8f78ba00abf0ef74bd2b2147755596edaee156cf
IRadioConfig 1.1 getPhoneCapability and setPreferredDataModem
are defined. Here we hook the calls into RadioConfig.
Bug: 121354686
Test: sanity
Change-Id: I2a198d446962510ef9a3019d3aa30b40e796ebe0
Merged-In: I2a198d446962510ef9a3019d3aa30b40e796ebe0
