Doc: go/hybrid-hotseat-tips
Issue 157683315: for fully populated hotseat, count returns to home screen and show discovery tip if Tip action was not tapped.
Issue 158301717: Don't use cached items if client has predicted items.
Test: Manual
Change-Id: I4747a1148caa62a6262fb6592d5185bdf216ede6
Bug: 156692295
Test: Swipe up from an app that has a HUN and ensure tapping on the
HUN (or anything that can restart the activity) will start the
activity while the recents animation is still running
Change-Id: Ia1fbd9cfb21aa64b3c8a0d431ba2d9824ee4c0a1
Doing this at the root instead of individually for all added
animators ensures none fall through the cracks.
Fixes: shelf moving too quickly in 2 button mode
Change-Id: I0de1ba9cee3fb8f1d6161371625d97e4b2305129
There's a race condition between when
the flag is read and when it gets set,
and not registering the listener that
the flag is gating can result in a lot
of bad rotation state.
Fixes: 158592847
Change-Id: Idd78e15669698bb0d057d0b6661ea69bfa5c8202
The problem is that in prepareToAnimate, we set the scrim sysUiProgress to 1.
When we call setScrim(Background) we create an animator to set sysUiProgress
to 0 with a duration of 0. We expect this to set sysUiProgress to 0 prior
to the next animation setScrirm(Normal).
When we call setScrim(Normal) we want to animate sysUiProgress to 1, but it
is still 1 since we haven't actually run the setScrim(Background) animation
(we've only added it to the list of animators). Therefore we don't create an
animator at all since the target is already at the final value.
Bug: 158148281
Change-Id: I8ca7ef00fc8a7dad6813c285ead60f5db15939b6
Tapping task icon will now show the scrim for rest of thumbnail and not snap to page that is already snapped to.
Pressing task icon from clear all will scroll to the page.
Bug: 158004853
Change-Id: I79d0a4ac5be3641c6bdf71c34dcbf136ddbbebd1
The actual task insets aren't used for display, so to make the
transition line up, use scaled ones.
Bug: 154524544
Test: local
Change-Id: I0f484e6dbf13a558c042f84aa68f1d6e9c23b328
Seeing bugs come in where display rotation value
is incorrect, correcting the check to only
exclude frame rate change flags since multiple
bits can be set.
Fixes: 158383147
Change-Id: If6cdd2c10bf80024ac655451b957034ed84684a7
This reverts commit 4dfcbec512.
Reason for revert: Fix the margin issue by handling the bottom
insets ourselves.
Change-Id: Ic01cadbbe847e419af8bb444ad57764e719152c3
3 Button overview orientation wasn't
getting set, but working because of the sensor.
Now we set orientation when entering overview,
and reset to rotation 0 when exiting overview.
Also fix related bug in RecentsOriented state
where we weren't updating the current sensor
rotation with foreground app orientation.
Fixes: 157069195
Change-Id: Ide1b7dbeb68aeaf6a3c45f7260595f69f4813d94
This reverts commit 160ca4b8a2.
Reason for revert: Got issues like b/158318606 when switch nav modes, also the margin seems not set properly. And this doesn't work for 3 button mode too. Would switch to just use task menu for all.
Change-Id: I645f2a2a9032ae99799c75bcc6c983c1bbfd8df8
- Until we update the fullscreen params, the tmp params have no radius
so in cases where a new task is created while overview is open, or if
we go to overview from home immediately after starting launcher for
the first time, there would be no corners
Bug: 158050383
Test: Kill launcher, swipe up to overview, ensure tasks have corner
radius (if device supports it)
Change-Id: I6b72c1a401b9203da3acffc88578c1ed743c8f68
FullscreenDrawParams.scale is caculated relative to TaskView matrix, but drawnInsets is
based on Thumbnail matix calculation, so the scale should be applied first, such that
dranInsets and other TaskView translations have the same base matrix
Bug: 157626483
Bug: 156268804
Change-Id: Id33c7db9a71dd001a41c66ddf07834791d0bd382
Samuel Fufa
TreeHugger Robot
Winson Chung
thiruram
Becky Qiu
Tony Wickham
Vinit Nayak
Zak Cohen
Hyunyoung Song
Vadim Tryshev
Jon Miranda
Sreyas
Sunny Goyal