Change-Id: I465731f45e663dbe699eca64c04061c6167c1813

Bug: 344870230
Test: Not required. Add owner only.
Change-Id: I5ef64a9604f7453a1704e5a7b8f49acce3bf37c3

This reverts commit c996b909.

Reason for revert: Fixed CTS tests

Change-Id: I4ebb7d1a05eec41e8c5f603c42972c2e16d60b3d

The remote color resources (under `remote_color_resources_res`) were
authored and checked in three years ago by pbdr@, and these resource
files are well isolated from other frameworks resources. It will make
sense to add Pierre as an owner.

Bug: 344870230
Test: Not required. Add owner only.
Change-Id: I338a40fe7118dd04f168e83e85bf03912da45842

No longer an appropriate reviewer for platform code.

Change-Id: I051251f7baee476dd95c4a85b1a6e2e51e9a00fd

Processing the large proto tombstones can cause OOM and there is no point adding tombstones larger than dropbox max capacity as they will not get uploaded.


Bug: 343135528
Change-Id: Ib308e48dcfc3282ae7ab0e9fa0827cc8fae97078

We have enough logging now, they have become excessive.

Change-Id: Ia26dbbf7d771554e29087527bea97d6e6d5887bb
Test: presubmit

TracingServiceProxy depends on external system services to forward its
requests to. There is an edge case where reportTrace was called before
the encrypted storage was unlocked and before external services can be
bound (e.g. occurs when reportTrace is concurrent to system_server
starting up).

This change defers the registration of the service until we are ready to
accept requests. As a side-effect this also means that the device needs
to be unlocked before the service is published.

Bug: 333846370
Test: atest PerfettoReporterTest
Test: boot device without lock and invoke perfetto reporting (verify the report is accepted immediately)
Test: boot device with lock and invoke perfetto reporting (verify the report is accepted after unlocking)
Test: invoke perfetto reporting concurrent to kill -9 `pidof system_server`
Change-Id: Ibb75c3e314d30b18cdc32e3774be1ee8022960b1

We've been profiling and making improvements to MessageQueue for
some time now and also have OWNERS for MessageQueueTest.java. Would
like to be able to review future changes to the core MessageQueue
class. I also added Message.java for good measure.

Test: presubmit
Change-Id: I961a2468c7b9a451d3b33d78a67f17cccf22cd60

Merge "Increase the dropbox disk quota to 20Mb for user debug builds as we add more debug to dropbox for user debug. (cherry picked from https://googleplex-android-review.googlesource.com/q/commit:ea261f6a2a9d1034abfaf2ebdaae72c9869c8c90) Merged-In: Ib758fa6fa47cfd26e895bf8d7b9d5bde98c99461 Change-Id: Ib758fa6fa47cfd26e895bf8d7b9d5bde98c99461" into main

While this offers minimal savings, there's no real reason to opt out of
optimization (the default for app targets).

Test: m + check APK diff
Bug: 203241149
Change-Id: Ib1bba31a95afa87f37aedb0251796bdb31ab65c0

Bug: 333854840
Test: atest android.os.BinderTest
Change-Id: Iaf1fd1e5daea7103a873bc8f8aa0b78377e57714

Increase the dropbox disk quota to 20Mb for user debug builds as we add more debug to dropbox for user debug.
(cherry picked from https://googleplex-android-review.googlesource.com/q/commit:ea261f6a2a9d1034abfaf2ebdaae72c9869c8c90)
Merged-In: Ib758fa6fa47cfd26e895bf8d7b9d5bde98c99461
Change-Id: Ib758fa6fa47cfd26e895bf8d7b9d5bde98c99461

There's some bad behaviour going on that's exclusive to WatchOS
(discovered on the Pixel Watch 2). The TombstoneWatcher class is
responsible for watching the /data/tombstones/ directory. It is a member
of the NativeTombstoneManager class, which is created when
ActivityManager starts, and lives until the device is powered off.

Unfortunately, some bad behaviour (unclear exactly what at this stage)
means that the TombstoneWatcher class is spuriously garbage collected,
even though the parent NativeTombstoneMenager class is still alive and
reachable. I chatted with hboehm@ from the ART team, and his hypothesis
is that because the TombstoneWatcher member is initialized in the
constructor and never used again, some optimiser is doing the wrong
thing and thinking that it's unused and can be GC'd.

The TombstoneWatcher uses inotify in native code to execute a callback
when a file is added to a directory, so it's clearly in use, but
unfortunately the bug allows this class to be GC'd anyway.

What this means, in practice, is that app native crashes on WatchOS are
not being handled correctly. This includes:
 - Apps cannot get their own crashes through the
   ApplicationExitInfo::getHistoricalProcessExitReasons API.
 - Crash reports are never sent to Google, with the exception of
   tombstones that last until the next reboot, where they're one-time
   scooped up and sent to Google. This has substantially increased
   latency (requires a reboot) and also probably drops quite a number of
   reports because there's a limit of tombstones on the device, and a
   rate limit of how many are sent by GMS.

Bug: 339371242
Test: atest CtsGwpAsanTestCases on eos (Pixel Watch 2, WatchOS)
Change-Id: I9226e4368b03bd4742fccdafde6018f145da63e6

method.

Accessing mDisplayInfos, mInputWindowHandlesOnDisplays and other
collections should add mLock lock according to AOSP requirements.

Test: OEM monkey test
Bug: 344434136
Change-Id: Icb18683680c40939e0ebd352818702f90b79179f

If a display has freeform windowing environments such as Desktop
or XR device, then resumed activity of task fragment will be set
to focused app. However, it can break focused state in embedded
task fragments.

Thus, allow it only if a focused task is different from a next task.

Bug: 343252725
Test: Settings(AE) > Launch SubSettings > Check focused app/window
Change-Id: Ib62ecb7c8e0fe453149f51c610c34d97bbde7cb1

Test: atest
Bug: 343818003
Change-Id: Ia30d818d6ac19c2a3e9ae31b29122fb5bbac338a

Bug: 324085891
Test: atest CtsResumeOnRebootHostTestCases \
FrameworksServicesTests: RebootEscrowDataTest \
FrameworksServicesTests: LockSettingsServiceTests \
FrameworksServicesTests: RecoverySystemServiceTest \
FrameworksServicesTests: RebootEscrowManagerTests \
FrameworksServicesTests: RebootEscrowProviderServerBasedImplTests
Change-Id: Ibba55830bb3168d312d3f92094d7a266931439e6

The generated EventLogTags helper class has the appropriate event IDs,
so use it for logging-related calls.

Bug: 203241149
Test: atest DynamicSystemInstallationServiceTests
Change-Id: I488b9fe53d0b3fbfdedc41037f604c60b9fca82f