From 9fb5a66b4bfd0e43c263cdf45dd7f049b34c55cb Mon Sep 17 00:00:00 2001
From: LuK1337 <priv.luk@gmail.com>
Date: Fri, 28 May 2021 16:12:02 +0200
Subject: [PATCH] lemonadep: overlay: Replace display cutout overlay with self
 made one

It appears that OnePlus is not using AOSP resources for display cutout.
Instead they are drawing it manually thus I used their x, y and radius
to prepare my own vector path:
  <dimen name="op_draw_cutout_circle_r">43.0px</dimen>
  <dimen name="op_draw_cutout_circle_x">155.0px</dimen>
  <dimen name="op_draw_cutout_circle_y">83.0px</dimen>

Change-Id: Ia061229717cd84277d792269aa1985ded07d1ae3
---
 .../frameworks/base/core/res/res/values/config.xml    | 11 +++++++++--
 1 file changed, 9 insertions(+), 2 deletions(-)

diff --git a/overlay/frameworks/base/core/res/res/values/config.xml b/overlay/frameworks/base/core/res/res/values/config.xml
index d4dadc6..6ab639b 100644
--- a/overlay/frameworks/base/core/res/res/values/config.xml
+++ b/overlay/frameworks/base/core/res/res/values/config.xml
@@ -417,7 +417,14 @@
          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 -525 79.5 A 41.5 41.5 0 0 1 -608 79.5 A 41.5 41.5 0 0 1 -525 79.5 Z M -608,0 L -525,0 Z M -720,0 L -720,121 Z</string>
+    <string translatable="false" name="config_mainBuiltInDisplayCutout">
+        M 154,83
+        M 111,83
+        A 43,43 0 1,0 197,83
+        A 43,43 0 1,0 111,83
+        Z
+        @left
+    </string>
 
     <!-- Like config_mainBuiltInDisplayCutout, but this path is used to report the
          one single bounding rect per device edge to the app via
@@ -428,7 +435,7 @@
     <string translatable="false" name="config_mainBuiltInDisplayCutoutRectApproximation">
         M 0,0
         H 236
-        V 121
+        V 126
         H 0
         Z
         @left