| <?xml version="1.0" encoding="utf-8"?> |
| <!-- |
| /* |
| ** Copyright 2011, The Android Open Source Project |
| ** |
| ** Licensed under the Apache License, Version 2.0 (the "License"); |
| ** you may not use this file except in compliance with the License. |
| ** You may obtain a copy of the License at |
| ** |
| ** http://www.apache.org/licenses/LICENSE-2.0 |
| ** |
| ** Unless required by applicable law or agreed to in writing, software |
| ** distributed under the License is distributed on an "AS IS" BASIS, |
| ** WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. |
| ** See the License for the specific language governing permissions and |
| ** limitations under the License. |
| */ |
| --> |
| |
| <!-- These resources are around just to allow their values to be customized |
| for different hardware and product builds. --> |
| <resources> |
| |
| <!-- This device is not "voice capable"; it's data-only. --> |
| <bool name="config_voice_capable">false</bool> |
| |
| <!-- This device does not allow sms service. --> |
| <bool name="config_sms_capable">false</bool> |
| |
| <!-- List of regexpressions describing the interface (if any) that represent tetherable |
| Wifi interfaces. If the device doesn't want to support tethering over Wifi this |
| should be empty. An example would be "softap.*" --> |
| <string-array translatable="false" name="config_tether_wifi_regexs"> |
| <item>"wlan\\d"</item> |
| </string-array> |
| |
| <!-- Array of ConnectivityManager.TYPE_xxxx values allowable for tethering --> |
| <!-- [1,7,9] for TYPE_WIFI, TYPE_BLUETOOTH and TYPE_ETHERNET--> |
| <integer-array translatable="false" name="config_tether_upstream_types"> |
| <item>1</item> |
| <item>7</item> |
| <item>9</item> |
| </integer-array> |
| |
| <!-- This string array should be overridden by the device to present a list of network |
| attributes. This is used by the connectivity manager to decide which networks can coexist |
| based on the hardware --> |
| <!-- An Array of "[Connection name],[ConnectivityManager connection type], |
| [associated radio-type],[priority],[restoral-timer(ms)],[dependencyMet] --> |
| <!-- the 5th element "resore-time" indicates the number of milliseconds to delay |
| before automatically restore the default connection. Set -1 if the connection |
| does not require auto-restore. --> |
| <!-- the 6th element indicates boot-time dependency-met value. --> |
| <string-array translatable="false" name="networkAttributes"> |
| <item>"wifi,1,1,1,-1,true"</item> |
| <item>"bluetooth,7,7,1,-1,true"</item> |
| <item>"ethernet,9,9,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>"7,1"</item> |
| <item>"9,1"</item> |
| </string-array> |
| |
| <!-- Integer indicating the framework scan interval in milliseconds. This is used in the scenario |
| where the chipset does not support background scanning (config_wifi_background_scan_suport |
| is false) to set up a periodic wake up scan so that the device can connect to a new access |
| point on the move. A value of 0 means no periodic scans will be used in the framework. --> |
| <integer translatable="false" name="config_wifi_framework_scan_interval">0</integer> |
| |
| <!-- Boolean indicating whether the wifi chipset has dual frequency band support --> |
| <bool translatable="false" name="config_wifi_dual_band_support">true</bool> |
| |
| <!-- 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>"bt-pan"</item> |
| </string-array> |
| |
| <!-- Separate software navigation bar required on this device. --> |
| <bool name="config_showNavigationBar">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 Flinger audio_policy.conf 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> |
| |
| </resources> |