We currently display the pointer for all devices that support displaying
it, but there are actually some devices that are disabled and shouldn't
actually have it displayed for them, here's an implementation for that.

This is done by adding an enabled state to the InputDeviceInfo to
determine its disabled status.

Bug: 335795596
Test: atest inputflinger_tests

Signed-off-by: Linnan Li <lilinnan@xiaomi.corp-partner.google.com>
(cherry picked from https://partner-android-review.googlesource.com/q/commit:d7c5c6d376f5eae7cbb7cce5ea12f2ba420d87ab)
Merged-In: Ibdad9f8424a29d83412866eace0ef96026fb270a
Change-Id: Ibdad9f8424a29d83412866eace0ef96026fb270a

The surface control and transaction are barely every null in most calls,
but some informational structures like HDR metadata, and the surface
control when reparenting are allowed to be null.

Change-Id: Ia1a456041daf8136d856a1901881b74f97b3593a
Test: make aosp_cf_x86_64_phone
Signed-off-by: Marijn Suijten <marijns95@gmail.com>

This keeps it consistent with the SDK doc.

Bug: 332253611
Test: n/a
Change-Id: I988f9be7eb37ac1d57edd403dc30f0e17e2b2db3

By declaring the ABI of `enum` types, the `enum` type can now be used in
place of a raw and untyped integer in function parameters and structure
fields, self-documenting what the possible values are.

Test: treehugger
Change-Id: I6b9cf8b36b16e23c0e992f8155452bd194e6e1ad
Signed-off-by: Marijn Suijten <marijns95@gmail.com>

Bug: https://github.com/android/ndk/issues/1920
Test: treehugger
Change-Id: Ib8296e7b9c86809d16fbde0787d016095a189387

This will change MotionPredictor::predict() outputs once
enable_prediction_pruning_via_jerk_thresholding is enabled.

Test: atest libinput_tests --host with local flag override to enable
enable_prediction_pruning_via_jerk_thresholding.
Test: atest CtsInputTestCases
Test: atest MotionPredictorBenchmark MotionPredictorTest
Bug: 266747654

Change-Id: I11eb1972246468a1f3824656f5ac57e01e0359cd

This will help understand when it's created and destroyed. This also helps disambiguate between multiple InputConsumers in the same process.

Test procedure:
1. Add "system tracing" to quick settings from developer options (enable
   the quick settings tile for system tracing)
2. Start system tracing via UI of quick settings
3. Open all apps and do some swipes
4. Click "stop tracing"
5. Pull the logs to the device `adb pull /data/local/traces/ ~/trace`
6. Go to https://ui.perfetto.dev/
7. Click "open trace file" and navigate to the local file
8. In the trace, open the process of interest. In this case, it's the
   launcher process
9. Scroll down to "InputConsumer processing"
10. The "cookie" field of each entry is the sequence number of this
    event (but not the event id).

Bug: 311142655
Test: perfetto test procedure described above

Change-Id: If8cdadd3604e8e3ab24c45a5ccf4ea9ffa9fee4a

This is a no-op

Test: atest libinput_tests
Bug: 266747654
Change-Id: I0f67a1d8ea59a6851afa6f523b6e00b2281745d0

to be shared between Java and C++.
The values of PointerIconStyle in Input.h and the constants in
PointerIcon.java are manually synced now.
This change introduces an AIDL file which can be used by both.

Bug: 235023317, 330827347
Test: presubmit
Change-Id: I01f31868e7c13270047673d97035783deaf0a7f6

Because of the existence of extra spaces, the owner of keycodes.h is
not configured as expected. We should delete this extra spaces.

Bug: none
Test: After merging, check whether the owner of keycodes.h includes
all users under INPUT_OWNER

Change-Id: I634c49f53a4633bdee3cdefbf0debae4dff90a47

Test: Builds
Bug: 330375394
Change-Id: I54a51e3f78d5c44067369d3fce3a61fd18a4157b

Bug: 324271765
Test: ASurfaceControlInputReceiverTest
Change-Id: I19a1c796c1d22e8b247368df07c34c1b4b195e64

This will allow the upper layers to release the ownership and hand the
object over to the ndk client. The client will then assume the
ownership. This is not possible with the current implementation of
rvalue, because the ndk interface is only using pointers.

Unfortunately, this makes things more clunky for tests (unless we modify
BlockingQueue).

Bug: 324271765
Test: TEST=libinput_tests; m $TEST && $ANDROID_HOST_OUT/nativetest64/$TEST/$TEST --gtest_repeat=100 --gtest_break_on_failure
Change-Id: I0cf326a22f840be6f8aa00d1e69f818815788487

In this CL, an InputConsumer with built-in looper handling is being
added. This will be useful for native code that needs batching, and that
provides choreographer callbacks directly into native code.

Before this CL (and with this CL, temporarily) the InputConsumer logic
was split between native and jni layers. In general, we shouldn't have
logic inside jni. But in this case, the situation was also making the
code difficult to reason and debug.

In this new InputConsumerNoResampling class, all of the features of
InputConsumer and NativeInputReceiver are combined, except for
resampling. That will be done separately, at a later time.

As a result, we will not be switching to the new
InputConsumerNoResampling class right away.

Once resampling is added, we can switch to the new
InputConsumerNoResampling (and rename it to InputConsumer), and delete
the old InputConsumer.

In the meantime, the new InputConsumerNoResampling will be useful in the
new NDK APIs. There, having resampling is not critical.

Bug: 311142655
Test: TEST=libinput_tests; m $TEST && $ANDROID_HOST_OUT/nativetest64/$TEST/$TEST --gtest_repeat=100 --gtest_break_on_failure
Change-Id: I468ddbd8406c4bf9f5e022f79fd1a582ba680633

Test: Builds
Bug: 203080148
Change-Id: I586339b82e408e0ac90944ab280a2d5b79309141

This helps to keep track of things, and it also allows easier deletion
in the future.

Bug: 311142655
Test: none
Change-Id: Iece2bf6857ab05f86072031a4cf3a36f843b1634

Added a native class that corresponds to the Java InputTransferToken.

Test: SurfaceControlInputReceiverTests
Test: AInputTransferTokenTest
Bug: 324271765
Change-Id: Ida2a7b34338560dfed9af7f510d64372e41384af

Instead of sending boolean to indicate the capture state,
InputDispatcher now sends an input window token that requests a
pointer capture, or nullptr otherwise.

This is useful for some InputReader implementations.
Also, this token can be used to verify if a pointer capture changed
event from a reader is valid.

Bug: 259346762
Bug: 301628662
Test: inputflinger_tests
Test: android.view.cts.PointerCaptureTest WindowFocusTests#testPointerCapture
Change-Id: Ie8343db6744dc2080f7f1dcff5a630be5c87fa3e

This is already useful in several places, and it's going to be also
useful in the future when InputConsumer is refactored.

So let's move it to include/input.

Bug: 311142655
Test: m inputflinger_blocking_queue_fuzzer
Change-Id: Idfc492c6bfc3cccab7e0b0d12b21a41a954cc44b

This way, they can be reused by other code in that file. For example,
by the new "InputConsumerNoResampling".

Also, pass the parameters by ref because they are not nullable.

Bug: 311142655
Test: m libinput libinput_tests
Change-Id: Ib40bcddfcb3d49b0a42d58533dcc566d9d49a500

Bug: 327182552
Test: builds
Change-Id: Ic8dd3ee6e649e493512a32956ac6d97e2627d25f

MotionEvents store the underlying axis values in the coordinate space of
the physical display, or "untransformed" space. The MotionEvent's
mRawTransform takes those coordinates into the coordinate space of the
logical display, or "raw" coordinates. The MotionEvent's mTransform
takes those coordinates into the window/View's local coordinates.

Previously, getting the motion event offset would return the offset with
respect to the origin of the "untransformed" space. This is of little
value to callers, since they are expecting the offset in "raw"
coordinates, which is the offset with respect to the logical display's
origin.

To calculate the raw offset, we calculate where the raw point (0, 0)
would map to in untransformed coordinates by applying the inverse raw
transform, and then apply the window transform.

Bug: 249340921
Test: atest libinput_tests
Test: atest inputflinger_tests
Change-Id: Iadbdde4dd45b5527b73be863b198b4c9a9e713cc

There is already a native implementation of split in InputDispatcher.
Prevent code duplication by moving the Java impl to native. The Java
impl is not correct, because it cannot access all values like the
transforms to initialize the split event with.

Bug: 326171104
Test: atest libinput_tests
Test: atest inputflinger_tests
Change-Id: I6230b6aa0696dcfc275a5a14ab4af3d4b7bd0b45

- Updates support checks to check status for UNKNOWN_TRANSACTION
- Adds PowerHintSessionWrapper class to check support on session methods
- Ensures that wrapper methods check the HAL version number for support
- Adds macros to cache returned wrapper call support status

Bug: 324255931
Test: atest libpowermanager_test
Test: atest libsurfaceflinger_unittest:PowerAdvisorTest
Change-Id: I4b329e6b55c53198bb064a34e792be6336e66e27

As AInputEvent_toJava makes JNI calls, the caller must ensure there are
no pending JNI exceptions as it may result in undefined behaviour. This
needs to be explicitly documented.
Refer: https://developer.android.com/training/articles/perf-jni#exceptions

Bug: 324375527
Test: atest MotionEventTest KeyEventTest
Change-Id: If9f40ba1ee2cb091514fb3baae28f2ca7520727e

This is far from the only C incompatibility in this file, but it's the
one that's most likely to not break builds, so I'm starting small.

This is a source compat break, but not an ABI break.

Bug: https://github.com/android/ndk/issues/1920
Test: treehugger
Change-Id: I5a32762fa61b1399fb354397479603858184ea05

Bug: 210460522
Test: atest inputflinger_tests
Change-Id: I2ab660ed0a6888c23bc711fb8494385c22b3c404

This is needed to create a host implementation of RenderThread.

Bug: 322360037
Test: build libandroid_runtime on host
Change-Id: I23f78155e0d2c511451e3e249537b83ca06f411a

This is needed for allowing apps to vote for HDR headroom restrictions
for SurfaceView and SurfaceControl

Bug: 323964760
Test: manually poking at test app
Test: SurfaceViewTests
Test: SurfaceControlTest
Test: ASurfaceControlTest
Change-Id: Ie886e67879525462d49fdedc535aea659d69321a

This CL adds an NDK API to obtain a copy of native AInputEvent as Java
InputEvent.

Test: atest MotionEventTest KeyEventTest
Bug: 298948992
Change-Id: If7b14867813f7b07bd628ebd6da7e3be4c3bb89e

This gets us closer to the goal of storing unique_ptr of InputChannel
inside the InputPublisher.

In this CL, we are still allowing the "copy" and "dup" functions to
exist. Removing those requires significant refactoring on the Java side,
including the jni layer and object ownership models.

Test: TEST=inputflinger_tests; m $TEST && $ANDROID_HOST_OUT/nativetest64/$TEST/$TEST
Bug: 161009324
Change-Id: If6f44d78c7fc9f3e12729068de1753847abf0ebb

This change creates a struct within InputDeviceInfo to hold View related
behaviors of an input device. Currently, a single behavior is supported:
device.viewBehavior_smoothScroll. This can be specified in an IDC file
to hint clients of the InputDevice that they should animate scrolls for
motion events generated by the InputDevice.

Bug: 246946631
Test: add property in IDC, check API returns expected value
Test: atest frameworks/native/services/inputflinger/tests/InputReader_test.cpp
Change-Id: Ibe373cadc40d2a08116e787b744dd30812638edb

This will replace the InputChannel. They don't both need to be shared
pointers. A lot of times, we are using InputChannel to look up the
connection. In this CL, this is simplified by using the connection
directly.

Bug: 161009324
Test: atest inputflinger_tests
Change-Id: I3fc2bbdd8c5076b5dbff5067e4fec6e45f5c3da6

This patch updates the checks, tests, and documentation to ensure ADPF
CPU == 0 is allowed, and instead checks to make sure that both CPU
and GPU cannot be 0 at the same time.

Bug: 323226967
Test: atest PerformanceHintManagerTest
Change-Id: I6927899793c7d9801541465280af32627e200dc9

Currently, InputChannel is a manually-written parcelable. In this CL, we
introduce an aidl-defined InputChannel, which eventually could also be
used in Java as well.

Now, whenever an InputChannel needs to be written to parcel, we first
create the new android.os.InputChannel and then write that object to
parcel.

Eventually, we can convert the Java side of InputChannel to use this
mechanism, as well.

Bug: 161009324
Test: adb shell monkey 1000
Test: atest libgui_test
Change-Id: Ib44c5ff02b3c77e0425b59a76195ed100e187317

Extend `base::expected` with `has_error()` and `value_opt()`.

Bug: 185536303
Test: ftl_test
Change-Id: I07d70dc8fe7ebfe2f08626dff51aef0b98430f61

Bug: 315307777
Test: manual
Change-Id: I737a7418f43afac4735bb1a5523713890f4df553

Bug: 185536303
Test: ftl_test
Change-Id: I3fc52c3dc3904ace7822200ca6c0f9ac39df8fe2

SmallVector<T, N>::emplace_back returns a reference, whereas
SmallVector<T, 0>::emplace_back returns an iterator (because
its API must be compatible with StaticVector).

Bug: 185536303
Test: ftl_test
Change-Id: I6bdcd983c0bb2d2a326f79906997f85e89d7df44

In some instances, a screenshot may be captured before a layer has a
release callback registered. This can happen when a new buffer has
not yet been transacted before a screenshot is captured. This causes the
screenshot fence to be dropped and the possibility of tearing when
capturing a screenshot while continuously rendering.

To resolve this, buffer screenshot fences into a list of future fences
when there is no callback registered, and merge those fences when
dispatching the release callback.

Bug: 302703346
Test: SurfaceViewTests#testMovingWhiteSurfaceView 100 times
Change-Id: I91aec3cdb0973092d48cd77e59dd3999e9d9e847