diff options
| author | tingna_sung <tingna_sung@htc.com> | 2015-05-12 13:23:15 +0800 |
|---|---|---|
| committer | Wale Ogunwale <ogunwale@google.com> | 2015-06-01 07:56:55 -0700 |
| commit | e785ffa059dcb3bcff242ae4c89cdb43b081dcb2 (patch) | |
| tree | ec931f252309f413073e852cfec0e8b8879b3f3d /tools/aapt2/java/JavaClassGenerator_test.cpp | |
| parent | 55b4b2d5a82ef7999a32b8163340a15085b2df38 (diff) | |
Should reset mDismissKeyguard on keyguard secure change
If user sets a non-secure lock screen, launch an activity which
appends window flag FLAG_DISMISS_KEYGUARD, then insert a PIN lock
SIM card, activity window will become black screen.
This is because mDismissKeyguard keeps on DISMISS_KEYGUARD_CONTINUE
when keyguard secure changes from non-secure to secure like in the
insert PIN lock SIM card case. If mDismissKeyguard is
DISMISS_KEYGUARD_CONTINUE and keyguard is secure, there is no chance
to launch keyguard unlock window anymore.
This patch handles the use case that to reset mDismissKeyguard to a
new cycle from DISMISS_KEYGUARD_START to DISMISS_KEYGUARD_CONTINUE
again once keyguard secure state change suddenly to let keyguard
window has chance to be launched.
https://code.google.com/p/android/issues/detail?id=78806
Change-Id: I0d4fd0b9bdf7d0a39f35427bfd4e1b928d9bca6b
Signed-off-by: tingna_sung <tingna_sung@htc.com>
Conflicts:
policy/src/com/android/internal/policy/impl/PhoneWindowManager.java
Diffstat (limited to 'tools/aapt2/java/JavaClassGenerator_test.cpp')
0 files changed, 0 insertions, 0 deletions