From 9ec8976f41e12fe83e7bbc8abcf456ccb459d97e Mon Sep 17 00:00:00 2001 From: Joshua McCloskey Date: Fri, 4 Nov 2022 15:39:46 +0000 Subject: [PATCH] Removed lockdown check for detectFingerprint Test: Verified the api can now be called when the phone is not locked down. Bug: 245778799 Change-Id: I0f0ee0d33312efc4b27fe6d525c7500d366fb3dc --- .../biometrics/sensors/fingerprint/FingerprintService.java | 7 ------- 1 file changed, 7 deletions(-) diff --git a/services/core/java/com/android/server/biometrics/sensors/fingerprint/FingerprintService.java b/services/core/java/com/android/server/biometrics/sensors/fingerprint/FingerprintService.java index 1c57151ed7bd1..229393def27f7 100644 --- a/services/core/java/com/android/server/biometrics/sensors/fingerprint/FingerprintService.java +++ b/services/core/java/com/android/server/biometrics/sensors/fingerprint/FingerprintService.java @@ -421,13 +421,6 @@ public class FingerprintService extends SystemService { return -1; } - if (!Utils.isUserEncryptedOrLockdown(mLockPatternUtils, userId)) { - // If this happens, something in KeyguardUpdateMonitor is wrong. This should only - // ever be invoked when the user is encrypted or lockdown. - Slog.e(TAG, "detectFingerprint invoked when user is not encrypted or lockdown"); - return -1; - } - final Pair provider = mRegistry.getSingleProvider(); if (provider == null) { Slog.w(TAG, "Null provider for detectFingerprint");