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)
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
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
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
This CL introduces cellular data stall recovery based on
network validation result. It still re-uses the existing
recovery steps but the triggers are based on networkStatus
from NetworkMonitor when the network is bad. Each recovery
step is spaced by a configurable grace period (default 3 mins)
to avoid back to back recovery.
This feature is controlled by the following settings. If this
feature is enabled then the legacy data stall detection based
on TrafficStats will automatically be disabled.
Settings.Global.DATA_STALL_RECOVERY_ON_BAD_NETWORK
1 => Enabled (default)
0 => Disabled
Settings.Global.MIN_DURATION_BETWEEN_RECOVERY_STEPS_IN_MS
3 minutes is default value
Bug: 113916551
Test: atest FrameworksTelephonyTests:com.android.internal.telephony.dataconnection.DcTrackerTest
Change-Id: I738fc7ed08803de1114f7a3d79bf278449e94ea8
Add support for dual SIM to carrier restrictions.
Add support to exclude specific carriers in the list of carrier
restrictions.
Bug: 120313541
Test: Created test application to verify correct functionality.
Test: Added test cases for CarrierRestrictionRules.
Change-Id: I2723fb07db13efdafbc74471a87182e2d2a32718
Merged-In: I2723fb07db13efdafbc74471a87182e2d2a32718
This is the preliminary work for adding handover
type for enable/disable APN.
Test: Telephony sanity tests + unit tests
Bug: 73659459
Merged-In: I51fd01d798cdf8d04fd41455126d017ac97f5f3f
Change-Id: I51fd01d798cdf8d04fd41455126d017ac97f5f3f
(cherry picked from commit ade6d1a66d)
Update sharedPreference to false when exits new device provisioning,
indicating no users modifications on the settings for new devices.
Thus carrier specific default roaming settings can be applied for new devices.
Bug: 122817867
Test: Manual test on VZW SIM in Setupwizard
Merged-in: Ic93b16f9f96ccc98d12f46c79ab1008ae0df8a07
Change-Id: Ic93b16f9f96ccc98d12f46c79ab1008ae0df8a07
onCallAttributesChanged can trigger whenever the PreciseCallState or
network type changes, or when the modem reports call quality changes.
Bug: 122366240
Test: builds
Change-Id: I9b13cbdd85c24c077e1a13df302bf60128c164e9
Make EuiccManager#updateSubscriptionNickname as public API to allow
carrier app to call it.
Only a privileged app of the given subscription can update the
subscription nickname.
Refresh cached subscription list after the nickname is successfully
updated.
Bug: 122597547
Test: test on phone
Change-Id: I63c5ec4366f32735a54adf40b9cc0b47af681736
Merged-In: I63c5ec4366f32735a54adf40b9cc0b47af681736
- RTT Voice information will be passed to the UI via
media profile changed message
- The RTT voice information - SPEECH/SILENCE, will be conveyed
via the ImsStreamMediaProfile.hasRttAudioSpeech
- A connection event will be sent from frameworks to the UI -
EVENT_RTT_AUDIO_INDICATION_CHANGED
- Add listeners, connection event and extras to propagate
media profile changed to the UI
Test: Manual
Bug: 110976450
Change-Id: I34d2dd612915d65f5047986dabece968c78f0abe
CallAttributes changes will not be reported until we have a full modem
and framework implementation. Registering for one right now is a no-op.
Test: builds
Bug: 110107501
Change-Id: I9c246438de407f5553fd90652e481cdc39b8c844
The data connection reasons are implementation details
of telephony and should not be exposed externally. The
data connection fail cause, which is different from
reasons, are still available.
Test: Telephony sanity tests + unit tests
Bug: 73659459
Merged-In: Ia005abf19664e6213118ee932495950af118456d
Change-Id: Ia005abf19664e6213118ee932495950af118456d
(cherry picked from commit 4d1c945000)
Renamed the scanning state to retrying. Removed the
old retrying dead code.
Test: Telephony sanity tests
Bug: 73659459
Merged-In: I54849bafbd0d05206e67636f0717b4b833a5e229
Change-Id: I54849bafbd0d05206e67636f0717b4b833a5e229
(cherry picked from commit 5de4a2d869)
Members modified herein are suspected to be false positives: i.e. things
that were added to the greylist in P, but subsequent data analysis
suggests that they are not, in fact, used after all.
Add a maxTargetSdk=P to these APIs. This is lower-risk that simply
removing these things from the greylist, as none of out data sources are
perfect nor complete.
For APIs that are not supported yet by annotations, move them to
hiddenapi-greylist-max-p.txt instead which has the same effect.
Exempted-From-Owner-Approval: Automatic changes to the codebase
affecting only @UnsupportedAppUsage annotations, themselves added
without requiring owners approval earlier.
Bug: 115609023
Test: m
Change-Id: Ia937d8c41512e7f1b6e7f67b9104c1878b5cc3a0
Merged-In: I020a9c09672ebcae64c5357abc4993e07e744687
1) Add Database source for EmergencyNumber
2) add mergeEmergencyNumber for merging two emergency numbers
3) enable Listener.EmergencyNumber enhancement
4) no need to pass any parameter to PhoneNotifier
5) modify API documentation
6) deprecate PhoneNumberUtils.isEmergencyNumber
7) modify API documentation for security exception and backward
compatibility
9) introduce some utils in EmergencyNumber for merging number purposes
10) add mnc into EmergencyNumber
Bug: 112657134
Test: Treehugger
Change-Id: I0dcd01bdad7d9c37294cd8b87eda54b4ac9d0a0b
Merged-In: I0dcd01bdad7d9c37294cd8b87eda54b4ac9d0a0b
(cherry picked from commit 9f93a12e1f)
