1<?xml version="1.0" encoding="utf-8"?> 2<!-- Copyright (C) 2023 The Android Open Source Project 3 4 Licensed under the Apache License, Version 2.0 (the "License"); 5 you may not use this file except in compliance with the License. 6 You may obtain a copy of the License at 7 8 http://www.apache.org/licenses/LICENSE-2.0 9 10 Unless required by applicable law or agreed to in writing, software 11 distributed under the License is distributed on an "AS IS" BASIS, 12 WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. 13 See the License for the specific language governing permissions and 14 limitations under the License. 15--> 16 17<!-- These resources are around just to allow their values to be customized 18 for different hardware and product builds for Thread Network. All 19 configuration names should use the "config_thread" prefix. 20--> 21 22<resources xmlns:xliff="urn:oasis:names:tc:xliff:document:1.2"> 23 <!-- Sets to {@code true} to enable Thread on the device by default. Note this is the default 24 value, the actual Thread enabled state can be changed by the {@link 25 ThreadNetworkController#setEnabled} API. 26 --> 27 <bool name="config_thread_default_enabled">true</bool> 28 29 <!-- Sets to {@code true} to enable Thread Border Router on the device by default. 30 --> 31 <bool name="config_thread_border_router_default_enabled">false</bool> 32 33 <!-- Whether to enable or disable setting Thread country code from the telephony, wifi, location, 34 etc. The country code could be used by the Thread co-processor for setting the fixed output 35 power of Thread radio. If the device needs to dynamically change the max output power according 36 to the user scenario to meet the requirement of Specific Absorption Rate (SAR), it should call 37 the API `setChannelMaxPowers()` to change the max output power, and this configuration could be 38 set to false to disable the Thread service from setting the Thread country code. 39 --> 40 <bool name="config_thread_country_code_enabled">true</bool> 41 42 <!-- Whether to use location APIs in the algorithm to determine country code or not. 43 If disabled, will use other sources (telephony, wifi, etc) to determine device location for 44 Thread Network regulatory purposes. 45 --> 46 <bool name="config_thread_location_use_for_country_code_enabled">true</bool> 47 48 <!-- Specifies the UTF-8 vendor name of this device. If this value is not an empty string, it 49 will be included in TXT value (key is 'vn') of the "_meshcop._udp" mDNS service as well as the 50 Vendor Name TLV for network diagnostic. A non-empty string value must not exceed length of 24 51 UTF-8 bytes. A special value "ro.product.manufacturer" indicates this value should be derived 52 from the `ro.product.manufacturer` system property. 53 --> 54 <string translatable="false" name="config_thread_vendor_name">ro.product.manufacturer</string> 55 56 <!-- Specifies the 24 bits vendor OUI of this device. If this value is not an empty string, it 57 will be included in TXT (key is 'vo') value of the "_meshcop._udp" mDNS service which is 58 published by the Thread service. The OUI can be represented as a base-16 number of six 59 hexadecimal digits, or octets separated by hyphens or dots. For example, "ACDE48", "AC-DE-48" 60 and "AC:DE:48" are all valid representations of the same OUI value. 61 --> 62 <string translatable="false" name="config_thread_vendor_oui"></string> 63 64 <!-- Specifies the UTF-8 product model name of this device. If this value is not an empty 65 string, it will be included in TXT (key is 'mn') value of the "_meshcop._udp" mDNS service as 66 well as the Vendor Model TLV for network diagnostic. A non-empty string value must not exceed 67 length of 24 UTF-8 bytes. A special value "ro.product.model" indicates this value should be 68 derived from the `ro.product.model` system property. 69 --> 70 <string translatable="false" name="config_thread_model_name">ro.product.model</string> 71 72 <!-- Specifies vendor-specific mDNS TXT entries which will be included in the "_meshcop._udp" 73 service. The TXT entries list MUST conform to the format requirement in RFC 6763 section 6. For 74 example, the key and value of each TXT entry MUST be separated with "=". If the value length is 75 0, the trailing "=" may be omitted. Additionally, the TXT keys MUST start with "v" and be at 76 least 2 characters. 77 78 Note, do not include credentials in any of the TXT entries - they will be advertised on Wi-Fi 79 or Ethernet link. 80 81 An example config can be: 82 <string-array name="config_thread_mdns_vendor_specific_txts"> 83 <item>vab=123</item> 84 <item>vcd</item> 85 </string-array> 86 --> 87 <string-array name="config_thread_mdns_vendor_specific_txts"> 88 </string-array> 89 90 <!-- Whether to enable / start SRP server only when border routing is ready. SRP server and 91 border routing are mandatory features required by a Thread Border Router, and it takes 10 to 92 20 seconds to establish border routing. Starting SRP server earlier is useful for use cases 93 where the user needs to know what are the devices in the network before actually needs to reach 94 to the devices, or reaching to Thread end devices doesn't require border routing to work. 95 --> 96 <bool name="config_thread_srp_server_wait_for_border_routing_enabled">true</bool> 97 98 <!-- Whether this border router will automatically join the previous connected network after 99 device reboots. Setting this value to false can allow the user to control the lifecycle of 100 the Thread border router state on this device. 101 --> 102 <bool name="config_thread_border_router_auto_join_enabled">true</bool> 103</resources> 104