This file notification ids to be used anywhere in the android package (e.g. system_server). Match platform resource OWNERS that has similar scope.

Change-Id: I2d525d59c24df63429ef090e41e45952506c1c59

This CL creates two new PhoneAccount capabilities for the SIM call
manager (and potentially telephony itself for PSTN PhoneAccounts) to
advertise that they support voice calling, potentially independent of
voice service state. With this information, telecom will feed updated
back into telephony for plumbing through the standard ServiceState-based
APIs.

Bug: 205737545
Test: atest android.telecom.cts.PhoneAccountOperationsTest
  (an additional CTS test for the TelephonyManager API will be added as
  a follow-up)
Change-Id: If7a5b03a7aa630823ac238ef27721e5e6cc596e6
Merged-In: If7a5b03a7aa630823ac238ef27721e5e6cc596e6

This CL fixes disconnectLeAudio to disconnect devices properly
and make it send becoming noisy intent when
an LE audio device is disconnected.

It also calls disconnectLeAudio for broadcast profiles.

Bug: 230298077
Test: manually turning off BT to check if
media is paused.

Merged-In: Ifd74c244e19f5e7f92fdbd8f7d20cd99a054425a
Change-Id: Ifd74c244e19f5e7f92fdbd8f7d20cd99a054425a
(cherry picked from commit 695a2648)

https://screenshot.googleplex.com/3WFzphfDAifZZvF

Bug: 241421504

Test: m droid dist

Change-Id: I1b85a60345bedb108ba5186bdc4a4667890ba4e5

Test: m droid dist

Change-Id: Ie27ab42f10a00d1c982f4d3ef928cca58019dc1f

This reverts commit 9cfd3674.

Reason for revert: <Break test>

Change-Id: Ibdd13c67c2f7cda5331df14f0bedd4e33f8df3fa

Invert the order to prevent confusing VPN disconnected
notification being sent before the runner actually exits.

Bug: 235322391
Test: atest FrameworksNetTests
Change-Id: I3b2eed8bf4de4b8dd00d4797509884ebeff9ad75

This CL fixes the growing list of Dispatchers in
RecordActivityMonitor by comparing dispatcher callback
via asBinder() method of the interface.

Bug: 242056995
Test: use the repro app from the bug
Change-Id: I3a2674dd339b84ecff609eef042ca41484a43255

Change-Id: I50719c5d5b19f0d5fd542a94726221b165020860

I noticed this while cleaning up includes in
https://skia-review.googlesource.com/c/skia/+/565005

Change-Id: Ibbd6fd7741a79b913b822baa207a61f419b23fe2

bug: 240984267
Change-Id: Ib3d0b9755f0ec99daf5b3241ca23d3b0cc1fb839

The INPUT_OWNERS file information is propagated to multiple folders,
and that information is used when approving CLs. This changeset will
add all the current team members as owners.

Test: Treehugger passes
Change-Id: I7289ca24055e4b22d955bdad91fb4aa6d7c8e55b

Bug: http://b/196856709
Test: treehugger
Change-Id: I90ccb32df5ef841a02e9b759891552291142979f

* changes:
  RELAND MediaCodec: don't cache buffers until requested
  Revert "MediaCodec: don't cache buffers until requested"

Auto-generated-cl: translation import
Change-Id: I4f2d21c08155b91ac7703e198ba1826996532db4

Adding the upper limit results in the correct error message being
displayed to the end user - "Type a PIN that is 4 to 8 numbers."

Limiting the SIM PIN length to between 4-8 digits is part of the
GSM SIM security requirements.  See GSM 02.17 version 5.0.1,
Section 5.6 PIN Management.

Bug: 31331481
Test: 1. Insert a SIM card with SIM PIN enabled
      2. Start the device
      3. Enter a SIM PIN with a length > 8
Change-Id: Ie5fba1c79074910b0bfd54df51e4412bbf32f5fe

This script has been deprecated and replaced by AyeAye checks
directly in Gerrit.

Bug: 164530987
Test: none
Change-Id: I6a36c0a7ac10cbec0667780c30ba4a20124edee4

Do not cache input/output buffers until explicitly requested.

Track validity of buffers before getInput/OutputBuffers so that the
dequeued buffers are marked accessible when the array is returned
to the client.

Bug: 189889230
Bug: 236106096
Test: manual
Change-Id: I6892f02853f00c3e355c827ec943fbdf183469f1

The "boot" compilation reason is now deprecated (since Android S),
but the mapping between PackageManagerService.REASON_BOOT_AFTER_OTA
and the corresponding value in ART_COMPILATION_FILTER has not been
updated (or it has been incorrect all along). Note that this will
require a change in APC/Pitot to make sure that both the previous and
the new value for this ID are treated in the same way (so we don't
lose data logged ahead of this change, which is still valid, just
associated with an unexpected ID).

Bug: 239548426
Test: atest ArtStatsLogUtilsTest
Change-Id: I38b4a16768f32f8ed2ecfe5d5c389ad4ec3b6b6e