marble: overlay: Configure sfps overlay
- Apparently there are 2 DisplayIds for marble, i.e, CN and other regions. config_sfps_sensor_props_0 worked well for CN variants meanwhile the fingerprint overlay was giving some problems on another variants. - Adding config_sfps_sensor_props_1 with IN variant's DisplayId seemed to solve this problem. Change-Id: Iae213911cf4c3c2722ed9497a29d34849111a95c
This commit is contained in:
@@ -308,6 +308,28 @@
|
||||
-->
|
||||
<string name="config_mainBuiltInDisplayCutout" translatable="false">M 0,0 H -28 V 94 H 28 V 0 H 0 Z</string>
|
||||
|
||||
<!-- An array of arrays of side fingerprint sensor properties relative to each display.
|
||||
Note: this value is temporary and is expected to be queried directly
|
||||
from the HAL in the future. -->
|
||||
<array name="config_sfps_sensor_props" translatable="false">
|
||||
<item>@array/config_sfps_sensor_props_0</item>
|
||||
<item>@array/config_sfps_sensor_props_1</item>
|
||||
</array>
|
||||
|
||||
<array name="config_sfps_sensor_props_0" translatable="false">
|
||||
<item>local:4630946480857061761</item> <!-- displayId -->
|
||||
<item>1080</item> <!-- sensorLocationX -->
|
||||
<item>920</item> <!-- sensorLocationY -->
|
||||
<item>210</item> <!-- sensorRadius -->
|
||||
</array>
|
||||
|
||||
<array name="config_sfps_sensor_props_1" translatable="false">
|
||||
<item>local:4630946370515662721</item> <!-- displayId -->
|
||||
<item>1080</item> <!-- sensorLocationX -->
|
||||
<item>920</item> <!-- sensorLocationY -->
|
||||
<item>210</item> <!-- sensorRadius -->
|
||||
</array>
|
||||
|
||||
<!-- Whether device implements proximity sensor based checks to prevent
|
||||
accidental unlocks when the screen is off. -->
|
||||
<bool name="config_proximityCheckOnFpsUnlock">true</bool>
|
||||
|
||||
Reference in New Issue
Block a user