| Age | Commit message (Collapse) | Author |
|---|
|
Bug: 220074017
Change-Id: Idfdd94e902f656ac65a2a75dfdd199f6f85ba472
|
|
This adds the new unlock animation, which is a subtle scale and translate from the bottom part of the screen. More importantly, it connects the surface behind the keyguard to your finger when swiping, so that it's one continuous motion between the lock screen and the app/launcher.
Issei's RemoteAnimation-enabling CL was rolled back for a test breakage, so you'll need to enable it to see this:
adb shell setprop persist.wm.enable_remote_keyguard_animation 1
A few P2 issues to be fixed in follow-up CLs since this one is getting large:
- Status bar icons need to animate mid-swipe so they don't jump cut post-unlock (b/183063033)
- Launcher should use a custom animation rather than surface-based animation (b/183063432)
- The scrim should probably animate out once the surface appears rather than at the end (b/183062235)
- Handle RemoteAnimation timeout, either by restarting it, or cancelling the gesture (b/183066204)
Test: change security to swipe, unlock via a slow swipe and a fast swipe and everything in between (also, release swipe halfway)
Test: PIN/password security
Test: double tap to open a notification
Test: fingerprint bypass
Test: fingerprint from lockscreen
Bug: 169692441
Change-Id: Ic78c603b2375d36cf2170b81cca7cddbf334408b
|
|
Remove the old icon below the status bar on keyguard. Instead, a lock
icon will show beneath the notification shade for devices with either
udfps or face auth enrolled. All other devices will no longer have a
lock icon.
Test: manual, atest SystemUITests
Bug: 183910378
Change-Id: I7eebc363150641b4d63ee0f35b379d163e3a71d5
|
|
This removes the factory method from SystemUIFactory that built the
KeyguardBouncer and moves it into its own subcomponent. This is the
first step in removing view injection from the last keygard related
views.
Bug: 166448040
Test: manual
Change-Id: I4a682f324dcee6d506b0f286f8f61682f9777859
|
|
The relevant logic has been moved to KeyguardViewController instead so
that phone and car can define this separately.
Bug: 140423092
Bug: 147455109
Test: atest SystemUITests, manual for automotive
Change-Id: I9473c2ec6993808cd41c0c1021250dbf550f60c2
|
|
statusbar.
Bug: 150162295
Bug: 150164054
Test: Manual. Unit Tests Pending.
Change-Id: I66586e15d114eb6da55254f778511bde4fce3154
|
|
We shouldn't mix wakefulness with dream states, they come asynchronously
from different parts of the system. This means that the device might
not be GOING_TO_SLEEP when DozeService is started.
We also can't rely on wakefulness to drive Doze animations.
Test: unlock with fingerprint
Test: press power from launcher and lock screen multiple times
Fixes: 152835247
Change-Id: I3eaf2ae1801bbb999a6466c214234f33804ccf19
|
|
in KeyguardViewMediator and re-wire Dagger accordingly.
Prior to this change, KeyguardViewMediator used StatusBarKeyguardViewManager for making view-related changes.
This meant that KeyguardViewMediator could only be used with a specific Keyguard view that is mounted to the StatusBar.
This change makes KeyguardViewMediator compatible with any Keyguard view no matter where it is mounted, as long as it implements
the methods defined in the KeyguardViewController interface.
For AAOS, This refactorization allows us to implements our own Keyguard View and its Manager as the next step.
Bug: 150467593
Test: Build and Manual Test -- Android builds successfully on Hawk and Pixel 2 and interacting with Keyguard functionalities works.
Change-Id: Idda93514eac030f1d92523aebc9444a4d55b21d2
|
