From 7a5037cb9e74fd0f1f12d17cf5c1e2870b2583d1 Mon Sep 17 00:00:00 2001
From: GiaSen <giammasena@gmail.com>
Date: Thu, 12 Nov 2020 14:06:20 +0100
Subject: [PATCH] Revert "kunlun2: import coral Telephony overlays"

This reverts commit 83a4082fe735f11bde5439035f10d52e07fa395e.
---
 .../services/Telephony/res/values/config.xml  | 22 -------------------
 1 file changed, 22 deletions(-)

diff --git a/overlay/packages/services/Telephony/res/values/config.xml b/overlay/packages/services/Telephony/res/values/config.xml
index 3fc4e6d..d2dc836 100644
--- a/overlay/packages/services/Telephony/res/values/config.xml
+++ b/overlay/packages/services/Telephony/res/values/config.xml
@@ -16,26 +16,4 @@
 <resources>
     <!-- The package name for the platform carrier config app, bundled with system image. -->
     <string name="platform_carrier_config_package" translatable="false">com.google.android.carrier</string>
-
-    <!-- Allow handover from telephony calls to another ConnectionService. -->
-    <bool name="config_support_handover_from">true</bool>
-
-    <!-- Flag indicating whether the device supports RTT (real-time text) -->
-    <bool name="config_support_rtt">true</bool>
-
-    <!-- String indicating the package name of the device ImsService implementation for MMTEL. -->
-    <string name="config_ims_mmtel_package" translatable="false">org.codeaurora.ims</string>
-
-    <!-- String indicating the package name of the device ImsService implementation for RCS. -->
-    <string name="config_ims_rcs_package" translatable="false">com.android.service.ims</string>
-
-    <!-- This device supports the AudioManager Telephony audio device and output onto this
-         device using {@link AudioDeviceInfo#TYPE_TELEPHONY}.
-         This is used to support carriers which generate a recording tone to the remote party
-         when a call recording app is in use. -->
-    <bool name="config_support_telephony_audio_device">true</bool>
-
-    <!-- This device requires that emergency calls are placed over the default data SIM when
-         possible because GNSS SUPL can only be received from the network on data subscription. -->
-    <bool name="config_gnss_supl_requires_default_data_for_emergency">true</bool>
 </resources>