Fix ambient display

Due to a refactoring for touch, wake and unlock for fingerprint
devices PhoneWindowManager now waits for Keyguard to draw its first
frame in all cases, including when screen turns on for pulsing.
However, since in this case the device is not awake, we need to check
for screen on instead of awakeness when proceeding with the wake-up
sequence. Without this change, screen on was blocked forever in the
pulsing case.

Bug: 22605235
Change-Id: Ib6089fd14b673e62347f2c9108d9a6783caa26b7
This commit is contained in:
Jorim Jaggi
2015-07-24 12:32:42 -07:00
parent 2a493532e6
commit f325548992

View File

@@ -5527,7 +5527,7 @@ public class PhoneWindowManager implements WindowManagerPolicy {
private void finishKeyguardDrawn() { private void finishKeyguardDrawn() {
synchronized (mLock) { synchronized (mLock) {
if (!mAwake || mKeyguardDrawComplete) { if (!mScreenOnEarly || mKeyguardDrawComplete) {
return; // We are not awake yet or we have already informed of this event. return; // We are not awake yet or we have already informed of this event.
} }