Otherwise GPU composition quality is degraded for:
* Non-prerotated layers
* Screenshots captured from devices with rotated panels

The second issue in particular is problematic for CTS.

Bug: 283075427
Test: SurfaceViewTests with a 90 degree panel installation
Test: libcompositionengine_test
Change-Id: I6dd7f0f385d7df0463a560d97c1ca5ee89998405

For screenshots that we know won't be used for seamless transitions:
* Don't do dimming workarounds
* Don't use enhance or vendor-specific render intents

This ensures that screenshots that do not tonemap, i.e., screenshots
that do not contain PQ or HLG content, are rendered consistently for
use-cases like CTS where color accuracy is important.

Bug: 297832714
Test: TextureViewTests
Change-Id: Idb3c6d0778d522d1487baaffba36fae5d7b0d524

Merge "Fix formatting." into main am: 92db70b6 am: 9039cb87 am: cbb641a9 am: 809ad417 am: a9084862

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



Change-Id: I74869fa5d0a842eb2894a4fff4c46314bf9b624d
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/+/2752733



Change-Id: I70ef42061c3f191e2075795eae86f59772139d01
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/+/2752733



Change-Id: If009092e5469b3a054f4e78b5c264fa56fc51094
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/+/2752733



Change-Id: I5f4fbd7199d0ef819bd4070c2f2d9d741a63eb60
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/+/2752733



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

These words are meant to be in the code _font_, not in their own
separate code _blocks_. See
https://developer.android.com/ndk/reference/group/thermal#athermal_getthermalheadroom
for the current wrong formatting.

Bug: https://github.com/android/ndk/issues/1933
Test: treehugger
Change-Id: I2a30439bd58dd1435c4efb525a90e06631fbe6cf

[automerger skipped] Don't dim screenshots when there's no HDR on-screen. am: 93a12837 am: 2cdc6e8d -s ours

am skip reason: Merged-In Id6de2c8d3987300a1c24bf79dc5b523f40420174 with SHA-1 b4814de1 is already in history

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



Change-Id: I216947d521931b93964edb523f68be89755815b2
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/+/24763138



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

This is a no-op since we only use it for HDR tonemapping but it makes
this code clearer.

Bug: 293560925
Bug: 298219334
Test: builds, boots
Test: HDR video playback and screen rotation
Change-Id: I9ba024d8d138d4c21178c98a961332073b98fc50

Test: dumpsys SurfaceFlinger --hwclayers
Fixes: 300525768
Change-Id: If23aa3abaf114ec5fcde26af0849996255bda326

Dimming the screenshot:
* Is incorrect for screenshots that leave the device
* For transitions, requires disabling dimming which reports to DisplayManager that the screenshot is HDR, which costs power.

Bug: 293560925
Bug: 298492174
Bug: 299055884
Flag: Exempt
Test: screen rotation with and without HDR
Test: systemui jank suite
Change-Id: Id6de2c8d3987300a1c24bf79dc5b523f40420174
(cherry picked from commit b4814de1)
Merged-In: Id6de2c8d3987300a1c24bf79dc5b523f40420174

The current implementation just assumes that the Surface
and BLASTBufferQueue lives in the same process and rely
on inheritance to handle setFrameRate. This doesn't work
for any usecase that the Surface is Parceled to a diffrent process.

Bug: 281695725
Test: atest CtsGraphicsTestCases --test-filter SetFrameRateTest*
Change-Id: I4e08b92b618fa7b863ca3ef4f7b46d9f1c30c775

If the layer has a buffer crop, it needs to be intersected with the
buffer size in case the crop passed in is larger than the buffer size

Test: ASurfaceControlTest
Test: LayerSnapshotTest
Fixes: 297171709
Change-Id: I62a0278a42a478ab31dd383f0a7b9741c5b6e8a8

Merge "binderRpcBenchmark: test many proxy behavior" into main am: 9b6a5392 am: 5e0ef9f4 am: beae769d am: 7827c78a am: 7cefc0fc

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



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

Merge "binderRpcBenchmark: test many proxy behavior" into main am: 9b6a5392 am: 5e0ef9f4 am: beae769d am: 7827c78a

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



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

Merge "binderRpcBenchmark: test many proxy behavior" into main am: 9b6a5392 am: 5e0ef9f4 am: beae769d

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



Change-Id: Ia12dd46b29ee0ba6c6671e02b9858d56826be4d2
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/+/2751625



Change-Id: Ie420d2322ce90a13f2e0094a43f65e6ad2876ab6
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/+/2751625



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

* changes:
  Fix FrameRateCategory::NoPreference in SF
  Add perfetto trace for layer vote

Merge "Replace ASan with HWASan" into main am: 480edf52 am: 69b302d2 am: 3bb3b8f5 am: 0d2d690c am: f83dc48f

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



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

Merge "Replace ASan with HWASan" into main am: 480edf52 am: 69b302d2 am: 3bb3b8f5 am: 0d2d690c

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



Change-Id: Ia4b026f4f20b5f190934b2b441ff2d4309e2f773
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/+/2751626



Change-Id: I90708d98bcf516e0e0599c979352ba87431669f5
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/+/2751626



Change-Id: I39522bc9f6b4005374d0066ca23d544698a0d0b7
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/+/2751626



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

ASan on device is deprecated and HWASan now works on all arm64 devices

Test: atest libcompositionengine_test
Bug: 300289881
Change-Id: I978bf4e3f5117e95799271a8fc4e8acdae58fc15

Run benchmark. Here are the results on cuttlefish, sorted by type:

--------------------------------------------------------------------
Benchmark                          Time             CPU   Iterations
--------------------------------------------------------------------
BM_collectProxies/0/10       1533424 ns       730683 ns          754 kernel
BM_collectProxies/0/100     11205890 ns      5137458 ns          100 kernel
BM_collectProxies/0/1000   142801788 ns     62453023 ns           13 kernel
BM_collectProxies/0/5000  1027138576 ns    343139318 ns            2 kernel
BM_collectProxies/0/10000 2693937199 ns    649060571 ns            1 kernel
BM_collectProxies/0/20000 6821069171 ns    993179895 ns            1 kernel

BM_collectProxies/1/10       1548213 ns       777264 ns          703 rpc
BM_collectProxies/1/100     11427798 ns      5646163 ns          100 rpc
BM_collectProxies/1/1000   139841963 ns     64293601 ns           10 rpc
BM_collectProxies/1/5000   704893121 ns    289427753 ns            2 rpc
BM_collectProxies/1/10000 2248307827 ns    646102929 ns            1 rpc
BM_collectProxies/1/20000 5540550470 ns   1045339220 ns            1 rpc

BM_collectProxies/2/10       1992236 ns      1131694 ns          641 rpc_tls
BM_collectProxies/2/100     17621061 ns      9583246 ns           73 rpc_tls
BM_collectProxies/2/1000   170796751 ns     93129790 ns           10 rpc_tls
BM_collectProxies/2/5000  1062981321 ns    473419293 ns            2 rpc_tls
BM_collectProxies/2/10000 2146783259 ns    782427997 ns            1 rpc_tls
BM_collectProxies/2/20000 7441237493 ns   2041843159 ns            1 rpc_tls

Note - super-linear scaling of behavior above 1000 binder objects.

Because we see this scaling in both RPC binder and kernel binder (but to
a lesser extend in 'rpc' - ignore 'rpc_tls' which has a lot of extra
overhead), this indicates that part of the nonlinearity likely comes
from userspace code OR RPC-binder itself has non-linearity similar
to the binder driver.

Fixes: 298049518
Test: binderRpcBenchmark

Change-Id: Ib43ac68a1b1f9c11df06af59e3c5572abeabbd5d

Decided the behavior should not be the same as LayerVoteType::NoVote.

Bug: 300152572
Test: atest libsurfaceflinger_unittest
Change-Id: I2e0a0d4959f1fdba3f5f7d04ca15ea9045d4cd36

Confusingly, this is not related to running inputflinger tests etc. on
the host, but a vestige of an architectural plan we had many years ago
but never followed through on. It should be safe to remove now.

Bug: 245989146
Test: Run `m`, check everything builds correctly
Change-Id: I24aa9809ef7d678b0371fb0e868c6298d1d05236