Set min_sdk_version so that the manifest cant be merged into
Launcher3 when it is converted to Android.bp.
Test: mmma packages/apps/Launcher3
Change-Id: I28543d4be54aa789fbb452be005373239e1e0a6e
This is a targeted fix for not receiving a task stack change callback
when a task with a resumed Activity is reparented to another display.
Bug: 128932906
Test: manual - launch activity from virtual display onto default display
in a new task, verify callback notified. atest WmTests
Change-Id: Idabad8379cded664bcf302d5c6fb69564d158eb7
Merged-In: Idabad8379cded664bcf302d5c6fb69564d158eb7
It is possible for the call to system windows to occur slightly after
the ChooserActivity gets launched, therefore preventing it from ever
showing. Wait on the future before attempting to launch the activity.
Bug: 134976976
Test: Screenshot, then share over and over
Change-Id: Iba98a079412f8e35643f3a1db04e749b3c654637
To ensure gesture navigation has sufficient time to intercept gestures,
use unbatched inputreceiver, meaning that input events will be processed
immediately rather than on vsync boundaries.
Also, reduce touch slop to ensure that interception happens before the
app starts to react to the gesture.
Fix provided by michaelwr@.
Note: if the device is slow (for example, still executing first-boot
instructions), then the symptom can still be reproduced. However, once
the performance is good, then the issue is no longer observed.
Bug: 130352502
Test: open google maps and swipe from right and left. observe that the
map doesn't start moving before the back gesture icon appears.
Change-Id: I0696509c7f1cb0a0d2450080e0b61e2218a01140
- Move setting of the flags to the responsible components, updating them
directly instead of duplicating the logic in OverviewProxyService
- Add flags for tracking keyguard state, overview disabled state, and
screen pinning state
- Ensure the notification expanded state excludes quicksettings
- Add logging for states and both back/assistant disabled states
Bug: 132107485
Bug: 131698989
Test: Immersive mode - ensure you can't swipe back, ensure you can't swipe
up or open the assistant
Test: Expanded notification - ensure back doesn't work when locked/unlocked
Test: Expanded QS - ensure back works when locked/unlocked
Test: A11Y - ensure that 2 finger swipe up shows accessibility menu
Test: A11Y - ensure that 2 finger swipe up & hold works
Test: Bouncer - launch notification over launcher, ensure back works,
ensure assistant doesn't work
Test: Screen pinning - ensure back/assistant doesn't work
Change-Id: Ife37bf40602b997e6c2b534d9fa274ce07c53b07
Signed-off-by: Winson Chung <winsonc@google.com>
Allows passing the incoming velocity for gestures. This lets
SystemUI react differently to flings vs drags.
Bug: 132356358
Test: manual
Change-Id: I91df5801eb3399c94320307ccdbeca7763075984
Bug: 130451254
Test: manual
This reverts commit d9b9847ad6.
Reason for revert: found a better way to extract scrim colors without going through OverviewProxy
Change-Id: Iac97fee4d9b15757f7211889f6c370757c0870e3
This allows Bubbles to be collapsed instead of finished
when there is only one activity in the stack.
Bug: 126852149
Test: launch activity, press back
Change-Id: Iad8db0549853e3f385d54fc6b6cea5e502d37139
Let the recents app to know the recent task was running from which display.
Bug: 118266305
Test: 1. atest ActivityManagerRecentTaskInfoTest
2. atest TaskRecordTests
Change-Id: Ief2538056d414d8317b495ea45d50ccb2dc4518f
This allows for a more granular whitelist, where a single package
could have multiple plugins available but only a subset are enabled.
Bug: 123881720
Test: manual
Change-Id: Ie9b2c31f08d9dac8a892501345e8ff85143f40f9
- Normally this will be picked up in the next GC, but there is no reason
to wait
Bug: 129295298
Test: Manual
Change-Id: I945336e86d0980f926586cfba6327c8c6c142ce8
- Load resources from the current user's context to ensure the right
overlays are read
- Create a controller in sysui to dispatch mode change to prevent callers
from calling with the wrong user's context
- Clean up the quickstep contract to prevent launcher from calling methods
using the baked in fw resource ids
Bug: 130185871
Test: Switch to secondary user, ensure the mode is read correctly
Change-Id: I00d9276185777e340b3e758345a00d2e9b3e3e64
Also, make a copy of protected data to prevent accidental changes
from outside callers.
Bug: 130525551
Test: Manual.
Change-Id: I7b6efa32bc6db88b79579effaa7ffe1466a80380
- Ensure not in immersive mode, and also that the notification panel is
not expanded
Bug: 130340004
Bug: 130417141
Test: Manual, ensure back doesn't work when notification panel is down or
app is in immersive mode
Change-Id: I29f5cd80cc89b28802ca8b2c9e2956ae5b3b1151
Callers are supposed to close the hardware buffer themselves. Creating
a utility method around this
Bug: 123874711
Test: No more leak warning on device
Change-Id: I2cf215f0646222f63e564a58edab1ffffa396ff3
The new fully gestural navigation changes how user goes home from an
app as well as the animation of the app transition. The current PiP animation (bounds) is not compatible with the new model because of the direction of movements. Instead of animating bounds, we can fade the PiP window in after app closing animation finishes.
Fixes: 122609330
Test: 1. Open youtube, play a video, tap home to observe the new PiP
animation (demo video attached in the ticket b/122609330) 2. With gestural nav on, observe pip transition when swiping up to home.
atest ActivityManagerPinnedStackTests
atest BoundsAnimationControllerTests
atest RecentsAnimationTestTest
Change-Id: I28eeb1aa99c4fd569845ca7a42561f6b20796f9b
Also fixes an infinite recursion when invoking
TestableContext.(un)registerComponentCallbacks().
Test: atest WindowInsetsPolicyTest
Bug: 126511573
Change-Id: I5c9f40054493a83746bce6124d72412e8eb8a0d1