From 0b1853f997e175dc9cf4b93088f63b774f05253f Mon Sep 17 00:00:00 2001 From: Adrian Roos Date: Mon, 23 Jan 2017 12:38:13 -0800 Subject: [PATCH] KeyguardManager: Fix user resolution of isDeviceSecure/Locked Fixes isDeviceSecure and isDeviceLocked APIs to use the user id of the app that executes the code rather than that of any incoming binder call. Change-Id: Ib7772b60c35a3ebf96830f9b013c539021e1f063 Fixes: 34592592 Test: manual --- core/java/android/app/KeyguardManager.java | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/core/java/android/app/KeyguardManager.java b/core/java/android/app/KeyguardManager.java index 036b47cafe645..6793c90f9be1c 100644 --- a/core/java/android/app/KeyguardManager.java +++ b/core/java/android/app/KeyguardManager.java @@ -322,7 +322,7 @@ public class KeyguardManager { * password. */ public boolean isDeviceLocked() { - return isDeviceLocked(UserHandle.getCallingUserId()); + return isDeviceLocked(UserHandle.myUserId()); } /** @@ -347,7 +347,7 @@ public class KeyguardManager { * @return true if a PIN, pattern or password was set. */ public boolean isDeviceSecure() { - return isDeviceSecure(UserHandle.getCallingUserId()); + return isDeviceSecure(UserHandle.myUserId()); } /**