With b/150232615, we will need an explicit value set for the exported
flag when intent filters are present, as the default behavior is
changing for future versions. This change adds the value reflecting the
previous default to the manifest.

These changes were made using an automated tool, the xml file may be
reformatted slightly creating a larger diff. The only "real" change is
the addition of "android:exported" to activities, services, and
receivers that have one or more intent-filters.

Bug: 150232615
Test: TH
Exempt-From-Owner-Approval: mechanical refactoring
Change-Id: I94a73c7d2c68ee5514b22f42c321b9fdad643c50

With the deprecation of WRITE_MEDIA_STORAGE in R. Apps should migrate
to requesting MANAGE_EXTERNAL_STORAGE permission

Test: m
Bug: 144914977
Change-Id: Idbcee2a29a3656cc1d48719f5cbd74ae97d6dc3e

We're working towards making MediaProvider into a Mainline module,
which means it can no longer share the "android.media" UID built
into the OS.  The major reason for this is because they're signed
with separate keys, but a secondary reason is that we don't know what
database customizations an OEM has performed in their MediaProvider.

Ensure that packages are requesting the permissions they actually
depend on, instead of relying on permissions requested by other
packages under the shared UID.

Bug: 144247087
Test: atest --test-mapping packages/providers/MediaProvider
Change-Id: I1593d64f8a240be66301e01b632ad0ff9b3f8f18

If com.android.mtp is the first package to get started in the shared
media process, then its manifest entry dictates whether clear text
traffic should be permitted or not. That's why we try to ensure
usesClearTextTraffic="true" for all packages sharing
android.process.media.

Fixes: 140749044
Test: atest cts/tests/app/src/android/app/cts/DownloadManagerTest.java
Change-Id: I42471fb2f8e7eb9747bffa3807e47d139097211a

As part of getting MediaProvider to compile against supported APIs,
we're moving MTP related logic into its own repository.

Bug: 135340257
Test: manual
Change-Id: I437d2b7f52c0ecbb54b992f3f4eedc73f23729c8

Now requires permission if targeting P.

Note that this is a separate permission from the existing one
that is required for instant apps to use foreground services.  The
reason for this is that their semantics are different (the instant
apps permission is associated with an app op for control over what
the app is allowed, while the regular app permission is just a
normal permission that is always granted and only there for
auditing of apps), and there are probably going to be cases where
a developer will want to use a foreground service in the full
version of their app but not as an instant app.

Bug: 72116995
Test: atest CtsAppTestCases
Change-Id: I883c9515c307ed8e39f0bf888c4045944c8183ac

This reverts commit a9da85fde4675ed0b03557e448b1cc67f1d391fe.

Reason for revert: b/73224471

Bug: 73224471
Bug: 72116995
Change-Id: I1485305f40d47fdb138cb1e484c329cf20892a6b

Now requires permission if targeting P.

Note that this is a separate permission from the existing one
that is required for instant apps to use foreground services.  The
reason for this is that their semantics are different (the instant
apps permission is associated with an app op for control over what
the app is allowed, while the regular app permission is just a
normal permission that is always granted and only there for
auditing of apps), and there are probably going to be cases where
a developer will want to use a foreground service in the full
version of their app but not as an instant app.

Bug: 72116995
Test: atest CtsAppTestCases
Change-Id: I95afb7185742b82c525e775ca20bb36015510b43

This reverts commit 994b5ad737831854ac3ba119abba533adca774fc.

Waiting for Chrome prebuilt.

Test: NA
Bug: 72116995
Change-Id: Ifcfea94ddefda27267640283038c9d0f933ea1d8

Now requires permission if targeting P.

Note that this is a separate permission from the existing one
that is required for instant apps to use foreground services.  The
reason for this is that their semantics are different (the instant
apps permission is associated with an app op for control over what
the app is allowed, while the regular app permission is just a
normal permission that is always granted and only there for
auditing of apps), and there are probably going to be cases where
a developer will want to use a foreground service in the full
version of their app but not as an instant app.

Bug: 72116995
Test: atest CtsAppTestCases
Change-Id: If5a79e7ed5ab9e0edc77410315eb4d2df8ac850b