Add halHandlesDisplayTouches and halControlsIllumination
Bug: 185522754 Test: m android.hardware.biometrics.fingerprint-update-api Change-Id: I3a1e71951e202212c0a0951d1b64249436619f56
This commit is contained in:
parent
a6d4024cb2
commit
d85ab6f7a7
2 changed files with 24 additions and 0 deletions
|
@ -39,4 +39,6 @@ parcelable SensorProps {
|
|||
android.hardware.biometrics.fingerprint.SensorLocation[] sensorLocations;
|
||||
boolean supportsNavigationGestures;
|
||||
boolean supportsDetectInteraction;
|
||||
boolean halHandlesDisplayTouches;
|
||||
boolean halControlsIllumination;
|
||||
}
|
||||
|
|
|
@ -48,4 +48,26 @@ parcelable SensorProps {
|
|||
* Specifies whether or not the implementation supports ISession#detectInteraction.
|
||||
*/
|
||||
boolean supportsDetectInteraction;
|
||||
|
||||
/**
|
||||
* Whether the HAL is responsible for detecting and processing of display touches. This is only
|
||||
* applicable to under-display fingerprint sensors (UDFPS). If the value is false, the framework
|
||||
* will be responsible for handling the display touch events and passing them down to the HAL by
|
||||
* using ISession#onPointerDown and ISession#onPointerUp. If the value is true, the framework
|
||||
* will not notify the HAL about touch events.
|
||||
*
|
||||
* This value must be ignored for non-UDFPS sensors.
|
||||
*/
|
||||
boolean halHandlesDisplayTouches;
|
||||
|
||||
/**
|
||||
* Whether the HAL is responsible for fingerprint illumination, for example through enabling the
|
||||
* display's high-brightness mode. This is only applicable to optical under-display fingerprint
|
||||
* sensors (optical UDFPS). If the value is false, the framework will be responsible for
|
||||
* illuminating the finger and reporting ISession#onUiReady. If the value is true, the framework
|
||||
* will not illuminate the finger and will not report ISession#onUiReady.
|
||||
*
|
||||
* This value must be ignored for sensors that aren't optical UDFPS.
|
||||
*/
|
||||
boolean halControlsIllumination;
|
||||
}
|
||||
|
|
Loading…
Reference in a new issue