This brings the size of the bottom sheet closer to the spec provided by UX. For that type of flexibility to be possible, more attributes are introduced and some calculations had to be changed.
This shouldn't affect phones.
Bug: 218638090
Test: visual, with dumpsys and HSV
Change-Id: Ieee7580d80d8e100837b1cdd7a1455c4d65612dc
This is a better name now that we have gestural nav.
Renaming will happen in stages, the first one being having 2 names side-by-side.
Test: presubmit
Bug: 187761685
Change-Id: Ifb15c838cc0e161d852cf6df025687e3f92d6124
- Added TAPL objects to support TAPL tests for taskbar features
- Added tests for major taskbar features: hiding/showing the taskbar, opening all apps, lauching apps and app deep shortcuts from the taskbar/all apps page, launching apps and app deep shortcuts in splitscreen
- These tests should only run for large devices
Design: go/taskbar-tapl-tests
Test: ran tests locally with invalid configurations and remotely
Bug: 215218813
Change-Id: I3c28c339707467414aa47fa633f87fa0c1fdee57
Revert submission 17128079-suggestionentry
Reason for revert: test monitor determined it broke tests: b/223859070
Reverted Changes:
I838896e2f:Add entry and cursor location in GetSuggestionRequ...
Ic9f5dd35b:Add cursorLocation and entry to GetSuggestRequest
Change-Id: I8a15f61c5ddb37b26d3e06de25f0d5b5b5c89abc
> Moving the code from ApiWrapper to Resource overlays for better maintainability
> Accounting for display cutouts in insets estimation
> Using same logic in display controller and view inset dispatching
Test: Verified on device
Bug: 221961069
Change-Id: I78466353563692ce3f7512b0146ef8b61ef14bc0
- IDP can get re-initializeed during grid migration task, causing src/dest dbFile to be the same when prepareForMigration, which fails the migration and causes a wipe
- The fix is to cache IDP state as DeviceGridState, and use DeviceGridState to determine migration, trigger migration and save configuration after migration
- This should avoid migration failure in b/198965093 that causes homescreen wipe. Homescreen icon may still be messed up by the migration, but won't completely disappear
Bug: 198965093
Fix: 223579388
Test: manually trigger grid migration
Change-Id: I9890a6d5d530ff87aed8f601ec7d35a672b7cd46
This reverts commit b0e0f5f44a.
Reason for revert: This cl prevents the ability to run tests from android studio.
Change-Id: I8a1cbcd2e8faefdd168aac5bcad4f21c73694839
- We have less space on tablets when 3 button nav is enabled because QSB is now inline with the icons. This creates a new attribute to define how many icons should be shown when in that mode. This could be used for other grids in the future as well.
- InvariantDeviceProfile now listens for nav mode changes
Fixes 214882090, 221420204
Test: manual
Change-Id: I012432a1a322c4e5505e46a1198c841ab124aaa6
- PromiseIcon installSession takes a long time to be created in certain device, incrase the timeout until b/222319304 is fixed
Bug: 202985412
Test: labtest
Change-Id: I51e6136b5a79e68f509745035206a6752f7318af
I want to include some stuff (like android.platform.test.rule.CrashDetector) but I want to land just the dependency part and see if I get postsubmit build problems that sometimes appear in obscure AOSP targets.
Test: presubmit
Bug: 187761685
Change-Id: I334b9f1029edbe8621df940900f43d0c5059373e
Merged-In: I334b9f1029edbe8621df940900f43d0c5059373e
While re-arranging icons the hotseat remains in scale 1.0f, while the workspace reduces it's scale (as defined by SpringLoadedState.java). Previously, the code to aggregate animations was assuming hotseat and workspace always had the same scale.
MultiScaleProperty.get() was being used to set the starting value of the animation. Previously, it was returning the last aggregated value. However, this value was correct only for the workspace, but not for the hotseat. Returning the current view scale makes it always correct.
Bug: 220271046
Test: Dragged icons from hotseat to workspace, and verified animation didn't jump
Change-Id: Ic01776c1d8e3967624626ed7c44d194a06295790
It seems if the dragging target position's X coordinate is 0
then there is a weird bug in portrait mode.
Test: atest TwoPanelWorkspaceTest
Bug: 197631877
Change-Id: I7d8702b06e5ed396814339080f8e814e9f8a6a65
The unfold progresses are mapped to 0.85 - 1 range and set as a scale for launcher.
In case of multiple scale animations for workspace and hotseat, they are combined using MultiScaleProperty (e.g. opening an app while unfolding/going to all apps while unfolding). Note that this is a pretty difficult scenario to be in. If that happens, we multiply all values and bound the result between the max and min values.
Bug: 217368525
Test: atest MultiScalePropertyTest and manually
Change-Id: I6131c39f36deade0b7280c72edda2d72045344e9
TAPL was expecting pilfer upon UP in the swipe-pause-to-overview gesture.
Actual Pilfer happens earlier, which resulted in wrong sequence-mismatch diags if the gesture fails before UP.
Now expecting Pilfer earlier.
Also fixing a problem that sneaked through earlier reviews when even down time was passed incorrectly.
Bug: 187761685
Test: presubmit
Change-Id: If4289a011247bf7801405ecaac8befa8461e8a37
Needed because when running tests in virtual devices is very slow. The previous number of steps was also greater than the default timeout for home gesture.
Fixes 215673732
Test: atest Launcher3Tests:RequestPinItemTest
Change-Id: I9b13d97deb158222ba0ebf3f6a536c5a7ae632cf
This reverts commit 1a9ef83988.
Reason for revert: Remove ScreenRecord to see if it resolves stale input event problem
Bug: 215672979
Change-Id: Ia7b7cd992c79af34b11d17becde98f253ab778ac
