Merge "Add negative tests for ServiceManager RegisterForNotifications and unregisterForNotifications" into main am: 77cd3a2b am: 8e0660dc

Original change: https://android-review.googlesource.com/c/platform/frameworks/native/+/3111381



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

Merge "Add negative tests for ServiceManager RegisterForNotifications and unregisterForNotifications" into main am: 77cd3a2b

Original change: https://android-review.googlesource.com/c/platform/frameworks/native/+/3111381



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

Merge "Add negative tests for ServiceManager RegisterForNotifications and unregisterForNotifications" into main

In order to support detached mirrors, we introduced a different path for
mirroring a hierarchy that excludes the root layer's transform. However,
when the mirrored layer was destroyed, references to this layer were not
properly removed from its mirroring hierarchy. Fix this and introduce a test
to cover this scenario.

Flag: EXEMPT bug fix
Fixes: 343901186
Test: presumbit

Change-Id: I32f41fc2c9db00590ede4509d75000ab0a38f116

Getting the display requires the SF state lock, and this can
cause deadlocks if this work is done on a binder thread. The
eventual goal is to place all the work in renderScreenImpl on the
binder thread, so reshuffling where we get the display to an area
where we already go onto the main thread will reduce lock contention.

Additional cleanups to remove overloaded renderScreenImpl for
testable SF suite.

Bug: b/294936197
Test: atest SurfaceFlinger_test
Test: atest CompositionTest
Test: presubmit
Change-Id: I95697a2508a9d936ac9689430d9060c49ed3f039

We may modify the layer hierarchy while updating
relative layers. Fix this by retrieving the list of descendants
and then attaching or detaching it from their relative
parent.

Test: presubmit
Fixes: 344113039
Flag: EXEMPT bugfixes
Change-Id: I7aff5085794aeeb0bbba90decaf4cec13d0d2485

Original change: https://android-review.googlesource.com/c/platform/frameworks/native/+/3079627



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

Original change: https://android-review.googlesource.com/c/platform/frameworks/native/+/3079627



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

Bug: 333132224
Test: presubmit
Change-Id: I4f9e96dd4811406d9273d37310e3b415c12928f2

Sony reported that Android will not group the player LEDs properly
for the DualSense controller. After investigating, our mechanism
to group LEDs would not support the standard name for player ID
lights. This fix expands the regular expression so it will support
this format in addition of the name that the gamepad driver will
use in certain older devices.

Bug: 289067916
Flag: EXEMPT bugfix
Test: `adb shell dumpsys input`
Change-Id: I5b5e3f5e8478422bbc717a6c272a24e6568464fc

Original change: https://android-review.googlesource.com/c/platform/frameworks/native/+/3097697



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

Original change: https://android-review.googlesource.com/c/platform/frameworks/native/+/3097697



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

* changes:
  Abstract atrace dependency into binder::os
  Skip Binder IPC tests on NoKernel builds

We can now use mocked PointerChoreographer policy in choreographer
tests.

Bug: 344554018
Test: atest inputlfinger_tests
Change-Id: I8fb0d0094a9a8ea311122c35f8a9a41ada0c12fa

Bug: 333854840
Test: atest binderLibTest

Change-Id: I8a304def1d26cd1a3a4b9b3e9a3048ad702aa941

These are just type aliases and Skia is aligning the Vulkan types
to be shared between Ganesh and Graphite.

Change-Id: I6ab6c6c977310c6c9d40526f5e6761c70e346952

Change-Id: I7f538b3e08704df7c99e13e59302832dfe517a1d
Test: atest inputflinger_test
Test: manually test a multi-touch screen, touchpad, mouse, and drawing
      tablet works
Bug: 245989146
Flag: EXEMPT refactor

Original change: https://android-review.googlesource.com/c/platform/frameworks/native/+/3110622



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

Original change: https://android-review.googlesource.com/c/platform/frameworks/native/+/3110622



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

frameworks/native/cmds/installd/file_parsing.h:55:17: error: no matching constructor for initialization of 'std::ifstream' (aka 'basic_ifstream<char>')
   55 |   std::ifstream ifs(str_file);
      |                 ^   ~~~~~~~~

Test: Build with ToT libc++
Change-Id: I6aa9c173ea0acf633b1662f2118b9271000f6af4

As the resampling is performed for better scrolling, even when a user
is dragging with a mouse or a stylus, we'd like to do the same as
touch inputs.

Also, when an event being resampled has any pointer with a tool type
that we don’t resample, the resampled event has an old coordinate but
a new timestamp. This event is confusing. With this change, when the
event has such a pointer, events won’t be resampled.

Bug: 337849873
Test: Enable debug and resampling happens for mouse events.
Test: TouchResamplingTest
Change-Id: I9344759e28685a08e233939761f93f0b3911413c

This will be used to guard compilation of Graphite in RenderEngine.
Enabling the flag will ONLY compile Graphite, but not enable it. The
debug.renderengine.graphite system property could then be set to true to
enable Graphite in RenderEngine.

The existing graphite_renderengine flag will both compile and enable
Graphite in RenderEngine.

Compilation is gated on a logical inclusive OR of the two flags.

Bug: b/293371537
Bug: b/331678326
Bug: b/341728634
Test: compiles
Change-Id: I4d6408b5e65b8b8862c79086dba2f4ce56a3d179

Merge "Create a pipe between otapreopt_script and Pre-reboot Dexopt." into main am: e19c5e32 am: d87e720c

Original change: https://android-review.googlesource.com/c/platform/frameworks/native/+/3110059



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

Original change: https://android-review.googlesource.com/c/platform/frameworks/native/+/3110059



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

This CL allowes DisplayInfoListener to be injected into
PointerChoreographer. This enables testing the logic inside the
listener.

Test: atest inputflinger_tests
Bug: 325252005
Change-Id: I0101119313070f9b0a4755398ea81ce1d0681faf

Pre-reboot Dexopt uses this pipe to check if otapreopt_script is alive,
and cancels itself when otapreopt_script dies.

Bug: 311377497
Test: -
  1. system/update_engine/scripts/update_device.py out/dist/aosp_cf_x86_64_phone-ota-*.zip
  2. Wait for update_engine to enter the postinstall stage.
  3. adb shell update_engine_client --cancel
Change-Id: I9ef4525f4d0b3b8344604166a044c9e3e1bf18a0