Bug: 149749602
Test: tested locally both the non-regression (no package names) and the new behaviour (package names) with carrier-provided test apps
Change-Id: I0b807ea1f6ae1f1663dd4362900ab61012a0aa8d
Give carriers the option of including a backup IMSI encryption key as a
carrier config.
Bug: 175801497
Test: manual and atest TelephonyManagerTest
Change-Id: I89d88daf2022672bf27125baae0247b75638bb6e
Merged-In: I89d88daf2022672bf27125baae0247b75638bb6e
Adding in AIDL definition for sending test messages.
Test: Verified operation of the adb shell command which lets test message
be sent.
Bug: 163085177
Change-Id: I7b1c5398e2117077482a02ea4fec6c5d773ca3f5
* Provide App Developers Qos related info associated to
a bound socket through ConnectivityManager
* Qos sessions are generated and filtered by Network Agents
and sent back through the Connectivity Service to the
API consumer.
* The structure of the code within com.android.server
is designed to support different types of filters in the
the future.
* The first type of Qos Attributes are related to EPS
Bearers in order support RCS.
Bug: 155176305
Test: Added to cts/NetworkAgentTest
Test: Added to ConnectivityServiceTest
Change-Id: I145dd065d9deeee449eb9695ab3f6c8556ee7c09
* Introduces a set of capabilities specific for the radio interface
that are determined by the vendor and are then surfaced through
TelephonyManager.
* There are no capabilities yet defined and will come later in S
Test: Added cts, ran cts, and telephony tests
Bug: 163085807
Merged-In: I56713e05cbd5200baa2a3bc79f7f4b0d580ad2a1
Change-Id: Icbbfa056dc5280acdf53c142742f4e4b8d60229e
Explain how to get TelephonyDisplayInfo through TelephonyManager and
PhoneStateListener
Test: build
Fix: 158760752
Change-Id: Ia59efcf68c77d79be1a223f9fd6cbf3ec333478a
Merged-In: Ia59efcf68c77d79be1a223f9fd6cbf3ec333478a
Introduce set/clearSignalStrengthUpdateRequest in TelephonyManager
and ITelephony to support customized signal request from applications.
Bug: 164432835
Test: atest android.telephony.cts.TelephonyManagerTest
Change-Id: I749376872915a91b9514884547140eaf969dba0e
This reverts commit 8ce575b256.
Bug: 176163590
Bug: 148500541
Test: manual smoke test on low-end device and aosp_crosshatch builds.
Reason for revert: Reapplying with a fix for the exceptions.
The exceptions were caused by an undocumented behavior difference in the APIs that just blindly catch runtime exceptions. The cause of the runtime exceptions is that people are calling isDataEnabled() before telephony is running; however, until a "better" fix is available, this API will apply the existing behavior of just catching the runtime exceptions (which is terrible, but it's the plan of record in the code today).
Change-Id: I9fbe7126ee7039dfb0b383f83017458a3525db66
Privileged apps can send the request through TelephonyManager APIs
(in following CL) to monitor signal strength change with interested
RAN/SignalMeausrementType/Thresholds.
Bug: 164432835
Test: atest com.android.internal.telephony.SignalStrengthUpdateRequestTest
Change-Id: Ifba384108b6627e4b808be34e6d828c93e8df995
1. Implement new API:
#getUpLinkFrequency
#getDownLinkFrequency
#getBand
#getChannelNumberUplink
#getChannelNumberDownlink
#getCellBandwidthUplink
2. Have mapping tables for converting frequency range
if getFrequencyRangeGroupFromXXXBand is unknown.
NR-ARFCN, E-UTRA, UTRA and Geran
3. Get the frequency from the band
#getFrequencyRangeGroupFromXXXBand
Bug: 162300897
Test: manual
Change-Id: I44101653659d2b5d593a2b06be6567e0d0ef433f
Merged-In: I44101653659d2b5d593a2b06be6567e0d0ef433f
Expose the fields and methods for application to specify
the customized signal update request.
Bug: 164432835
Test: atest com.android.internal.telephony.SignalThresholdInfoTest
Change-Id: I879efb2e6b4366e96059973cf4264e4192c1cf29
The interface CapabilityExchangeEventListener is exposed.
However the API "onRemoteCapabilityRequest" is hidden and it will cause it cannot be implemented.
Remove this api for now and add it back when the api is ready to exposed.
Bug: 177451691
Test: atest CtsSystemApiSignatureTestCases:android.signature.cts.api.system.SignatureTest#testSignature
Change-Id: I9ac1b8a5654fe16b9ae862d6e65aec9319cb6be5
Introduce RAN to better associate it with thresholds. Later CL
should be able to further simplify APIs which ask for both RAN and
SignalThresholdInfo.
Validate threshold values during constructing.
Deliberately hide all the public fields and methods, so the following
CL will only need to expose designed properties. Make it easy
for API review.
Bug: 164432835
Test: atest com.android.internal.telephony.SignalThresholdInfoTest
Change-Id: Ib0600c43b90ab0231b29f989976cb090f4b37bf8
In cases where the framework/ImsService is not available,
locally extract the transaction ID from the SipMessage in order
to call the appropriate error method back to the caller.
Bug: 173828358
Test: atest FrameworksTelephonyTests:SipMessageParsingUtilsTest
Change-Id: I4ff5ed9ad4492e817c4a687e90d3a294e5514d8b
The RCS publishing device's capabilities APIs are exposed to be the SystemAPI and add the CTS for these APIs.
bug: 174187744
Test: atest -c CtsTelephonyTestCases:android.telephony.ims.cts.ImsServiceTest
Change-Id: I731dbe64614b91efa0002ffccb638b4a10f7c5f4
Per request from a partner, these APIs will not be restricted as they
are in use. This is conceptually a partial revert of change 5d123b6775.
NoNonSdkCheck: b/170729553
Bug: 171933273
Test: Treehugger
Change-Id: Ibb525e9a9e2fc90248b74f45f3cdcb0be7487c3a
