Launcher can now receive onTaskAppeared callback from
RecentsAnimationController to get remote animation target when in quick
switch mode.
Note: This CL just demonstrates how to receive callback and then
calling removeTask & finish recents animation,
in order to really improve quick switch flicking, launcher side needs
to implement the rest of logic to animate task's remote animation target
to make task switching more smoothly.
Bug: 152480470
Test: WIP
Change-Id: Id0371db7339cfe84942cc905a89b0a2c1fab62ec
- Always just fetch the tasks that will end up in recents
Bug: 152133859
Test: Manual, swipe up with pip/assistant and verify nothing
changed
Change-Id: I41719e111cba85da7e93f65681b7b50b4c5c4a46
(cherry picked from commit 8e714d42ae)
- Whenever the delegate consumer sets itself as active, it will cancel
the base consumers which can cause onConsumerInactive() which will
clear the active consumer. Instead, we should only clear the active
consumer, and in the case where isConsumerDetachedFromGesture() is
checked, only check the active consumer before resetting.
ie.
base ic (detached) -> on touch up (do nothing) -> onConsumerInactive (active == base) -> reset
base ic (detached), wrapped ic (active) -> onConsumerInactive (active != base) -> on touch up (active == wrapped) -> reset
base ic (detached, active), wrapped ic -> on touch up (do nothing) -> onConsumerInactive (active == base) -> reset
base ic (not detached) -> on touch up (active == base) -> reset
base ic (not detached), wrapped ic (active) -> onConsumerInactive (active != base) -> on touch up (active == wrapped) -> reset
base ic (not detached, active), wrapped ic -> on touch up (active == base) -> reset
Change-Id: I2d623c501d9c9799dadcf2005f34e1e0062c113f
- Update existing arrow bounce animation to repeat 3 times,
and play it when swiping up from nav bar on first home
screen as well as when tapping the arrow.
Bug: 151768994
Change-Id: Ib120764fdeab6cd932018b6fed8b1093dda20641
- Change drawable to match specs, using ShadowDrawable to
add shadow when necessary based on workspace theme.
- New drawable is 18dp by 6dp; add support for different
width vs height, and decouple from workspace page
indicator (which is still 24dp tall).
Bug: 151768994
Change-Id: Icfd0eac197ebc4d1f5bb799f8538c4bd99d800cd
Adds the back gesture panel directly to the fragment
View hierarchy rather than a separate Window.
Bug: 148542211
Change-Id: I196a72d29217308a5bdb78fdcff1face5d475379
Slight revert of ag/10668129 with adjustment
of disabling it for tests.
Fixes: 151456795
Test: Ran the labtest command for OOP
tests for crosshatch (where this issue
was first detected)
Change-Id: I315d138c2e4a6d4068304e9b5fb2e1b7feb34e63
Bug: 144953948
Bug: 137777105
The new lite proto builder is used to send two types of logging to statsd
1) Snapshot logging
2) App launch, task launch, task dismiss
Statsd will be connected once platform CL is submitted
Change-Id: If606cee5288fe4bd6c522605ae84eb0f24174f5b
Before, we did this by extending the window/launcher animation to
match the scroller duration. But now that we are using springs to
control the scroller, that duration is not really accurate. So
instead, we now let the window/launcher move at its own pace, and
wait for both that animation and the scroller to finish before
calling onSettledOnEndTarget().
Bug: 147302669
Change-Id: I37a9dd3eea17ebe663c33c3a4478b1b53a63dcc2
- When we have multiple wrapped input consumers, mConsumer will be
set to the wrapper while the caller can actually be the input
consumer being delegated to (ie. other activity ic). So we should
clear the consumer state if the caller is anywhere in the IC
hierarchy. This results in a separate issue where mGesture
could be cleared during onConsumerAboutToBeSwitched() before being
passed to the new consumer, so make a copy of the previous state
just for passing to the new consumer.
Bug: 152318829
Change-Id: I4afcef5b18aa772889e9104f3977887893f174ea
It also turned out that Pilfer event seems to come in a
non-deterministic order relative to the events from the Main and TIS
sequences. So I moved it to its own sequence.
Change-Id: Ie4ea5865afd900bebbd8287dad2372c94dce8ad5
Unlike isStarted(), mHasLauncherTransitionControllerStarted is true
even after the animation has ended. Once it's ended, we shouldn't
continue updating it even if window shift is still changing.
This can happen when springs are enabled, as that can increase the
recents scroll duration beyond the window/launcher animation
duration (and we updateFinalShift() when the scroll changes).
Test: quick switch by swiping up and over at angle, or really hard
directly to the right, to engage the springs long enough to have a
few frames where you can notice the flicker before this change.
Bug: 147302669
Change-Id: I6a38662612de91352c0f956e6a3137f6c24eba66
lumark
Becky Qiu
Vinit Nayak
Winson Chung
TreeHugger Robot
Sunny Goyal
Matt Casey
Tracy Zhou
Tony Wickham
Andy Wickham
Adam Cohen
Samuel Fufa
Hyunyoung Song
Sreyas
vadimt