These are not being used yet in Taskbar, but they are hardcoding
DEFAULT_DISPLAY for the primary ID. In tests, we want the primary to be
considered the ID of the virtual display tests are running on.
This change also moves dagger classes to its own file for organization.
Flag: TEST_ONLY
Bug: 415326979
Test: Taskbar multivalent tests
Change-Id: Ibd0cdf46bc53dbd7a3dd5f34d7171d9a6cdebb38
> Adding a completionSignal when preview is generated so that callers can wait on it
> Also adding support for proving an optional screen-id for preview
Bug: 400403115
Test: atest GridPreviewTest
Flag: EXEMPT refactor and unused new API
Change-Id: I569e0ab318ad101e4f6dd808f2e1cfc39ba50bda
This feature aims to work only for desktop mode. Add a check to
the desktop state when checking the aconfig feature flag.
Bug: 375648361
Test: EXEMPT flag update
Flag: com.android.window.flags.enable_pinning_app_with_context_menu
Change-Id: I19eb17d756f17892637bd303464748b505c89190
Now early wakeup is controlled by BaseDepthController (with the
exception of Taskbar which uses TaskbarOverlayController). It does
all of the following:
- Increase GPU clock
- Increase CPU clock (notifyRendererOfExpensiveFrame)
- Tell SurfaceFlinger to wake up early
By default these happen the first time we render a non-0 blur, but
in some cases we can proactively activate it even earlier:
- Swipe up to All Apps begins
- Home screen QSB is tapped
These early cases were already handled for CPU and GPU, but now SF
is also in the loop.
In addition, SF early wakeup is disabled when Launcher is no longer
in the foreground.
Bug: 410973453
Test: Log manually to see early wakeup start/end
Flag: com.android.launcher3.all_apps_blur
Change-Id: I39ac0baf8c706b20f0818d31dbc8165b798ea54a
Currently, if we create 4 (upper limit) non-empty desks, reboot, and
enter Overview, the addDesktopButton shows up when it actully shouldn't.
This change fixes this edge case by checking if we can create a desk or
not when inflating addDesktopButton and update its visibility
accordingly.
Bug: 416052493
Flag: com.android.window.flags.enable_multiple_desktops_frontend
Flag: com.android.window.flags.enable_multiple_desktops_backend
Test: create desks and reboot
Change-Id: I7142c3aeb88cc1f06b99ddef753ea20c63b17297
- CD grids should override startAlignTaskbar.
- The DP.toBuilder method should carry forward DisplayInfoSpec instead
of always recalculating.
Fix: 416276424
Test: m
Flag: EXEMPT updating recently added logic
Change-Id: I7b1cb8eab5fedc09b29e96a765d1341655474e8a
Note: enableOverviewOnConnectedDisplays must be true to enable the
functionality (taskbar button --> home) in the first place
Bug: 378443899
Test: m
Flag: com.android.window.flags.enable_reject_home_transition
Change-Id: Icf5e5939c8e4f59a7d87c30df0d74a151bdbd1d5
- Set both to null instead of just one or the other
- Clean up in TaskbarUIController#onDestroy instead of only in
FallbackTaskbarUIController
Test: presubmit + leak detection
Flag: EXEMPT bug fix
Fixes: 411767825
Change-Id: I1571f126e2df01009777359eac1973976a8bb661
When the dismiss length is short, like in fixed landscape, we must account for a minimum distance to ensure dismissal
Fix: 415773066
Test: TaplTestsQuickstep#testOverview
Flag: EXEMPT Bugfix.
Change-Id: I31a1a9e0bbd23145455df35937cf85ce8ac2c20f
Test: tested overview in a connected display with a full screen app. Verified the full screen app is shown in a small tile.
Flag: com.android.launcher3.enable_overview_on_connected_displays
Bug: 415030147
Change-Id: I3e9313a17e9a323ecada89ac6fac29ea126cc613
is triggered instead of in RecentsView#onActivityUnpinned, so that
Recents is updated in sync with PiP transitions.
Bug: 416075099
Test: m
Test: Presubmits
Flag: com.android.wm.shell.enable_pip2
Change-Id: If593c2e7271e972e96b1ab21b4396af66b1e3ea4
Particularly with predictive back in cases that the app doesn't
support peeking the home screen, there was a thrashing animation
due to a secondary blur animation being applied. So in some cases,
it would rapidly alternate between 0 blur and the correct animation
blur. This wasn't necessarily user-visible, but likely contributed
to some performance jank.
Also ensure the scaling workspace blur uses the correct starting
depth and duration.
Demo: https://drive.google.com/file/d/1AffSvzlXycg8Yl4ULpctKADO6IdvvO3m/view?usp=drive_link&resourcekey=0--zqQ341w7U3MhRBwSYrsyA
Bug: 407534544
Test: Manual (predictive back, back without predictive peek, home)
Flag: com.android.launcher3.predictive_back_to_home_blur
Flag: com.android.launcher3.all_apps_blur
Change-Id: I76ed59e99aaef5bd44e8f5b0290f01763a8d4b0f