dubai: Debrand manifests & overlays

This makes it easier to compare devices and/or convert device trees.

Change-Id: I74edc128a9c825cbc3189a6c1594ac5b19bae591
This commit is contained in:
Michael Bestas 2025-01-21 08:21:48 +02:00
parent 0e3357e8e6
commit 65585bf2bf
No known key found for this signature in database
GPG key ID: CC95044519BE6669
26 changed files with 2 additions and 2 deletions

View file

@ -0,0 +1,5 @@
runtime_resource_overlay {
name: "SystemUIResDubai",
sdk_version: "current",
vendor: true
}

View file

@ -0,0 +1,10 @@
<?xml version="1.0" encoding="utf-8"?>
<!--
Copyright (C) 2022 The LineageOS Project
SPDX-License-Identifier: Apache-2.0
-->
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
coreApp="true"
package="com.android.systemui.overlay.dubai">
<overlay android:targetPackage="com.android.systemui" android:isStatic="true" />
</manifest>

View file

@ -0,0 +1,35 @@
<?xml version="1.0" encoding="utf-8"?>
<!--
Copyright (C) 2022 The LineageOS Project
SPDX-License-Identifier: Apache-2.0
-->
<resources xmlns:xliff="urn:oasis:names:tc:xliff:document:1.2">
<!-- A path similar to frameworks/base/core/res/res/values/config.xml
config_mainBuiltInDisplayCutout that describes a path larger than the exact path of a display
cutout. If present as well as config_enableDisplayCutoutProtection is set to true, then
SystemUI will draw this "protection path" instead of the display cutout path that is normally
used for anti-aliasing.
This path will only be drawn when the front-facing camera turns on, otherwise the main
DisplayCutout path will be rendered
-->
<string translatable="false" name="config_frontBuiltInDisplayCutoutProtection">
M 498.5,65
a 41.5,41.5 0 1 0 83,0
a 41.5,41.5 0 1 0 -83,0
Z
</string>
<!-- ID for the camera that needs extra protection -->
<string translatable="false" name="config_protectedCameraId">1</string>
<!-- Flag to turn on the rendering of the above path or not -->
<bool name="config_enableDisplayCutoutProtection">true</bool>
<!-- Microns/ums (1000 um = 1mm) per pixel for the given device. If unspecified, UI that
relies on this value will not be sized correctly. -->
<item name="pixel_pitch" format="float" type="dimen">48.3</item>
</resources>

View file

@ -0,0 +1,37 @@
<?xml version="1.0" encoding="utf-8"?>
<!--
Copyright (C) 2022 The LineageOS Project
SPDX-License-Identifier: Apache-2.0
-->
<resources>
<!-- the padding on the start of the statusbar -->
<dimen name="status_bar_padding_start">20.0dip</dimen>
<!-- The padding on the end of the statusbar -->
<dimen name="status_bar_padding_end">7.0dip</dimen>
<!-- The padding on the top of the statusbar (usually 0) -->
<dimen name="status_bar_padding_top">20.0px</dimen>
<!-- Height of the status bar header bar when on Keyguard -->
<dimen name="status_bar_header_height_keyguard">@*android:dimen/status_bar_height</dimen>
<!-- Margin on the left side of the carrier text on Keyguard -->
<dimen name="keyguard_carrier_text_margin">4dp</dimen>
<!-- Margin on the right side of the system icon group on Keyguard. -->
<dimen name="system_icons_keyguard_padding_end">10.0px</dimen>
<!-- Bottom margin size when fingerprint in display is active -->
<dimen name="keyguard_indication_margin_bottom">15dp</dimen>
<!-- Location on the screen of the center of the physical power button. -->
<dimen name="physical_power_button_center_screen_location_y">1000.0px</dimen>
<!-- Location on the screen of the center of the physical volume up/down buttons. -->
<dimen name="physical_volume_up_button_center_screen_location_y">600.0px</dimen>
<dimen name="physical_volume_down_button_center_screen_location_y">760.0px</dimen>
<!-- Total minimum padding to enforce to ensure that the dot can always show -->
<dimen name="ongoing_appops_dot_min_padding">14dp</dimen>
</resources>

View file

@ -0,0 +1,8 @@
<?xml version="1.0" encoding="utf-8"?>
<!--
Copyright (C) 2022 The LineageOS Project
SPDX-License-Identifier: Apache-2.0
-->
<resources>
<integer name="config_showUsbPortAlarm">1</integer>
</resources>