There is no need to explicitly lock the device on short power button
press if not going to a dream. The default behavior already locks the
device. This fixes a very short flicker when turning off the screen with
the power button.
Also fixes a bug where double-tapping locks the device before showing
the camera.
Bug: 262205573, 262484867
Test: manually by undocking device, tapping the power button, and seeing
there is no flicker before the screen turns off. Also, make sure the
device is locked after the screen turns off.
Change-Id: Iec72119495fb4fd47176094d9a0c33fc312600bd
onTrustChanged doesn't notify listeners if the trust change was actually
used to unlock the device, and so listeners cannot react to the change
properly. We need to pass an additional boolean.
Test: manual test
Bug: 258001148
Change-Id: Ia205640fbdb5ddeb328ea81f1fe74c80ce25bca8
The top-most Task was invisible because all activities in the Task
was finishing. This somehow prevents the activities of Tasks behind
from being resumed.
Bug: 260691453
Test: atest TaskTests
Test: Repro steps on the bug
Change-Id: I1fdda18a118915b4328d62e9d0984581fafa4f44
Manual test steps:
- Post some notifications in different sections
- Change the wallpaper of your device
Previous behavior: Notifications no longer stayed rounded
New behavior: Notifications remain rounded
Test: atest ActivatableNotificationViewTest.roundnessShouldBeTheSame_after_onDensityOrFontScale()
Bug: 262573700
Change-Id: I12550d1201b8e43ca7af92a1ba5fd1e164446bd0
Before, we call sendTaskFragmentVanished after the removeImmediately,
which may not have any following activity paused/resumed to trigger
relayout to dispatch the pending event to the organizer.
Now, we call mWindowPlacerLocked.requestTraversal() to ensure the
vanished event will be dispatched.
Without this change, the splitInfo callback can be stucked on waiting
for empty TaskFragment vanished event.
Bug: 262666213
Test: atest CtsWindowManagerDeviceTestCases:TaskFragmentOrganizerTest
Test: atest WmTests:TaskFragmentOrganizerControllerTest
Change-Id: Ibf76af205a5fc91400bdd5fc967a0d13591cfe92
the flags for
1. routes processing, which will include deduplicate device
id and apply application routes listing preference.
2. device status allow checking the flags or status of routes and show
corresponded status in the subtext of device.
both of flags will only take effect on android U.
Test: N/A
Bug: 261538825
Change-Id: If1b2134136bef715629de81531f9a3d64812fb42
Increases animation asset size in BiometricPrompt, sets BP width to 560dp, and modifies DT->LT color mapping for better visibility
Test: (manual) Open BP, observe new animation size, dialog width, and LT colors
Fixes: 260015824
Change-Id: I6890058668b570ee3c73debdd00f31d78d26b3b1
The exitSplit called while we launch the same split pair caused
it cannot enter split successful then lead to tests failed.
Add check isEnteringSplit check for that exitSplit.
Fix: 262595710
Test: atest NexusLauncherTests
Change-Id: I8666476ff76e3912542d30441b144c67baed9f38
Before, we only launch placeholder from the top most
TaskFragmentContainer. Now we also launch placeholder from the one
that is not the top most, but is visible. This can happen when the
top most is transparent.
Bug: 261550242
Test: atest WMJetpackUnitTests:SplitControllerTest
Merged-In: I6e3c4122d5d618b8a9ac054c19b0a3d19e7d3b20
Change-Id: I6e3c4122d5d618b8a9ac054c19b0a3d19e7d3b20
MockToken class was extracted from DesktopModeControllerTest. But
conflicting changes landed which broke the build and the changes were
reverted. Applying the changes again by reverting the revert and fixing
the test.
Bug: 260645044,261234251,260645044
Test: atest DesktopModeControllerTest DesktopTasksControllerTest
Change-Id: I95f66c35c671e774c3a4f7ba6b64167595f69b60
