In an effort to remove it from telephony-common as that will not be
accessible to other modules, and some of them need mms code like
MmsService, TelephonyProvider, Bluetooth.
Test: basic sanity
Bug: 140763963
Merged-in: I03eda5a5dbd003659a90e2b9f6be9d4c2b767add
Change-Id: I03eda5a5dbd003659a90e2b9f6be9d4c2b767add
(cherry picked from commit fda8bc058c)
1) Introduce a system api intent for notifying OTA emergency number
database installation complete
2) Notify the installation complete in ConfigUpdater
Test: Build
Bug: 136027884
Change-Id: I62777e9e2a4a2cc3b5207c504884762768ad08e0
Merged-In: I62777e9e2a4a2cc3b5207c504884762768ad08e0
(cherry picked from commit 00a3710617)
Restructure registration API to allow for MMTEL and RCS to
both manage registration callbacks as well as provide new
query APIs for registration state and transport type.
Bug: 122098288
Test: atest GtsTelephonyTestCases
Merged-In: Ia568dcd059c2bcef26462e808088901edf6b072f
Change-Id: Ia568dcd059c2bcef26462e808088901edf6b072f
This does not change the API in anyway other than to enforce a
consistent, sorted order for all annotations; sorted by qualified
name of the annotation.
A simple bug in metalava meant that annotations were not sorted on an
API item that had exactly two annotations in the source. Fixing the
bug forced the regeneration of the signature files.
Bug: 143556317
Test: m checkbuild
(cherry picked from commit 7ba7991568)
Change-Id: I27795de6a8c83e419cda8807b8551a13bec1db10
Merged-In: I0a3d967571bb2f796f65c96a9ce9121e3538bad9
Currently, this is with a 1.4 -> aidl shim, but this will be removed
when the 1.4 HAL interface is removed.
Bug: 141828236
Test: the following:
- device w/ aidl vibrator (cuttlefish) - see logs
- device w/o aidl vibrator, HIDL vibrator still used
Change-Id: Ib4d9841bae1e0bff3c4196959a9a20e03a4297eb
Broke up the halCall() API into two components, one that implements the
initial service retrieval and one that implements the retry on
connection loss. This allows the service retrival API to double as test
for supported version with little overhead.
Test: Manually via CLI
Change-Id: I12cf8838e933187d473157c9576d1b13b03913d4
Signed-off-by: Harpreet \"Eli\" Sangha <eliptus@google.com>
(cherry picked from commit e0b7951d63)
Merged-In: I12cf8838e933187d473157c9576d1b13b03913d4
Both of services.net and services.core statically link
netd_aidl_interface. But they use different version.
Since services.core already include service.net, removing
netd_aidl_interface from service.core.
Bug: 143560726
Bug: 139280289
Test: -build, flash, boot
-Off/On tethering
Change-Id: Ifa83880ee7ee88ed67f8b638228ef1b0887e201e
These apis are required for adding UI in the Developer options for
modifying compatibility change overrides.
Bug: 138280620
Test: atest CompatConfigTest
Change-Id: If55aa68f9bdd6bed0765324e972de3683bacb553
Added getSmscAddress() and setSmscAddress() to access SMSC address in
(U)SIM through the SmsManager.
getSmscAddress() requires that the calling app is the default SMS app,
or has READ_PRIVILEGED_PHONE_STATE or the carrier privileges.
setSmscAddress() requires that the calling app is the default SMS app,
or has MODIFY_PHONE_STATE or the carrier privileges.
Test: Manual
Change-Id: Icb21aff450f71b30ef6a1181834014bf7b85b8e1
Signed-off-by: Taesu Lee <taesu82.lee@samsung.com>
1) Adds new system APIs that provide more access to IMS state.
2) Remove dependence on IPackageManager, which is not accessible
in mainline.
Bug: 141457496
Bug: 122098288
Test: atest FrameworksTelephonyTests
Merged-In: I17cbad4642ad3099668a354bb2588f2b55602311
Change-Id: I17cbad4642ad3099668a354bb2588f2b55602311
This CL is to fix a bug that found in
TransitionSelectionTests#testCloseTask_BothWallpaper_SlowStop may flaky
because when TopActivity launched & call finish(), the activity will destroy
too soon before BottomActivity resume & idle.
When TopActivity launched, suppose BottomActivity's nowVisible state should
be false because both activities are fullscreen activity & TopActivity should
cover BottomActivity.
After TopActivity called finish(), normally the activity should wait for
BottomActivity visible and then destroy, and this test is to verify if
TRANSIT_WALLPAPER_INTRA_CLOSE state will coming when opening & closing animation
target with wallpaper theme are animating case.
But the flakiness may happen if device is in low-performance stage, when
TopActivity launched, system calls setClientHidden for BottomActivity's all
windows to update its viewVisibility but can't update in time, and then
the next relayoutWindow comes, mis-detected BottomActivity's Floating child
window as drawn state, so that can't update BottomActivity's nowVisible
state as invisible with onWindowsGone().
So when TopActivity called finish(), TopActivity will soon going to destroy
state since BottomActivity is still in nowVisible state.
The fix is to add isNextNotYetVisible, if the next activity the nowVisible or visible
is not yet true, which means we need to add the current finishing
activity into stopping list and destory until the next activity idle.
Bug: 140088359
Test: atest TransitionSelectionTests
Change-Id: If1907d71135158bafea69881205f351ab666025e
Merged-In: If1907d71135158bafea69881205f351ab666025e
