Now that we don't show DWB toast for negative remaining time
Bug: 127689526
Change-Id: I3ced3ec0da9bd7b09df9b66b4ef608e87339573f
(cherry picked from commit e921bacfb8)
Contexts were added for better diags when an assert happens, but they
are also useful for tracing the test execution.
Change-Id: I1512f3f7e02a373096bab4f0b390b1febfc96334
(cherry picked from commit 77ca70fea6)
It's the presence of the context menu if we long-press a shortcut, and
the drop target bar if we press a menu item.
Change-Id: Ic02462fa766e23b74f41b8a73fefd519aea08407
(cherry picked from commit e77fc83222)
Bug: 129785904
Test: Try to swipe up with various sysui states enabled
Change-Id: I654e0efd1f29ee6b4123e7f8aa717f62a55fdb50
(cherry picked from commit f0625fd93a)
Bug: 129785904
Test: Manual, change states and verify state is sent
Change-Id: Ia1f69494a6cbae68085fb09670ffa309ce147430
(cherry picked from commit c4b88c3dfb)
This allows us to revert the change that fades in the shelf during swipe
up in 2 button mode, since the shelf doesn't show up until the window is
out of the way anyway.
Bug: 129746879
Change-Id: I929d8095989f9eae32d71b5bc3f67997e9df4ba0
For the app open animation, we load the adaptive icon on the bg thread.
When the icon is done loading, we swap the og view with the FloatingIconView.
If the icon loads after the animation is done, we still set the og view
to INVISIBLE and it never gets restored since the animation is already done.
To fix this, we do not swap the views if the animation has already ended.
Bug: 130245920
Change-Id: I5cf85de4e2c533da8c395a23899980d27a941e1b
There's an edge case where user isn't unlocked even if device is. In
that case, we still need to use DeviceLockedInputConsumer because
variables needed for any other input consumer aren't initialized until
the user is unlocked.
Bug: 129947426
Change-Id: I33a5e9a8d5c4266d45bd0d5a16657fa3c9644a1f
The autority of the provider should be set in secure settings:
launcher3.layout.provider
Bug: 127987071
Change-Id: Iccf2960aa6c0a5a8ff9621b13d8963d9daecb993
- Don't allow back gesture at all whenever we hid back button before
- Exclude RecyclerViewFastScroller thumb rect
Bug: 129297464
Change-Id: I40a33697592b02619218c18d1b3def7c3c203f56
It's no longer necessary, and causes issues when trying to scroll
a PagedView that only takes up the bottom half of the screen (e.g.
RecentsView in split screen mode).
Bug: 126606858
Change-Id: I117dfe9416cdeef1247d6e783390cf5c391e8254
More specifically, any window (e.g. qsb search) or AbstractFloatingView.
NavBarToHomeTouchController now implements TouchController directly instead
of AbstractStateChangeTouchController, as it not only dealing with
launcher states. This makes it easier to override intercept logic to
handle cases like not having window focus, for example.
AbstractFloatingViews can createHintCloseAnim() to play an animation
hinting that it is about to be closed by swiping up. Widgets sheets use
this to pull back similar to the all apps transition to home.
Bug: 129976669
Change-Id: Ie157b978d9f1ee36d5fd32cea72ec02ce40878c0
SecondaryLauncher crash after change material source.
From the error log the style of this component should be
Theme.MaterialComponents or as descendant.
Change theme parent to fix it.
Bug: 130151609
Bug: 130182878
Test: atest MultiDisplaySystemDecorationTests
Change-Id: Iad2817864326b04fac00bfc57b8ab6eaf2bd9c13
vadimt
Beth Thibodeau
TreeHugger Robot
Hyunyoung Song
Winson Chung
Tony Wickham
Jon Miranda
Sunny Goyal
Tracy Zhou
wilsonshih
Bill Yi