Screenshot: https://screenshot.googleplex.com/TckWKGYWwHW
Note: Shortcut predictions will not be cached.
Bug: 159500320
Test: Manual
Change-Id: Id8ec81544bddb8be87a5e748fd9f9e93aaaf8fea
It flakes when one of the tests starts calculator while there zero
activities in the system.
Bug: 143488140
Change-Id: Id9d350f0de8a83eb50e35e9efa4226b8d45ca641
This is a workaround until we can support app transitions when starting
an activity in mw mode.
Bug: 158613217
Change-Id: I843d6669722c543728ab532e1c4fbd4643f6f135
- Reverts change from ag/11900651 that deferred setting
mRecentsViewScrollLinked = true
- Instead, setCurrentPage(mCurrentPage) after updating layout rotation
to ensure we recompute page scrolls before using them
Test:
- Auto rotate on, home rotation off, open Calculator in landscape,
swipe up slowly and ensure it never turns invisible
- Quick switch from Calculator to Clock, start swiping directly up
immediately after settling on Clock, ensure Calculator window
remains at its scroll position to the side (b/159461591)
Fixes: 159461591
Change-Id: Iab92963cc6c33df42b77f5ccfa3932382e8f869a
Sends AppTargetEvent with action launch and container CONTAINER_OVERVIEW to AppPredictor when user launches app form recents.
Bug: 155996363
Test: Manual
Change-Id: I3eb38f5737ecaeb07e59db460e8d809416132825
> Using common code for Launcher and recents for insets dispatching
> Fixing recents auto closing when there is no running task
Bug: 158750568
Bug: 159133601
Change-Id: Iee25c603a77a1ac546ada1840f3afaf5797b8802
Feedback wasn't working, also Share wasn't showing its preview.
Bug: 159122067
Test: built and run locally
Change-Id: Iccea012a8fc0009a6a980f6233f42c4e7619f4ec
Sometimes other methods modify things like icon scale that setting
the fullscreen progress should override.
Test: open Calculator, open Clock, quick switch to Calculator and
ensure its task icon is not showing
Bug: 157105795
Change-Id: Iaed3e42f540fdff3648e9db7e6d7dc0b0d0a75df
- This was only used in RecentsView#resetTaskVisuals() anyway
- Previously resetVisualProperties() just called resetViewTransforms()
plus setFullscreenProgress(0) and setModalness(0)
- The latter 2, specificially setFullscreenProgress(0) led to problems
such as the bug below. Instead, we should reset to the current
mFullscreenProgress and mTaskModalness.
Bug: task view sometimes shifted up during quick switch
Steps:
- Do the quick switch gesture very quickly
- At the start of the gesture, we call getTasks(), which calls
applyLoadPlan() asynchronously
- applyLoadPlan() calls resetTaskVisuals(), so if this happened
after the gesture ended, we would setFullscreenProgress(0) on all
the task views, hence the upwards shift (if the gesture was still in
progress, it would reapply the real fullscreen progress)
Fixes: 157105795
Change-Id: Idb9d91ff89701d726838b47f955d4300f5ef13bd
ModelTask posted in setupViews does not get called.
Bug: 159151258
Change-Id: I45bfe7cf8ea18b09faaf3c0e612be90722e1e410
(cherry picked from commit 345f728f2c)
- If a user has mostly predicted hotseat, show a snack bar. otherwise, show migration option.
- Guard onboarding activity with permission `com.google.android.apps.nexuslauncher.permission.HOTSEAT_EDU`
Bug: 158569583
Test: Manual
Change-Id: Id0c1c812233fcf288a2f49848720199dedd2015d
Also fixes bug where user continuously swipes to hint view causes count
to increase more than the max count which prevents all apps edu from showing.
Bug: 151768994
Change-Id: I3186398d441e723a2cfb6e396b03944502a65cf5
The first time a user long presses a predicted icon, suppress drag/drop and show a snackbar about app predictions.
Bug: 159170242
Test: Manual
Change-Id: I5f853a9774b38ad9fad22ff55feff417a801f52c
> Adding tests for TaskViewSimulator to ensure proper calculations
> Disabling orientation listener while user is interacting with quickstep
Bug: 158781568
Bug: 156891776
Change-Id: I299c3b1243ac0dbf28faee1b8566c77ea3954e33
Verified window is moving as expected using winscope.
Note: Position is off when launching non-center task.
Bug: 159171509
Change-Id: Ib11ed7df9a877348d76543279203f9bfc25f7829
eEarlyWakeup flag is used as a hint to SurfaceFlinger to adjust its
offsets so it can wakeup earlier and have sufficient time to compose
more complex scenes.
This flag has been replaced with explicit start and stop flags which
ensure the SurfaceFlinger offsets remain consistent during animation.
WM will now set the flags so this change removes use of the deprecated
flag.
Bug: 158127834
Test: go/wm-smoke
Test: systrace to verify new tracepoint and offset behavior
Change-Id: I680d680525482ed61ae38289076bb4213aeb1722
