For packages:
android.telephony
android.telephony.cdma
android.telephony.data
android.telephony.euicc
android.telephony.gsm
android.telephony.ims
android.telephony.ims.aidl
android.telephony.ims.compat
android.telephony.ims.compat.feature
android.telephony.ims.compat.stub
android.telephony.ims.feature
android.telephony.ims.stub
android.telephony.mbms
android.telephony.mbms.vendor
This is an automatically generated CL. See go/UnsupportedAppUsage
for more details.
Exempted-From-Owner-Approval: Mechanical changes to the codebase
which have been approved by Android API council and announced on
android-eng@
Bug: 110868826
Test: m
Change-Id: I02d900d6d0ec9a6b2172a71911fec61d04e4d235
Merged-In: I22547ac0ed384d74d61cfd51d20c140e392a597f
Added a new carrier config that can trigger modem restart when
receiving specific setup data fail cause code.
Test: Telephony sanity tests
Bug: 111774203
Change-Id: I39d648117f778a4548a3d50e624dbd841956c6cc
Added the qualified networks service, which is a base
class for vendor's qualified network service to extend.
The service is to update frameworks the available
networks for data setup for each APN type.
Test: Manual
Bug: 73659459
Change-Id: I7238aeac8e48be2a17245de77239b242703bcb7e
Add OO conversion from CellIdentity to CellLocation
in the respective CellIdentity classes.
Bug: 67711865
Test: manual
Change-Id: I4e2dab7de5e5c5fa3bb42a22b14934874560c9fc
In P the PHONE_STATE broadcast behavior changed due to new permission
requirements. Updating the API docs for this broadcast to make it more
clear to developers how the broadcast will work given different permission
scenarios.
Also, made a minor change to how the "EXTRA_INCOMING_NUMBER" is populated
on the phone state broadcast. Originally we opted to remove
EXTRA_INCOMING_NUMBER when the number is empty. Developer feedback reveals
it is difficult to know for an unknown caller (where numer is empty)
whether the broadcast they're receiving is the one associated with the
broadcast for receivers with READ_CALL_LOG, or the one for receivers
without it. This minor change eliminates the need to count broadcasts and
instead allows the developer to just focus on whether the extra is present
or not.
Test: make docs and verify the javadoc appears as expected.
Test: Used test app to confirm functionality.
Bug: 110190165
Merged-In: I55e3519fcbad4dcb7da041d0194bf4e1c7d38949
Change-Id: I35967d53274b99d66b63f4ff5acb60a689745f9d
Put common codes of set APIs in Subscription into an unified method.
So that later it's easier to add APIs.
Bug: 112167869
Test: unittest
Change-Id: Idd2312c98fc178f078c75937ba2d8c2e414f3c3a
Merged-In: Idd2312c98fc178f078c75937ba2d8c2e414f3c3a
For packages:
android.providers.settings
android.provider
This is an automatically generated CL. See go/UnsupportedAppUsage
for more details.
Exempted-From-Owner-Approval: Mechanical changes to the codebase
which have been approved by Android API council and announced on
android-eng@
Bug: 110868826
Test: m
Change-Id: I993adf36dc31a5e224e88217c9e8dc140b6ba880
Merged-In: I3865ac184fcb6f52c6bfab9729611b065b27722e
TelephonyManager now calls TelecomManager#isTtySupported directly, instead of calling from its implementation PhoneInterfaceManager.
Bug: 79502396
Test: Manual
Change-Id: I686b93d31850103f1cfb7003fe0506d08a424f27
CellIdentity and CellInfo had redundant enums to
designate the structure type. This CL merges the
better-formatted enums from CellIdentity to
CellInfo, removing the set from CellIdentity.
For cases where the structure type must be determined
at runtime based on a CellInfo record, (where
polymorphic behavior isn't/shouldn't be supported),
this provides a consistent mechanism for determining
the type without using RTTI.
In addition, this CL fixes two other minor issues:
1) The constructor for CellInfoWcdma() provided the
wrong parcel type to the parent class.
2) The TYPE_TDSCDMA had a typo in CellInfo and was
written as TYPE_TDCDMA.
Bug: 112003199
Bug: 67711865
Test: runtest frameworks-telephony
Change-Id: I5ca3c2de1433dfcef264e1273a658d1a0fe864b6
For regulatory requirements, prevent certain sensitive numbers from
being logged in the call log. The numbers can either be specified in the
carrier config or in the mcc config for the device.
Bug: 111470439
Test: unit, manual
Change-Id: Icc4db12def802c2ce5485422a0ec199e3e7452fa
Merged-In: Icc4db12def802c2ce5485422a0ec199e3e7452fa
As part of removing neighboring cell info this
CL adds support for constructing a NeighboringCellInfo
object from a CellInfo object.
Bug: 62490173
Test: tested manually using SL4A with both O-MR1 and current
target SDKs
Change-Id: I278487e506b07ab97589da85f69f1188c73b6eb9
When we fixed proper handling of location permisison gating
sensitive telephony calls we stopped throwing a security
exception when the permission is not held by the caller.
While this is not a security issue there is no reason to
change this behavior which is checked by CTS. This CL starts
throwing a security exception if the permission is not held.
Test: atest android.permission.cts.NoLocationPermissionTest
bug: 74074103
Merged-In: Ic891d62b408c692f84a345f24503f7f25d583e35
Change-Id: Ic891d62b408c692f84a345f24503f7f25d583e35
(cherry picked from commit 33b1509375)
In CarrierConfigManager, add pass context in constructor, so that
when calling CarrierConfigLoader#getConfigForSubId, it can pass
callingPackage.
Bug: 73136824
Test: regression
Change-Id: I4bbff4ea30e2d5473c14d24d6833bf3ca3c595ec
Merged-In: I4bbff4ea30e2d5473c14d24d6833bf3ca3c595ec
1. Pass parameter priority, expectMore and validityPeriod
to API sendMultipartTextMessage.
2. Modify validity check algrithm for parameter priority and
validityPeriod, so that avoids the exception for invalid inputs.
Bug: 112013111
Change-Id: I7a90db6e427b3daf6589e6a2b6dad2c4b3458832
