From 68420e6d2a48b7c140a310e21b97b78e45c394d9 Mon Sep 17 00:00:00 2001
From: TQMatvey <maybeetube@gmail.com>
Date: Thu, 23 Feb 2023 13:52:47 +0700
Subject: [PATCH 1/6] Rework S21 Ultra (p3s) overlays

---
 Samsung/p3s-SystemUI/Android.mk            |   8 +
 Samsung/p3s-SystemUI/AndroidManifest.xml   |  10 ++
 Samsung/p3s-SystemUI/res/values/config.xml |  48 ++++++
 Samsung/p3s/res/values-land/config.xml     |   6 +-
 Samsung/p3s/res/values/config.xml          | 190 +++++++++++++++++++--
 5 files changed, 243 insertions(+), 19 deletions(-)
 create mode 100644 Samsung/p3s-SystemUI/Android.mk
 create mode 100644 Samsung/p3s-SystemUI/AndroidManifest.xml
 create mode 100644 Samsung/p3s-SystemUI/res/values/config.xml

diff --git a/Samsung/p3s-SystemUI/Android.mk b/Samsung/p3s-SystemUI/Android.mk
new file mode 100644
index 0000000..e9648b0
--- /dev/null
+++ b/Samsung/p3s-SystemUI/Android.mk
@@ -0,0 +1,8 @@
+LOCAL_PATH := $(call my-dir)
+include $(CLEAR_VARS)
+LOCAL_MODULE_TAGS := optional
+LOCAL_PACKAGE_NAME := treble-overlay-samsung-p3s-systemui
+LOCAL_MODULE_PATH := $(TARGET_OUT_PRODUCT)/overlay
+LOCAL_IS_RUNTIME_RESOURCE_OVERLAY := true
+LOCAL_PRIVATE_PLATFORM_APIS := true
+include $(BUILD_PACKAGE)
diff --git a/Samsung/p3s-SystemUI/AndroidManifest.xml b/Samsung/p3s-SystemUI/AndroidManifest.xml
new file mode 100644
index 0000000..77a9e49
--- /dev/null
+++ b/Samsung/p3s-SystemUI/AndroidManifest.xml
@@ -0,0 +1,10 @@
+<manifest xmlns:android="http://schemas.android.com/apk/res/android"
+        package="me.phh.treble.overlay.samsung.p3s.systemui"
+        android:versionCode="1"
+        android:versionName="1.0">
+        <overlay android:targetPackage="com.android.systemui"
+                android:requiredSystemPropertyName="ro.vendor.build.fingerprint"
+                android:requiredSystemPropertyValue="+*samsung/p3s*"
+		android:priority="399"
+                android:isStatic="true" />
+</manifest>
diff --git a/Samsung/p3s-SystemUI/res/values/config.xml b/Samsung/p3s-SystemUI/res/values/config.xml
new file mode 100644
index 0000000..f53fa99
--- /dev/null
+++ b/Samsung/p3s-SystemUI/res/values/config.xml
@@ -0,0 +1,48 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!--
+ * Copyright (c) 2006, The Android Open Source Project
+ *
+ * Licensed under the Apache License, Version 2.0 (the "License");
+ * you may not use this file except in compliance with the License.
+ * You may obtain a copy of the License at
+ *
+ *     http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+*/
+-->
+<resources>
+    <!-- the padding on the top of the statusbar (usually 0) -->
+    <dimen name="status_bar_padding_top">12dp</dimen>
+
+    <!-- the padding on the start of the statusbar -->
+    <dimen name="status_bar_padding_start">10dp</dimen>
+
+    <!-- the padding on the end of the statusbar -->
+    <dimen name="status_bar_padding_end">14dp</dimen>
+
+    <!-- Margin on the left side of the carrier text on Keyguard -->
+    <dimen name="keyguard_carrier_text_margin">8dp</dimen>
+
+    <!-- for 20dp of padding at 3.5px/dp at default density -->
+    <dimen name="rounded_corner_content_padding">70px</dimen>
+
+    <!-- Minimum margin between clock and status bar
+         TLDR: Move the clock on lockscreen lower so
+	 it looks like a google pixel, ty Haridhayal -->
+    <dimen name="keyguard_clock_top_margin">60dp</dimen>
+
+    <!-- Doze: does this device support STATE_DOZE?  -->
+    <bool name="doze_display_state_supported">true</bool>
+
+    <!-- Doze: does this device support STATE_DOZE_SUSPEND?  -->
+    <bool name="doze_suspend_display_state_supported">false</bool>
+
+    <!-- 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">1400px</dimen>
+</resources>
diff --git a/Samsung/p3s/res/values-land/config.xml b/Samsung/p3s/res/values-land/config.xml
index 3d9e332..4cea3f3 100644
--- a/Samsung/p3s/res/values-land/config.xml
+++ b/Samsung/p3s/res/values-land/config.xml
@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="utf-8"?>
 <resources>
-    <dimen name="status_bar_height">110px</dimen>
-    <dimen name="status_bar_height_default">110px</dimen>
-    <dimen name="status_bar_height_portrait">110px</dimen>
+    <dimen name="status_bar_height">112px</dimen>
+    <dimen name="status_bar_height_default">112px</dimen>
+    <dimen name="status_bar_height_portrait">112px</dimen>
 </resources>
diff --git a/Samsung/p3s/res/values/config.xml b/Samsung/p3s/res/values/config.xml
index f97dfd3..6f17653 100644
--- a/Samsung/p3s/res/values/config.xml
+++ b/Samsung/p3s/res/values/config.xml
@@ -18,12 +18,11 @@
         <item>20</item>
         <item>30</item>
     </integer-array>
-	    <integer name="config_autoBrightnessBrighteningLightDebounce">3000</integer>
+        <integer name="config_autoBrightnessBrighteningLightDebounce">3000</integer>
         <integer name="config_screenBrightnessSettingDefault">128</integer>
-        <integer name="config_screenBrightnessSettingMaximum">255</integer>
-        <integer name="config_screenBrightnessSettingMinimum">0</integer>
-	    <integer name="config_screenBrightnessDoze">17</integer>
-		<integer name="config_screenBrightnessDark">1</integer>
+        <integer name="config_screenBrightnessSettingMaximum">561</integer>
+        <integer name="config_screenBrightnessSettingMinimum">1</integer>
+	<integer name="config_screenBrightnessDark">1</integer>
 	    <array name="config_autoBrightnessDisplayValuesNits">
         <item>13</item>
         <item>18</item>
@@ -82,7 +81,7 @@
         <item>50</item>
         <item>100</item>
         <item>300</item>
-        <item>500</item>
+        <item>505</item>
         <item>1000</item>
         <item>2000</item>
         <item>2999</item>
@@ -599,7 +598,7 @@
         <item>497</item>
         <item>498</item>
         <item>499</item>
-        <item>500</item>
+        <item>505</item>
         <item>501</item>
         <item>502</item>
         <item>503</item>
@@ -918,7 +917,7 @@
         <item>487.578</item>
         <item>492.05</item>
         <item>496.025</item>
-        <item>500</item>
+        <item>505</item>
         <item>510</item>
         <item>512</item>
         <item>513</item>
@@ -1226,12 +1225,171 @@
         <item>1098</item>
         <item>1100</item>
     </array>
-            <bool name="config_automatic_brightness_available">true</bool>
-            <bool name="config_dozeAfterScreenOffByDefault">true</bool>
-            <bool name="config_displayBlanksAfterDoze">false</bool>
-	    <dimen name="status_bar_height">110px</dimen>
-            <dimen name="status_bar_height_default">110px</dimen>
-            <dimen name="status_bar_height_portrait">110px</dimen>
-	    <integer name="config_defaultRefreshRate">0</integer>
-	    <integer name="config_defaultPeakRefreshRate">120</integer>
+
+    <!-- Flag indicating whether we should enable the automatic brightness.
+         Software implementation will be used if config_hardware_auto_brightness_available is not set -->
+    <bool name="config_automatic_brightness_available">true</bool>
+
+    <!-- Is the device capable of hot swapping an UICC Card -->
+    <bool name="config_hotswapCapable">true</bool>
+
+    <!-- If true, the display will be shifted around in ambient mode. -->
+    <bool name="config_enableBurnInProtection">true</bool>
+
+    <!-- Whether device supports double tap to wake -->
+    <bool name="config_supportDoubleTapWake">true</bool>
+
+    <!-- Screen brightness used to dim the screen while dozing in a very low power state.
+         May be less than the minimum allowed brightness setting
+         that can be set by the user. -->
+    <integer name="config_screenBrightnessDoze">65</integer>
+
+    <!-- Control whether the always on display mode is available. This should only be enabled on
+         devices where the display has be tuned to be power efficient in DOZE and/or DOZE_SUSPEND
+         states. -->
+    <bool name="config_dozeAlwaysOnDisplayAvailable">true</bool>
+
+    <!-- Whether the display blanks itself when transitioning from a doze to a non-doze state -->
+    <bool name="config_displayBlanksAfterDoze">false</bool>
+
+    <!-- If AOD can show an ambient version of the wallpaper -->
+    <bool name="config_dozeSupportsAodWallpaper">false</bool>
+
+    <!-- True if the display hardware only has brightness buckets rather than a full range of
+         backlight values -->
+    <bool name="config_displayBrightnessBucketsInDoze">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>
+
+    <!-- Specifies the maximum burn-in offset displacement from the center. If -1, no maximum value
+         will be used. -->
+    <integer name="config_burnInProtectionMaxRadius">70</integer>
+
+    <!-- Specifies the minimum burn-in offset horizontally. -->
+    <integer name="config_burnInProtectionMinHorizontalOffset">-15</integer>
+
+    <!-- Specifies the maximum burn-in offset horizontally. -->
+    <integer name="config_burnInProtectionMaxHorizontalOffset">15</integer>
+
+    <!-- Specifies the minimum burn-in offset vertically. -->
+    <integer name="config_burnInProtectionMinVerticalOffset">-40</integer>
+
+    <!-- Specifies the maximum burn-in offset vertically. -->
+    <integer name="config_burnInProtectionMaxVerticalOffset">40</integer>
+
+    <!-- Default list of files pinned by the Pinner Service -->
+    <string-array translatable="false" name="config_defaultPinnerServiceFiles">
+        <item>"/system/framework/framework.jar"</item>
+        <item>"/system/framework/services.jar"</item>
+        <item>"/apex/com.android.runtime/javalib/core-oj.jar"</item>
+        <item>"/apex/com.android.runtime/javalib/core-libart.jar"</item>
+        <item>"/product/priv-app/SystemUI/SystemUI.apk"</item>
+        <item>"/system/bin/surfaceflinger"</item>
+    </string-array>
+
+    <!-- Should the pinner service pin the Home application? -->
+    <bool name="config_pinnerHomeApp">true</bool>
+
+    <!-- Boolean indicating whether the HWC setColorTransform function can be performed efficiently
+         in hardware. -->
+    <bool name="config_setColorTransformAccelerated">true</bool>
+
+    <!-- If this is true, device supports Sustained Performance Mode. -->
+    <bool name="config_sustainedPerformanceModeSupported">true</bool>
+
+    <!-- Radius of the software rounded corners at the top of the display in its natural
+        orientation. If zero, the value of rounded_corner_radius is used. -->
+    <dimen name="rounded_corner_radius_top">52px</dimen>
+
+    <!-- Radius of the software rounded corners at the bottom of the display in its natural
+        orientation. If zero, the value of rounded_corner_radius is used. -->
+    <dimen name="rounded_corner_radius_bottom">52px</dimen>
+
+    <!-- Top adjustment for the software rounded corners since corners are not perfectly
+        round.  This value is used when retrieving the "radius" of the top rounded corner in cases
+        where the exact bezier curve cannot be retrieved.  This value will be subtracted from
+        rounded_corner_radius_top to more accurately provide a "radius" for the top rounded corners.
+         -->
+    <dimen name="rounded_corner_radius_top_adjustment">5px</dimen>
+
+    <!-- Bottom adjustment for the software rounded corners since corners are not perfectly
+        round.  This value is used when retrieving the "radius" of the bottom rounded corner in
+        cases where the exact bezier curve cannot be retrieved.  This value will be subtracted from
+        rounded_corner_radius_bottom to more accurately provide a "radius" for the bottom rounded
+        corners. -->
+    <dimen name="rounded_corner_radius_bottom_adjustment">4px</dimen>
+
+    <!-- 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 translatable="false" name="config_mainBuiltInDisplayCutout">M 0,0 H -30 V 102 H 30 V 0 H 0 Z</string>
+
+    <!-- Height of the status bar in portrait.
+         Do not read this dimen directly. Use {@link SystemBarUtils#getStatusBarHeight} instead.
+         -->
+    <dimen name="status_bar_height_portrait">112.0px</dimen>
+
+    <!-- Height of the status bar in landscape.
+         Do not read this dimen directly. Use {@link SystemBarUtils#getStatusBarHeight} instead.
+         -->
+    <dimen name="status_bar_height_landscape">10dp</dimen>
+
+    <!-- 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">120</integer>
 </resources>

From 24c728bc8b47fc76277dd3ef49ed4b9b45548cd6 Mon Sep 17 00:00:00 2001
From: TQMatvey <maybeetube@gmail.com>
Date: Thu, 23 Feb 2023 14:01:10 +0700
Subject: [PATCH 2/6] fix after tests

---
 Samsung/p3s/res/values/config.xml | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/Samsung/p3s/res/values/config.xml b/Samsung/p3s/res/values/config.xml
index 6f17653..ce52b9b 100644
--- a/Samsung/p3s/res/values/config.xml
+++ b/Samsung/p3s/res/values/config.xml
@@ -50,8 +50,8 @@
         <item>892</item>
         <item>948</item>
         <item>1000</item>
-        <item>1000</item>
-        <item>1000</item>
+        <item>1050</item>
+        <item>1100</item>
     </array>
 	   <integer-array name="config_autoBrightnessLcdBacklightValues">
         <item>6</item>
@@ -81,7 +81,7 @@
         <item>50</item>
         <item>100</item>
         <item>300</item>
-        <item>505</item>
+        <item>500</item>
         <item>1000</item>
         <item>2000</item>
         <item>2999</item>
@@ -598,7 +598,7 @@
         <item>497</item>
         <item>498</item>
         <item>499</item>
-        <item>505</item>
+        <item>500</item>
         <item>501</item>
         <item>502</item>
         <item>503</item>
@@ -917,7 +917,7 @@
         <item>487.578</item>
         <item>492.05</item>
         <item>496.025</item>
-        <item>505</item>
+        <item>500</item>
         <item>510</item>
         <item>512</item>
         <item>513</item>

From 2328c28d5aeaf44774c6b4b8ecce8736537bb9e5 Mon Sep 17 00:00:00 2001
From: TQMatvey <maybeetube@gmail.com>
Date: Thu, 23 Feb 2023 23:28:22 +0700
Subject: [PATCH 3/6] fix CI builds

---
 Samsung/p3s/res/values/config.xml | 14 --------------
 fail                              |  0
 overlay.mk                        |  1 +
 3 files changed, 1 insertion(+), 14 deletions(-)
 delete mode 100644 fail

diff --git a/Samsung/p3s/res/values/config.xml b/Samsung/p3s/res/values/config.xml
index ce52b9b..31cdc69 100644
--- a/Samsung/p3s/res/values/config.xml
+++ b/Samsung/p3s/res/values/config.xml
@@ -1334,20 +1334,6 @@
         orientation. If zero, the value of rounded_corner_radius is used. -->
     <dimen name="rounded_corner_radius_bottom">52px</dimen>
 
-    <!-- Top adjustment for the software rounded corners since corners are not perfectly
-        round.  This value is used when retrieving the "radius" of the top rounded corner in cases
-        where the exact bezier curve cannot be retrieved.  This value will be subtracted from
-        rounded_corner_radius_top to more accurately provide a "radius" for the top rounded corners.
-         -->
-    <dimen name="rounded_corner_radius_top_adjustment">5px</dimen>
-
-    <!-- Bottom adjustment for the software rounded corners since corners are not perfectly
-        round.  This value is used when retrieving the "radius" of the bottom rounded corner in
-        cases where the exact bezier curve cannot be retrieved.  This value will be subtracted from
-        rounded_corner_radius_bottom to more accurately provide a "radius" for the bottom rounded
-        corners. -->
-    <dimen name="rounded_corner_radius_bottom_adjustment">4px</dimen>
-
     <!-- 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}.
diff --git a/fail b/fail
deleted file mode 100644
index e69de29..0000000
diff --git a/overlay.mk b/overlay.mk
index e3d9bc4..30fcbf0 100644
--- a/overlay.mk
+++ b/overlay.mk
@@ -221,6 +221,7 @@ PRODUCT_PACKAGES += \
 	treble-overlay-samsung-n9q \
 	treble-overlay-samsung-o1s \
 	treble-overlay-samsung-p3s \
+	treble-overlay-samsung-p3s-systemui \
 	treble-overlay-samsung-r0q \
 	treble-overlay-samsung-r0q-systemui \
 	treble-overlay-samsung-r0s \

From 08abb7c58af183e1057163ab17c5f893bfe88483 Mon Sep 17 00:00:00 2001
From: TQMatvey <maybeetube@gmail.com>
Date: Fri, 10 Mar 2023 16:12:53 +0700
Subject: [PATCH 4/6] p3s: final improvements

---
 Samsung/p3s/res/values/config.xml | 15 +++++++++++++--
 1 file changed, 13 insertions(+), 2 deletions(-)

diff --git a/Samsung/p3s/res/values/config.xml b/Samsung/p3s/res/values/config.xml
index 31cdc69..97fa5d4 100644
--- a/Samsung/p3s/res/values/config.xml
+++ b/Samsung/p3s/res/values/config.xml
@@ -1242,7 +1242,7 @@
     <!-- Screen brightness used to dim the screen while dozing in a very low power state.
          May be less than the minimum allowed brightness setting
          that can be set by the user. -->
-    <integer name="config_screenBrightnessDoze">65</integer>
+    <integer name="config_screenBrightnessDoze">55</integer>
 
     <!-- Control whether the always on display mode is available. This should only be enabled on
          devices where the display has be tuned to be power efficient in DOZE and/or DOZE_SUSPEND
@@ -1252,6 +1252,10 @@
     <!-- Whether the display blanks itself when transitioning from a doze to a non-doze state -->
     <bool name="config_displayBlanksAfterDoze">false</bool>
 
+    <!-- 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>
+
     <!-- If AOD can show an ambient version of the wallpaper -->
     <bool name="config_dozeSupportsAodWallpaper">false</bool>
 
@@ -1273,7 +1277,7 @@
          to maximize power savings but not all devices support it.
          Refer to autosuspend.h for details.
     -->
-    <bool name="config_powerDecoupleAutoSuspendModeFromDisplay">true</bool>
+    <bool name="config_powerDecoupleAutoSuspendModeFromDisplay">false</bool>
 
     <!-- Power Management: Specifies whether to decouple the interactive state of the
          device from the display on/off state.
@@ -1378,4 +1382,11 @@
          rates are available from hardware composer. Only has an effect if the value is
          non-zero. -->
     <integer name="config_defaultPeakRefreshRate">120</integer>
+
+    <!-- The properties of a UDFPS sensor in pixels -->
+    <integer-array name="config_udfps_sensor_props">
+      <item>720</item>  <!-- sensorLocationX -->
+      <item>2420</item> <!-- sensorLocationY -->
+      <item>142</item>  <!-- sensorRadius -->
+    </integer-array>
 </resources>

From 3c81196f3476384839fdac633683f0b5d77108b6 Mon Sep 17 00:00:00 2001
From: TQMatvey <maybeetube@gmail.com>
Date: Thu, 13 Apr 2023 14:38:40 +0700
Subject: [PATCH 5/6] p3s: adjust status bar

---
 Samsung/p3s-SystemUI/res/values/config.xml | 6 +++---
 Samsung/p3s/res/values-land/config.xml     | 6 +++---
 Samsung/p3s/res/values/config.xml          | 6 +++---
 3 files changed, 9 insertions(+), 9 deletions(-)

diff --git a/Samsung/p3s-SystemUI/res/values/config.xml b/Samsung/p3s-SystemUI/res/values/config.xml
index f53fa99..659b2d9 100644
--- a/Samsung/p3s-SystemUI/res/values/config.xml
+++ b/Samsung/p3s-SystemUI/res/values/config.xml
@@ -17,13 +17,13 @@
 -->
 <resources>
     <!-- the padding on the top of the statusbar (usually 0) -->
-    <dimen name="status_bar_padding_top">12dp</dimen>
+    <dimen name="status_bar_padding_top">2dp</dimen>
 
     <!-- the padding on the start of the statusbar -->
-    <dimen name="status_bar_padding_start">10dp</dimen>
+    <dimen name="status_bar_padding_start">4dp</dimen>
 
     <!-- the padding on the end of the statusbar -->
-    <dimen name="status_bar_padding_end">14dp</dimen>
+    <dimen name="status_bar_padding_end">4dp</dimen>
 
     <!-- Margin on the left side of the carrier text on Keyguard -->
     <dimen name="keyguard_carrier_text_margin">8dp</dimen>
diff --git a/Samsung/p3s/res/values-land/config.xml b/Samsung/p3s/res/values-land/config.xml
index 4cea3f3..e0987b1 100644
--- a/Samsung/p3s/res/values-land/config.xml
+++ b/Samsung/p3s/res/values-land/config.xml
@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="utf-8"?>
 <resources>
-    <dimen name="status_bar_height">112px</dimen>
-    <dimen name="status_bar_height_default">112px</dimen>
-    <dimen name="status_bar_height_portrait">112px</dimen>
+    <dimen name="status_bar_height">125px</dimen>
+    <dimen name="status_bar_height_default">125px</dimen>
+    <dimen name="status_bar_height_portrait">125px</dimen>
 </resources>
diff --git a/Samsung/p3s/res/values/config.xml b/Samsung/p3s/res/values/config.xml
index 97fa5d4..373de7f 100644
--- a/Samsung/p3s/res/values/config.xml
+++ b/Samsung/p3s/res/values/config.xml
@@ -1355,17 +1355,17 @@
                 <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 translatable="false" name="config_mainBuiltInDisplayCutout">M 0,0 H -30 V 102 H 30 V 0 H 0 Z</string>
+    <string translatable="false" name="config_mainBuiltInDisplayCutout">M 0,0 H -30 V 125 H 30 V 0 H 0 Z</string>
 
     <!-- Height of the status bar in portrait.
          Do not read this dimen directly. Use {@link SystemBarUtils#getStatusBarHeight} instead.
          -->
-    <dimen name="status_bar_height_portrait">112.0px</dimen>
+    <dimen name="status_bar_height_portrait">125.0px</dimen>
 
     <!-- Height of the status bar in landscape.
          Do not read this dimen directly. Use {@link SystemBarUtils#getStatusBarHeight} instead.
          -->
-    <dimen name="status_bar_height_landscape">10dp</dimen>
+    <dimen name="status_bar_height_landscape">8dp</dimen>
 
     <!-- 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

From bf4abc6d8645e352232a10225d2d5fd9c4610ac0 Mon Sep 17 00:00:00 2001
From: TQMatvey <maybeetube@gmail.com>
Date: Fri, 14 Apr 2023 19:11:26 +0700
Subject: [PATCH 6/6] p3s: remove config_udfps_sensor_props

---
 Samsung/p3s/res/values/config.xml | 7 -------
 1 file changed, 7 deletions(-)

diff --git a/Samsung/p3s/res/values/config.xml b/Samsung/p3s/res/values/config.xml
index 373de7f..42c59ae 100644
--- a/Samsung/p3s/res/values/config.xml
+++ b/Samsung/p3s/res/values/config.xml
@@ -1382,11 +1382,4 @@
          rates are available from hardware composer. Only has an effect if the value is
          non-zero. -->
     <integer name="config_defaultPeakRefreshRate">120</integer>
-
-    <!-- The properties of a UDFPS sensor in pixels -->
-    <integer-array name="config_udfps_sensor_props">
-      <item>720</item>  <!-- sensorLocationX -->
-      <item>2420</item> <!-- sensorLocationY -->
-      <item>142</item>  <!-- sensorRadius -->
-    </integer-array>
 </resources>