From 42169728d79f842728166e6d8eb73308c0cda8b5 Mon Sep 17 00:00:00 2001
From: Albert I <kras@raphielgang.org>
Date: Mon, 21 Mar 2022 15:08:00 -0300
Subject: veux: Set up display color compositions

* Use default color mode for all color modes
* Enable QDCM combined mode and disable factory mode
* Drop LiveDisplay's color mode support as it conflicts with AOSP display
  color adjustment
* Rest of configuration is kanged off Pixel's overlay

Signed-off-by: Albert I <kras@raphielgang.org>
Change-Id: Ib26033fe00a6cc1e8c7d8f93da417516e31a52e3
---
 .../FrameworksResOverlayVeux/res/values/config.xml | 37 ++++++++++++++++++++++
 1 file changed, 37 insertions(+)

(limited to 'rro_overlays/FrameworksResOverlayVeux/res')

diff --git a/rro_overlays/FrameworksResOverlayVeux/res/values/config.xml b/rro_overlays/FrameworksResOverlayVeux/res/values/config.xml
index e27a489..87058d3 100644
--- a/rro_overlays/FrameworksResOverlayVeux/res/values/config.xml
+++ b/rro_overlays/FrameworksResOverlayVeux/res/values/config.xml
@@ -685,6 +685,43 @@
     <!-- Flag specifying whether or not IMS will use the ImsResolver dynamically -->
     <bool name="config_dynamic_bind_ims">true</bool>
 
+    <!-- Indicate available ColorDisplayManager.COLOR_MODE_xxx. -->
+    <integer-array name="config_availableColorModes">
+        <item>0</item> <!-- COLOR_MODE_NATURAL   -->
+        <item>1</item> <!-- COLOR_MODE_BOOSTED   -->
+        <item>2</item> <!-- COLOR_MODE_SATURATED -->
+        <item>3</item> <!-- COLOR_MODE_AUTOMATIC -->
+    </integer-array>
+
+    <!-- Color mode to use when accessibility transforms are enabled. This color mode must be
+         supported by the device, but not necessarily appear in config_availableColorModes. The
+         regularly selected color mode will be used if this value is negative. -->
+    <integer name="config_accessibilityColorMode">2</integer>
+
+    <!-- The following two arrays specify which color space to use for display composition when a
+         certain color mode is active.
+         Composition color spaces are defined in android.view.Display.COLOR_MODE_xxx, and color
+         modes are defined in ColorDisplayManager.COLOR_MODE_xxx and
+         ColorDisplayManager.VENDOR_COLOR_MODE_xxx.
+         The color space COLOR_MODE_DEFAULT (0) lets the system select the most appropriate
+         composition color space for currently displayed content. Other values (e.g.,
+         COLOR_MODE_SRGB) override system selection; these other color spaces must be supported by
+         the device for for display composition.
+         If a color mode does not have a corresponding color space specified in this array, the
+         currently set composition color space will not be modified.-->
+    <integer-array name="config_displayCompositionColorModes">
+        <item>0</item> <!-- COLOR_MODE_NATURAL   -->
+        <item>1</item> <!-- COLOR_MODE_BOOSTED   -->
+        <item>2</item> <!-- COLOR_MODE_SATURATED -->
+        <item>3</item> <!-- COLOR_MODE_AUTOMATIC -->
+    </integer-array>
+    <integer-array name="config_displayCompositionColorSpaces">
+        <item>0</item> <!-- COLOR_MODE_DEFAULT -->
+        <item>0</item> <!-- COLOR_MODE_DEFAULT -->
+        <item>0</item> <!-- COLOR_MODE_DEFAULT -->
+        <item>0</item> <!-- COLOR_MODE_DEFAULT -->
+    </integer-array>
+
     <!-- Boolean indicating whether the HWC setColorTransform function can be performed efficiently
          in hardware. -->
     <bool name="config_setColorTransformAccelerated">true</bool>
-- 
cgit v1.2.3