These were system API but we should expose them for apps with carrier
privileges.
Test: manual
Bug: 122974656
Change-Id: Ie60e4c580dfa9dd0d7d6fb6b94226661d0620dad
The utilities are not supported as public API but required as SystemApi
for the NetworkStack.
Test: flashed, boots, WiFi works
Bug: 112869080
Change-Id: Ia64b3bf9c6c33cf61bed76469ea9963b550bed2b
attach*Filter and addArpEntry are necessary for the NetworkStack but are
only usable for apps that have system permissions.
Also includes system API for IpPrefix, LinkAddress, LinkProperties,
Network, and static modifier in ApfCapabilities that were missed in
previous CLs.
Test: Builds, flashed, WiFi works
Bug: 112869080
Change-Id: If141ae6a2f9145f5af64ba002ca44938f39b90a9
Define entry bandwidth threshold for opportunistic data
Define entry and hysteresis time for opportunistic data
Bug: 120847469
Test: make
Change-Id: Ie7c35e10aeaf791dba49d9f5e881d292068f81f3
Merged-In: Ie7c35e10aeaf791dba49d9f5e881d292068f81f3
Add EMERGENCY_NUMBER_SOURCE_TEST_MODE
This also does not allow to send the service categories from database when
dialing.
Bug: 122840137
Test: Manual; Treehugger
Merged-in: I4ea3539e3b814b71e03e956d4a857ec20141fa8c
Change-Id: I4ea3539e3b814b71e03e956d4a857ec20141fa8c
(cherry picked from commit cb4bd3a30f)
Data profile should use the public defined types
instead of the internal defined data types.
1. Using integer instead of string for protocol type.
2. Using TelephonyManager.NetworkTypeBitMask instead of
the internal ServiceState.RIL_RADIO_TECHNOLOGY_XXX
in data profile.
Test: Telephony sanity tests
Bug: 73659459
Merged-In: I04b910f8e349e8b7819ff058bf37ad06c3fd9adc
Change-Id: I04b910f8e349e8b7819ff058bf37ad06c3fd9adc
(cherry picked from commit af6b47af54)
These utilities can only be used for privileged apps. The underlying
implementation cannot be @SystemApi.
Test: m
Bug: 112869080
Change-Id: Idfa90561102e5b03ab2b79486d3ad46457128bf8
Includes @SystemApi for Context.NETD_SERVICE so system apps (including
the network stack) can obtain the service.
Test: m
Bug: 112869080
Change-Id: Ida63747cd30abb7b3c19559803353eb0e42e6efa
Another CL in this topic turns the methods into nonfinal
ones in oder to be able to add covariant method overloads
in java.nio.{Byte,Char,Double,Float,Int,Long,ShortBuffer.
Bug: 71597787
Test: Treehugger
Change-Id: Ife6d5938c932f4e881f8f23c85422c84b6c6a41a
Adds two new carrier config options for UT:
1) Whether or not the carrier supports UT over IMS
2) Whether or not the carrier requires a carrier app to
provision the device to use UT over IMS.
Also adds new ITelephony AIDL for querying/setting
provisioning for MMTEL currently used for UT over
IMS only.
Bug: 119896853
Test: atest FrameworksTelephonyTests
Change-Id: I51260afed85b99cf6ed89374daf417c3a25c7fb9
Policies of silence mode:
1) If an active device (for A2DP or HFP) enters silence mode,
the active device for that profile will be set to null.
2) If a device exits silence mode while the A2DP or HFP active
device is null, the device will be set as the active device
for that profile.
3) If a device is disconnected, it exits silence mode.
4) If a device is set as the active device for A2DP or HFP,
while silence mode is enabled, then the device will exit
silence mode.
5) If a device is in silence mode, AVRCP position change event
and HFP AG indicators will be disabled.
6) If a device is not connected with A2DP or HFP, it cannot
enter silence mode.
Bug: 112323989
Test: Manual, runtest bluetooth
Change-Id: If7f340de38c350f17c37f00a3a2e871876baa20d
There are a few non-OMADM specific configs that need to
be exposed in ProvisioningManager to handle cases
like turning on WFC "non-persistently" for provisioning
on certain networks. These should be well defined for
compatibility as well as ease of use.
Test: atest FrameworksTelephonyTests, turn on WFC
Change-Id: I79c9492664d4bf41b10639c0596d4f2697cd46f2
