Per-user fingerprint lockout
Also changed from AlarmManager.set() to AlarmManager.setExact(), since
this should be infrequent and not impact power savings (alarm batching)
Fixes: 64485566
Test: manual test with multiple users, with added logs in
schedule/cancelLockoutResetForUser
Change-Id: I54a2058ddc081ab843bb37efe68913eca0a91916
Loading
Please register or sign in to comment