From 2dc145da28d149a46729f59c40b3849e4e0d4f8c Mon Sep 17 00:00:00 2001
From: Sam Mortimer <sam@mortimer.me.uk>
Date: Fri, 16 Aug 2019 11:20:00 -0700
Subject: [PATCH] a3xelte: Remove config_tether_upstream_types

* Made redundant by enabling config_tether_upstream_automatic
  in vendor/lineage

Change-Id: I0441f36f34546f3dfd6aad664d4c2711d51687ee
---
 .../frameworks/base/core/res/res/values/config.xml   | 12 ------------
 1 file changed, 12 deletions(-)

diff --git a/overlay/frameworks/base/core/res/res/values/config.xml b/overlay/frameworks/base/core/res/res/values/config.xml
index f10b7b5..a8f838f 100644
--- a/overlay/frameworks/base/core/res/res/values/config.xml
+++ b/overlay/frameworks/base/core/res/res/values/config.xml
@@ -121,18 +121,6 @@
         <item>mobile_ent1,28,0,2,-1,true</item>
     </string-array>
 
-    <!-- Array of ConnectivityManager.TYPE_xxxx values allowable for tethering -->
-    <!-- Common options are [1, 4] for TYPE_WIFI and TYPE_MOBILE_DUN or
-    <!== [0,1,5,7] for TYPE_MOBILE, TYPE_WIFI, TYPE_MOBILE_HIPRI and TYPE_BLUETOOTH -->
-    <integer-array translatable="false" name="config_tether_upstream_types">
-        <item>0</item>
-        <item>1</item>
-        <item>4</item>
-        <item>5</item>
-        <item>7</item>
-        <item>9</item>
-    </integer-array>
-
     <!-- Flag indicating whether we should enable the automatic brightness in Settings.
          Software implementation will be used if config_hardware_auto_brightness_available is not set -->
     <bool name="config_automatic_brightness_available">true</bool>
-- 
2.20.1