Age | Commit message (Collapse) | Author |
|
Change-Id: Ic4fb6897a8fb5dae80cb3b3e68c09ad0fe45c87a
|
|
The token is now assigned in the constructor. It is read-only. When you
open inputchannelpair, the same token is assigned to both server and client
side channels.
Bug: 142581626
Test: presubmit
Change-Id: I603603844b41f478e244b89dcdd1dab7e6260347
|
|
Change-Id: Ia4a3905cee90acbbf1d5dfff66654c5d07f7c7fb
|
|
Change-Id: If55a795bdcc08bc6b932b65f835fd7ec0971fc39
|
|
Bug: 139494112
Test: atest libgui_test
Change-Id: Ia8d71b95d387d0a912100fd91a4201e36cab5c31
|
|
|
|
Change-Id: Id91d081aed7b9484bc4e178f7b7be04c2ca0423a
|
|
This reverts commit fbe5d9c4233dcd802a122f70ca5a3641fcd556ca.
Bug: 137819199
Test: manual
Change-Id: I7afec569519b9c69eb03225672db6db141b20241
|
|
WM does not consider window size or alpha value when setting it as the focused window. However, SF
will check if the window has a buffer and that its alpha is not 0. Because of this difference,
Input Dispatcher will not be able to send input to the window while WM thinks the window is
focused. This will cause apps to stop responding.
While we define what the intended behavior should be, this fix reverts
to previous behavior in P.
Bug: 139494112
Test: adb shell monkey 10000; make sure monkey does not get stuck
Test: check test app from can receive input b/140478820
Change-Id: I4160b49161dd1780713980707a5c911034f414b5
|
|
Check if scale is 0 before trying to apply it on the window scale.
Bug: 137560795
Test: Set Window Scale Animation to off from developer options menu
Change-Id: I7ae84e2838b1562ff62cdd94484bedba954e1f33
|
|
Change-Id: I38320dfda9684c3d6a687cd1ef1aebdb3f8511b0
|
|
The surface insects would be also scaled if window scale is not
identical.
Bug: 130693161
Test: atest libgui_test
Change-Id: I60a3c6b3ac1f930d3151edd86c3e798369c8c483
|
|
Change-Id: I7cb67115eea9811e02bb08a5b7385184a528296c
|
|
This CL replaces ISurfaceComposer::{eDisplayIdMain,eDisplayIdHdmi} with
the stable 64-bit display IDs generated by SF. Note that the 64-bit IDs
fall back to the old values if the HWC API for display identification is
not supported.
Bug: 74619554
Test: LocalDisplayAdapter and Choreographer receive 64-bit IDs
Test: 64-bit IDs fall back to 0 and 1 on HWC 2.2 and below
Change-Id: I3c08eff6eb8bb179ecce596ab2820a2aa44c8649
|
|
Change-Id: I5e5cc611a0970d405a1df01bfdd70ce3fdf6958d
|
|
SurfaceFlinger overwrite the input frame info by the layer
bounds, and the input coordinate should match the active buffer bounds.
The touch region should intersect the active buffer and screen bounds.
Bug: 120641923
Bug: 120781892
Test: atest com.android.server.wm
Test: atest libgui_test
Test: use landscape mode, split screen, touch on secondary window.
Test: create legacy application (<N), no title bar,
window flags=FLAG_LAYOUT_IN_SCREEN|FLAG_LAYOUT_INSET_DECOR
Change-Id: Idc3b5bb707ce733c77ee700821bde5786594e430
|
|
Conflicts:
libs/ui/Gralloc2.cpp
Change-Id: I65f60c788e5bda5c1623f8466e4110afb3685907
|
|
Handle InputWindowCommands in SurfaceFlinger. Send transferTouchFocus from
SurfaceFlinger to InputFlinger.
Test: InputSurfacesTest.transfer_touch_focus
Bug: 120463595
Change-Id: I6592cc9ee4a77700ea191fd1ca337b91895b61fe
|
|
Change-Id: Iddd6a5bed1ea4b6e8cdeeb3f702db85a9afdee5e
|
|
Currently input window info is populated when a surface flinger transaction is applied. When
populating input window info for a layer that is yet to receive its first buffer, the window
will be invisible and not receive any input until another transaction is applied. This can
result in input being dispatched to a window beneath the target window.
To fix, populate the input window info when we latch a new buffer as well.
Test: sf unit tests+go/wm-smoke
Bug: 120839715
Change-Id: I42f9dc3a64a7af2f3359f0dfeefb57f7a3e75306
|
|
- Change the remaining references to layer size with buffer size
- Fail SurfaceFlinger::createLayer if the caller provides a buffer size and the layer is a color or
container layer
- Update Transation_test to explicitly set crop for buffer-less layers
Bug:114413815
Test: go/wm-smoke
Test: mmma frameworks/native/services/surfaceflinger/tests/ && \
mmma frameworks/native/libs/gui/tests/ && adb sync data && \
adb shell /data/nativetest64/libgui_test/libgui_test && \
adb shell /data/nativetest64/libsurfaceflinger_unittest/libsurfaceflinger_unittest && \
adb shell /data/nativetest64/SurfaceFlinger_test/SurfaceFlinger_test && \
adb shell /data/nativetest64/SurfaceParcelable_test/SurfaceParcelable_test && \
echo "ALL TESTS PASSED"
Change-Id: Ic40a2ea3e629ce774891075afaf9a4d05e95ca4d
|
|
We need to pass the computed scaling factors through SurfaceFlinger
as well as appropriately scaling the touchable region. We also need
to be careful as to which axes we scale. In the past screen magnification
has not lead to scaling of the TOUCH_MAJOR/MINOR axes, whereas whole-screen
display compatibility scaling has. We preserve this behavior by differentiating
between the global scale and a scale on any particular window. The window scale
works like the global scale used to and the global scale is only used for additional
scaling of the MAJOR/MINOR axes.
Bug: 80101428
Bug: 113136004
Bug: 111440400
Change-Id: I97d809826f86b452f28443cb1046e8bfef1bbf9d
|
|
First we move it inside of InputWindowInfo instead of InputWindowHandle
so it is part of the data sent across binder. Second we give it a persistent
identity of an IBinder token and use this for comparisons.
Bug: 80101428
Bug: 113136004
Bug: 111440400
Test: EndToEndNativeInputTest. Existing tests pass.
Change-Id: Id89a40e66887d834020f8e645fd1fb48adb7ee2e
|
|
The IBinder token is now being used as the UUID for InputWindows.
We can pass it around without the channel to avoid unnecessary FD
parcelling, duping, and other juggling.
Test: Existing tests pass.
Bug: 80101428
Bug: 113136004
Bug: 111440400
Change-Id: I8eba3fa05f249b7dfcb5c3d9817241cbfe9ab76c
|
|
Test some important scenarios for input being driven by
SurfaceControl rather than the WindowManager.
Test: EndToEndNativeInputTest
Bug: 80101428
Bug: 113136004
Bug: 111440400
Change-Id: I46b302774a19c43d12680a8b7e2bb553dfcf4175
|