Constructor of PredictionUiStateManager posts an action in 5 sec, which
may interfere with the process of opening all apps.
Waiting until the posted action happens.
Hopefully this will fix massive flakes.
Bug: 131854153
Change-Id: I6544eae1a3b063c03e78185826c05a76add1f71b
This is to ensure the task thumbnail is captured in the correct
orientation, rather than waiting until after the task pauses
which might be after the device rotates to portrait.
Also update the state to wait until screenshot is captured
before finishing the transition to home.
Test: testStressPressHome
Test: Swipe up from a forced landscape app, enter overview;
ensure task view thumbnail is shown correctly
Bug: 132687470
Change-Id: I5cd5f4b2a413628a8bdcb456e2d132c1c2da5258
Don't use OvershootParams for 0 button mode, since that interpolator
assumes the shelf is moving in conjunction with recents/app window.
Instead, use OVERSHOOT_1_2 like we do when not flinging.
Also bound the duration when entering recents, since scroller
duration could be 750ms if we are snapping to the current page.
Now we cap at MAX_SWIPE_DURATION (350ms). This case is most likely
to be hit when ending a slow swipe near the final recents scale,
since in that case duration is close to 0 and the scroller duration
is taken instead.
Test:
- Artificially always detect a pause, fling up in 0 button mode;
ensure shelf doesn't jump
- Either with the above artifical change in 0 button, or 2 button
mode, end a swipe to recents near its final scale with a slight
scroll to the right; ensure duration is 350 instead of 750
Bug: 132283018
Bug: 127783075
Change-Id: I8d5fbd0b30af21b9587fba47d141ba90b3b6e778
We had a resolved case in the past where an app's context menu didn't
open on a long click (thanks to app updates), now the menu opens, but
the drag gesture doesn't drag the icon.
Bug: 133009122
Change-Id: I45d104a92fab6556ecd937aef76f0a8147e67f56
issue 132366412
-> First, we shouldn't accept flings when the delegate has intercepted. This prevents any situation
where both are triggered.
-> Modified the slop to be the standard 8dp. This acts as a standalone fix because
it means that there are no situations where we cross all apps slop before assistant slop.
ie. in a purely vertical gesture from the corner, without this change, it's possible to trigger
all apps instead of Assistant.
Change-Id: I39e3d8a525e165024399d9802d4cc1d7ae329ee6
Calls SystemUIProxy.onGestureCompletion for a completed gesture
(either drag or fling) and passes in the velocity (0 for drags).
Bug: 132356358
Test: manual
Change-Id: I080adc401e19a6141627d1806b425056f7eefcbd
This can happen when opening an app from a folder, and then immediately
swiping up back to home.
This happens because when we swipe up to go home, there's a race condition
where the folder close animation finishes and sets the FolderIcon to VISIBLE
right before FloatingIconView sets it to INVISIBLE.
To fix it, in OverviewState#onStateEnabled we call
AbstractFloatingView#closeAllOpenViews(animate=false). Then we added logic
to cancel any Folder closing animation (which there is,
from WindowTransformSwipeHandler#onLauncherStart) and to just close the
folder right then and there.
Bug: 132588097
Change-Id: I4379431815e7cbddede5ea0213fe9323f001484b
If the centermost task is null or doesn't yet have thumbnail data,
don't use its sysui flags - continue using the window we're swiping
from instead.
Bug: 132898688
Change-Id: I202937d8aa01ee24ef01693d9594c4929e6bd314
If the second touch happens outside the swipe region, for eg when the user
is using a different gesture like pinch-to-zoom, do not capture the
input events
Bug: 132916535
Change-Id: I59df3831b96689586a2a684bf11805d42f1cb1d9
- When tasks are restored, they don't have a valid display id yet,
but they will still be started on the default display and should
have the same options until proven otherwise.
Bug: 132892578
Change-Id: I8ba0a976bd5682fbcda72ca1a98bf2517eb31312
Instead of faking recents scaling up when swiping down on a task,
actually scale it up. This is more consistent with what we do
for scaling to/from fullscreen elsewhere, and cleans up some code.
Bug: 130020567
Change-Id: I1a07813468d9a66f8f4e7b5d3d9a191b565f165c
- BackgroundAppState sets this to 1, all other states set it to 0
- QuickSwitchState extends BackgroundAppState, and calculations for
fullscreen scale/translation are moved to BackgroundAppState
- Move fullscreen progress logic out of WindowTransformSwipeHandler
and into the launcher activity controller, which uses the new
RecentsView.FULLSCREEN_PROGRESS property to animate it
Bug: 130020567
Change-Id: If6265fcce3749050be354742e7d2c418d11ee9bb
If the user drags almost all the way to gesture completion and
then flings, the haptic got triggered twice: first for the drag,
and then once the fling was registered. This checks whether the
assistant was already invoked before triggering the fling
invocation.
Bug: 132908798
Test: manual
Change-Id: Ibeed7279b8db32527490a0e11b8e5f0761187bbf
This ensures that they do not fight for the space. This is intended to
be iterated upon as we find solutions to some of the technical
challenges in the current POR.
Change-Id: I831e8797b16f28fe2cd742c96e9b7c916abf77a5
TreeHugger Robot