This command should not do anything when feature flag is off,
and let developer knows this command fails.

Bug: 177228735
Test: run "sm unmount-app-data-dirs" when the app data isolation flag is off and returns error message
Change-Id: If07107712e8215a58ffade08aedce3e80ad1ac12

The API surface is planned to move to the Connectivity module, meaning
that it will be maintained across multiple Android releases.
This is incompatible with TestApi semantics, which are designed to be
removable across releases. Effectively the APIs become SystemApi, so
mark them as such considering that TestApi is not supported by modules.

Remove the NetworkCapabilities.getCapabilities test API that is not
essential for tests, and mark other APIs as module API.

Test: m
Bug: 174436414
Change-Id: Ic04551a9874b3d756cf5e6c77ceabfc7c85d52a6

Change-Id: I89d2fa5339a37c64e76698ed1aa3825d27f88097
Test: manual

Explain how to get TelephonyDisplayInfo through TelephonyManager and
PhoneStateListener

Test: build
Fix: 158760752
Change-Id: Ia59efcf68c77d79be1a223f9fd6cbf3ec333478a
Merged-In: Ia59efcf68c77d79be1a223f9fd6cbf3ec333478a

* changes:
  OMS: reduce number of OVERLAY_CHANGED broadcasts
  Revert "Revert "OMS: add transactional API""
  Revert "Revert "Push OverlayDeviceTests onto /system""
  Revert "Revert "OMS: add tests for the OMS transactional API""
  Revert "Revert "OMS: block until settings are persisted""
  Revert "Revert "OMS: replace OMSImpl.OverlayChangeListener with return v...""

As part of "I63df58510:OMS: add transactional API", the OMS changed how
to broadcast OVERLAY_CHANGED. The intent used to be sent <once> when an
overlay changed state. This was modified to <once per package affected>
when an overlay changed state.

While this makes it easier for applications to detect if they have been
forced to reload their resources, the change drastically increased the
number of OVERLAY_CHANGED intents, especially when the target package is
"android" which affects all packages. To make matters worse, the package
manager responds to an OVERLAY_CHANGED intent by broadcasting
PACKAGE_CHANGED.

Ultimately the flood of intents caused lock contentions in the activity
manager.

Revert the OMS strategy for how to broadcast OVERLAY_CHANGED to the old
behaviour.

Bug: 177065099
Test: atest FrameworksServicesTests:com.android.server.om OverlayDeviceTests OverlayHostTests CtsAppSecurityHostTestCases:OverlayHostTest
Test: manual: adb exec-out cmd activity dump  # check for OVERLAY_CHANGED in "Historical broadcasts"
Change-Id: I33358ce4dc1d72e6e695c70cf02ab72526592b17

This reverts commit 295e0d71.

Change-Id: I5746ffae41f3e907c39420dce433c4dc91d1145c

This reverts commit 118ddbcc.

Change-Id: Ie307ce308aa45c0b6fcd5ff7001153c41ea8b7f8

This reverts commit 0ad9a225.

Change-Id: I8cd5eb46cfefdeaab783716c270059ea3faf9153

This reverts commit b8c651c9.

Change-Id: Ie02ddd3710395c3c53ca3604076c5f34c73b8387

This reverts commit 8448c33e.

Change-Id: I8fbbd8106acd9e11f1a0c14cdf823561f64eca5e

The bundle is no longer necessary, as this message is not sent across
processes: the network list can be sent directly in the message obj
pair.

Bug: 173574274
Test: atest FrameworksNetTests CtsNetTestCasesLatestSdk
Change-Id: Iae049a24212ff9df19b29aead20bf4a594f05f99

Using FileDescriptor in the aidl will refer to
Parcel.readRawFileDescriptor() and Parcel.writeRawFileDescriptor()
whilie trying to do parcel operations. Those two APIs are hidden
and not accessible for the incoming ConnectivityService mainline
module. For such use cases in a module, it should be replaced by
using ParcelFileDescriptor that is designed for such usages.

Bug: 170598012
Test: atest FrameworksNetTests CtsNetTestCasesLatestSdk
Change-Id: Ia7e3a71ccb4b136cc55c9e90a384870c32cfd37b

Create an inner class to handle the network activity related
logic to isolate the code for code cleanliness. It's helpful for
the follow-up modifications to move network activity logic from
NMS to CS to support Connectivityservice mainline.

Bug: 170598012
Test: atest FrameworksNetTests
Change-Id: I33b3b11f2700cb10eb6e3b58b6dfa52251bece80

Reporting interface change is planning to move from NMS to CS
for incoming CS mainline. The event sent from CS to NMS will
be replaced by sending to netd directly, so the change reported
via NMS to BSS should be handled by BSS directly. This commit
allows BSS to listen interface change itself to separate the
design.

Bug: 170598012
Test: m ; atest FrameworksCoreTests:BatteryStatsTests
Change-Id: I4c9202be31cad09451ef47ac7b5b87f7efb2020c
Merged-In: I9c1b2294905d3b59f6945c3f8acb91b2e419b492

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