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
Currently we are seeing TEMPORARILY_NOT_METERED occurs on non-5G
devices. This fix adds more checks to prevent incorrect
TEMPORARILY_NOT_METERED being set. Before we root cause the issue,
we only allow this bit when all of the following conditions met.
1. Devices should support 5G.
2. Carriers should support 5G unmetered data.
3. Device should camp on 5G network.
This temporary fix should be removed after we root cause the issue.
Bug: 176119724
Test: Manual
Merged-In: I2b987d24851cdb16d8457b0ec5c546ace5485ed0
Change-Id: I2b987d24851cdb16d8457b0ec5c546ace5485ed0
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
Bug: 175370724
Test: Simulate call end reason from vendor code and check IMS call
end reason is correctly mapped.
Change-Id: Iea0a5115548530350c5a2645cdf5487870943f72
Currently we are seeing TEMPORARILY_NOT_METERED occurs on non-5G
devices. This fix adds more checks to prevent incorrect
TEMPORARILY_NOT_METERED being set. Before we root cause the issue,
we only allow this bit when all of the following conditions met.
1. Devices should support 5G.
2. Carriers should support 5G unmetered data.
3. Device should camp on 5G network.
This temporary fix should be removed after we root cause the issue.
Bug: 176119724
Test: Manual
Merged-In: I2b987d24851cdb16d8457b0ec5c546ace5485ed0
Change-Id: I2b987d24851cdb16d8457b0ec5c546ace5485ed0
Currently we are seeing TEMPORARILY_NOT_METERED occurs on non-5G
devices. This fix adds more checks to prevent incorrect
TEMPORARILY_NOT_METERED being set. Before we root cause the issue,
we only allow this bit when all of the following conditions met.
1. Devices should support 5G.
2. Carriers should support 5G unmetered data.
3. Device should camp on 5G network.
This temporary fix should be removed after we root cause the issue.
Bug: 176119724
Test: Manual
Change-Id: I2b987d24851cdb16d8457b0ec5c546ace5485ed0
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
