The new authenticatorId will always be needed by the client after
invalidation finishes. This change allows the client to receive it
without requesting getAuthenticatorId.
Test: m android.hardware.biometrics.face-update-api
Test: m android.hardware.biometrics.fingerprint-update-api
Test: m VtsHalBiometricsFaceTargetTest
Test: m VtsHalBiometricsFingerprintTargetTest
Bug: 159667191
Change-Id: I63166315789945966ff8081e07dd714cc14bc2f0
Note that we're configuring this default HAL as "STRONG" so that the
framework can eventually test multi-sensor authenticatorId invalidation
Bug: 173453845
Test: atest CtsBiometricsTestCases
Change-Id: Idd7b74f0a22c5078dc5c2b0b99f62fdc4b51e25d
These methods were moved into ISession, but forgot to remove the
sensorId, userId parameters
Bug: 173453845
Test: m android.hardware.biometrics.face-update-api
Test: m android.hardware.biometrics.face-service.example
Test: m VtsHalBiometricsFaceTargetTest
Change-Id: I78efd095e0b86f8a8568c8d74d946fd8436f6e65
1) Removes HAT param from fingerprint AIDL
2) Update documentation for fingerprint and face AIDL
Fixes: 173432893
Test: m android.hardware.biometrics.face-update-api
Test: m android.hardware.biometrics.fingerprint-service.example
Change-Id: I9c5e219c6f7a59609b6ff9d692f5a931f4bcea24
Fixes: 168541000
Test: m android.hardware.biometrics.face-update-api
Test: m android.hardware.biometrics.face-service.example
Change-Id: I664fe1f641e09217b27aef232e39ba7d6fa1e171