summaryrefslogtreecommitdiffstats
path: root/quickstep
Commit message (Collapse)AuthorAgeFilesLines
* [DO NOT MERGE] Fix some visual jumps when swiping homeJon Miranda2020-03-092-1/+10
| | | | | | | | | | | | | | | | All caused by running the transform progress from 0 to 1 instead of starting at whatever the progress was before ending the gesture, e.g.: - When swiping to home without animating into an icon, the corner radius was set back to the window corner radius. - Before this change, the clip didn't update throughout the animation, making the window slightly bigger than the floating icon view; after this change, the clip jumped to show the insets again before clipping back down during the home animation. Partial backport of ag/Ie48f4b665a5bf3cbef76bdf7f043febe99fb84a0 Bug: 150680980 Change-Id: Ida65097f0ef7d2e11d48b84ecdd353ef89078015
* Merging from ub-launcher3-qt-future-dev @ build 6048032Hyunyoung Song2019-12-0613-129/+680
|\ | | | | | | | | | | | | | | Test: manual, presubmit on the source branch http://x20/teams/android-launcher/merge/ub-launcher3-qt-future-dev_6048032.html Change-Id: I74059dbc75a8530884f8b4f67917b83c75f32d14 Merged-In: Ieee38cc301364f96cf252b2387142b0aa1b75317
| * Merge "Fix quick switch from home biased towards returning home" into ↵TreeHugger Robot2019-11-221-3/+14
| |\ | | | | | | | | | ub-launcher3-qt-future-dev
| | * Fix quick switch from home biased towards returning homeTony Wickham2019-11-201-3/+14
| | | | | | | | | | | | | | | | | | | | | | | | When flinging up and to the right, we previously always returned home. Now, if the right velocity is stronger, we quick switch. Bug: 126596417 Change-Id: I14fa0584399bb90f2e07e0b296fc5932d8224fbf
| * | Fix bug where icon remains invisible after returning home.Jon Miranda2019-11-213-40/+6
| |/ | | | | | | | | | | | | | | | | | | | | | | - The bug is caused by cancelling of the RectFSpringAnim before the StaggeredWorkspaceAnim has started. - Instead of having logic in StaggeredWorkspaceAnim control the visibility of the icon, we instead maintain all the visibility within the FloatingIconView class itself. Bug: 142120338 Change-Id: I94f3a066d395f9c3b97dc6ee9fc836e9401650a5 Merged-In: I082291ca9b288f57701cc00d61a9b3a84da8b084
| * Merge "Fix recents scale sometimes lagging behind window scale" into ↵TreeHugger Robot2019-11-202-7/+2
| |\ | | | | | | | | | ub-launcher3-qt-future-dev
| | * Fix recents scale sometimes lagging behind window scaleTony Wickham2019-11-202-7/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We were previously offsetting the launcher animation progress based on when we got onGestureStart, which meant it would lag behind if onGestureStart came late. Now that we track the window instead of the launcher shelf, and we don't show the launcher animation right away in fully gestural mode anyway, we should remove this to ensure the launcher part of the animation always lines up with the app window. We also reapply state whenever predictions are enabled, e.g. when launcher starts after being force stopped, and previously this was canceling the existing state animation. We don't want to do that because predictions can be enabled at any point on a cold start, and cancelling the existing state animation means that RecentsView shows up in fullscreen and not attached to the app window for the duration of the gesture. Bug: 144454486 Change-Id: I65a2c71c9acd2f5345941ea2cff7d32c04b7be3f Merged-In: I65a2c71c9acd2f5345941ea2cff7d32c04b7be3f
| * | Improve quick switch from home by tracking both x and y motionTony Wickham2019-11-149-41/+535
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | - Add NoButtonQuickSwitchTouchController which uses BothAxesSwipeDetector to track horizontal and vertical motion. - Initially, we only detect swipe left to right to quick switch (like before), but then we allow swipe up to either go to overview (if you hold) or back home (if you don't hold). - xDisplacement transitions non-overview components out (e.g. shelf and workspace), and translates overview in. - yDisplacement translates overview up and scales it down Bug: 126596417 Change-Id: Id679ad84c08246e205c667a78ed5df00d7276258 Merged-In: Id679ad84c08246e205c667a78ed5df00d7276258
| * | Move shelf peeking anim code to ShelfPeekAnim classTony Wickham2019-11-145-46/+131
| | | | | | | | | | | | | | | | | | Bug: 126596417 Change-Id: I5ba501b04b3eaf12a20ba1312ef362f9734761c3 Merged-In: I5ba501b04b3eaf12a20ba1312ef362f9734761c3
* | | Merging from ub-launcher3-qt-future-dev @ build 6018744Hyunyoung Song2019-11-2065-401/+1378
|\| | | | | | | | | | | | | | | | | | | | | | | Test: manual, presubmit on the source branch http://x20/teams/android-launcher/merge/ub-launcher3-qt-future-dev_6018744.htmlMerge commit '9353b00616ac688d2df6b9f8513c4895bb4119d7' into merge_ub-launcher3-qt-future-dev_6018744 Change-Id: Ie6235a262b7bba0aa9f2a2962a7aa499a0a2cb53 Merged-In: I8a1e20d0b175f03a1a05c81749f07ab5314e872a
| * | include predicted_rank in app launch loggingPinyao Ting2019-11-135-3/+80
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Test: 1. . build/envsetup.sh && tapas NexusLauncher 2. ccdebug && cclogcat 3. launch from workspace any app that is also in predicted apps 4. verify in terminal it has correct predicted_rank Bug: 143855018 Change-Id: I07a62f07057537a6c09384cf944bbc5aa5888d22 Merged-In: I07a62f07057537a6c09384cf944bbc5aa5888d22
| * | Scaling down hotseat to match prediction row size when going to overviewSunny Goyal2019-11-066-24/+76
| | | | | | | | | | | | | | | Bug: 141265005 Change-Id: I3b11146881af334508f553e4ca3a36b9291511d9
| * | Forces OveriewInputConsumer to be used when Assistant is running on top of ↵Andy Wickham2019-10-295-27/+81
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Launcher. Previously it was using OtherActivityInputConsumer, which got things in a pretty weird state (e.g. most recent app would appear in the center as if it was the active app when you started Quick Switching, etc.). By default (toggleable by a feature flag), OverviewWithoutFocusInputConsumer is used because Assistant doesn't seem to respect the CLOSE_SYSTEM_DIALOGS broadcast, at least in half-shelf mode. In this case, the Home intent is sent on swipe up, or you can dismiss it with the back gesture or by tapping above the half shelf. The new feature flag ASSISTANT_GIVES_LAUNCHER_FOCUS routes touches through OverviewInputConsumer. As opposed to OverviewWithoutFocusInputConsumer, this allows Quick Step to work while Assistant is running. Additional logic is added to dismiss the Assistant when appropriate. Note that the dismissal happens atomically, so it's not completely fluid with the other animations. As mentioned above, this is disabled by default because Assistant doesn't currently respect CLOSE_SYSTEM_DIALOGS. Demo with the flag enabled (and Assistant respecting CLOSE_SYSTEM_DIALOGS): https://drive.google.com/open?id=1W5jGpn_TEC-KjrYwQtaBT3pzxG_5tC4W Bug: 139661510 Change-Id: I261653118aff289b329ec2a7ca6e52f100f7835a Merged-In: I261653118aff289b329ec2a7ca6e52f100f7835a
| * | Move overview haptic feedback to VibratorWrapper singletonTony Wickham2019-10-252-25/+6
| | | | | | | | | | | | | | | | | | Bug: 141886704 Change-Id: I0178a52088dd4150d7ba054983697ea63a00d9a8 Merged-In: I0178a52088dd4150d7ba054983697ea63a00d9a8
| * | Merge "Refactor SwipeDetector to track both axes" into ↵TreeHugger Robot2019-10-247-30/+38
| |\ \ | | |/ | |/| | | | ub-launcher3-qt-future-dev
| | * Refactor SwipeDetector to track both axesTony Wickham2019-10-247-30/+38
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Existing clients now use the SingleAxisSwipeDetector subclass. A followup CL will add BothAxesSwipeDetector, whose first client will be the quick switch from home controller. Bug: 126596417 Change-Id: I54c71088cfe99ff28cdc719a1eb7a7d06ac95d2d Merged-In: I54c71088cfe99ff28cdc719a1eb7a7d06ac95d2d
| * | Fix testQuickSwitchFromAppTony Wickham2019-10-231-10/+9
| |/ | | | | | | | | | | | | | | | | | | | | | | | | | | Instead of starting getAppPackageName() and relying on it being our Test Pin Item activity, instead launch our own test activities with the FLAG_ACTIVITY_MULTIPLE_TASK and FLAG_ACTIVITY_NEW_DOCUMENT flags. Test: - Locally run testQuickSwitchFromApp() from Android Studio - flake -oop -t com.android.quickstep.TaplTestsQuickstep#testQuickSwitchFromApp Bug: 140252765 Change-Id: Ie137261ce65bfd3dd39df78d57784854a026e967 Merged-In: Ie137261ce65bfd3dd39df78d57784854a026e967
| * Fix quick switch test gesture in landscape 2-button modeTony Wickham2019-10-151-0/+1
| | | | | | | | | | | | | | | | | | | | | | It should swipe from the bottom right to top right when the nav bar is on the right, rather than from the bottom left to bottom right. For now, disable testQuickSwitchFromApp() because it seems to have other failures as well. Bug: 140252765 Change-Id: I1f4989f3ea5456c18bb9cbf42ea4b157cee500d7
| * Changing the taskAffinity for LockScreenRecentsActivity so that other ↵Sunny Goyal2019-10-151-0/+1
| | | | | | | | | | | | | | | | | | | | activities do not get started in this task Bug: 138473688 Change-Id: I63b72236496a818d08ccb14e02e4fbf698a0cc49 (cherry picked from commit 657d3f8ca7f6ea92b42edfaf7ede534eca0e21bd)
| * Merge "Fades out Assistant when entering Overview." into ↵Andy Wickham2019-10-141-2/+6
| |\ | | | | | | | | | ub-launcher3-qt-future-dev
| | * Fades out Assistant when entering Overview.Andy Wickham2019-10-141-2/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This makes the transition smoother, since the Assistant goes away at the end of it. Note this only applies to the transition while an app other than Launcher is live. Before: https://drive.google.com/open?id=18SOWTtTUzt19TReAYnofQLIShJ2I-odP After: https://drive.google.com/open?id=1hqsikXSlCnSvNg0ZQYHxP-OIbS5yt9aW Bug: 136282913 Change-Id: Ia53c2407c82725c776f27b0d6e80a34554b4a303 Merged-In: Ia53c2407c82725c776f27b0d6e80a34554b4a303 Tested: Manually
| * | Merge "Add tests for quick switch from an app and home" into ↵Tony Wickham2019-10-141-4/+54
| |\ \ | | | | | | | | | | | | ub-launcher3-qt-future-dev
| | * | Add tests for quick switch from an app and homeTony Wickham2019-10-141-4/+54
| | | | | | | | | | | | | | | | | | | | Bug: 140252765 Change-Id: I5621b614ae2d8cd3db03cae818cf8b8c1c6cb20f
| * | | Merge "Create hooks for Recents Card plugin. This adds another card in the ↵Sreyas Rangaraju2019-10-143-2/+163
| |\ \ \ | | |/ / | |/| | | | | | Recents Overview space which can show various items." into ub-launcher3-qt-future-dev
| | * | Create hooks for Recents Card plugin.Sreyas2019-10-113-2/+163
| | | | | | | | | | | | | | | | | | | | | | | | | | | | This adds another card in the Recents Overview space which can show various items. Change-Id: Ifc36639ece8aa6b554bdbd3256f4195b1b220d68 Merged-In: Ifc36639ece8aa6b554bdbd3256f4195b1b220d68
| * | | Import translations. DO NOT MERGEBill Yi2019-10-112-0/+74
| |/ / | | | | | | | | | | | | Change-Id: I2ce1448b6a7ee5cb455a2fc044336c37e03093aa Auto-generated-cl: translation import
| * | Merge "Fix quickswitch flickers/ignored swipes" into ub-launcher3-qt-future-devTony Wickham2019-10-072-7/+17
| |\ \
| | * | Fix quickswitch flickers/ignored swipesTony Wickham2019-10-072-7/+17
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | - Don't set current page to running task when applying load plan, if we are already settling on a new task to launch. - When starting a new task, finish to the running app if that's the task being started (should not happen with above change) - When disabling free scroll mode, don't snap to a page if we're already on it. This was setting mNextPage so the first check was falsing. Bug: 142068081 Change-Id: I5b392d9726a81c51718d2f94eee6cd4f78b61f69
| * | | Increasing wait time for navigation mode switch.vadimt2019-10-041-1/+1
| |\ \ \ | | |/ / | |/| | | | | | | | | | | | | | am: d230af4e09 Change-Id: Ia5150735244249dd76c1993ff588036e4f18402b
| | * | Increasing wait time for navigation mode switch.vadimt2019-10-041-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | Sometimes this fails in Cuttlefish. Change-Id: Ifa2ffed5165625d51441fc3b203185fc55f7d53f
| * | | resolve merge conflicts of 08776ada1e37c4b424893306c058b1de9f85903f to ↵vadimt2019-10-031-6/+5
| |\| | | | |/ | |/| | | | | | | | | | | | | | | | | | | ub-launcher3-qt-future-dev Bug: None Test: I solemnly swear I tested this conflict resolution. Change-Id: I9a3b0f67ee874b5ec4ad67f41a46ec7876d19082 Merged-in: I9a3b0f67ee874b5ec4ad67f41a46ec7876d19082
| | * Waiting for Launcher model load in out-of-proc tests.vadimt2019-10-011-6/+5
| | | | | | | | | | | | | | | | | | | | | | | | Not doing this seems to have caused flakes. Bug: 141770616 Change-Id: Ia9caf20e4a2d93298adf4249ca815ad79bced802 Merged-in: Ia9caf20e4a2d93298adf4249ca815ad79bced802
| * | Merge "Fill in LauncherTarget fields with values extracted from ↵TreeHugger Robot2019-10-021-1/+114
| |\ \ | | | | | | | | | | | | LauncherLogProto.Target." into ub-launcher3-qt-future-dev
| | * | Fill in LauncherTarget fields with values extracted from ↵Becky Qiu2019-09-201-1/+114
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | LauncherLogProto.Target. Test: manual Bug: 137777105 Log result: 1. Swipe to -1: data { elapsed_timestamp_nanos: 1372265229686264 atom { launcher_event { action: SWIPE_LEFT src_state: HOME dst_state: HOME extension { src_target { } } is_swipe_up_enabled: true } } } 2. Swipe out of -1: data { elapsed_timestamp_nanos: 1372368006970305 atom { launcher_event { action: SWIPE_RIGHT src_state: HOME dst_state: HOME extension { src_target { page_id: -1 } } is_swipe_up_enabled: true } } } 3. Launch app from homescreen: data { elapsed_timestamp_nanos: 1372397640628726 atom { launcher_event { action: LAUNCH_APP src_state: HOME dst_state: BACKGROUND extension { src_target { item: APP_ICON grid_x: 2 grid_y: 1 } src_target { } } is_swipe_up_enabled: true } } } 4. Launch app from hotseat: data { elapsed_timestamp_nanos: 1372399813031963 atom { launcher_event { action: LAUNCH_APP src_state: HOME dst_state: BACKGROUND extension { src_target { item: APP_ICON grid_x: 2 } src_target { container: HOTSEAT } } is_swipe_up_enabled: true } } } 5. Launch app from allapps prediction: data { elapsed_timestamp_nanos: 1372403080724736 atom { launcher_event { action: LAUNCH_APP src_state: ALLAPPS dst_state: BACKGROUND extension { src_target { item: APP_ICON } src_target { container: PREDICTION } } is_swipe_up_enabled: true } } } Change-Id: I981401d06577c15948cfee0062b8a6f8a5594345
| * | | Update all apps fade interpolators for home <-> all appTony Wickham2019-10-022-5/+41
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Previously, predictions faded in quickly but then all apps faded in linerally over entire rest of the transition. Now, all apps fades in quickly after reaching the overview threshold where predictions are opaque. Also implemented the reverse, so that predictions/all apps content remain opaque when returning home until reaching the overview threshold near the bottom, where they fade out as quickly as they faded in. We do this for 3-button mode as well. Bug: 141986013 Change-Id: Ia35ab3ac9714e89f754293445a7839e15da5313d
| * | | Don't allow scrolling RecentsView outside navbar during quickswitchTony Wickham2019-10-011-0/+27
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Once the inputProxy (OverviewInputConsumer) was enabled, it was never disabled. And while it was enabled, touches above the nav bar would go through to launcher, allowing you to scroll RecentsView (for example) during quick switch transitions. This breaks some assumptions, since it doesn't go through our normal shared swipe state logic that cancels the animation, updates the new end target (e.g. NEW_TASK vs LAST_TASK), etc. Thus, if you tried returning to LAST_TASK via this route, we would end up starting it as a new activity instead of resuming the existing one, causing a flicker (I guess because that TaskView is hidden). Test: - Swipe up from task A to home (to enable input proxy) - Open A - Swipe to B, and during transition scroll back to A from the center of the screen Before, this caused a flicker, now the last scroll is ignored. TODO: we should increase the nav region during quick switch to make it easier to continue scrolling Bug: 136829198 Bug: 138620399 Change-Id: I5ffb53743b728e1909066c5dd18cc9308aff2c7e
| * | | Merge "Deprecating LauncherInstrumentation constructor with parameter" into ↵Vadim Tryshev2019-09-271-1/+1
| |\ \ \ | | | |/ | | |/| | | | | | | | | | | | | | | | | | | | | ub-launcher3-qt-qpr1-dev am: dd079691c1 Change-Id: I7419be6416f26274bf03abfd84eedef20fd6f084
| | * | Deprecating LauncherInstrumentation constructor with parametervadimt2019-09-271-1/+1
| | | | | | | | | | | | | | | | Change-Id: I779b4a8fde2db73cced8133f12d1356ad0b8729e
| * | | Merge "Fix ScrimView caret alignment and ignore touches" into ↵TreeHugger Robot2019-09-271-1/+1
| |\ \ \ | | | | | | | | | | | | | | | ub-launcher3-qt-future-dev
| | * | | Fix ScrimView caret alignment and ignore touchesSamuel Fufa2019-09-261-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Test:Manual Bug:79868152 Change-Id: Idd5a2b965173b8071697b50aac8760b0d84e469f
| * | | | Merge "Add OverviewScreenshotActions plugin interface and use it in ↵Becky Qiu2019-09-261-1/+38
| |\ \ \ \ | | |/ / / | |/| | | | | | | | TaskView." into ub-launcher3-qt-future-dev
| | * | | Add OverviewScreenshotActions plugin interface and use it in TaskView.Becky Qiu2019-09-261-1/+38
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Bug: 139828243 Change-Id: Idbefc11ef32619dd5eaaa5552088859eb2304e1e Merged-In: Idbefc11ef32619dd5eaaa5552088859eb2304e1e
| * | | | Merge "Removing debug tracing for a fixed bug" into ub-launcher3-qt-qpr1-devvadimt2019-09-252-12/+0
| |\ \ \ \ | | |/ / / | |/| / / | | |/ / | | | | | | | | am: b72cd2629c Change-Id: Id28e20b5fe23c6f6501f3c7a38305f0a306b287a
| | * | Removing debug tracing for a fixed bugvadimt2019-09-252-12/+0
| | | | | | | | | | | | | | | | | | | | Bug: 141275518 Change-Id: I171361d4f797f587b404eed07108224d8ab844f8
| * | | Merge "Removing temporary checks that tests are running on AVD" into ↵Vadim Tryshev2019-09-241-5/+0
| |\| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | ub-launcher3-qt-qpr1-dev am: 6929199c8a Change-Id: Iaa6200f0371a4deca630194ac8ecfcfc04313750
| | * | Merge "Removing temporary checks that tests are running on AVD" into ↵Vadim Tryshev2019-09-251-5/+0
| | |\ \ | | | | | | | | | | | | | | | ub-launcher3-qt-qpr1-dev
| | | * | Removing temporary checks that tests are running on AVDvadimt2019-09-241-5/+0
| | | | | | | | | | | | | | | | | | | | | | | | | Bug: 136278866 Change-Id: I2b7b63b7745936ea84b7cba599e21d954b682ba5
| * | | | Merge "Move offscreenTranslation calculation to LauncherRecentsView" into ↵TreeHugger Robot2019-09-243-12/+23
| |\ \ \ \ | | | | | | | | | | | | | | | | | | ub-launcher3-qt-future-dev
| | * | | | Move offscreenTranslation calculation to LauncherRecentsViewTony Wickham2019-09-243-12/+23
| | | |_|/ | | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Couple of benefits here: - Doesn't rely on having a measured TaskView, since it already knows how to calculate the task size - Code can be shared (planning to use this for quick switch from home) Bug: Change-Id: I517a78506ac95fcc37d9225a074427941d691903
| * | | | Removing "Failed to get system health diags" message from fallback testsvadimt2019-09-241-0/+6
| |\ \ \ \ | | | |/ / | | |/| | | | | | | | | | | | | | | | | am: 9b1c168273 Change-Id: I4528370073f0258e5f0276dfb1d71dae9816ddea