Set divider bar surface position after the corresponding leash ready.
Make sure app pair renders rounded corners with proper insets. And
prevent re-inflating divider bar redundantedly.
Fix: 201966641
Fix: 201966626
Test: atest WMShellUnitTests
Test: manual check divider bar behavior while in app pair split.
Change-Id: I70305df9ab8d77a8b474f573cea82026b9eb5298
Update window-extensions aar to match updated interface.
Interface was changed due to API council feedback to prefer a single
method that returns a nullable value.
Bug: 199123327
Test: Manual
Change-Id: I6cc5a66857de97c6b55ca3131a3e516d593e1c83
Test: It builds.
Bug: 193883067
Change-Id: I3c310ab6a631750377a069e926567279bedc9d3b
Merged-In: I3c310ab6a631750377a069e926567279bedc9d3b
(cherry picked from commit 78893c2317)
DO NOT MERGE
Now they are both 500ms. Otherwise if the duration of exit animation
is longer, it may cover the entering task.
Bug: 201998178
Test: Back from a task in a different orientation, the exiting
task should not flash on screen.
Merged-In: Iefa134e4217ba35d33801225368b7a5df60d932c
Change-Id: Iefa134e4217ba35d33801225368b7a5df60d932c
Now they are both 500ms. Otherwise if the duration of exit animation
is longer, it may cover the entering task.
Bug: 201998178
Test: Back from a task in a different orientation, the exiting
task should not flash on screen.
Change-Id: Iefa134e4217ba35d33801225368b7a5df60d932c
onActivityResult was called before onStart when resuming an activity
from STOPPED state.
Ensure the onActivityResult callback to be called before onResume.
But we only fix this after Android S to avoid some app compatibility
issues.
Bug: 78294732
Bug: 130178098
Test: atest ActivityLifecycleTests
Change-Id: I9ff060ff26d3fc517aae0a094fc041887326a963
As now the new split-screen system has been migated to wmShell
with using WINDOWING_MODE_MULTI_WINDOW to setup the split task.
so inSplitScreenWindowingMode() will no longer be true since this
method is used for legacy split-screen.
It affects WindowState#needsRelativeLayeringToIme can not
check if the app is in split-screen window and makes system can't
set relative layering to IME for popupWindow to make it above IME.
Note that setting relative layering with IME also benefits for other
non-fullscreen windowing mode like in bubble/freeform mode, the
dropdown menu can above the IME when the parent window is IME
layering target.
Changing to use DC#isImeAttachedToApp() to fix this layering issue.
Fix: 201504527
Test: atest ZOrderingTest#\
testPopupWindowAndParentIsImeTarget_expectHigherThanIme_inMultiWindow
Test: manual as issue steps
1) Go to "Create contact" in Phone.
2) Enter split-screen mode.
3) Click on a text box of "Create contact".
4) Click the menu button to show the menu of "Create contact".
5) Expect the layer of the menu should above the IME surface.
Change-Id: I2f466a2305e56e4fd2a0c509d7c8027104cb51b6
Update the style of side stage outline to match the current design. And
make sure the outline will interact properly with task bar expanding,
collapsing, swipe up, drag to split, recents shortcut to split and drag
divider bar to resize gestures.
Bug: 200850654
Test: atest WMShellUnitTests
Test: enable side stage outline, observed it behaves properly.
Change-Id: I3f0795adc34a0efb19d35b78d54364da4189a043
Currently DisplayModeDirector casts Vote.PRIORITY_HIGH_BRIGHTNESS_MODE
based on whether High Brightness Mode (HBM) is allowed, rather than
based on whether HBM is actually active. This can lead to cases where
the HBM refresh rate vote is cast when HBM is allowed but not actually
used.
This change corrects this behavior, and makes DisplayModeDirector check
that HBM is both allowed (enabled) and actually in use (active).
Bug: 200851199
Test: atest DisplayModeDirectorTest
BrightnessLevelPreferenceControllerTest
HighBrightnessModeControllerTest
Change-Id: I8cb8f023a6bca11de976866259032143f43d9a4f
