| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
| |
Before: https://screenshot.googleplex.com/iw6baTCfoy2.png
After: https://screenshot.googleplex.com/8CcsQvLhYDo.png
Desired: https://b.corp.google.com/action/issues/139551306/attachments/26925873?download=false
Test: Examined before and after padding and verified 3-button is unaffected.
Fixes: 139551306
Change-Id: Ia416399cf25e7c6c2fb8aa84ad20e7ad74dcd31b
|
|
|
|
| |
Change-Id: I44bca49b8adb6fa22c3b48d10f674e42c28d792c
|
|
|
|
|
|
|
| |
set of person
Bug: 132336512
Change-Id: I975524e28168c10a186cdc24b188c161faf433cf
|
|\
| |
| |
| |
| |
| | |
am: 84fa94e2fc
Change-Id: If9a5d88062addbd09909e04ef5c2c59e7e5488a7
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Test: manual
Bug: 137953006
Swipe from workspace:
07-30 15:15:44.031 9779 9779 D UserEvent: action:FLING direction=UP direction=UP
07-30 15:15:44.031 9779 9779 D UserEvent: Source child:WORKSPACE id=0 span(951,1313) parent:WORKSPACE id=0
07-30 15:15:44.031 9779 9779 D UserEvent: Destination child:ALLAPPS
07-30 15:15:44.031 9779 9779 D UserEvent: Elapsed container 826 ms, session 9361 ms, action 0 ms
Swipe from hotseat:
07-30 15:15:46.010 9779 9779 D UserEvent: action:FLING direction=UP direction=UP
07-30 15:15:46.010 9779 9779 D UserEvent: Source child:HOTSEAT id=0 span(786,1908) parent:WORKSPACE id=0
07-30 15:15:46.010 9779 9779 D UserEvent: Destination child:ALLAPPS
07-30 15:15:46.010 9779 9779 D UserEvent: Elapsed container 1139 ms, session 11339 ms, action 0 ms
Change-Id: I959528889fda778efc569bb59e7f44d3bd5b81bc
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
and displays system shortcut when long click on deep shortcut.
In this CR we
1) for each shortcut, we filters the notifications to ensure we only
get notifications with identical shortcutId.
2) allow system shortcut to be displayed when user long click on a
DeepShortcut
Bug: 132336512
Change-Id: Idc9eaed55e900ed4027a43ee9c3fd7dc6f4480b2
Merged-In: Idc9eaed55e900ed4027a43ee9c3fd7dc6f4480b2
|
| |
| |
| |
| |
| |
| |
| |
| | |
same shortcut id
Bug: 132336512
Change-Id: Iddf4cfe8ad60c12e8de8b171bed392f1bb0a6761
Merged-In: Iddf4cfe8ad60c12e8de8b171bed392f1bb0a6761
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
and displays system shortcut when long click on deep shortcut.
In this CR we
1) for each shortcut, we filters the notifications to ensure we only
get notifications with identical shortcutId.
2) allow system shortcut to be displayed when user long click on a
DeepShortcut
Bug: 132336512
Change-Id: Idc9eaed55e900ed4027a43ee9c3fd7dc6f4480b2
|
| |
| |
| |
| |
| |
| |
| | |
same shortcut id
Bug: 132336512
Change-Id: Iddf4cfe8ad60c12e8de8b171bed392f1bb0a6761
|
| |
| |
| |
| |
| | |
Bug: 137568159
Change-Id: I4d8bb5c01cabe642731ebd3f57fe15bdc5a569b7
|
|\|
| |
| |
| |
| |
| |
| |
| | |
of hardcoding it to 16ms" into ub-launcher3-qt-r1-dev
am: b7094fcf36
Change-Id: Icd4e52b33b33718cb91b2fd082d85637e820390f
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
hardcoding it to 16ms
> Creating a utility class for caching display property changes
Bug: 128940249
Change-Id: I6f9a214548de65bd1c8530508d665ee88312da4a
|
|\|
| |
| |
| |
| |
| | |
am: c8d496fe00
Change-Id: I7d764152d5d9da8c9df8db479dd01683d9e6148a
|
| |
| |
| |
| |
| |
| | |
Bug: 137836033
Change-Id: Ifc8ce867abd85eaeacd09a2b39636ecc4109c046
|
|/
|
|
|
|
| |
This makes DeepShortcutManager thread-safe and avoids any locks
Change-Id: If4593b3541da6259591ff7a607efa58158006481
|
|
|
|
|
|
|
|
| |
Waiting for touch interaction service; waiting for package-restart
events.
Bug: 136215685
Change-Id: I0c31c09fe3a58b898168dfdb4e4d23757b94a47c
|
|
|
|
|
|
|
|
| |
tasks
BackgroundExecutor is also using thread pool executor where the order is perserved
Change-Id: Ieef8825599f35fe22da3e9adb1270c5525449d62
|
|
|
|
|
| |
Bug: 135038270
Change-Id: Ie0af9c7d47f69b32caedd72f98ed1706bdbef5fa
|
|
|
|
|
|
|
|
|
| |
- Defer starting the activity when an activity is paused, and finish
the current animation to trigger launcher to be resumed
Bug: 132811175
Test: Swipe up and launch a new app
Change-Id: I78b76800052512eb93f69ccf0523f4d752a82ece
|
|
|
|
|
|
|
| |
Bug: 132461400
Test: Manual tests
Change-Id: Icee3730454db8129e597714c147c2cbaddc70987
(cherry picked from commit 219208a0f53e8d5f613b9d197cf4072685dd9c0f)
|
|
|
|
|
|
|
|
|
|
|
| |
- Peek in overview further, and with more overshoot
- Fade out and scale down workspace faster while swiping up
- Scale and translate workspace slower when letting go to enter
overview (so it doesn't zoom out at warp speed)
- Fade in all apps shelf sooner
Bug: 132455160
Change-Id: Ieafad0ccf9bb587889bc35d536627661db10e358
|
|
|
|
|
|
|
|
| |
When quick switching from home or overview, go to OverviewState if the
task launch failed. Otherwise we get stuck in BackgroundAppState.
Bug: 135038270
Change-Id: I42785c261cef0df95666bc106ec5ca6ef0553cc7
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When ending in recents, we reapply the state - therefore, it's important
to make sure we are in OverviewState before onSwipeUpComplete(). This is
done by mLauncherTransitionController, which sets OverviewState on end.
We already force mLauncherTransitionController to end before calling
onSwipeUpComplete(), but in this case we were calling cancel() and
setting mLauncherTransitionController = null, which meant we could never
call end() on it. Instead, we should always call end() if we set it to
null.
Also ensure mLauncherTransitionController is created even if the gesture
is completed, if an existing controller isn't already running. This can
happen if you swipe up quickly enough that we get onGestureEnd before
launcher is drawn, and in that case we still want the launcher component
to animate once its ready. This is even more important for 2-button
mode, because again, we rely on mLauncherTransitionController to set the
state to OverviewState before we reapply it.
Finally, clarified some methods by renaming "swipeUp" to
"swipeUpToRecents".
Bug: 132757019
Change-Id: Ieb24a4f36a39780e5d64d7bc312791608db474d1
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
System apps in Q should attempt to conform to device style, so naturally
Recents Go should also conform to this so that text changes with the
device style changing. This CL ensures all text views change font based
off system theming title fonts.
Bug: 131839392
Fix: 131839392
Test: Change device theme body font, see that change is propogated to
Recents Go app texts, clear all, and empty recents message
Change-Id: Ib85ff49383221ef18ed8aa9e53eff129129e37c2
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The recents Go app to overview transition has app scale down to a
thumbnail but normally covers the thumbnail. However, apps with
transparency will be semi-visible and will allow the user to see
the thumbnail in the back at its final size. Instead, we should fit
the thumbnail to the surface so that they both scale down at the same
time.
Bug: 132458092
Test: Go to app with transparency, scale down
Change-Id: Iaebeaaf2ddcfc86fd4f55ef9d8c3f19583947c48
|
|\ \
| | |
| | |
| | | |
ub-launcher3-qt-dev
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Hook into the remote animation API on the recents view for the
fallback recents code path. This ensures the views are attached before
attempting the layout animation.
Bug: 132112131
Test: Set separate default launcher, go to recents from app, views
animate correctly
Change-Id: Id73f18e5f864e1970f954c7ec633e25e466d832e
|
| | |
| | |
| | |
| | |
| | | |
Bug: 131360075
Change-Id: If6e3a4fbb011fc313efeb91686a9d787761862c5
|
|\ \ \ |
|
| | |/
| |/|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Navigation bar insets are not always transparent and shouldn't be used
for margin. So we put the margin back to get a bit more space from the
nav bar.
Bug: 132461256
Test: Manual test, see margins
Change-Id: Id92e8b80a0d2c18c0a603942600366e355649ea8
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This reverts commit d849ef084c180c393c7f3c69f6f00a01358a644f.
Reason for revert: not needed
I was too eager to merge this CL. It turns out all I need is these
three constants and doesn't actually need the aidl change.
public static final int MAIN_COLOR_LIGHT = 0xffdadce0;
public static final int MAIN_COLOR_DARK = 0xff202124;
public static final int MAIN_COLOR_REGULAR = 0xff000000;
Change-Id: Iafd539a06455ba0878a6d3750f3c7194f8919fbf
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Bug: 130451254
Test: make
Change-Id: Ifd66f9e53dd86d21fe66e4617cc4b209fecd7328
(cherry picked from commit 904c429b9998c96476ab5026bc04e7242d559f8d)
|
|\ \ \ |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Add logging points for launching tasks in Recents Go to match up with
non-Go Recents.
Bug: 131840601
Test: Log calls to confirm writing to stats log on task launch
Change-Id: I3d7b1ed30f99ce9f551c3481628ca81540e366b5
|
|\ \ \ \
| | | | |
| | | | |
| | | | | |
ub-launcher3-qt-dev
|
| | |/ /
| |/| |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
For users/OEMs who ship with a different default launcher, we should
provide at least a basic animation from home to recents. This creates a
simple cross-fade animation if coming from a separate home activity.
Bug: 132449252
Test: Have different default launcher, go to home, go to recents
Change-Id: I5ac7b0eedbcdf1e020c31d9cf120887a4bb3826a
|
|\ \ \ \
| |/ / /
|/| | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Fix a missing early return for when we don't have the bottom view laid
out on remote animation start.
Test: Builds
Change-Id: Iba0d5097ce59d017dc43030552f2171c5e6e4fb1
|
|\ \ \ \
| | |_|/
| |/| | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
We should not use an in-line lambda here as we allocate a new
RemoteAnimationProvider object to do so which hooks into the already
existing AppToOverviewAnimationProvider. This can be a problem if
AppToOverviewAnimationProvider overrides methods as we would not use the
overridden methods but instead the default ones.
Instead, we use the same AppToOverviewAnimationProvider object but hook
into the activity ready and window animation calls with a listener to
add on the logging logic.
Bug: 132112131
Test: Manual test; app to overview functions as before
Change-Id: Ie70541691ed420c33770d6ed4f54d9555374dc0a
|
|/ / /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
If insets are set after the activity requests the foreground scrim to be
shown, the scrim will not be correctly added. This is an issue for
fallback recents which requests the foreground scrim right after
initialization.
To fix this, we save the request to show the scrim in a local variable
and check this on inset updates to determine whether we should show the
scrim or not.
Bug: 131853975
Test: Fallback recents now has foreground scrim added correctly
Change-Id: I15a19a3184bbc97a20fbcbba2106fd7221410df0
|
|\ \ \ |
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Ensure fallback recents uses the correct layout animation by hooking
into usingRemoteAnim API.
Bug: 132112131
Test: Manual test
Change-Id: I9bb96dbf436018e5488ede0c5ca48af787180aec
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The new remote animation may start after the tasks are loaded and we
start the content fill animation. This means the layout happens after
and the content fill animation will conflict with the layout animation.
To fix this, we should only do the content fill animation after the
layout animation as intended. If the tasks load before we start the
layout animation, we should just directly update to the latest UI
without animating as the views won't be visible before the layout
animation starts.
Bug: 132381412
Test: Manual test
Change-Id: Ibb55d8ef4499260ffa4bef5c6bba605ffdc85da7
|
|\ \
| | |
| | |
| | | |
ub-launcher3-qt-dev
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
We should call dispatchFinishedWhenDone in endAnimations instead of
calling dispatchAnimationsFinished as the former will run the listener.
However, we only do this if we were running animations in the first
place.
Bug: 132285006
Test: Build and manual test endAnimations() call
Change-Id: I31afdc4c9e3ef5f56eda6178569d5c264c16ae78
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Pending animations have not started but when ending animations, we
should ensure they are set to their end values based off the
documentation for ItemAnimator's endAnimations and endAnimation.
Bug: 132285006
Test: Build using endAnimations and manual test
Change-Id: I3039a4f192d68a0ead700cd81675b3e7b4ef51f9
|
| |
| |
| |
| |
| |
| |
| |
| | |
Some of the logic in endAnimations and endAnimation is shared and should
be moved to a common helper method.
Test: Builds and functions as before
Change-Id: I4973d50ad8778bb397938b5d65d9f95f48ff145b
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
* changes:
Polish app => recents animation (5/5)
Polish app => recents animation (4/5)
Polish app => recents animation (3/N)
Polish app => recents animation (2/N)
Polish app => recents animation (1/N)
|