From a56918ab1cb36cff712fcf933dadcf17a65f3a16 Mon Sep 17 00:00:00 2001
From: KakatkarAkshay <akshayakakatkaraa@gmail.com>
Date: Wed, 25 Jan 2023 14:49:06 +0530
Subject: [PATCH] avicii: Import camera cutout overlay from AC2003_11_F.17

Change-Id: Ib2e5b59940838d911c751002c23e91892818acff
---
 device.mk                                     |  1 +
 .../res/values/config.xml                     | 50 +++++++++++++++++++
 2 files changed, 51 insertions(+)

diff --git a/device.mk b/device.mk
index 2ec6d94..ced3d09 100644
--- a/device.mk
+++ b/device.mk
@@ -323,6 +323,7 @@ PRODUCT_PACKAGES += \
     CarrierConfigResCommon \
     FrameworksResTarget \
     OPlusFrameworksResCommon \
+    OPlusFrameworksResTarget \
     OPlusSettingsResCommon \
     OPlusSystemUIResCommon \
     WifiResTarget
diff --git a/overlay/OPlusFrameworksResTarget/res/values/config.xml b/overlay/OPlusFrameworksResTarget/res/values/config.xml
index 457a093..986f5b0 100644
--- a/overlay/OPlusFrameworksResTarget/res/values/config.xml
+++ b/overlay/OPlusFrameworksResTarget/res/values/config.xml
@@ -303,4 +303,54 @@
     <!-- Light sensor event rate in milliseconds for automatic brightness control. -->
     <integer name="config_autoBrightnessLightSensorRate">300</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.
+
+         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 translatable="false" name="config_mainBuiltInDisplayCutout">
+        M -436.5 33
+        L -319.5 33
+        A 38.5 38.5 0 0 1 -281 71.5
+        L -281 71.5
+        A 38.5 38.5 0 0 1 -319.5 110
+        L -436.5 110
+        A 38.5 38.5 0 0 1 -475 71.5
+        L -475 71.5
+        A 38.5 38.5 0 0 1 -436.5 33
+        Z
+        M -475 0
+        L -283 0
+        Z
+        M -540 0
+        L -540 113
+        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">
+	M 0,0
+	H 285
+	V 113
+	H 0
+	Z
+	@left</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>