mirror of
https://github.com/Anything-at-25-00/android_device_tecno_LG8n.git
synced 2024-11-25 15:06:26 -08:00
LG8n: overlay: Import Display Cutout data and Configure refresh rate
Co-authored-by: dodyirawan85 <dev.irawans@gmail.com> Signed-off-by: Shirayuki39 <lorddemecrius83@proton.me>
This commit is contained in:
parent
26c00c0c76
commit
9f285c4a05
|
@ -105,7 +105,47 @@
|
||||||
<!-- Light sensor event rate in milliseconds for automatic brightness control. -->
|
<!-- Light sensor event rate in milliseconds for automatic brightness control. -->
|
||||||
<integer name="config_autoBrightnessLightSensorRate">250</integer>
|
<integer name="config_autoBrightnessLightSensorRate">250</integer>
|
||||||
|
|
||||||
<!-- Whether device uses power button fingerprint sensor or not -->
|
<!-- The bounding path of the cutout region of the main built-in display.
|
||||||
|
Must either be empty if there is no cutout region, or a string that is parsable by
|
||||||
|
{@link android.util.PathParser}.
|
||||||
|
The path is assumed to be specified in display coordinates with pixel units and in
|
||||||
|
the display's native orientation, with the origin of the coordinate system at the
|
||||||
|
center top of the display. Optionally, you can append either `@left` or `@right` to the
|
||||||
|
end of the path string, in order to change the path origin to either the top left,
|
||||||
|
or top right of the display.
|
||||||
|
To facilitate writing device-independent emulation overlays, the marker `@dp` can be
|
||||||
|
appended after the path string to interpret coordinates in dp instead of px units.
|
||||||
|
Note that a physical cutout should be configured in pixels for the best results.
|
||||||
|
Example for a 10px x 10px square top-center cutout:
|
||||||
|
<string ...>M -5,0 L -5,10 L 5,10 L 5,0 Z</string>
|
||||||
|
Example for a 10dp x 10dp square top-center cutout:
|
||||||
|
<string ...>M -5,0 L -5,10 L 5,10 L 5,0 Z @dp</string>
|
||||||
|
@see https://www.w3.org/TR/SVG/paths.html#PathData
|
||||||
|
-->
|
||||||
|
<string name="config_mainBuiltInDisplayCutout">M -24,0 L -24,36 L 24,36 L 24,0 Z @dp</string>
|
||||||
|
|
||||||
|
<!-- Whether the display cutout region of the main built-in display should be forced to
|
||||||
|
black in software (to avoid aliasing or emulate a cutout that is not physically existent).
|
||||||
|
-->
|
||||||
|
<bool name="config_fillMainBuiltInDisplayCutout">false</bool>
|
||||||
|
|
||||||
|
<!-- The default refresh rate for a given device. Change this value to set a higher default
|
||||||
|
refresh rate. If the hardware composer on the device supports display modes with a higher
|
||||||
|
refresh rate than the default value specified here, the framework may use those higher
|
||||||
|
refresh rate modes if an app chooses one by setting preferredDisplayModeId or calling
|
||||||
|
setFrameRate().
|
||||||
|
If a non-zero value is set for config_defaultPeakRefreshRate, then
|
||||||
|
config_defaultRefreshRate may be set to 0, in which case the value set for
|
||||||
|
config_defaultPeakRefreshRate will act as the default frame rate. -->
|
||||||
|
<integer name="config_defaultRefreshRate">0</integer>
|
||||||
|
|
||||||
|
<!-- The default peak refresh rate for a given device. Change this value if you want to prevent
|
||||||
|
the framework from using higher refresh rates, even if display modes with higher refresh
|
||||||
|
rates are available from hardware composer. Only has an effect if the value is
|
||||||
|
non-zero. -->
|
||||||
|
<integer name="config_defaultPeakRefreshRate">90</integer>
|
||||||
|
|
||||||
|
<!-- Indicates whether device has a power button fingerprint sensor. -->
|
||||||
<bool name="config_is_powerbutton_fps">true</bool>
|
<bool name="config_is_powerbutton_fps">true</bool>
|
||||||
|
|
||||||
<!-- An array of arrays of side fingerprint sensor properties relative to each display.
|
<!-- An array of arrays of side fingerprint sensor properties relative to each display.
|
||||||
|
|
Loading…
Reference in a new issue