summaryrefslogtreecommitdiff
path: root/packages/SystemUI/src/com/android/systemui/doze/DozeLog.java
Commit message (Collapse)AuthorAgeFilesLines
* Update SysUI to use new PowerManager WakeReasonsBeverly2022-12-201-0/+26
| | | | | | | Test: manual - check PowerManagerService logs Test: atest CentralSurfacesImplTest PulsingGestureListenerTest Bug: 242628816 Change-Id: I9ff9845a1f98beb336993170ce65886a31dbfdb9
* Allow UDFPS to be triggerd from AOD_PAUSED stateBeverly2022-12-121-0/+13
| | | | | | | | | | | | | | | | And from the AOD_PAUSING state. So if users immediately attempt UDFPS right after the prox sensor has become unblocked, the authentication will still go through rather than being dropped. The UDFPS longpress gesture is also prox gated (by the sensor), so this is a safe change. Test: programmatically set DOZE_AOD_PAUSED and see that UDFPS longpress can still be triggered when prox isn't blocked Test: atest DozeTriggersTest Fixes: 244011650 Change-Id: Ic4f7956cb6082bec5c55d5177c8546e12b969378
* Decouple CentralSurfaces and NPVCJustin Weir2022-11-161-2/+2
| | | | | | | | | | Continuing effort started in ag/20327965, this time focusing on references to CentralSurfaces in NPVC. Removes 5 more methods from the CentralSurfaces API. Bug: 249277686 Test: manual and atest Change-Id: Ib8180339413c7209e5380eebf38f430dbd9f34a1
* Migrate DozeSensor logcat logging to LogBufferBeverly2022-10-211-2/+43
| | | | | | | Test: adb shell dumpsys activity service com.android.systemui/.SystemUIService dependency DumpController DozeLog Fixes: 253418636 Change-Id: I552b3b47f241ebf40408dfd5b578b5bce59f4ecc
* Eval KG showing, occluded and visibility togetherBeverly2022-10-061-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Keyguard visibility is based on the keyguard showing and occluded states, but the KUM state changes were previously separated so that KG would respond to a occlusion change but not have the newest visibility, so it would inaccurately update its fingerprint listening state. To avoid this race condition, this CL consolidates KG showing, occlusion and visibility changes to a single setKeyguardShowing(showing, occluded) method. The method updates the KUM state and then sends the change out to listeners. This CL also updates some of the vocab used. In the future, keyguardVisibility from a KUM perspective means that the keyguard is showing and NOT occluded. Test: atest SystemUITests Test: enable a screensaver and successfully authenticate from the screensaver with a non UDFPS fp sensor Test: double press power button to the camera (occluded state), and see that rear FP will stop running. Can still auth when accessing the photo gallery. Test: double press power button to the camera (occluded state), and see that UDFPS affordance isn't available. Can still auth when accessing the photo gallery. Test: Setup a timer to go off, see that going to/from the occluded activity updates the occluded & keyguard visibility state correctly Bug: 248089638 Fixes: 247580913 Change-Id: I3478be2d304a42beebdb6a4baaf2e571d74e61b1
* Add the ability to end pulsing immediatelyBeverly2022-10-051-2/+9
| | | | | | | | | | | | | | If a HUN is immediately cancelled after posting, make sure the Doze pulsing state can correctly exit so that the device isn't stuck pulsing in screen on. Test: manually (hardcode) a notification to immediately stop pulsing after its been requested to pulse. observe that AoD eventually exits the pulsing state. Test: atest DozeTriggersTest DozeServiceHostTest Fixes: 221601821 Change-Id: Ibf349f97edbb54a9eb36eb4d33175867d7cf7b13
* Suspend and resume DozeTriggers when entering and exiting car mode.Chandru2022-05-311-0/+14
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This change introduces a new DozeMachine state DOZE_SUSPEND_TRIGGERS that is equivalent of DOZE but also suspends any triggers that awaken the device. Entering car mode transitions the state machine to DOZE_SUSPEND_TRIGGERS and leaving the car mode transitions to either DOZE or DOZE_AOD depending on whether Always on Display is enabled. Current behavior when entering car mode: - DozeService is finished. - Always on display is turned off - Tap on screen doesn’t wake up the device - Lifting device doesn’t wake up the device - Sending a notification doesn’t wake up the device. New behavior when entering car mode: - DozeService is not finished. - Remaining behavior is the same as DozeTrigger stops listening to all triggers (sensors, intents, notifications) Current behavior when exiting car mode: - DozeService is not running, normal triggers don't wake up the device New behavior when exiting car mode: - DozeService is running, normal triggers wake up the device as expected. - DozeSuppressor transitions from DOZE_SUSPEND_TRIGGERS to DOZE/DOZE_AOD Bug: 230968777 Fixes: 230968777 Test: manual Test: atest com.android.systemui.doze Change-Id: I5f49bb5700d7ed38763dccc8c5b6438d934c6476
* Remove FileDescriptor from systemui.Dumpable.Dave Mankoff2022-04-051-2/+1
| | | | | | | | | | This is the first step in moving over to the new public android.util.Dumpable api. Bug: 217567642 Test: m SystemUI Merged-In: Ibaebcfb2c6c5326d0c45b8c72d868c76655d89a0 Change-Id: Ibaebcfb2c6c5326d0c45b8c72d868c76655d89a0
* Separate out bouncer updatesBeverly2022-03-311-2/+2
| | | | | | | | | | | | | | | | | | Some callbacks want to know when the bouncer starts transitioning to show (ie: UDFPS animations) while other callbacks only care if the bouncer actually fully showed (ie: running face auth). We want to make sure we don't over-trigger face auth, so only request face auth when we know the bouncer is fully shown rather than in the middle of a transition to potentially showing the bouncer (sometimes it can be quickly cancelled). Test: atest SystemUITests Fixes: 226967764 Change-Id: Ifca6fb1861992a78815066571019226322260279
* DOZE instead of DOZE_AOD when batterySaver=activeBeverly2022-03-181-2/+3
| | | | | | | | | So we don't mistakenly briefly show the AOD UI when entering AOD with battery saver active. Test: manual Fixes: 219030172 Change-Id: Ida3b52a3a091736b8ba2d3ad614662a0ac4724e1
* Refactor doze suppressors into its own classBeverly2022-02-251-12/+29
| | | | | | | | | | | | | | | | | There are multiple ways doze/aod can be suppressed/blocked. This CL consolidates the majority of the logic to DozeSuppressor.java and breaks apart the terminology `doze suppressed` (which refers to the entire doze experience) from `always on suppressed` (which refers to only suppressing always-on-display, but continuing to register for wake-up-gestures). + Added DozeSuppressorTests + Added extra logging to DozeLog Test: atest SystemUITests Test: atest DozeSuppressorTest Bug: 218509239 Change-Id: I8cec55d57b67a6e171849febabf8e92804d74f4e
* Add extra logs to track dozing state changesBeverly2021-11-081-1/+9
| | | | | | | | | When starting AOD Test: manual see logs Bug: 202630143 Change-Id: Ib78145e068ea40dd727980b4845c8b2d5e250d1f
* Update DozeSensors and DozeBrightnessSensor on posture changesBeverly2021-10-181-6/+17
| | | | | | | | | | | | | If the posture changes while AOD is running, make sure sensors are unregistered + registered properly. Test: manual, enable AOD and then close/open and check that correct sensors are registered (dumpsys sensorservice) Test: atest DozeScreenBrightnessTest DozeSensorsTest Fixes: 192805135 Fixes: 199344667 Change-Id: I5093dc43e062144adca757c94fa708f51be57a44
* Merge "Don't wakeup from the pickup gesture when kg is occluded" into ↵Beverly Tai2021-09-161-0/+7
|\ | | | | | | sc-qpr1-dev
| * Don't wakeup from the pickup gesture when kg is occludedBeverly2021-09-151-0/+7
| | | | | | | | | | | | | | | | | | | | | | | | Also finish() wallet activity onStopped. Consequently, the activity will always close on screen off. For example, this includes when the activities are launched via their lock screen affordances + qs tiles. Fixes: 194925434 Test: manual, atest DozeTriggersTest Test: atest UdfpsControllerTest UdfpsKeyguardViewControllerTest Change-Id: I9856571e104ef05aec93d32056cd2097c2d2a1da
* | Delay the transition to AOD1 if udfps is activatedBeverly2021-09-141-0/+8
|/ | | | | | | | | | We don't want to change display states while the user is interacting with the UDFPS sensor or else we'll lose the touch and cut fp authentication short. Test: atest DozeScreenSTateTest Bug: 198710028 Change-Id: I3a8168e6f1970c36717e0a7a223bcc74c3ec5600
* Doze - remove metrics logger, add uieventBeverly2021-04-231-2/+2
| | | | | | | | | | | | - UiEvent wasn't being used onWakeScreen even though the events themselves already exist. Use ui-event and add event for wake timeout - Inject UiEventLogger for easier testability Test: manually view ui events using command `$ANDROID_HOST_OUT/bin/statsd_testdrive-terse 90` Test: atest DozeTriggersTest Fixes: 186230887 Change-Id: I7ac4c11e5c95ed774499ee8b62931321fa812549
* Add quickpickup gestureBeverly2021-03-101-4/+6
| | | | | | | | | | | | | | | 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
* Adding more Doze logs for brightnessBeverly2020-12-071-0/+16
| | | | | | | Test: manually check logs adb shell dumpsys activity service com.android.systemui/.SystemUIService DozeLog Bug: 174102413 Change-Id: I6a9969c2ee96a70983e6a9affdb5722e59a68278
* Add logs for whether doze is suppressedBeverly2020-10-121-0/+8
| | | | | | | | | Dozing can be suppressed by the PowerManager. Log when doze is suppressed this way so it's easier to debug when users no longer see AOD when they expect AOD. Test: manual Change-Id: I4c2b2d322cb8b6af5d18bed73f32b3d7f5b0b4c1
* Add debugging logs for DozeBeverly2020-09-181-0/+16
| | | | | | Test: manual Bug: 168778910 Change-Id: If6c89df1a426fb2f15abf1d53567b5a72d4aab5f
* UDFPS on AODRobert Snoeberger2020-09-141-2/+5
| | | | | | | | | This change establishes a connection between the AOD interrupt and the fingerprint sensor. Bug: 165267247 Test: manual - enter device from AOD with fingerprint Test: manual - On AOD, fail fingerprint auth, check that HBM turns off Change-Id: Ia8ca9a145590d8b5629a584807e110ca3600b813
* 6/N Move everything into SysUIComponent.Dave Mankoff2020-08-161-2/+2
| | | | | | | | | | | | | | | It is far easier to move _everything_ into SysUIComponent, and then selectively promote things back to GlobalScope and/or WMScope than it is to try to do it one at a time. With this change, though lots of files are touched, very little actually changes structurally. After this change goes in, folks should stop using @Singleton quite so freely. Most things should live in @SysuiSingleton. @Singleton is due to quickly be replaced by @GlobalScope. Bug: 162923491 Test: atest SystemUITests && manual Change-Id: Idc31d3d83b030581fb1fa869f7fafc4f2d3a8828
* Migrate DumpController -> DumpManagerNed Burns2020-02-201-3/+3
| | | | | | | Unify "everything that needs to dump stuff" to use the DumpManager. Test: atest, manual Change-Id: Ib475aba4eeccb24bd49ab909896f7d779a8e1b04
* Add a content observer for DOZE_SUPPRESSED.Yogisha Dixit2020-02-031-0/+8
| | | | | | Test: manual, atest PlatformScenarioTests:DozeMachineTest Bug: 147584235, 147587999 Change-Id: I5265f8d0572813e28278134196fc0fd26e0dfb25
* Switch DozeLog over to new bufferNed Burns2020-01-291-82/+95
| | | | | | | | DozeLog should really be renamed DozeTracer or similar (to avoid clashes with the new DozeLogger) but I didn't want to nuke the change history. Test: atest Change-Id: Id74d04f3b073b0680b3b39707d2fa38a1706e418
* Revert "Revert "Recycle SysuiLogs + add NotifLogs""Beverly2019-12-111-35/+31
| | | | | | | | | | | | | | | - Add back NotifLogs without feature flag set to true. - Update ForegroundCoordinator to end lifetime extenders on the main thread instead of the bgthread. This reverts commit 4f2a8bfe15176078979dba948c39728777e69180. Test: atest SystemUiTests Fixes: 145689836 Fixes: 145709036 Bug: 145134683 Bug: 141470043 Change-Id: Iefc12b7da9c64c332bf43bb88533db87dc5525ec
* Revert "Recycle SysuiLogs + add NotifLogs"Aurimas Liutikas2019-12-051-31/+35
| | | | | | | | | This reverts commit e7219f10b1a484aed89ecfa2aa337df7432d30de. Reason for revert: This is causing SysUI to crash when running presubmit CTS themehosttests. Bug: 145709036 Change-Id: I3c073bcbf5d1564e6f2a9d527ccb9ce4cd062068
* Recycle SysuiLogs + add NotifLogsBeverly2019-12-031-35/+31
| | | | | | | | | - Add Notification logging for NotifListBuilderImpl - Recycle SysuiLogs Test: atest SysuiLogTest Bug: 141470043 Change-Id: Id292488be0e2e3e9ad136a0400dc6c5f1bbd1ab5
* DozeLog uses new SysuiLogBeverly2019-09-271-208/+213
| | | | | | Test: atest SystemUITests Bug: 141470043 Change-Id: I089dd42ab67b0a37841159c5f1f9702ea45f57e6
* Fix the looper that KeyguardUpdateMonitor is using.Dave Mankoff2019-08-311-1/+2
| | | | | | Bug: 139051615 Test: atest SystemUITests && atest SystemUIGoogleTests Change-Id: Ic4dd5978001c208504c137cee41f363d7e70b1b5
* Debug when pulses are droppedLucas Dupin2019-08-011-0/+6
| | | | | | | Test: adb shell dumpsys activity service com.android.systemui Test: adb logcat | grep NotificationInterruptionStateProvider Bug: 138336424 Change-Id: I57c0d059e139991a67bdb85dba6f1e81382806dc
* Biometric auth keyguard adjustmentsLucas Dupin2019-01-311-7/+7
| | | | | | | | | | | | | | | | - During passive authentication, the keyguard should not be dismissed because the user might be looking at notifications. - Keyguard should still be dismissed if bouncer was visible. - Some sensors are allowed to trigger biometrics auth Change-Id: Iff492c5e1eb807ab3b9b187a376c4db975606b5a Fixes: 123581946 Fixes: 123364930 Test: fake bio unlock from (lock screen, bouncer) Test: fingerprint unlock from LS, bouncer, AOD Test: atest BiometricsUnlockControllerTest Test: atest StatusBarTest Test: atest KeyguardUpdateMonitorTest
* Add support to SLPI tap gesturesLucas Dupin2019-01-161-1/+3
| | | | | | | | | | This CL introduces a new configurable sensor type: config_dozeTapSensorType Test: atest SystemUITests Test: set config_dozeTapSensorType to double tap gesture on overlay Bug: 121198822 Bug: 111414690 Change-Id: I54f3c20473a6d97c860ee02f324edbcf89ba85d1
* make wake event trigger a pulseLucas Dupin2018-12-261-10/+3
| | | | | | | | Test: manual Test: atest ScrimControllerTest Bug: 111405682 Bug: 111395593 Change-Id: I5a7b9024ecd5aea691ac5e3f23e70818186fc37c
* Launch AoD override the settingsTYM Tsai2018-12-261-2/+4
| | | | | | | | | | Improved the docking experence, let DozeService can enter always on mode when docking if device has a docking manager. Listening the docking events to enter/leave pulsing state. Bug: 120464108 Test: atest SystemUITests Change-Id: Ic3d89bdd7a18a069e3ee4f35c9bd677069bf1c43
* Merge "Fix NPE in DozeLog"TreeHugger Robot2018-12-191-1/+1
|\
| * Fix NPE in DozeLogLucas Dupin2018-12-181-1/+1
| | | | | | | | | | | | Test: atest tests/src/com/android/systemui/statusbar/phone/StatusBarTest.java Change-Id: I79706d175adf891e6db4c7e65c5581b300d321fa Fixes: 121197117
* | Merge "Fix log description"TreeHugger Robot2018-12-181-2/+2
|\ \ | |/ |/|
| * Fix log descriptionLucas Dupin2018-12-141-2/+2
| | | | | | | | | | | | Test: make Bug: 111405682 Change-Id: I765d8bd2810737b7b26dc228ce72c1d8c75197dd
* | Initial sleep-lock-screen implementationLucas Dupin2018-12-171-3/+1
|/ | | | | | | | | | | | | | | We're now listening for sleep events and forcing the device into sleep mode when necessary. Display state is now cached and handled properly for cases where the device wakes up and should go back to sleep. Test: atest LockScreenWakeUpControllerTest Test: manual Bug: 111414690 Bug: 111405682 Fixes: 120864496 Change-Id: I3096329e8f6a07a686582d35c4b0e9977bf9ab1b
* Wake-up sensors integrationLucas Dupin2018-11-161-2/+15
| | | | | | | Bug: 111414690 Bug: 111405682 Test: manual Change-Id: I9db42b3e5f1964ebe1e52066b1eecf0754e6e3b7
* Renaming gestureLucas Dupin2018-09-281-4/+4
| | | | | | Bug: 111414690 Test: make Change-Id: I9d2a6507a942c56fe5b626d8dce46321ff70014b
* Merge "Log time tick alarms"TreeHugger Robot2018-09-061-0/+6
|\
| * Log time tick alarmsLucas Dupin2018-09-061-0/+6
| | | | | | | | | | | | | | | | | | So we can be sure that our time ticks were scheduled and are working properly - or not. Change-Id: I6b3beac69a324ea577ce2f14d041b6b90d1f9800 Fixes: 113550401 Test: adb shell dumpsys activity service com.android.systemui
* | Wake-screen gesture implementationLucas Dupin2018-09-051-12/+14
|/ | | | | | | Bug: 111414690 Test: adb shell dumpsys activity service com.android.systemui Test: manual with alternative sensor event Change-Id: Ib38085388c0e9ebce9eb59712cdfde5f8d7ccc8c
* Reach gesture implementationLucas Dupin2018-08-161-1/+8
| | | | | | | | | | Add configurable doze gesture. OEMs should define the gesture type on a device overlay. Bug: 111414690 Test: look at logs in adb shell dumpsys activity service com.android.systemui Test: manual with alternative sensor event Change-Id: I048b99b53151427006e42eb6b4780a420020cd78
* Double tap and lift should take to lock screenLucas Dupin2018-08-101-2/+2
| | | | | | | | | | | | | | The current ambient display design doesn't make sense when the display is not 'always on', let's wake-up directly to the lock screen instead. Change-Id: I217720dcf01a507f43e9da6e1970b2246fb75211 Test: double tap from AOD or screen off Test: lift from AOD or screen off Test: receive pulsing notification, long press Fixes: 73148491 Fixes: 111881300 Bug: 111414690
* AOD: When prox covered disable touch during pulse instead of abortingAdrian Roos2017-07-281-2/+7
| | | | | | | | | | | | | Fixes a UX issue where covering the prox would abort dozing. This was done to prevent falsing and save power, but in practice results in a frustrating experience when the proximity sensor is covered transiently when reaching for the device. Instead, just ignore touch while the sensor is covered. Change-Id: Id70f8605c6c7a37288a383d587025bb9b4191b42 Fixes: 64007762 Test: Trigger AOD2, cover sensor. Verify phone stays on but double tap does nothing.
* AOD: Implement long press gesture to launch assistAdrian Roos2017-07-121-1/+3
| | | | | | Bug: 37684244 Test: adb shell settings put secure doze_pulse_on_long_press 1; turn screen off, long press, verify assistant is launched Change-Id: I87335d3c091bbb17022d79e599f46fb826039b7d
generated by cgit v1.2.3 (git 2.25.1) at 2026-01-13 13:33:32 +0000