hardware_samsung/hidl/sensors/2.1/android.hardware.sensors@2....

<manifest version="1.0" type="device">
    <hal format="hidl" override="true">
        <name>android.hardware.sensors</name>
        <transport>hwbinder</transport>
        <version>2.1</version>
        <interface>
            <name>ISensors</name>
            <instance>default</instance>
        </interface>
    </hal>
</manifest>
samsung: hidl: import default sensors 2.1 multihal * hardware/interfaces/sensors/2.1/multihal from android-11.0.0_r27 Signed-off-by: josip-k <d3hum4niz3d@gmail.com> Change-Id: I253755c6a46873c04b65d4c14fea65e3c5308f0b 4 years ago			`<manifest version="1.0" type="device">`
sensors: 2.1: Squash previous sensors commits 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 4 years ago			`<hal format="hidl" override="true">`
samsung: hidl: import default sensors 2.1 multihal * hardware/interfaces/sensors/2.1/multihal from android-11.0.0_r27 Signed-off-by: josip-k <d3hum4niz3d@gmail.com> Change-Id: I253755c6a46873c04b65d4c14fea65e3c5308f0b 4 years ago			`<name>android.hardware.sensors</name>`
			`<transport>hwbinder</transport>`
			`<version>2.1</version>`
			`<interface>`
			`<name>ISensors</name>`
			`<instance>default</instance>`
			`</interface>`
			`</hal>`
			`</manifest>`