* android.hardware.sensors@aidl-multihal sources taken from hardware/interfaces @ android-13.0.0_r3
Change-Id: Ifec53372d142dcaf3f2111431ee2b3c2674744f2
* DRP is not supported, switch back to what we had with our old 1.1-typec HAL
* Restores support for external display
Change-Id: I0792a629bb082ceb95582bc28447d7cdea757f2e
* Helps with the now rare enrollment calibration errors we get
and also with fingerprint enrollment after enrolling a fingerprint
in DSU (without this it constantly fails with calibration error after that)
[Linux4: Pass 1 as parameter and unconditionally call it]
Change-Id: Idde4a4b06efc279d227ab2e3b4056ed8855dbf8f
* used by Exynos 850 devices
* requires a kernel patch in touchscreen driver to invert reported proximity values,
see d7ab9befc3
Change-Id: I3d5d7de2f6ef7877490fa36968a4c07e0ac1e40e
While Google found that fingerprint HAL is insensitive to
increased CPU throughput, we have not found that to be the
case. Allowing more CPUs makes fingerprint unlock up to
2x faster in some tests.
SM8250 device with fingerprint on display:
- Before: 3128ms
- After: 944ms
SDM845 device with fingerprint on the power button:
- Before: 1146ms
- After: 688ms
This reverts commit d0fdb4431d26e4f257b8867f67ffd9b4a9818d9e.
Change-Id: I7a28d82caee2b8503b974a8226b29240eb072ceb
* Move fingerprint HIDL to 2.3
* Remove Lineage FOD HIDL
[Linux4: Autodetect if fingerprint is udfps]
Change-Id: I8c628d2ee9158b45eeb04dd324b56ef3697296b7
sensors: 2.1: get rid of com.samsung.permission.SSENSOR
Samsung uses a permission com.samsung.permission.SSENSOR
for Samsung-specfic sensors. Android obviously does not
have that and the default is denied when there is no
permission. As such, those sensors are inaccessible.
Thus, this change removes this permission from those sensors
so we can use them.
Android does not require special permissions for most sensors
so this change doesn't attach additional permission requirements
to those sensors.
However, note that it is possible that some sensitive sensors
introduced by Samsung in the future may use SSENSOR permission
and for privacy reasons they should be handled separately with
appropriate permission control attached.
Change-Id: Ia3033898722039b285e522e226074238508f6093
sensors: 2.1: map Samsung proximity sensor type to generic
Samsung uses their own com.samsung.sensor.physical_proximity
type instead of SENSOR_TYPE_PROXIMITY of Android.
This makes proximity sensor unavailable for us as we only
look for SENSOR_TYPE_PROXIMITY.
Thus, this change maps Samsung's vendor-specific proximity
sensor type to generic one.
Change-Id: I64f6558876e1398dfbea0e5c0eb76aa1aafd2dfd
sensors: 2.1: set max range of proximity sensor to 1
Samsung's proximity sensor type is binary in nature.
There are only two state: FAR and NEAR.
However, Samsung uses values between min and max for
other purposes like proximity detection during Always-On
Display.
This breaks proximity detection during Doze for AOSP as
AOSP only considers the proximity sensor in FAR state
when the value equals or larger than max.
Thus, this change sets the max to 1 so any > 1 value
would be considered as FAR and the behavior of this vendor
proximity sensor type matches the behavior expected by AOSP.
Change-Id: I56af8e2ae743b47e3c4894e5ef68ce0b54e5cfdb
hidl:sensors: 2.1 Dump sensor information if verbose is turned on
This is useful for improving the sensors HAL.
Change-Id: I41430974b40e14095396aaf645b8b37d08b13710
sensors: 2.1: declare override="true" in manifest
Change-Id: If8349ca7b8102c3ffee545d1065d0e7d08d22652
* Newer samsung devices require 2.X implementation of the sensor
HAL, in order to avoid issues with importing 2.X service to existing
directory, move each to its subdir
Signed-off-by: josip-k <d3hum4niz3d@gmail.com>
Change-Id: If6fc05c166ba488e0be90ec59c9c79ac29c92d79
Bruno Martins