Evolution-X-Devices/device_xiaomi_umi
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

umi: overlay: Configure cutout

Browse Source
This commit is contained in:
Bartłomiej Rudecki
2024-02-08 19:17:25 +01:00
committed by Yumi Yukimura
parent e22ce74927
commit c396116ddf
2 changed files with 40 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

33
overlay/frameworks/base/core/res/res/values/config.xml
View File

@@ -444,4 +444,37 @@
<!-- How long it takes for the HW to start illuminating after the illumination is requested. -->
<integer name="config_udfps_illumination_transition_ms">0</integer>
<!-- 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.
-->
<string name="config_mainBuiltInDisplayCutout" translatable="false">
M -376 58 A 31 31 0 0 1 -438 58 A 31 31 0 0 1 -376 58 Z M -438,0 L -391,0 Z M -540,0 L -540,90 Z
</string>
<!-- Like config_mainBuiltInDisplayCutout, but this path is used to report the
one single bounding rect per device edge to the app via
{@link DisplayCutout#getBoundingRect}. Note that this path should try to match the visual
appearance of the cutout as much as possible, and may be smaller than
config_mainBuiltInDisplayCutout
-->
<string name="config_mainBuiltInDisplayCutoutRectApproximation" translatable="false">
M -903,0 H -1080 V 90 H -903 V 0 Z@right
</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">true</bool>
</resources>

8
overlay/frameworks/base/packages/SystemUI/res/values/dimens.xml
View File

@@ -20,11 +20,17 @@
<dimen name="rounded_corner_content_padding">7dp</dimen>
<!-- the padding on the start of the statusbar -->
<dimen name="status_bar_padding_start">178px</dimen>
<dimen name="status_bar_padding_start">0px</dimen>
<!-- the padding on the top of the statusbar (usually 0) -->
<dimen name="status_bar_padding_top">34px</dimen>
<!-- Margin on the left side of the carrier text on Keyguard -->
<dimen name="keyguard_carrier_text_margin">178px</dimen>
<!-- The padding on the end of the status bar. -->
<dimen name="status_bar_padding_end">18px</dimen>
<!-- Margin on the right side of the system icon group on Keyguard. -->
<dimen name="system_icons_keyguard_padding_end">@dimen/status_bar_padding_end</dimen>
</resources>