BOBtheBlinker/android_device_motorola_milanf
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

dubai: Cleanup overlays

Browse source 
* Correct pixel_pitch
* Make AndroidManifest consistent
* Fix spacing and newlines
* Correct comments
* Sort as per AOSP order
* Correct array types
* Remove overlays that no longer exist:
  config_scrollBarrierVibePattern
  physical_volume_up_button_center_screen_location_y
  physical_volume_down_button_center_screen_location_y
  system_icons_keyguard_padding_end
* Remove overlays that are the same as defaults:
  config_deviceHardwareKeys
  config_deviceHardwareWakeKeys
  config_udfpsColor
* Remove overlays that shouldn't be overlaid anymore:
  quick_qs_offset_height
* Move config_showUsbPortAlarm to common

Change-Id: I504039ea2646b12a5af6f3c040236459ee7ac772
This commit is contained in:
Michael Bestas 2025-02-26 09:09:27 +02:00
parent 5ce27d005e
commit 7847b69d59
No known key found for this signature in database
GPG key ID: CC95044519BE6669
18 changed files with 204 additions and 252 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
resource-overlay/device/Frameworks/Android.bp
View file

@ -5,5 +5,5 @@
runtime_resource_overlay {
name: "FrameworksResDubai",
vendor: true
vendor: true,
}

6
resource-overlay/device/Frameworks/AndroidManifest.xml
View file

@ -5,5 +5,9 @@
-->
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
package="android.overlay.dubai">
<overlay android:targetPackage="android" android:isStatic="true" android:priority="600"/>
<overlay
android:isStatic="true"
android:priority="600"
android:targetPackage="android" />
</manifest>

276
resource-overlay/device/Frameworks/res/values/config.xml
View file

@ -1,10 +1,53 @@
<?xml version="1.0" encoding="utf-8"?>
<!--
SPDX-FileCopyrightText: 2022-2024 The LineageOS Project
SPDX-FileCopyrightText: 2022-2025 The LineageOS Project
SPDX-License-Identifier: Apache-2.0
-->
<resources>
<!-- Array of light sensor LUX values to define our levels for auto backlight brightness support.
<!-- Indicate whether to allow the device to suspend when the screen is off
due to the proximity sensor. This resource should only be set to true
if the sensor HAL correctly handles the proximity sensor as a wake-up source.
Otherwise, the device may fail to wake out of suspend reliably.
The default is false. -->
<bool name="config_suspendWhenScreenOffDueToProximity">true</bool>
<!-- Vibrator pattern for feedback about a long screen/key press -->
<integer-array name="config_longPressVibePattern">
<item>0</item>
<item>67</item>
</integer-array>
<!-- Vibrator pattern for feedback about touching a virtual key -->
<integer-array name="config_virtualKeyVibePattern">
<item>0</item>
<item>67</item>
</integer-array>
<!-- Vibrator pattern for feedback about booting with safe mode enabled -->
<integer-array name="config_safeModeEnabledVibePattern">
<item>0</item>
<item>0</item>
<item>94</item>
</integer-array>
<!-- Note: This setting is deprecated, please use
config_screenBrightnessSettingMinimumFloat instead -->
<integer name="config_screenBrightnessSettingMinimum">2</integer>
<!-- Stability requirements in milliseconds for accepting a new brightness level. This is used
for debouncing the light sensor. Different constants are used to debounce the light sensor
when adapting to brighter or darker environments. This parameter controls how quickly
brightness changes occur in response to an observed change in light level that exceeds the
hysteresis threshold. -->
<integer name="config_autoBrightnessBrighteningLightDebounce">500</integer>
<integer name="config_autoBrightnessDarkeningLightDebounce">500</integer>
<!-- Screen brightness used to dim the screen when the user activity
timeout expires. May be less than the minimum allowed brightness setting
that can be set by the user. -->
<integer name="config_screenBrightnessDim">2</integer>
<!-- Array of light sensor lux values to define our levels for auto backlight brightness support.
The N entries of this array define N + 1 control points as follows:
(1-based arrays)
@ -16,15 +59,15 @@
The control points must be strictly increasing. Each control point
corresponds to an entry in the brightness backlight values arrays.
For example, if LUX == level[1] (first element of the levels array)
For example, if lux == level[1] (first element of the levels array)
then the brightness will be determined by value[2] (second element
of the brightness values array).
Spline interpolation is used to determine the auto-brightness
backlight values for LUX levels between these control points.
backlight values for lux levels between these control points.
Must be overridden in platform specific overlays -->
<array name="config_autoBrightnessLevels">
<integer-array name="config_autoBrightnessLevels">
<item>2</item>
<item>4</item>
<item>5</item>
@ -35,11 +78,10 @@
<item>1250</item>
<item>3500</item>
<item>5500</item>
</array>
</integer-array>
<!-- Array of desired screen brightness in nits corresponding to the lux values
in the config_autoBrightnessLevels array. As with config_screenBrightnessMinimumNits and
config_screenBrightnessMaximumNits, the display brightness is defined as the measured
in the config_autoBrightnessLevels array. The display brightness is defined as the measured
brightness of an all-white image.
If this is defined then:
@ -50,7 +92,7 @@
This array should have size one greater than the size of the config_autoBrightnessLevels
array. The brightness values must be non-negative and non-decreasing. This must be
overridden in platform specific overlays -->
<array name="config_autoBrightnessDisplayValuesNits">
<integer-array name="config_autoBrightnessDisplayValuesNits">
<item>2</item>
<item>7</item>
<item>10</item>
@ -62,13 +104,13 @@
<item>192</item>
<item>252</item>
<item>500</item>
</array>
</integer-array>
<!-- An array describing the screen's backlight values corresponding to the brightness
values in the config_screenBrightnessNits array.
This array should be equal in size to config_screenBrightnessBacklight. -->
<array name="config_screenBrightnessBacklight">
<integer-array name="config_screenBrightnessBacklight">
<item>0</item>
<item>1</item>
<item>4</item>
@ -81,7 +123,7 @@
<item>98</item>
<item>129</item>
<item>255</item>
</array>
</integer-array>
<!-- An array of floats describing the screen brightness in nits corresponding to the backlight
values in the config_screenBrightnessBacklight array. On OLED displays these values
@ -90,7 +132,7 @@
brightness modes but only the maximum brightness value obtainable in a sustainable manner.
This array should be equal in size to config_screenBrightnessBacklight -->
<array name="config_screenBrightnessNits">
<integer-array name="config_screenBrightnessNits">
<item>0</item>
<item>2</item>
<item>7</item>
@ -103,15 +145,82 @@
<item>192</item>
<item>252</item>
<item>500</item>
</array>
</integer-array>
<!-- Stability requirements in milliseconds for accepting a new brightness level. This is used
for debouncing the light sensor. Different constants are used to debounce the light sensor
when adapting to brighter or darker environments. This parameter controls how quickly
brightness changes occur in response to an observed change in light level that exceeds the
hysteresis threshold. -->
<integer name="config_autoBrightnessBrighteningLightDebounce">500</integer>
<integer name="config_autoBrightnessDarkeningLightDebounce">500</integer>
<!-- MMS user agent string -->
<string name="config_mms_user_agent" translatable="false">motorolaedge30</string>
<!-- MMS user agent prolfile url -->
<string name="config_mms_user_agent_profile_url" translatable="false">http://uaprof.motorola.com/phoneconfig/motov1/Profile/motov1.rdf</string>
<!-- ComponentName of a dream to show whenever the system would otherwise have
gone to sleep. When the PowerManager is asked to go to sleep, it will instead
try to start this dream if possible. The dream should typically call startDozing()
to put the display into a low power state and allow the application processor
to be suspended. When the dream ends, the system will go to sleep as usual.
Specify the component name or an empty string if none.
Note that doze dreams are not subject to the same start conditions as ordinary dreams.
Doze dreams will run whenever the power manager is in a dozing state. -->
<string name="config_dozeComponent" translatable="false">com.android.systemui/com.android.systemui.doze.DozeService</string>
<!-- If true, the doze component is not started until after the screen has been
turned off and the screen off animation has been performed. -->
<bool name="config_dozeAfterScreenOffByDefault">true</bool>
<!-- Type of the double tap sensor. Empty if double tap is not supported. -->
<string name="config_dozeDoubleTapSensorType" translatable="false">org.lineageos.sensor.double_tap</string>
<!-- Type of the udfps long press sensor. Empty if long press is not supported. -->
<string name="config_dozeUdfpsLongPressSensorType" translatable="false">org.lineageos.sensor.udfps</string>
<!-- Control whether the always on display mode is available. This should only be enabled on
devices where the display has been tuned to be power efficient in DOZE and/or DOZE_SUSPEND
states. -->
<bool name="config_dozeAlwaysOnDisplayAvailable">true</bool>
<!-- Control whether the always on display mode is enabled by default. This value will be used
during initialization when the setting is still null. -->
<bool name="config_dozeAlwaysOnEnabled">false</bool>
<!-- Power Management: Specifies whether to decouple the auto-suspend state of the
device from the display on/off state.
When false, autosuspend_disable() will be called before the display is turned on
and autosuspend_enable() will be called after the display is turned off.
This mode provides best compatibility for devices using legacy power management
features such as early suspend / late resume.
When true, autosuspend_display() and autosuspend_enable() will be called
independently of whether the display is being turned on or off. This mode
enables the power manager to suspend the application processor while the
display is on.
This resource should be set to "true" when a doze component has been specified
to maximize power savings but not all devices support it.
Refer to autosuspend.h for details.
-->
<bool name="config_powerDecoupleAutoSuspendModeFromDisplay">true</bool>
<!-- Power Management: Specifies whether to decouple the interactive state of the
device from the display on/off state.
When false, setInteractive(..., true) will be called before the display is turned on
and setInteractive(..., false) will be called after the display is turned off.
This mode provides best compatibility for devices that expect the interactive
state to be tied to the display state.
When true, setInteractive(...) will be called independently of whether the display
is being turned on or off. This mode enables the power manager to reduce
clocks and disable the touch controller while the display is on.
This resource should be set to "true" when a doze component has been specified
to maximize power savings but not all devices support it.
Refer to power.h for details.
-->
<bool name="config_powerDecoupleInteractiveModeFromDisplay">true</bool>
<!-- 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
@ -127,6 +236,9 @@
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.
If the display supports multiple resolutions, please define the path config based on the
highest resolution so that it can be scaled correctly in each resolution.
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:
@ -161,137 +273,21 @@
-->
<bool name="config_fillMainBuiltInDisplayCutout">true</bool>
<!-- Indicate whether to allow the device to suspend when the screen is off
due to the proximity sensor. This resource should only be set to true
if the sensor HAL correctly handles the proximity sensor as a wake-up source.
Otherwise, the device may fail to wake out of suspend reliably.
The default is false. -->
<bool name="config_suspendWhenScreenOffDueToProximity">true</bool>
<!-- Power Management: Specifies whether to decouple the auto-suspend state of the
device from the display on/off state.
When false, autosuspend_disable() will be called before the display is turned on
and autosuspend_enable() will be called after the display is turned off.
This mode provides best compatibility for devices using legacy power management
features such as early suspend / late resume.
When true, autosuspend_display() and autosuspend_enable() will be called
independently of whether the display is being turned on or off. This mode
enables the power manager to suspend the application processor while the
display is on.
This resource should be set to "true" when a doze component has been specified
to maximize power savings but not all devices support it.
Refer to autosuspend.h for details.
-->
<bool name="config_powerDecoupleAutoSuspendModeFromDisplay">true</bool>
<!-- List of biometric sensors on the device, in decreasing strength. Consumed by AuthService
when registering authenticators with BiometricService. Format must be ID:Modality:Strength,
where: IDs are unique per device, Modality as defined in BiometricAuthenticator.java,
and Strength as defined in Authenticators.java -->
<array name="config_biometric_sensors" translatable="false" >
<string-array name="config_biometric_sensors" translatable="false">
<item>0:2:15</item> <!-- ID0:Fingerprint:Strong -->
</array>
<!-- Power Management: Specifies whether to decouple the interactive state of the
device from the display on/off state.
When false, setInteractive(..., true) will be called before the display is turned on
and setInteractive(..., false) will be called after the display is turned off.
This mode provides best compatibility for devices that expect the interactive
state to be tied to the display state.
When true, setInteractive(...) will be called independently of whether the display
is being turned on or off. This mode enables the power manager to reduce
clocks and disable the touch controller while the display is on.
This resource should be set to "true" when a doze component has been specified
to maximize power savings but not all devices support it.
Refer to power.h for details.
-->
<bool name="config_powerDecoupleInteractiveModeFromDisplay">true</bool>
</string-array>
<!-- The properties of a UDFPS sensor in pixels, in the order listed below: -->
<integer-array name="config_udfps_sensor_props" translatable="false" >
<integer-array name="config_udfps_sensor_props" translatable="false">
<item>540</item> <!-- sensorLocationX -->
<item>2164</item> <!-- sensorLocationY -->
<item>91</item> <!-- sensorRadius -->
</integer-array>
<!-- Screen brightness used to dim the screen when the user activity
timeout expires. May be less than the minimum allowed brightness setting
that can be set by the user. -->
<integer name="config_screenBrightnessDim">2</integer>
<!-- Minimum screen brightness setting allowed by the power manager.
The user is forbidden from setting the brightness below this level. -->
<integer name="config_screenBrightnessSettingMinimum">2</integer>
<!-- Vibrator pattern for feedback about a long screen/key press -->
<array name="config_longPressVibePattern">
<item>0</item>
<item>67</item>
</array>
<!-- Vibrator pattern for feedback about touching a virtual key -->
<array name="config_virtualKeyVibePattern">
<item>0</item>
<item>67</item>
</array>
<!-- Vibrator pattern for feedback about booting with safe mode enabled -->
<array name="config_safeModeEnabledVibePattern">
<item>0</item>
<item>0</item>
<item>94</item>
</array>
<!-- Vibrator pattern for feedback about hitting a scroll barrier -->
<array name="config_scrollBarrierVibePattern">
<item>0</item>
<item>15</item>
<item>30</item>
<item>15</item>
</array>
<!-- ComponentName of a dream to show whenever the system would otherwise have
gone to sleep. When the PowerManager is asked to go to sleep, it will instead
try to start this dream if possible. The dream should typically call startDozing()
to put the display into a low power state and allow the application processor
to be suspended. When the dream ends, the system will go to sleep as usual.
Specify the component name or an empty string if none.
Note that doze dreams are not subject to the same start conditions as ordinary dreams.
Doze dreams will run whenever the power manager is in a dozing state. -->
<string name="config_dozeComponent">com.android.systemui/com.android.systemui.doze.DozeService</string>
<!-- If true, the doze component is not started until after the screen has been
turned off and the screen off animation has been performed. -->
<bool name="config_dozeAfterScreenOffByDefault">true</bool>
<!-- Whether the always on display mode is available. This should only be enabled
on devices where the display has been tuned to be power efficient in DOZE and/or
DOZE_SUSPEND states. -->
<bool name="config_dozeAlwaysOnDisplayAvailable">true</bool>
<!-- Control whether the always on display mode is enabled by default. This value will be used
during initialization when the setting is still null. -->
<bool name="config_dozeAlwaysOnEnabled">false</bool>
<!-- MMS user agent string -->
<string name="config_mms_user_agent" translatable="false">motorolaedge30</string>
<!-- MMS user agent profile url -->
<string name="config_mms_user_agent_profile_url" translatable="false">http://uaprof.motorola.com/phoneconfig/motov1/Profile/motov1.rdf</string>
<!-- Type of the double tap sensor. Empty if double tap is not supported. -->
<string name="config_dozeDoubleTapSensorType" translatable="false">org.lineageos.sensor.double_tap</string>
<!-- Type of the udfps long press sensor. Empty if long press is not supported. -->
<string name="config_dozeUdfpsLongPressSensorType" translatable="false">org.lineageos.sensor.udfps</string>
<!-- Whether the device enable the standalone (SA) mode of 5G NR.-->
<bool name="config_telephony5gStandalone">true</bool>

22
resource-overlay/device/Frameworks/res/values/dimens.xml
View file

@ -1,21 +1,16 @@
<?xml version="1.0" encoding="utf-8"?>
<!--
SPDX-FileCopyrightText: 2022-2024 The LineageOS Project
SPDX-FileCopyrightText: 2022-2025 The LineageOS Project
SPDX-License-Identifier: Apache-2.0
-->
<resources>
<!-- Radius of the software rounded corners. -->
<dimen name="rounded_corner_radius">95.0px</dimen>
<!-- Default paddings for content around the corners. -->
<dimen name="rounded_corner_content_padding">14dp</dimen>
<!-- The default height of the status bar used in {@link SystemBarUtils#getStatusBarHeight} to
calculate the status bar height. -->
<dimen name="status_bar_height_default">28dp</dimen>
<!-- Height of the status bar in portrait. The height should be
Max((status bar content height + waterfall top size), top cutout size) -->
<!-- Height of the status bar in portrait.
Do not read this dimen directly. Use {@link SystemBarUtils#getStatusBarHeight} instead.
-->
<dimen name="status_bar_height_portrait">130px</dimen>
<!-- Height of the status bar in landscape.
@ -23,8 +18,9 @@
-->
<dimen name="status_bar_height_landscape">28dp</dimen>
<!-- Height of area above QQS where battery/time go.
Do not read this dimen directly. Use {@link SystemBarUtils#getQuickQsOffsetHeight} instead.
-->
<dimen name="quick_qs_offset_height">@dimen/status_bar_height_default</dimen>
<!-- Default radius of the software rounded corners. -->
<dimen name="rounded_corner_radius">95.0px</dimen>
<!-- Default paddings for content around the corners. -->
<dimen name="rounded_corner_content_padding">14dp</dimen>
</resources>

2
resource-overlay/device/Frameworks/res/xml/power_profile.xml
View file

@ -114,4 +114,4 @@
<array name="memory.bandwidths">
<value>17</value>
</array>
</device>
</device>

43
resource-overlay/device/LineageSystemUI/res/values/config.xml
View file

@ -1,43 +0,0 @@
<?xml version="1.0" encoding="utf-8"?>
<!--
SPDX-FileCopyrightText: 2022 The LineageOS Project
SPDX-License-Identifier: Apache-2.0
-->
<resources>
<!-- Hardware keys present on the device, stored as a bit field.
This integer should equal the sum of the corresponding value for each
of the following keys present:
1 - Home
2 - Back
4 - Menu
8 - Assistant (search)
16 - App switch
32 - Camera
64 - Volume rocker
For example, a device with Home, Back and Menu keys would set this
config to 7. -->
<integer name="config_deviceHardwareKeys">64</integer>
<!-- Hardware keys present on the device with the ability to wake, stored as a bit field.
This integer should equal the sum of the corresponding value for each
of the following keys present:
1 - Home
2 - Back
4 - Menu
8 - Assistant (search)
16 - App switch
32 - Camera
64 - Volume rocker
For example, a device with Home, Back and Menu keys would set this
config to 7. -->
<integer name="config_deviceHardwareWakeKeys">64</integer>
<!-- Color of the UDFPS pressed view -->
<color name="config_udfpsColor">#ffffff</color>
<!-- Doze: does the double tap sensor need a proximity check? -->
<bool name="doze_double_tap_proximity_check">true</bool>
<!-- Doze: does the long press sensor need a proximity check? -->
<bool name="doze_long_press_proximity_check">true</bool>
</resources>

12
resource-overlay/device/LineageSystemUI/res/values/lineage_config.xml Normal file
View file

@ -0,0 +1,12 @@
<?xml version="1.0" encoding="utf-8"?>
<!--
SPDX-FileCopyrightText: 2022-2025 The LineageOS Project
SPDX-License-Identifier: Apache-2.0
-->
<resources>
<!-- Doze: does the double tap sensor need a proximity check? -->
<bool name="doze_double_tap_proximity_check">true</bool>
<!-- Doze: does the long press sensor need a proximity check? -->
<bool name="doze_long_press_proximity_check">true</bool>
</resources>

2
resource-overlay/device/Settings/Android.bp
View file

@ -5,5 +5,5 @@
runtime_resource_overlay {
name: "SettingsResDubai",
vendor: true
vendor: true,
}

7
resource-overlay/device/Settings/AndroidManifest.xml
View file

@ -4,7 +4,10 @@
SPDX-License-Identifier: Apache-2.0
-->
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
coreApp="true"
package="com.android.settings.overlay.dubai">
<overlay android:targetPackage="com.android.settings" android:isStatic="true" android:priority="600" />
<overlay
android:isStatic="true"
android:priority="600"
android:targetPackage="com.android.settings" />
</manifest>

6
resource-overlay/device/Settings/res/values/config.xml
View file

@ -1,14 +1,12 @@
<?xml version="1.0" encoding="utf-8"?>
<!--
SPDX-FileCopyrightText: 2022 The LineageOS Project
SPDX-FileCopyrightText: 2022-2025 The LineageOS Project
SPDX-License-Identifier: Apache-2.0
-->
<resources xmlns:xliff="urn:oasis:names:tc:xliff:document:1.2">
<resources>
<!-- Whether to show a preference item for regulatory information in About phone -->
<bool name="config_show_regulatory_info">true</bool>
<!-- The radius of the enrollment progress bar, in dp -->
<integer name="config_udfpsEnrollProgressBar">65</integer>
</resources>

6
resource-overlay/device/SettingsProvider/AndroidManifest.xml
View file

@ -4,7 +4,9 @@
SPDX-License-Identifier: Apache-2.0
-->
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
coreApp="true"
package="com.android.providers.settings.overlay.dubai">
<overlay android:targetPackage="com.android.providers.settings" android:isStatic="true" />
<overlay
android:isStatic="true"
android:targetPackage="com.android.providers.settings" />
</manifest>

2
resource-overlay/device/SettingsProvider/res/values/config.xml → resource-overlay/device/SettingsProvider/res/values/defaults.xml
View file

@ -1,6 +1,6 @@
<?xml version="1.0" encoding="utf-8"?>
<!--
SPDX-FileCopyrightText: 2022 The LineageOS Project
SPDX-FileCopyrightText: 2022-2025 The LineageOS Project
SPDX-License-Identifier: Apache-2.0
-->
<resources>

2
resource-overlay/device/SystemUI/Android.bp
View file

@ -5,5 +5,5 @@
runtime_resource_overlay {
name: "SystemUIResDubai",
vendor: true
vendor: true,
}

6
resource-overlay/device/SystemUI/AndroidManifest.xml
View file

@ -4,7 +4,9 @@
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" />
<overlay
android:isStatic="true"
android:targetPackage="com.android.systemui" />
</manifest>

24
resource-overlay/device/SystemUI/res/values/config.xml
View file

@ -1,34 +1,28 @@
<?xml version="1.0" encoding="utf-8"?>
<!--
SPDX-FileCopyrightText: 2022-2024 The LineageOS Project
SPDX-FileCopyrightText: 2022-2025 The LineageOS Project
SPDX-License-Identifier: Apache-2.0
-->
<resources xmlns:xliff="urn:oasis:names:tc:xliff:document:1.2">
<resources>
<!-- 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.
config_mainBuiltInDisplayCutout that describes a path larger than the exact path of a outer
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">
<string name="config_frontBuiltInDisplayCutoutProtection" translatable="false">
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>
<!-- ID for the camera of outer display that needs extra protection -->
<string name="config_protectedCameraId" translatable="false">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>

24
resource-overlay/device/SystemUI/res/values/dimens.xml
View file

@ -1,16 +1,16 @@
<?xml version="1.0" encoding="utf-8"?>
<!--
SPDX-FileCopyrightText: 2022-2024 The LineageOS Project
SPDX-FileCopyrightText: 2022-2025 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 -->
<!-- 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) -->
<!-- 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 -->
@ -19,19 +19,17 @@
<!-- 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>
<!-- Location on the screen of the center of the physical power button. This is a reasonable
default that should be overridden by device-specific overlays. -->
<dimen name="physical_power_button_center_screen_location_y">1000.0px</dimen>
<!-- 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 format="float" name="pixel_pitch" type="dimen">62.73</item>
</resources>

8
resource-overlay/device/SystemUI/res/values/integers.xml
View file

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

6
resource-overlay/device/Wifi/res/values/config.xml
View file

@ -1,11 +1,9 @@
<?xml version="1.0" encoding="utf-8"?>
<!--
SPDX-FileCopyrightText: 2021 The LineageOS Project
SPDX-FileCopyrightText: 2022-2025 The LineageOS Project
SPDX-License-Identifier: Apache-2.0
-->
<resources>
<!-- Default access point SSID used for tethering -->
<!-- Do not translate. Default access point SSID used for tethering -->
<string name="wifi_tether_configure_ssid_default" translatable="false">motorola edge 30</string>
</resources>