Skip to content

SystemUI: Keep the display on when a biometric unlock ends a pulse - #1375

Closed
AnkitSavani111 wants to merge 1 commit into
crdroidandroid:17.0from
AnkitSavani111:17.0
Closed

AnkitSavani111 wants to merge 1 commit into
crdroidandroid:17.0from
AnkitSavani111:17.0

Conversation

@AnkitSavani111

Copy link
Copy Markdown

With always-on display off, a screen-off UDFPS unlock starts from a DOZE_PULSING_WITHOUT_UI pulse. BiometricUnlockController notifies its listeners (dozing=false) before it calls PowerManager.wakeUp(), so the pulse ends while wakefulness is still asleep, DozeMachine goes back to DOZE and DozeScreenState turns the display off. PowerManager turns it on again right after, and that off/on cycle costs about 500 ms ("Screen on took 530 ms") before the unlocked screen shows.

Treat a pulse that ends because of a biometric wake and unlock like one that ends while waking up, and finish dozing without touching the display state.

With always-on display off, a screen-off UDFPS unlock starts from a
DOZE_PULSING_WITHOUT_UI pulse. BiometricUnlockController notifies its
listeners (dozing=false) before it calls PowerManager.wakeUp(), so the
pulse ends while wakefulness is still asleep, DozeMachine goes back to
DOZE and DozeScreenState turns the display off. PowerManager turns it on
again right after, and that off/on cycle costs about 500 ms ("Screen on
took 530 ms") before the unlocked screen shows.

Treat a pulse that ends because of a biometric wake and unlock like one
that ends while waking up, and finish dozing without touching the
display state.

Signed-off-by: AnkitSavani111 <ankitmsavani12345@gmail.com>
@neobuddy89

Copy link
Copy Markdown
Member

4c11bcf

@neobuddy89 neobuddy89 closed this Nov 8, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants