summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
-rw-r--r--overlay/frameworks/base/core/res/res/values/config.xml18
1 files changed, 18 insertions, 0 deletions
diff --git a/overlay/frameworks/base/core/res/res/values/config.xml b/overlay/frameworks/base/core/res/res/values/config.xml
index 05ca381..0aa6af4 100644
--- a/overlay/frameworks/base/core/res/res/values/config.xml
+++ b/overlay/frameworks/base/core/res/res/values/config.xml
@@ -126,6 +126,18 @@
<item>"mobile_supl,3,0,2,60000,true"</item>
<item>"mobile_dun,4,0,4,60000,true"</item>
<item>"mobile_hipri,5,0,3,60000,true"</item>
+ <item>"bluetooth,7,7,0,-1,true"</item>
+ </string-array>
+
+ <!-- This string array should be overridden by the device to present a list of radio
+ attributes. This is used by the connectivity manager to decide which networks can coexist
+ based on the hardware -->
+ <!-- An Array of "[ConnectivityManager connectionType],
+ [# simultaneous connection types]" -->
+ <string-array translatable="false" name="radioAttributes">
+ <item>"1,1"</item>
+ <item>"0,1"</item>
+ <item>"7,1"</item>
</string-array>
<!-- List of regexpressions describing the interface (if any) that represent tetherable
@@ -149,6 +161,12 @@
<item>"wl0.1"</item>
</string-array>
+ <!-- List of regexpressions describing the interface (if any) that represent tetherable
+ bluetooth interfaces. If the device doesn't want to support tethering over bluetooth this
+ should be empty. -->
+ <string-array translatable="false" name="config_tether_bluetooth_regexs">
+ <item>"bnep\\d"</item>
+ </string-array>
<!-- Boolean indicating if we require the use of DUN on mobile for tethering -->
<bool translatable="false" name="config_tether_dun_required">false</bool>