- When the launcher activity is killed, the next init will attempt to
create a sync applier, which uses the ViewRootImpl of the target
view. But when onActivityInit() is called, the recents view has not
been attached to the hierarchy so the view root is not accessible.
The SyncRtSurfaceTransactionApplier also ignores scheduling all
updates when it has a non-existant view root, which leads to the
app surface getting stuck midway during a swipe up (only affects the
duration of the animation)
Bug: 119661847
Test: adb shell am force-stop com.google.android.apps.nexuslauncher
then try and swipe up slowly
Change-Id: I8eef9fe38c55c0cb438d63b41c335f78679278a3
The size of the window changes during the animation progress, making the
window look rounded for longer. What we want is to animate it from the
shape of the icon to the shape of the display.
Change-Id: Ib4889b697bf78cdc37c160130fde961650080fb7
Fixes: 120553563
Test: visual
Fixes:
- Windows too round during launch animation
- Radius not matching window when swiping down
Test: visual
Bug: 120553563
Change-Id: I20ac56ac21c196c2f599b8b45af1e3c072ee59f0
Navigation bar can show on non-default display now. So the caller
should specify which display the desired navigation bar is on.
Bug: 117474929
Test: atest Launcher3Tests
Change-Id: Ibb22e51730ab145a42a129b4d964299acd4efd56
(cherry picked from commit f1bb3a4d4c)
Test: Manualy launch an app
Test: Press home when activity is on top of the stack
Test: Quick scrub
Test: Swipe up on the home button, swipe down
Bug: 111514493
Fixes: 116745318
Change-Id: I66d25bc433061ede46107ea9651c198614306692
(cherry picked from commit faa443308e)
Navigation bar can show on non-default display now. So the caller
should specify which display the desired navigation bar is on.
Bug: 117474929
Test: atest Launcher3Tests
Change-Id: Ibb22e51730ab145a42a129b4d964299acd4efd56
Previously we were comparing the controller's progress at the time of
the end of the animation... which is always 1. Instead, we should be
comparing the effective final progress based on the interpolator.
Change-Id: I18110b5a3b914839860931187f39cfa11182b3e2
Using View#getDisplay().getDisplayId() into
IWindowManager.overridePendingAppTransitionMultiThumbFuture()
for multi-display support.
Bug: 119530958
Test: manual
Change-Id: Icde73b2545f879771a62030c8151a86a324fa593
(cherry picked from commit 233622d907)
Test: Manualy launch an app
Test: Press home when activity is on top of the stack
Test: Quick scrub
Test: Swipe up on the home button, swipe down
Bug: 111514493
Fixes: 116745318
Change-Id: I66d25bc433061ede46107ea9651c198614306692
No UX spec is ready, so using some placeholder layout.
No attention to string localization since I feel that strings may
change, compared to current mocks.
Not using remaining-time API, as it is not ready.
Bug:118319143
Test: Manual
Change-Id: I50cff9099677db543e95963f058d3e89eab07d8f
Using View#getDisplay().getDisplayId() into
IWindowManager.overridePendingAppTransitionMultiThumbFuture()
for multi-display support.
Bug: 119530958
Test: manual
Change-Id: Icde73b2545f879771a62030c8151a86a324fa593
When the developer option for freeform is enabled, provides
a "Freeform" option in the recents task overlay menu. This
is sort-of an analog to the freeform option in N recents;
however, since recents now is part of home, there's no
straightforward way to have multiple freeforms at a time,
so this really is only useful for developers.
Bug: None
Test: manual - enable freeform in dev settings, then pick
Freeform from recent task overlay menu.
Change-Id: I5d8e95aaffb8fe43e655f705cacdd51859c95d3b
(cherry picked from commit 9beb6bf251)
Winson Chung
Lucas Dupin
TreeHugger Robot
Vadim Tryshev
Bill Yi
Tiger Huang
Tony
lumark
Sunny Goyal
Evan Rosky