*Set correct X and Y position and size per device, according to set_fod_rect
*Check bootloader in a seperate method
*Correct dot radius in overlay
Change-Id: I1b15ceeba189dd4279e31e5ebeeba8d722592153
*Brightness should be boosted only when fingerprint is pressed to correctly light up the screen
*Return 0 in getDimAmount since we dont want to dim the screen
*Set brightness to 331 instead of 319 since this is default on A52 stock
Change-Id: Ieccc170f14e75f3ec998bb5d4a10b8dc49085cc7
*Instead of dimming the screen when the sensor is pressed we should boost the brightness for better results
*This also makes fingerprint work even when the screen brightness is at its minimum
*Implement a 120ms delay to wait for the brightness to be boosted
Change-Id: I23ff521c289347b4b1c92a11049c7a9670d3d819
Samsung enables FOD in TS driver (fod_enable) at all times except
a small number of optical FOD sensor that doesn't have BiometricFeature
.FEATURE_SUPPORT_AOD. As optical type sensor support is not implemented
currently, this HAL is only used on device that has FOD always-on.
This change follows behavior of stock firmware and without toggling of
FOD enable state FOD should be more stable.
Plus it allows setInteractive and config_powerDecoupleInteractiveModeFromDisplay
to function properly with FOD. Currently setInteractive(0) happens before
a onShowFODView (which is the current point to call fod_enable) can be
triggered by the Doze, as TS driver only handles command when it is enabled,
FOD doesn't work when there is a setInteractive(0) that disables TS.
Signed-off-by: Michael Benedict <michaelbt@live.com>
Change-Id: If1ce9cab58717a9b9dcfce496da79bcf74773a33
Simon1511