Do not update cache on screen lifecycle
The authentication state is unrelated to the screen lifecycle, keyguard
visibility events should be used instead to track the state.
We still have #onKeyguardVisibilityChanged and #onBiometricsCleared that
will make sure that the state will be updated properly and callbacks
will be triggered.
The call to #onScreenTurnedOff was introduced to work around face auth
when the device was not interactive. This CL doesn't cause a regression
because 1) the device now wakes up whenver face auth happens, 2) the new
biometrics cleared callback would be invoked.
(Also using this CL to daggerize some components since tests started to
fail with dependency entanglement ⚛️)
Test: atest KeyguardStateControllerTest
Test: reach, auth, sleep, reach
Bug: 139363827
Bug: 138786270
Change-Id: I0a1e86f3e8a69ffab4a621f9ce15034a0e35fa31
59 files changed