Bug: 109698096
Test: Launch app in launcher, launch same task from overview, ensure we are
logging the same component
Change-Id: I1c34267e7d4ac6ec467fab9467001b6301ee785c
Back button changes opacity when moving the shelf during swipe up
between home screen and overview. The alpha changes depending on the
progress of the swipe up animation. When going from app to home and vice
versa, the fade animation does not tie with the swipe up progress. The
fade animation also masks the back button drawable when ime visibility
changes.
Change-Id: Idaf219923af58732715d0f0b59386dea7ab0d0ad
Fixes: 74581837
Fixes: 76900236
Test: swipe up from home screen to overview
Otherwise it could lead to parameters applied in the wrong frame,
leading to jank.
Test: Open notification
Bug: 78611607
Change-Id: Ia7900e753b29187a7a7b81f393666687e8b8e04b
Merged-In: Ia7900e753b29187a7a7b81f393666687e8b8e04b
Previously we mis-count each different activity, regardless of the app
it belongs, as one app launch. We should instead count each different
app open, either created, or brought front as a different app launch,
but different tasks created from the same app is considered one launch.
Fixes: 79885137
Test: Manual test
Change-Id: I5b4b8bee9b0ed4aa23a4ea9eefdfa112b6442455
- Allow SystemUI/Launcher to determine whether the snapshot is of a
translucent activity (to reduce overdraw by skipping drawing task
background) and also the sysui visibility flags are (to determine how
to update the nav bar while animating before the app is started.
- Fixing issue where the recents animation was reporting task fillsparent
state instead of the app's fillsparent state (as we do in normal remote
animations)
Bug: 79228291
Bug: 77984778
Bug: 78659249
Test: atest FrameworksServicesTests:TaskSnapshotPersisterLoaderTest
Change-Id: I19bdf7f780e7d94014d6a115bf84fa614b1dffa0
Refactored docked position code into PhoneWindowManager to determine
which side the docked app should go based on the position of the nav bar
in landscape (as portrait will only have top). Fixed the split screen
entrance animation for quick step's overview.
Change-Id: I30f1be9d791c23f4cd197f17487609964f78fac0
Fixes: 73250406
Test: play around with splitscreen and minimized mode
Test: atest com.android.server.policy.PhoneWindowManagerTest
All shared touch and drag slops are not static anymore but are computed
for the current system density if the user were to switch density of
device.
Test: change density and use quick scrub
Fixes: 78244075
Change-Id: If593568404c00bc1fbccd8a31379bb5fd03beefd
Access through the overview proxy to get the bounds of the secondary
split screen app when split screen is enabled.
Test: manual
Fixes: 77678123
Change-Id: Iabbcf30dc7194ac6fff9b4d7cad8a9fe5ee48a2b
Didn't work anymore since the animation refactoring. Doesn't look
like we still need it, and only causing issues with stuck
animations.
Test: go/wm-smoke
Test: Dock task from recents
Change-Id: Ibb3543d15f42fc7689c3ad705aee693eba93e8b7
Fixes: 77993227
Also fxing some wrong thresholds being used for slop comparisions
Test: Verified on device
Bug: 78232923
Change-Id: I0b10a921002f2e45d0d2472a3e690d1526f4aecb
Bug: 77747389
Test: Manual, create work profile user, create an apk with an icon resource
in its task description, and ensure that launcher can load the icon.
Change-Id: I33c7eaca9481fe44440b4b584b64531835e2fe9e
On some devices it's very likely that we fall into GL comp during
app transitions. However, SF offsets are chosen in a way such that
the time to finish a frame is just too tight to be completely jank
free when hitting GL composition in SurfaceFlinger. Thus, we
introduce the concept of a separate early offset, and wakeup
SurfaceFlinger at that time if we think that hitting GL comp is
likely, or we already hit GL comp in the last frame.
Test: Open app, check vsync offsets in systrace
Test: Open many dialogs/apps to fall into GPU comp.
Bug: 75985430
Change-Id: I461fdcd573583f3ea0348c8b23cc9945d33f8976
