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
Test: go to overview from home and vice versa in 0 and 3 button modes,
ensure QSB fades at the same rate as the rest of workspace
Bug: 154637581
Change-Id: I2f15aaf2ba59e6b1d4754060e7b3005bed5db9c7
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
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
Whenever device rotates, we notify sysui to hide/show
the back gesture if the foreground app also rotates.
We also notify sysui when device rotates to match
the orientation of the current foreground app (this
is for apps with fixed rotations).
Fixes: 154580671
Test: Created test apps of different rotations
and ensured that back functionality was present when
attempting to go back.
Change-Id: I33a71698411d9bc2416b6660f8dbd53233628917
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
With b/150232615, we will need an explicit value set for the exported
flag when intent filters are present, as the default behavior is
changing for future versions. This change adds the value reflecting the
previous default to the manifest.
These changes were made using an automated tool, the xml file may be
reformatted slightly creating a larger diff. The only "real" change is
the addition of "android:exported" to activities, services, and
receivers that have one or more intent-filters.
Bug: 150232615
Bug: 158198882
Test: TH
Exempt-From-Owner-Approval: mechanical refactoring
Change-Id: I083a7bcab968c881f7cdff7152a249691ffac316