- Remove duplicate app info changed / activity relaunch messages caused by
applying several overlay packages sequentially; this eliminated the
double launcher activity restart
- Asynchronously enable each overlay from SystemUI; this increases the
speed of enabling overlays, thus decreasing the effect of the frozen
activity transition
Fixes: 130151718
Test: make; change themes many times
Change-Id: Idcf04edc88cb9391b9920b9e1f9f873a5b62b311
The root cause is that the initial clock plugin was set before the onPluginConnected() was
called.
Set the clock plugin once the onPluginConnected() is called and it's
current clock plugin.
Bug: 131044332
Test: manual
Change-Id: I133183d66db05620d6da77abb0643e8e5ee60ebc
Delay bouncer for a few millis if face auth is happening to avoid
overlaping animations.
Fixes: 130327140
Test: manual
Test: atest KeyguardBouncerTest
Change-Id: I6873605ba3e8d54af86325d81b10cc6aec131cf2
- 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
Clicking on next alarm will send the user to the app that sets the
alarm, using their PendingIntent
Test: manual using default clock and 3rd party clock
Fixes: 130977970
Bug: 129350749
Change-Id: I4c1be9fe9ea60787ecb2b863e7463d827aef0075
Separate "assist is rendering something" from "assist session is in
progress". If an assist session is in progress, the status bar should be
focusable and back gestures should cause the session to be canceled.
This also intercepts touches outside of the status bar when a session is
in progress, but those touches will cancel (separate CL), so this
shouldn't be a problem.
Bug: 123413054
Test: Ensure in-progress assist sesion is canceled on back, ensure back
is not affected outside of a session.
Change-Id: Ife24b58a7851c5865ff75e66e00e32ae3293a0e8
Some errors such as ERROR_TIMEOUT should not caues the BiometricPrompt
dialog to be dismissed. Updated plumbing to allow
onBiometricAuthenticated to pass a string indicating the failure reason
Fixes: 131240917
Test: BiometricPromptDemo
Change-Id: I63a6f1138a24fbc3736184efefc620dd5bb640dd
Change summary:
- Position below status bar on AOD, and account for burn in prevention
movement.
- Position below lock icon on lock screen.
Fixes: 130797849
Test: visual - checked position on AOD and lock screen
Test: visual - checked position with music playing
Change-Id: Iad088e8b1d301e19ec9a095462a420e1723aba00
Bug: 127848641
Test: builds, manually verified
TL;DR;; the unhandled back gesture direction was opposite of handled
back gesture.
Change-Id: I828543bc86e6fbb24d1a6ee5d6b5b92118401323
This should help prevent Settings and SysUI from getting
out of sync with each other.
Test: manual by adjusting battery levels with adb
Bug: 124030091
Change-Id: I8eaba920a10e045c4c983406873de66208c22fb7
- Cancel animations when explicitly moving the stack to the start position, so that the new translation doesn't get animated away.
- Set the flyout to 0 alpha before posting the animation, so it's invisible from the start.
- Tell the stack if the drag finished with a dismiss intent, so we can reset the drag flags.
Bug: 130441552
Test: atest SystemUITests
Change-Id: I31d753a6fb76468c4e2b68563f9c5f06fbd782a1
There are some extra onPause / onResume events in ActivityView due to
SysUI calling startActivity in onActivityViewReady which happens a bit
before the display being turned on.
This CL posts the startActivity call which is enough to avoid the extra
lifecycle events.
This CL also adds new method on ActivityView to startActivity with your own
ActivityOptions (because posting causes activity transition to occur...)
Test: manual - have Bubbles test APK
- create a new bubble
- adb logcat | grep "BubbleActivity"
- observe the logging to make sure lifecycle events behave
normally
Bug: 130363466
Change-Id: Ia44d6033e5cff625222006632b7bdc4dc1e59e81
Previously, the rotation of bounds is simulated by swapping the width
and height, and also adjust the insets in app bounds. But it is still
not accurate enough because the decors can be moved or resized according
to rotation.
Now the activity bounds are computed as it is in a pseudo display that
provides the same size and insets information as the original display
where the activity launched.
This change also handles a special case for task level letterboxing.
The container bounds for activity is also calculated as the task,
so the activity can always best fit in the parent when the orientation
is changed.
Fixes: 130417317
Bug: 112288258
Test: atest ActivityRecordTests TaskRecordTests
Test: atest SizeCompatModeActivityControllerTest
Test: Enable fully gestural navigation and launch camera.
The restart button should not show after rotating screen.
Change-Id: Ifbb31f9ee84723c85bd4cbc03abd8cdf70fee6af
HeaderTileLayout width should always be MATCH_PARENT. The width is
controlled at the QSContainerImpl level by making it the width of
notification panel and it's MATCH_PARENT all the way down.
Test: visual, using emulator on really high density screen and phone
Fixes: 128776927
Change-Id: I3d5dc679cb77fb50ccadd6c3cb86a022e5f02f70
some older code that flashed the dialog on screen initially and
triggered dismiss too often.
Bug: 131178834
Test: VolumeDialogImplTest still passes with atest
Change-Id: Ia8879aabe1d97fd2bb78620b962ad959bbbeaa25
Bug: 131183785
Test: adb shell settings put global power_button_long_press 5
then longpress power button
Change-Id: I0d6c25f75efc1e0e7a04f44ba91f7603ab8f311b
