diff options
author | tingna_sung <tingna_sung@htc.com> | 2015-05-12 13:23:15 +0800 |
---|---|---|
committer | tingna_sung <tingna_sung@htc.com> | 2015-05-18 13:56:34 +0800 |
commit | 38cd664c68d0ae41e88a7e2471f1ba84394562ee (patch) | |
tree | da16df066dc9a2cc44c34772de9b225b66a27486 /rs/java/android/renderscript/Allocation.java | |
parent | a194eb9b5d36acc083aa55b9a152567d68e84f14 (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>
Diffstat (limited to 'rs/java/android/renderscript/Allocation.java')
0 files changed, 0 insertions, 0 deletions