cupid: overlay: Beautify FrameworksResCupid

Change-Id: I9eca49066390e53f338b6ac8079a132537e4bdcc

overlay/Frameworks/res/values/arrays.xml

@@ -1,21 +0,0 @@
-<?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">
-    <!-- The properties of a UDFPS sensor in pixels, in the order listed below: -->
-    <integer-array name="config_udfps_sensor_props" translatable="false" >
-        <item>540</item>
-        <item>2163</item>
-        <item>107</item>
-    </integer-array>
-
-    <!-- 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 -->
-    <string-array name="config_biometric_sensors" translatable="false">
-        <item>0:2:15</item>
-    </string-array>
-</resources>

overlay/Frameworks/res/values/config.xml

@@ -1,9 +1,11 @@
 <?xml version="1.0" encoding="utf-8"?>
 <!--
-     Copyright (C) 2022 The LineageOS Project
+     Copyright (C) 2024 The LineageOS Project
      SPDX-License-Identifier: Apache-2.0
 -->
 <resources xmlns:xliff="urn:oasis:names:tc:xliff:document:1.2">
+    <integer name="config_udfps_illumination_transition_ms">0</integer>
+
     <!-- 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>
 
@@ -21,6 +23,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:
@@ -30,19 +35,31 @@
          -->
     <string name="config_mainBuiltInDisplayCutout" translatable="false">M -33 52 a 33 33 0 1 0 66 0 a 33 33 0 1 0 -66 0 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 -33 V 87 H 33 V 0 H 0 Z</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).
-        -->
+    <!-- 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" translatable="false">M 0,0 H -33 V 87 H 33 V 0 H 0 Z</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>
 
-    <!-- How long it takes for the HW to start illuminating after the illumination is requested. -->
-    <integer name="config_udfps_illumination_transition_ms">0</integer>
+    <!-- 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 -->
+    <string-array name="config_biometric_sensors" translatable="false">
+        <item>0:2:15</item>
+    </string-array>
+
+    <!-- The properties of a UDFPS sensor in pixels, in the order listed below: -->
+    <integer-array name="config_udfps_sensor_props" translatable="false">
+        <item>540</item>
+        <item>2163</item>
+        <item>107</item>
+    </integer-array>
 </resources>

overlay/Frameworks/res/values/dimens.xml

@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="utf-8"?>
 <!--
-     Copyright (C) 2022 The LineageOS Project
+     Copyright (C) 2024 The LineageOS Project
      SPDX-License-Identifier: Apache-2.0
 -->
 <resources xmlns:xliff="urn:oasis:names:tc:xliff:document:1.2">

overlay/Frameworks/res/xml/power_profile.xml

@@ -1,11 +1,9 @@
 <?xml version="1.0" encoding="utf-8"?>
 <!--
-     Copyright (C) 2022 The LineageOS Project
+     Copyright (C) 2024 The LineageOS Project
      SPDX-License-Identifier: Apache-2.0
 -->
 <device name="Android">
-
-        <!-- No extra UI options. This is the default. -->
     <item name="none">0</item>
 
     <!-- Additional power used when screen is turned on at minimum brightness -->
@@ -14,8 +12,6 @@
     <!-- Additional power used when screen is at maximum brightness, compared to
          screen at minimum brightness -->
     <item name="screen.full">365.32</item>
-
-    <!-- Number of cores each CPU cluster contains -->
     <array name="cpu.clusters.cores">
         <value>4</value>
         <value>3</value>
@@ -150,39 +146,27 @@
         <value>937.03</value>
     </array>
 
-    <!-- Additional power consumption by CPU excluding cluster and core when  running -->
+  <!-- Additional power consumption by CPU excluding cluster and core when
+       running -->
     <item name="cpu.active">23.50</item>
 
-    <!-- Additional power consumption when CPU is in a kernel idle loop -->
+  <!-- Current when CPU is idle -->
     <item name="cpu.idle">8.18</item>
 
     <!-- Power consumption when CPU is suspended -->
     <item name="cpu.suspend">0</item>
 
-    <!-- This is the battery capacity in mAh -->
+  <!-- This is the battery capacity in mAh (measured at nominal voltage) -->
     <item name="battery.capacity">4500</item>
     <item name="wifi.on">1.62</item>
     <item name="wifi.active">267.74</item>
     <item name="wifi.scan">72.58</item>
     <item name="dsp.audio">23.28</item>
     <item name="dsp.video">67.05</item>
-
-    <!-- Average power used by the camera flash module when on -->
     <item name="camera.flashlight">143.35</item>
-
-    <!-- Average power use by the camera subsystem for a typical camera
-         application. Intended as a rough estimate for an application running a
-         preview and capturing approximately 10 full-resolution pictures per
-         minute. -->
     <item name="camera.avg">696.90</item>
-
-    <!-- Additional power used when GPS is acquiring a signal -->
     <item name="gps.on">2.12</item>
-
-    <!-- Additional power used when cellular radio is transmitting/receiving -->
     <item name="radio.active">485.02</item>
-
-    <!-- Additional power used when cellular radio is paging the tower -->
     <item name="radio.scanning">37.18</item>
     <array name="radio.on">
         <value>86</value>
@@ -223,4 +207,4 @@
     <item name="bluetooth.active">83.37</item>
     <item name="bluetooth.on">0.62</item>
     <item name="bluetooth.controller.voltage">3700</item>
-</device>
+</device>