Add isMobileDataPolicyEnabled and setMobileDataPolicyEnabledStatus in
TelephonyManager. These are intended to replace the mms-always-allowed
and data-during-voice-call setters/getters.
Old methods will be removed in a follow up commit.
Fixes: 169367013
Test: atest TelephonyManagerTest
Change-Id: I6033a84f0a0163e460343ebf603d66078455fe38
Merged-In: I6033a84f0a0163e460343ebf603d66078455fe38
instead of null, so that when a certificate is removed, it is also
removed in SubscriptionInfoUpdater#updateSubscriptionByCarrierConfig
Bug: 162700101
Test: manual
Change-Id: I921007498f42119581f565fcc6625c1275c59df8
Merged-In: I921007498f42119581f565fcc6625c1275c59df8
Add implementation for SipDelegateManager#isSupported as well
as CTS tests.
Bug: 154763999
Test: atest CtsTelephonyTestCases
Merged-In: I7fbd39a8ff17c4e947fdbcca148857684faa3252
Change-Id: I7fbd39a8ff17c4e947fdbcca148857684faa3252
Create base SipTransport implementation and make it available to
listeners.
Expose new SipDelegate creation capability to the framework from the
ImsService.
The next CL will start the integration of the SipDelegateManager
with the framework and SipTransport.
Bug: 154763999
Test: atest FrameworksTelephonyTests TeleServiceTests
Merged-In: I9a51b850f370a865c9d9109f238e8ed2eea4b6f6
Change-Id: I9a51b850f370a865c9d9109f238e8ed2eea4b6f6
Refactor the class RcsContactUceCapability to make it conform to the PIDF format.
Bug: 170785010
Test: atest
Change-Id: Idc2e43c72f1d4ce7afe75a810f3c06f72820d35c
A disambiguation dialog will be shown if default SmsManager is used for
MMS as well.
Bug: 170591590
Test: Manual
Signed-off-by: Taesu Lee <taesu82.lee@samsung.com>
Change-Id: I86bb70261eb7fecf3e8b72f0df8d2338bab4bb57
Expose the MmTelCapabilities#isCapable() API to complete
a chain of APIs exposed for debuggability in Android RVC.
Without this API, there is no (public) way for a caller that
receives a capability callback to determine whether a particular
MMTel feature is enabled for a particular IMS Connection.
Bug: 156107100
Test: make update-api && make offline-sdk-docs && make
Test: cts - ImsServiceTest#testCapabilityStatusCallback()
Merged-In: I0a0d72897112460370e6981ae33cef4da6e3ce4b
Change-Id: I0a0d72897112460370e6981ae33cef4da6e3ce4b
(cherry picked from commit 21157d56a9)
Adds a BinderCacheManager class, which does the following:
1) Manages a cached Binder node and recreates it when the Binder node dies.
2) Allows Runnables to be associated with the cached Binder,
which will be called when the node dies.
3) Associates the Runnable with an Object key, which can be used to
remove the runnable without needing to keep a separate map
of Object->Runnable pairs when the user unregisters a persistent
listener.
Test: atest CtsTelephonyTestCases FrameworksTelephonyTests:BinderCacheManagerTest
Change-Id: I23a97371435b7aca8153a30997b91bd324a781a0
Instead of having a special case for ImsManager#getInstance,
implement it properly.
Test: atest CtsTelephonyTestCases
Merged-In: I2e986fb2a1086043a25b11c71c005481cea74196
Change-Id: I2e986fb2a1086043a25b11c71c005481cea74196
[RESUBMISSION AFTER REVERT aosp/1443078]
Instead of requiring that listeners poll for an ImsFeature binder
when they go down, modify interfaces to notify listeners when a
new instance of a Binder is available.
Test: atest CtsTelephonyTestCases FrameworksTelephonyTests ImsCommonTests
Test: manual E2E tests of IMS functionality (call, SMS, settings...)
Merged-In: I0bb48f82ecf7a1283be8fd441a787dff587d6d61
Change-Id: I0bb48f82ecf7a1283be8fd441a787dff587d6d61
When the device receives an incoming call indication and quickly
receives another call terminated indication (such as the auto
reject case), there is the possiblity that the call terminated indication
happens while onIncomingCall is still being processed. This is due to the
fact that binder oneway calls are only guaranteed to be on the same binder
thread for the same IBinder node. Since these callbacks are happening on
two separate nodes potentially, there are running in two binder threads
at the same time, causing race conditions.
Instead, the onIncomingCall binder call should not be oneway (as it is
required to complete before other indications should occur) and only
return control back to the ImsService thread once the
MmTelFeature#notifyIncomingCall call completes.
Bug: 160213239
Fixes: 169723915
Test: incoming call, auto-rejected incoming call on MSIm
Merged-In: I054e6b00656fc04f48f7f378076e29322daf59ad
Change-Id: I054e6b00656fc04f48f7f378076e29322daf59ad
Revert "Move IMS to a listener type model instead of a poll model"
Revert "Push Binder updates when ImsFeatures change"
Revert submission 1425374-ims_poll
Reason for revert: b/169729036, ANR in phone process
Reverted Changes:
I1d6dd2dfd:Move to a push model of querying ImsFeature Binder...
Ie3982c245:Move IMS to a listener type model instead of a pol...
I8b9ded0f4:Push Binder updates when ImsFeatures change
Ia9f7ae3db:Clean up IMS based interfaces to use a push model ...
Merged-In: I7ef3c07021a79e809d2c8b30ed2422372eae962d
Change-Id: I7ef3c07021a79e809d2c8b30ed2422372eae962d