The set of audio files is frequently customized, so move the default
set to /product. The frameworks scans both of these directories.

Bug: 80410283
Bug: 118826166
Test: verify sounds available in soundpicker
Change-Id: I3bfc71b46eb64b4d4614b62c65fb8821bf1c271a

* changes:
  Call into application to do AppZygote preloading.
  Allocate isolated UID ranges for app zygote and its children.
  Initial support for application Zygote.

For now, assume a class named <package_name>.ZygotePreload
exists, with a method named doPreload() to do the preload.

This should probably be replaced by having an entry in
the manifest.

Bug: 111434506
Test: preload called
Change-Id: Id632e46087eb5c719e6b310ffe007f76d3cbaf7d

Introduce a new range of app-zygote isolated UIDs, [90000..98999].
For each app that uses an application Zygote, allocate a range of
100 isolated UIDs. The application Zygote for an app will get a
UID out of that range, and all other children that are forked
from that zygote will get a UID from the same range.

Bug:  111434506
Test: app Zygote and its children run in the new range of
      isolated UIDs (with SELinux disabled). New set of
      tests for UID allocators pass.

Change-Id: I7a6883a5ddb95683932c93ea77f4e52d8f37fa4f

When an application has requested isolated services to be spawned
from an app zygote, we need to spawn the app zygote itself, and then
ask it to fork an isolated service.

The application zygote currently only creates the class loader, and
doesn't do much else. We keep track of the isolated services that
use the app zygote, and when the last isolated service goes away,
we stop the app zygote itself (after a timeout).

The app zygote itself runs with the app's UID and under the app
seccomp filter. That last one is too restricted, so this currently
only works with SELinux disabled.

Future CLs will add an application callback for preloading.

Test: start multiple isolated services with useAppZygote="true",
      verify app_zygote starts, services start as a child of
      app_zygote. Stopping all services stops app_zygote as well.

Bug: 111434506

Change-Id: I10ee1d4bd148c9298974d434fbc5e5eccbec16cb

am: 084b7f51 -s ours
am skip reason: change_id I54849bafbd0d05206e67636f0717b4b833a5e229 with SHA1 5de4a2d8 is in history

Change-Id: I62597bee4d8f782347a00ed914b04071193e0ae1

am: bcea9421

Change-Id: Ic3701fac667f51f1ab8faef451355fff4ac97249

am: d14ed44c

Change-Id: I2b28c73090b0a1a9a15e4a104acdbca7e43abecf

* changes:
  Invert BubbleController <-> NEM dependency
  Inline a few methods in NotificationEntryManager
  Change onRemoteEntry() to only fire when entries are removed

am: e9fe9372

Change-Id: I715e3b8126e1506c9d02f0be278fb8baad396018

am: 95681916

Change-Id: Iab284dfc831a9079e339c8c23fba8f3e7e4ec04d

am: 179f30a4

Change-Id: I8ae92392e70c046194df1c8ebee0bd32ed9513cf

The case is a test using the same package name as default home.
Starting the instrumentation of the test will kill the home process.
When AM try to restart the default home, there is a wrong logic that
cause the instrumentation process to be killled.

The problem of original logic is always set knownToBeDead as true even
the existing process is ok.

Test: atest CtsAppTestCases#ServiceTest
Bug: 120107272
Change-Id: Ic2c3f6236c3631b0e386d24750bf5952d8227ea9

The frequency will be used for fast group connection and Wifi p2p metrics.

Bug: 119998319
Test: manuall test
      * check this value in metrics dump

Change-Id: I5e153d3b022b2d27ddabf5f0fb43f499aeec924a

Bug: 122234817
Test: Build and flash manually.
Change-Id: If210762c51d33e72ea09e6328eea435b68d2eaa4

Renamed the scanning state to retrying. Removed the
old retrying dead code.

Test: Telephony sanity tests
Bug: 73659459

Merged-In: I54849bafbd0d05206e67636f0717b4b833a5e229
Change-Id: I54849bafbd0d05206e67636f0717b4b833a5e229
(cherry picked from commit 5de4a2d8)

Entries from DownloadProvider are added to MediaStore Downloads
collection. COLUMN_MEDIASTORE_URI will be used to track corresponding
entries in MediaProvider. We can't re-use COLUMN_MEDIAPROVIDER_URI
for this purpose because it is updateable by apps.

Bug: 120876251
Test: atest DownloadProviderTests
Test: atest cts/tests/app/src/android/app/cts/DownloadManagerTest.java
Test: atest MediaProviderTests
Test: atest cts/tests/tests/provider/src/android/provider/cts/MediaStore*
Change-Id: Ifd252c54f4ee739a31be2866896efac6696a088e

am: 36f0d9b9

Change-Id: I74bf7e8a7c8d2e0e9cece2ec15b829b445ac0cfa

am: 57d3db12

Change-Id: I409f34fddeb833802be67cc2c49767ba8157af24

am: 7ec9e684

Change-Id: Ie6800e9dbcf0bb56fafe0fa7791dd524df72162c

This reverts commit 1c3e7431.

Reason for revert: likely cause for broken build 5211430 and later

Change-Id: I2ef3a24c16d09b7c7d1c8c4f8a4e5570237a5bf1

The new isolated storage model we're building in Q introduces new
strongly-typed media permissions which replace the broad "Storage"
runtime permission.

That legacy "Storage" permission is marked as being "removed", and
it also splits into the new media permissions, but apps are confused
when they request the "Storage" permission, which no longer appears
as granted when the user accepts the new split media permissions.

After discussing with the permissions team, the best short-term
solution is to add special-case logic that grants the legacy
permissions when *any* of the new media permissions have also been
granted.  Only when the user revokes *all* of the new media
permissions is the legacy permission then revoked.  (MediaProvider
is already internally filtering the relevant content based on what
new media permissions the caller holds.)

Bug: 121227859
Test: manual
Change-Id: Ic87f7f93a816e91f7189509386255a260378c255