Debuggable reamdump data collection dialog is triggering up while
running tests. These are causing flakes. While a better fix would be
figuring out why these are triaggered, the wm tests should be
independent of internal apps which an end user of Android won't see.
Test: Forrest
Bug: 258578781
Bug: 239384214
Change-Id: Ia4c0c670fe3e35f84640787cb8fce70e74edb264
This relands commit 8dc06e5335
The Different from the original patch:
Ignore the layers of popup windows.
The original CL description:
Align the long press duration to AutomationUtils.
Bug: 257099231
Bug: 258787797
Test: atest WMShellFlickerTests:CopyContentInSplit
Change-Id: I391e0e4e71aa0ae13221ecd571e187e1c10f7c96
This CL did some refactors include:
- Make the back animation will follow these two phases to better
understand.
1. Phase 1 animation will start from gesture start, and end when
gesture released.
2. Phase 2 animation aka post commit animation will start after gesture
released.
3. When the animation is finished, make sure we could trigger the real
back behavior and notify the core.
Bug: 238475694
Test: atest BackAnimationControllerTest
Change-Id: I251b9674a4aa9965c338ccf592efaeabdcecd5e8
This enables accessibility services to take a screenshot of
a window without any overlay windows drawn on top, which is
beneficial for ML-based understanding of the visual content
in the window.
Bug: 249830826
Test: atest AccessibilityTakeScreenshotTest
Test: use in an a11y service, observe screenshots
contain only content from the requested windows
and no overlays
Change-Id: Ic886aeace9cb2984a472273858281b4f2c3a0e46
for both shell and legacy transition system.
The general sequence will be:
1. Create animation leash in core, pass to remote animation runner.
2. Remote animation finish, collect finish transaction before
transition happen. Apply finish transaction here if back event won't
trigger.
3. Check whether next transition is triggered from back gesture via
checking the open/close targets.
The 3rd step introduce another change, which to let the back transition
happen. Instead of consume next transition, we should try to find out
whether the participant was the animation target, because we cannot
assume what the opening target will do in resume stage. For example,
the opening activity could finish itself, or start another activity at
onResume, so in either case, the opening activity will become closing
activity. We can only ensure that activity will participant in next
transition.
So the more robust way should be, find out those targets which were
animated. For shell transition, and add a flag to the corresponding
change, then the transition handler can determine what to do based on
the targets. For legacy transition, ignore those targets when estimate
the transition type in AppTransitionController#getTransitCompatType.
Bug: 238474994
Bug: 131727607
Test: varify transition can be handled for some unexpected scenario:
1. launch new activity when close app.
2. launch singleInstance activity when close app.
Test: do back gesture on both shell/legacy transiton system, verify
no flicker happen whenever the back is triggered.
Change-Id: I9364be25c608f7b5797577d26b57bc7d6f2dde9c
Allows WM Shell to indicate the start/end of drag resizing, which
core can use as a signal to reuse a single (larger) surface size
for the entire drag resize operation to avoid continuous buffer
allocations after each size change.
Bug: 249808500
Test: drag resize a freeform window, verify WindowLayout requests
a fullscreen sized surface; atest TaskPositionerTest
Change-Id: I27e2b44270d7ea4f701fa8037f93b20dc691284b
Align the long press duration to AutomationUtils.
Bug: 257099231
Test: atest WMShellFlickerTests:CopyContentInSplit
Change-Id: Ic54df7aa6b0d9236728285dffea7012487ac33df
When switching to desktop mode, move home task behind visible task(s).
This ensures that only the visible task is shown at first on the
desktop.
Bug: 258282673
Test: atest DesktopModeControllerTest
Change-Id: I1d593900789846d8389decaddbaf92eb4a1d6e87
Expose list of running tasks per display from ShellTaskOrganizer.
This allows us to move desktop mode related logic out from
ShellTaskOrganizer and to DesktopModeController.
Bug: 258282673
Test: atest DesktopModeControllerTest ShellTaskOrganizerTests
Change-Id: I179c69c185153a07de3602627ed18734420abda2
- Make sure mDecorView is attached before calling its
WindowInsetsController.
- Amend modifier declare sequence for a better code style.
Bug: 258270145
Test: atest SplashscreenTests StartingSurfaceDrawerTests
Change-Id: I4d3b184252ed9516827812adfa0c76e07a6527e7
