summaryrefslogtreecommitdiff
path: root/tools/aapt2/java/JavaClassGenerator_test.cpp
diff options
context:
space:
mode:
authorKevin Chyn <kchyn@google.com>2017-05-06 15:11:53 -0700
committerKevin Chyn <kchyn@google.com>2017-05-08 15:33:27 -0700
commit3fdbbf87bd0c7a1b8cca3ef0ff5a441876d5c8d1 (patch)
treeba427bd34a944c0854df44be52abd5008fbd2a4d /tools/aapt2/java/JavaClassGenerator_test.cpp
parenta6cf18f431348087e88847cc6fdcd703ec833826 (diff)
update trust state immediately when user auths via FP on keyguard
KeyguardUpdateMonitor onFingerprintAuthenticated currently doesn't immediately update the trust state. TrustManager.isDeviceLocked() should return "unlocked" after FP is authenticated. Fixes: 37963501 Test: Two tests as follows 1) use custom app that polls isDeviceLocked(), make sure it returns "unlocked" after FP is authenticated but keyguard is showing. To get that state, slide keyguard up slightly and touch FP sensor without letting go of the other finger. 2) with at least 2 accounts, run the app on both accounts. when switching users, the app should show that the "inactive/underneath" user is locked. the app should report that the current user is locked before touching fp, and unlocked after touching fp Change-Id: I2a11411deebf369d85dee62cffdcd631bd99649f
Diffstat (limited to 'tools/aapt2/java/JavaClassGenerator_test.cpp')
0 files changed, 0 insertions, 0 deletions