1) Clarify why there are new APIs being added as @deprecated
(backwards compatibility), and
2) onLineIdentificationSupplementaryServiceResponse should throw
an exception instead of silently failing.
Test: atest CtsTelephonyTestCases FrameworksTelephonyTests
Bug: 149997057
Bug: 143987946
Fixes: 151172761
Merged-In: I5c2bacad43917a6ecad49dcf9d3213b3472534cc
Change-Id: I5c2bacad43917a6ecad49dcf9d3213b3472534cc
This had the consequence of making two large metalava invocations
run in sequence rather than parallell.
For now, add back the dependency on framework-all instead. Building
framework-all should be a lot faster than the sdk stubs.
Also move the module stubs dep from framework_defaults to
framework-minus-apex. framework-all does not need this dep.
Bug: 151092414
Test: m
Test: NINJA_ARGS="-t path out/soong/.intermediates/frameworks/base/module-lib-api-stubs-docs/android_common/module-lib-api-stubs-docs-stubs.srcjar \
out/soong/.intermediates/frameworks/base/system-api-stubs-docs/android_common/system-api-stubs-docs-stubs.srcjar" m
Change-Id: Ifdf8823d374254e594330b43ae3a39a76c7b90c5
Merged-In: Ifdf8823d374254e594330b43ae3a39a76c7b90c5
(cherry picked from commit 92d79fddd49b1b502f0b47c574fb1aec7ca85b15)
Some MMS applications have a settings option to allow user to set
reply MMS delivery to on or off. To support this, application will
set REPORT_ALLOWED into NofiyResp.
PduComposer.makeNofiyResp needs to be added REPORT_ALLOWED to make
application setting work.
Test: Set REPORT_ALLOWED in NotifyResp by application. It should be
contained in MMS PDU.
Bug: 143447617
Change-Id: I0ff4a875596efa2fd45f9e20bab880949651faac
getBaseBandVersion tries to get value from a legacy API and rewrites it
back. However the read value is the full list but the write is to a
specific phone, causing the list to grow unexpectedly.
Bug: 149342541
Test: manual - using test app, call API and check result.
Change-Id: I78b0443c5e38a30010796fcb69f01a8c7ebaf160
This permission is needed for wifi CTS tests.
Is the minimally scoped permission that needs to be added?
- Yes, this only allows the app to influnce wifi vs lte network
selection algorithm.
What options did you explore that did not need this permission?
- Without this permission, it would be impossible to test these API's:
WifiManager.setWifiConnectedNetworkScorer()
WifiManager.clearWifiConnectedNetworkScorer()
WifiManager.clearWifiConnectedNetworkScorer()
WifiManager.addOnWifiUsabilityStatsListener()
Bug: 150236894
Test: Device boots up.
Change-Id: Ic173e44ab818cdfecebde80715ddaec347019db6
Merged-In: Ic173e44ab818cdfecebde80715ddaec347019db6
(removed all references to CustomerId) and added link to explain what
the HiSyncId represents
Bug: 149238489
Test: Manual
Change-Id: I4ff2a8d46f3fc5d06a29829a69a27a0c15e466f8
Hide API that is only used by telephony registry.
Test: Telephony sanity tests
Bug: 149850449
Merged-In: Ie4c46de336097fb7231291f15048329aea0b639c
Change-Id: Ie4c46de336097fb7231291f15048329aea0b639c
(cherry picked from commit f0df0ba2ba735b6c484d3e752c20650d3c222bf1)
Filter out changes that are: logging only, older then enabled after P,
newer then enabled after Q.
Added missing @Test that broke builds.
Test: atest com.android.server.compat.PlatformCompatTest
Bug: 151299145
Change-Id: Ic4c12ceec3f4018a1f206b8498e8216466ecf960
Merged-In: Ic4c12ceec3f4018a1f206b8498e8216466ecf960
When the Ethernet interface becomes unavailable (e.g., because
the cable was unplugged or the interface was removed), or when
setEthernetTethering(false) is called, release the Ethernet
interface request.
This ensures that:
- The Ethernet interface immediately becomes available for use in
client mode.
- If an interface later becomes available, tethering is not
automatically started. This is consistent with what happens for
other downstream types such as wifi and USB. Evey time one of
those downstreams goes down, tethering is stopped and will not
be restarted.
Test: manual
Bug: 148824036
Change-Id: Iaf85e800569f2e08c39f7ebb96f8aa34f6e53133
Per API review:
- @IntDef defined on the type integer parameter
- have getters on each parameter that is set in the
TetheringRequest.Builder
- new added API should not be deprecated
Below APIs is moved from system-current to module-lib-current that only
plafrom code(e.g. ConnectivityManager and Settings) can use them.
TetheringRequest.
onTetherableInterfaceRegexpsChanged, TetheringInterfaceRegexps:
Only platform code can use them because interfaces by regular
expressions are a mechanism which is planning to be deprecated.
Also rename some constants for easier to understand.
Bug: 149858697
Bug: 151243337
Test: m doc-comment-check-docs
atest TetheringTests
Change-Id: I45cb21d5bc919f6d32c42650326597d5173ea028
Merged-In: Idd041f0fbeca411ea23e49786a50dd7feb77ef45
* changes:
[SM08] Add NetworkTemplate unit test for fetching mobile data usage
[SM07] Make combine subtype configurable from Settings
[SM05] Enable record mobile network stats by collapsed rat type
[SM04] Support fetching data with NetworkTemplate with subType
[SM02] Support record mobile network stats by collapsed rat type
