DozeSensors and DozeTriggers have code that perform proximity
checks in slightly different ways. DozeSensors was updated as
part of ag/9185335 bug DozeTriggers wasn't.
Bug: 9185335
Fixes: 140701062
Test: partially cover prox, send notification, look at screen
Change-Id: Ic85181abb3edd4c77c427faefa4cd6b9c35b498f
Bug: 138388637
Test: tested with local override and made sure they are read and parsed
Change-Id: I50fb11444f0da33ae48683b834e6ca50941ad1b7
Merged-In: I50fb11444f0da33ae48683b834e6ca50941ad1b7
Test: presubmit setup on source branch
Bug: 130289146 Create a Gradle build for SystemUI
Bug: 136279712 Daggerize FalsingManager
Bug: 137324767 "Unable to instantiate service com.android.systemui.doze.DozeService" exception breaks launcher tests
Bug: 137563419 Remove Bouncer reveal delay from bypass flow
Bug: 138787339 Allow Services and Activities to be injected into directly.
Bug: 139128921 [AS 3.5 RC2, SDK API 29 rev 2] Overload resolution ambiguity: while removing element from HashMap
Bug: 64712476 Import translations for dev branches
Change-Id: Ib7fd4706c070907fd556c3532957f3b1b046de6d
am: 776d0367b0 -s ours
am skip reason: change_id I8f7bd7a6a0562942ed3e12f28705043722d177e8 with SHA1 65c96f2fd4 is in history
Change-Id: I581e414b3e50377facc94d1145c6976f4779da05
am: cceea08cc7 -s ours
am skip reason: change_id I8f7bd7a6a0562942ed3e12f28705043722d177e8 with SHA1 65c96f2fd4 is in history
Change-Id: I5451e6467e8ffebd08360abfab9f86a429ed0721
Since we're using the pulsing state for docking, the icons would now
become clipped while pulsing.
Fixes: 139096431
Test: dock, observe notification icons showing
Change-Id: If251e6b18c03b2824b4d3ea4dab82d4a403565f1
Merged-In: I8f7bd7a6a0562942ed3e12f28705043722d177e8
Non-notification background vibrations are ignored. However, we don't
want to ignore notifications that represent various events, such as
reminders.
Test: Create a calendar event with a reminder. Close calendar and wait
for reminder. The device should vibrate when the reminder pops up.
Bug: 139523314
Change-Id: I231239daf7cc85bf69aaeef1da31218a23fcf311
Long-pressing on the lock icon after the device has been unlocked causes
it to relock until the user manually authenticates. This intentionally
disables face unlock, since we don't want the device to unlock again
immediately after the lock icon has been pressed. However, when the
device screen turns off, pressing the power button again should
re-trigger face auth.
This commit fixes a bug in that flow where, if a user long presses the
lock icon, then turns the screen off and back on very quickly, face auth
is not retriggered. It does this by resetting the lock icon pressed
status when the device begins going to sleep, rather than when the
screen has been fully turned off.
Test: manual
1. Enroll face and turn off "skip lock screen"
2. Lock device, then wake and unlock with face
3. Long-press on the lock icon to relock device
4. Enter PIN/pattern/password to unlock the device
5. Press power twice in quick succession (without triggering camera)
Before: Lock screen would be shown but face auth would not trigger
After: Lock screen is shown and face auth is triggered
Fixes: 138974321
Change-Id: I7d6a8c2b9cc95d3003f006a403866796dab67e82
Merged-In: Icecd7cb76688cd19f7e3b445a8228b21e1599068
