From fc960539214819e278f5e020d812fef0ac102ee3 Mon Sep 17 00:00:00 2001
From: LuK1337 <priv.luk@gmail.com>
Date: Fri, 24 Jun 2022 15:40:14 +0200
Subject: [PATCH] FrameworksResCommon: Enable WiFi display

Change-Id: Ibedd77780aa8adebc5ae948ce2ca25956c8692ac
---
 .../qssi/FrameworksResCommon/res/values/config.xml | 14 ++++++++++++++
 1 file changed, 14 insertions(+)

diff --git a/overlay/qssi/FrameworksResCommon/res/values/config.xml b/overlay/qssi/FrameworksResCommon/res/values/config.xml
index 28cbbeb..0fc36b1 100644
--- a/overlay/qssi/FrameworksResCommon/res/values/config.xml
+++ b/overlay/qssi/FrameworksResCommon/res/values/config.xml
@@ -68,6 +68,20 @@
     <!-- Whether to select voice/data/sms preference without user confirmation -->
     <bool name="config_voice_data_sms_auto_fallback">true</bool>
 
+    <!-- Whether WiFi display is supported by this device.
+         There are many prerequisites for this feature to work correctly.
+         Here are a few of them:
+         * The WiFi radio must support WiFi P2P.
+         * The WiFi radio must support concurrent connections to the WiFi display and
+           to an access point.
+         * The Audio Server audio_policy_configuration.xml file must specify a rule for
+           the "r_submix" remote submix module.  This module is used to record and stream system
+           audio output to the WiFi display encoder in the media server.
+         * The remote submix module "audio.r_submix.default" must be installed on the device.
+         * The device must be provisioned with HDCP keys (for protected content).
+    -->
+    <bool name="config_enableWifiDisplay">true</bool>
+
     <!-- Set to true if the wifi display supports compositing content stored
          in gralloc protected buffers.  For this to be true, there must exist
          a protected hardware path for surface flinger to composite and send