getCarrierConfigValues() is removed from MmsManager and SMS service
loads Carrier configuration values directly since MmsService could
return null or cached config instead if an app requests the config by
receiving ACTION_CARRIER_CONFIG_CHANGED before the config is loaded
newly in MmsService by ACTION_CARRIER_CONFIG_CHANGED.
Bug: 145768042
Test: manual
Change-Id: Idc21015cab2902bd0f67e2131ea89b04c4fc4f5e
Merged-In: Idc21015cab2902bd0f67e2131ea89b04c4fc4f5e
Signed-off-by: Taesu Lee <taesu82.lee@samsung.com>
Create new APIs in TelephonyManager for DevicePolicyManager to add
override APNs, and use them in DevicePolicyManagerService instead of
directly accessing the APN database.
Bug: 146834818
Test: cts-tradefed run cts --module DevicePolicyManager --test
com.android.cts.devicepolicy.DeviceOwnerTest#testOverrideApn
Test: atest TelephonyManagerTest
Change-Id: I6c6214424169c05fd452db71a8c6593f8473b9d4
Merged-In: I6c6214424169c05fd452db71a8c6593f8473b9d4
- Clean up usages of hidden AppOpsManager APIs in SmsApplication
- Add unit tests for SmsApplication
- Expose RoleManager#getDefaultSmsPackage for use in SmsApplication.
Bug: 146834818
Test: atest SmsApplicationTest
Change-Id: I4ab49d7f6274389e7de7cd7223cab3c433936044
Parcelable creators should be public per API guidelines
Bug: 146834818
Test: atest android.telephony.cts.SignalStrengthTest
Change-Id: Ib15e21c005ea5fecd5886583213af5fdb9f70abb
Current AOSP LTE signal bar has following limitation:
- For Threshold type, "RSRP & RSSNR" or "RSRP only" are selectable,
but "RSRP & RSRQ" is unavailable.
- For threshold value, RSRP is flexible by carrier config,
but RSSNR is hard-coded.
- The signal strength reporting criteria apply to only the RSRP.
This change allows following customizations by new carrier config:
- Threshold type can select "RSRP & RSRQ" too.
- Threshold value of RSRQ and RSSNR can be flexible.
- RSRQ and RSSNR thresholds can set signal strength reporting criteria.
Test: auto - Confirmed that run
FrameworksTelephonyTests#testSignalStrength and it has no problem.
Test: auto - Confirmed that run
FrameworksTelephonyTests#SignalThresholdInfoTest and it has no problem.
Bug: 133400544
Change-Id: I37d0dc5ff41169b0309cfaabaa0f2595894b3749
Merged-In: I37d0dc5ff41169b0309cfaabaa0f2595894b3749
We would make the constructor of PreciseCallState system API, to resolve
the mainline concern from TelephonyRegistry.
Also clean up unused imports.
Test: built
Bug: 146585782
Change-Id: I0bbca065f86fe352a06c63bdd1b25d34e77a9265
Audio offload support was added to AudioTrack in Q,
but only a few encoding were exposed (MP3 & AAC).
This patch adds only Opus support.
For R we probably want to expose all format that the framework supports.
Bug: 146540917
Test: AudioTrackOffloadTest AudioFormatTest
Change-Id: I2ca57d45081668f76f8d9e153f66d1fd41209685
Signed-off-by: Kevin Rocard <krocard@google.com>
1) Remove Unused Parameters for onDataConnectionState:
The data connection state broadcast includes a number of
parameters that are never used anywhere. To prepare for
updated code that relies on PreciseDataConnectionState,
remove the unused parameters that were internal-only and
included in the broadcast.
-LinkProperties
-NetworkCapabilities
-DataRoaming
-DataAllowed
-Interface name
2) Add Disconnecting State for Data Connections
Add a disconnecting state to correct a mismatch
between the internal and externally visible enums.
This will allow apps to know when connections are
in the process of being torn down, which in the case
of radio link issues could be as much as 15 seconds.
3) Expose PreciseDataConnection for Carrier Apps
Exposes the PSL for PreciseDataConnectionState along
with existing fields in the PreciseDataConnectionState
class.
-Make PreciseDataConnectionState public along with some
of its fields.
-Expose onPreciseDataConnectionStateChanged.
-Add onPreciseDataConnectionStatesChanged to provide PDCS
for all APNs in one cohesive batch.
4) Cache PreciseDataConnectionState by APN Type
In telephony registry, multiple different APN types
are all piped through the same cache entry, so every
time any APN changes relative to the previous type,
it triggers an update. This also means that when
a registrant requests the data connection state, only
the most recent type's state is updated.
This change caches entries in TelephonyRegistry based
on the APN's type (specifically the type among types
which triggered the change).
Bug: 143083105
Test: make update-api && make offline-sdk-docs
(no functional change in this CL).
Test: atest FrameworksTelephonyTests
Merged-In: Ib6a769f5a0cae923ca47a842733bd28755a90ed5
Change-Id: Ib6a769f5a0cae923ca47a842733bd28755a90ed5
(cherry picked from commit 4d340f12c9)
(cherry picked from commit c95b4e5421)
Make this API system to resolve mainline concern. It is ok to make it
system API as it is not a key in CarrierConfigManager. We can add
permission check on the other side.
Test: built
Bug: 146583148
Change-Id: I7c4297d659635622ba4523abf2ce32e21f961ad0
If device doesn't support userspace reboot then call to
PowerManager.reboot("userspace") will throw an
UnsupportedOperationException.
For the case of upgrading devices, Treble enforces that previous vendor
image should work with the new system image. Since userspace reboot
requires services to be stopped and restarted cleanly, which upgrading
devices might not be able to comply with, we need to have an API to
distinguish between devices that support userspace reboot and the ones
that do not.
Test: atest PowerManagerTest
Test: atest CtsUserspaceRebootHostSideTestCases
Bug: 138605273
Bug: 135984674
Change-Id: I8303f43ab29499eb2995f0256854c787055d9560
Move tethering out of ConnectivityService. All client would
use TetheringManager to talk with TetheringService directly.
Bug: 144320246
Test: -build, flash, boot
-atest TetheringTests
Change-Id: Ib051bea724a256f9c4572b566e46ae7b9c4abe6e
Merged-In: Ib051bea724a256f9c4572b566e46ae7b9c4abe6e
In order to allow sockets to be set as non-blocking after the creation,
fcntlInt must be exposed.
Test: new tests added, passing
Change-Id: Ib9951b5391cafda2b88c25f0cb7245b04a1adfb0
