1. Ignore display overlays since we don't want screen decorations
   included in the occlusion

2. Handle occluded region as separate Rects to ensure that disconnected
   Rects in a Region are not considered occluding in the disconnected
   area.

Test: LayerTrustedPresentationListenerTest
Bug: 256993331
Change-Id: Ib0a4b850e2aafb42e206b8728fcc9b6013171f3f

* changes:
  Ensure a callback is registered for all surfaces for jank data.
  Send available JankData in all transaction completion callbacks.
  Add a flag to callbacks whether to include jank data.

Merge "Clarify binder RPC error message with linkToDeath" am: a718db26 am: 7b4342a8 am: 3d6715c9

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



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

If there is a jank listener registered for a surface, the client will now ensure that a completion callback is added to the transaction for that surface with the jank data flag set.

Bug: 235178314
Bug: 221393601
Test: atest SurfaceFlinger_test
Change-Id: I77504c05d396fb9d9d91514d320ecd4e3dc7c4e2

This, effectively, adds JankData to the callbacks also for layers that will not present in the current transaction.

Bug: 235178314
Bug: 221393601
Test: atest SurfaceFlinger_test
Change-Id: Ia6afaa31ad98a71cb6d6dc146f1094b857ab92b2

For transaction on-complete callbacks, SurfaceFlinger will now only send the JankData if the flag is set. If the flag is not set on all callbacks on a surface in a transaction, any pending jank data for that surface is now dropped. The client ensures that the flag is set on any callback on surfaces for which a jank listener is registered. Thus, the data now dropped by SurfaceFlinger would have been dropped on the client side anyways.

Bug: 235178314
Bug: 221393601
Test: atest SurfaceFlinger_test
Change-Id: I176d6962f09b587b39c5d106c48949571151f3bd

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



Change-Id: I3f0f4288027e465bf8c46c07b66f1e7c4ac32198
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/+/2426275



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

[automerger skipped] Merge "Include WMShell protolog in bug-report" into tm-qpr-dev am: 74482fc0 -s ours am: d1c6c060 -s ours

am skip reason: Merged-In I2f48511868a871a290ca38126c4a4c3016169db4 with SHA-1 9ec5c257 is already in history

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



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

[automerger skipped] Include WMShell protolog in bug-report am: f1115a2b -s ours am: cd3789e9 -s ours

am skip reason: Merged-In I2f48511868a871a290ca38126c4a4c3016169db4 with SHA-1 9ec5c257 is already in history

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



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

Merge "Merge "Added support annotations for vendor atoms" am: 0b3159fb am: 6fd0175e am: b4526584"

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



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

[automerger skipped] Merge "Include WMShell protolog in bug-report" into tm-qpr-dev am: 74482fc0 -s ours

am skip reason: Merged-In I2f48511868a871a290ca38126c4a4c3016169db4 with SHA-1 9ec5c257 is already in history

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



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

am skip reason: Merged-In I2f48511868a871a290ca38126c4a4c3016169db4 with SHA-1 9ec5c257 is already in history

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



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

[automerger skipped] Merge "Merge TQ1A.230205.002" am: b5e5e128 -s ours am: 44a7e1dc -s ours am: 42d8c73e -s ours

am skip reason: Merged-In I96a738dcb01bf1c9e2792d3fee547c147dba33b5 with SHA-1 69d75577 is already in history

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



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

[automerger skipped] Merge TQ1A.230205.002 am: 6fe6ebf9 -s ours am: fa28dcf5 -s ours am: b0360c2f -s ours

am skip reason: Merged-In I96a738dcb01bf1c9e2792d3fee547c147dba33b5 with SHA-1 69d75577 is already in history

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



Change-Id: I95aaf42dd483ce070ca9988785b093dd6118f99f
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/+/2404740



Change-Id: I693584259951dc4dd95c498376cacdd4d121ff9d
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/+/2404740



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

am skip reason: Merged-In I96a738dcb01bf1c9e2792d3fee547c147dba33b5 with SHA-1 69d75577 is already in history

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



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

am skip reason: Merged-In I96a738dcb01bf1c9e2792d3fee547c147dba33b5 with SHA-1 69d75577 is already in history

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



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

am skip reason: Merged-In I96a738dcb01bf1c9e2792d3fee547c147dba33b5 with SHA-1 69d75577 is already in history

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



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

am skip reason: Merged-In I96a738dcb01bf1c9e2792d3fee547c147dba33b5 with SHA-1 69d75577 is already in history

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



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

There needs to be threads for incoming connections before linking to
death so the service can get the notifications.

Test: none
Bug: none
Change-Id: I2e850de4fbb171b2b5c302c85980bb4966d73421

[automerger skipped] Merge "BBQ: Check if we have already acquired max num of buffers" into tm-qpr-dev am: ff5b3212 am: cb4ecc82 -s ours

am skip reason: Merged-In I77b34f6151a9d1b461649c575be98df1f00f2464 with SHA-1 b4b484ac is already in history

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



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

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



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

Revert submission 21292947-reland_blobcache_20230203

Reason for revert: Suspected cause of boot time regression

Reverted changes: /q/submissionid:21292947-reland_blobcache_20230203

Bug: b/266725576
Bug: b/268248090
Change-Id: Ic70ffa65d8d194b00106853d8c05b9cc2992e02d

- implemented logging APIs to pass annotations

Test: m
Bug: 259104358
Change-Id: I19c9f44c7246cd7c52437388cfd6219df1e29002

Due to a recent change, the TouchWindows are getting persisted inside
TouchState. As a result, we need to keep a consistent state inside them.

Before this CL, the downTime of the TouchedWindow would get set with the
first pointer, but it would never reset. We used to rely on the fact
that the TouchedWindow would go away.

Now that is no longer the case.

In this CL, the downTime is cleared when all pointers leave the window.
The downTime can be set again when a new pointer appears.

This fixes one of the crashes due to the mismatching downTimes. To
reproduce the failure, we need to:
1) Find a way to persist a window
This can be done by injecting a mouse pointer into the window, and keep
the mouse there
2) Establish a downTime
This can be done by tapping on the window
3) Send another DOWN event while splitting the pointers.
Normally, a DOWN event would not go through the "splitting" path, and
therefore the crash would be avoided. The splitting path can be
triggered if we first touch another window, and then touch the first
one. The split touch feature would cause an ACTION_DOWN to get
generated, which would then trigger the 'split' case.

Bug: 266455987
Test: m inputflinger_tests && $ANDROID_HOST_OUT/nativetest64/inputflinger_tests/inputflinger_tests --gtest_filter="*HoverTapAndSplitTouch*"
Change-Id: I2340b5ab70a3659f52fc38fa4d9e2c9edfe1a768

A transaction can be sent to SurfaceFlinger with a layer state change
of this type to wake up SurfaceFlinger and have it perform the layer
state update logic, without updating anything, but triggering any
side-effects, especially jank data processing.

Bug: 235178314
Bug: 221393601
Bug: 225105422
Test: atest SurfaceFlinger_test
Change-Id: Idf458c96cbe8f54224ebde6f517c08b9a5c48a06