We should be able to handle multiple emergengy sos activities on the
device without showing a disambig dialog. This CL adds a config string
to set the package name of the preferred app to handle the emergengy sos
intent (not using RoleManager#ROLE_EMERGENCY since SysUI doesn't have
the necessary permission).
The preference is given to the activity as follows:
1. Activity is from a system app with package name matching new config string
2. Activity is from a system app
3. Gesture becomes a no-op (will not match non-system activities)
Test: manual {StatusBar makes testing a launched activity
challenging}
Bug: 181610572
Change-Id: I862b4e3edf990d5f011aa0dc073070ede8b474b1
Only registered when:
- udfps enrolled
- AOD is not enabled
- quickpick enabled:
adb shell settings put secure doze_quick_pickup_gesture 1
Currently by default, quickpickup is not enabled
On gesture trigger, AOD screen will show for 5 seconds
Test: manual
Bug: 176550666
Change-Id: I804a2590c1d95acad62fbfbc85228ecfc8bfa3ed
Continue to support launching from both global actions as well as the
QS tile. Use an activity for QS tile launches, which supports
lockscreen visibility.
Bug: 172360102
Test: manual
Change-Id: I002aa32f9126745ee310e203ad45f9c28f39fa8d
Fix issue where low priority icons fade into the shelf
then immediately fade out into the dot.
Remove unused things
- openedAmount: originally added to fix cutout issue
but we won't show the shelf near the cutout anymore
- expandedAmount: tweaks shelf transformation near the status bar
but we won't show the shelf near the status bar anymore
- handleCustomTransformHeight: leftover from shelf-icon to notif-icon
animation, which we already removed
Bug: 178479515
Test: scroll shade up and down
Change-Id: I7c3e2cb6dac1ce70de1dbe575734c393f7f511de
This is only necessary when a notification is posted without a title.
Fixes: 177976174
Test: Manual inspection of various staes.
Change-Id: I15fdc31e1557b7e5d6fb99e410f4bf37d6734ac4
This CL prevents the Shade from collapsing if a notification expansion
animation is pending/running. It does so by:
1. Making sure that StatusBarNotificationActivityStarter#shouldCollapse
is checked *after* ActivityLaunchAnimator#setLaunchResult is called.
2. Updating the clipped area of the parent of the notification that is
expanding, if any.
3. Not moving the QS or the notification siblings while the animation is
running.
4. Making sure that the notification is displayed above the QS.
See b/181654098#comment4 for before/after videos.
Bug: 181654098
Test: Manual; atest ActivityLaunchAnimatorTest ExpandableNotificationRowTest NotificationChildrenContainerTest NotificationStackScrollLayoutTest StatusBarNotificationActivityStarterTest
Change-Id: I5a7beb4dc4883ed2757e286c4b480f83709680f7
This CL animates the notification corner radius when the notification is
expanding, from its initial radius up to the final window corner radius.
See b/181654098#comment5 for before/after videos.
Bug: 181654098
Test: Manual
Change-Id: I2b4889f3c811f27166e405248c512052d145922d
Also continue to listen for fingerprints on shade and fullscreen user
switcher, logic to hide icon is in UdfpsAnimationView
Test: manual
Fixes: 181573493
Change-Id: I7e7aed339498bb5cac588bb67f432251a93638a5
This separate dimension was really a bug waiting to happen. Add a little padding here or there, forget to update this dimension, and suddenly in rare cases the UI would be cropped.
Bug: 179178086
Test: Post CallStyle notifications with title, text, progress, smart actions.
Change-Id: I35500885eb53750fa2ccde4f2f602e6cfdb02113
- In some cases, the ML model may return that it is a valid swipe
even if it is out of the current inset bounds
Bug: 178561216
Test: Enable ML model, rotate to landscape and try to swipe near
the edges
Change-Id: Iaecd11acf50a1a19fe5964e11e06fb564ca6988c
Modifies the layout of BiometricPrompt for under-display fingerprint
sensors so that the fingerprint icon is aligned with the sensor when the
device is in the landscape orientation and/or using 3-button navigation.
Test: atest AuthBiometricViewTest
Test: Manually, using the biometric integration test app
Bug: 179044674
Change-Id: I4da075b4cbf8b7119c071361336ddebd0a505ce0
I'm not able to reproduce the bug, but we can avoid calling removeView
if the view isn't attached.
Bug: 180114844
Test: Manual verification of existing behavior
Change-Id: I1173f7d3656aaa10815f07717c09d3a3869d9878
With the relaxation of FGS visiblity rules in S, we
no longer need to boost FGS notifications to the
alerting section to ensure visibility on the lockscreen.
Test: atest HighPriorirtProviderTest
Bug: 182164793
Change-Id: I363c16708ab00bb3b2c4e3663bac2a6470a75274
An ill-timed onThemeChanged() event can occur after boot, which forces
the bouncer to be destroyed. In most cases this is fine, but after
boot this leaves the keyguard with nothing to show, as PIN/PUK views
are required to unlocked the device.
Bug: 182130809
Test: manual, reboot the device with SIM inserted
Change-Id: If7b86df15de29b295d86eff610da476b4dbee566
