Original change: https://android-review.googlesource.com/c/platform/frameworks/base/+/3113720



Change-Id: Ifd503b3e35f6d745cc1caea13714922798a02699
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>

No longer an appropriate reviewer for platform code.

Change-Id: I051251f7baee476dd95c4a85b1a6e2e51e9a00fd

Original change: https://android-review.googlesource.com/c/platform/frameworks/base/+/3109837



Change-Id: I11a3044a8adafc3ec4950b0e6e06b28ee1ec5f12
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>

Original change: https://android-review.googlesource.com/c/platform/frameworks/base/+/3107962



Change-Id: I5468a00e3bb1062ce84ddd7469fc5bc3f1449f0a
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>

Original change: https://android-review.googlesource.com/c/platform/frameworks/base/+/3105763



Change-Id: I3c1cc551b6356218d92e3d26a3700bc52399238c
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>

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

Original change: https://android-review.googlesource.com/c/platform/frameworks/base/+/3099917



Change-Id: If4a58a49a9e83ee38b46d2c0e185944f7ada89eb
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>

Original change: https://android-review.googlesource.com/c/platform/frameworks/base/+/3033592



Change-Id: I7e893947535f9321d443630ad139450559cd9d8a
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>

Merge "AccessibilityWindowsPopulator:fix CWE problem by add mLock in dump method." into main am: ef549343

Original change: https://android-review.googlesource.com/c/platform/frameworks/base/+/3109838



Change-Id: I58c24b9d03135d5d981eb6936a11afa3a1d19169
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>

Original change: https://android-review.googlesource.com/c/platform/frameworks/base/+/3111779



Change-Id: Ie52fe99acc7800f148eee861f8b699b5990bff34
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>

Original change: https://android-review.googlesource.com/c/platform/frameworks/base/+/3112599



Change-Id: I56f4508ca21bdd015faac8f563713c8e0e82056f
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>

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

Original change: https://android-review.googlesource.com/c/platform/frameworks/base/+/3110298



Change-Id: I8b1f96118ab7bfcaf13611d7b84731c7cb5b2b54
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>

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 am: 06cb3424

Original change: https://android-review.googlesource.com/c/platform/frameworks/base/+/3110910



Change-Id: Icc2ea678c6c894ed09c2648270dea8169a1361dc
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>

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

Original change: https://android-review.googlesource.com/c/platform/frameworks/base/+/3111199



Change-Id: I25bfdf5a7ab08af51996469d0af85c2589620d0c
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>

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

Merge "Don't unlock other users if user 0 or parent user does not contain escrow data." into main am: 284075a5

Original change: https://android-review.googlesource.com/c/platform/frameworks/base/+/3095877



Change-Id: I2e19caa02961d5d26ae01780fe75907cf57a0c71
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>

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

Original change: https://android-review.googlesource.com/c/platform/frameworks/base/+/3040395



Change-Id: I704e30274903f8d75f2d11aba9391602b8770e1c
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>