diff options
| author | dooyoung.hwang <dooyoung.hwang@lge.com> | 2015-05-21 16:09:43 +0900 |
|---|---|---|
| committer | Adrian Roos <roosa@google.com> | 2015-06-02 03:01:20 +0000 |
| commit | 328472ebd8f9c139fef1ad859ed4f7b43b3f86c6 (patch) | |
| tree | 054dc93dd5a63fefacbf1d940b77bd72f36c312c /tools/aapt2/java/JavaClassGenerator_test.cpp | |
| parent | db2911321b1cb0870d10baab370c93da13a91067 (diff) | |
Patches for IKeyguardStateCallback
1. Also notify input is restricted or not when IKeyguardStateCallback callback is added.
When first Keyguard is showing after boot, the mInputRestricted is not updated. So,
inKeyguardRestrictedInputMode still returns false, although device is locked.
2. If mShowing remains false during setup time of KeyguardViewMediator, mInputRestricted
is not updated. This is because updateInputRestrictedLocked is called only if showing
value is changed during setup time.
For this reason, when device is not provisioned, inKeyguardRestrictedInputMode returns
false, and device does not restrict key.
3. If one of callbacks causes RemoteException, the other callbacks are not called.
This is because catching RemoteException breaks for-loop.
(cherry-picked from commit 516dad062580201d7a4ad6c112b23434385d5268)
Change-Id: I0281405127bcc75285b908d01485da3ac9b40b52
Signed-off-by: Dooyoung Hwang <dooyoung.hwang@lge.com>
Diffstat (limited to 'tools/aapt2/java/JavaClassGenerator_test.cpp')
0 files changed, 0 insertions, 0 deletions