tree 5803b05e7d20b58db73005574b87024233a23972
parent abc127673bf8f030cfb92d2f94d8f14baf9cd2aa
author Joe Bolinger <jbolinger@google.com> 1642107470 -0800
committer Joe Bolinger <jbolinger@google.com> 1643159278 +0000

Check current user when the operations runs for fingerprint hidl.

The current and target user are both provided to the switch
client constructor which is brittle unless operations are scheduled and
run synchronously. Commit 9a99503870074d40d794245d9e3ac7a076f5b2f2
changed the handlers and somehow caused a bug where the cached current
user was out of sync. The switch client tries to optimize for this and
can skip switching when that occurs.

This also includes two additonal changes 1) a few updated logs from
the original change and 2) restores each scheduling having its own
handler for clarity.

Bug: 213962104
Bug: 210090299
Test: atest UserAwareBiometricSchedulerTest BiometricSchedulerTest BiometricSchedulerOperationTest  SensorTest Face10Test
Test: manual (flash, enroll fingerprint, add work profile account, reboot, verify fingerprint still works)

Change-Id: Ifb73b0145aeb8afb62d1f55d2f881347b0d2ef8a
Merged-In: Ifb73b0145aeb8afb62d1f55d2f881347b0d2ef8a