<?xml version="1.0" encoding="utf-8"?>
<!-- Copyright (C) 2023 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 for Thread Network. All
	 configuration names should use the "config_thread" prefix.
-->

<resources xmlns:xliff="urn:oasis:names:tc:xliff:document:1.2">
    <!-- Sets to {@code true} to enable Thread on the device by default. Note this is the default
    value, the actual Thread enabled state can be changed by the {@link
    ThreadNetworkController#setEnabled} API.
    -->
    <bool name="config_thread_default_enabled">true</bool>

    <!-- Sets to {@code true} to enable Thread Border Router on the device by default.
    -->
    <bool name="config_thread_border_router_default_enabled">false</bool>

    <!-- Whether to enable or disable setting Thread country code from the telephony, wifi, location,
     etc. The country code could be used by the Thread co-processor for setting the fixed output
	 power of Thread radio. If the device needs to dynamically change the max output power according
	 to the user scenario to meet the requirement of Specific Absorption Rate (SAR), it should call
	 the API `setChannelMaxPowers()` to change the max output power, and this configuration could be
	 set to false to disable the Thread service from setting the Thread country code.
    -->
    <bool name="config_thread_country_code_enabled">true</bool>

    <!-- Whether to use location APIs in the algorithm to determine country code or not.
    If disabled, will use other sources (telephony, wifi, etc) to determine device location for
    Thread Network regulatory purposes.
    -->
    <bool name="config_thread_location_use_for_country_code_enabled">true</bool>

    <!-- Specifies the UTF-8 vendor name of this device. If this value is not an empty string, it
    will be included in TXT value (key is 'vn') of the "_meshcop._udp" mDNS service as well as the
    Vendor Name TLV for network diagnostic. A non-empty string value must not exceed length of 24
    UTF-8 bytes. A special value "ro.product.manufacturer" indicates this value should be derived
    from the `ro.product.manufacturer` system property.
    -->
    <string translatable="false" name="config_thread_vendor_name">ro.product.manufacturer</string>

    <!-- Specifies the 24 bits vendor OUI of this device. If this value is not an empty string, it
    will be included in TXT (key is 'vo') value of the "_meshcop._udp" mDNS service which is
    published by the Thread service. The OUI can be represented as a base-16 number of six
    hexadecimal digits, or octets separated by hyphens or dots. For example, "ACDE48", "AC-DE-48"
    and "AC:DE:48" are all valid representations of the same OUI value.
    -->
    <string translatable="false" name="config_thread_vendor_oui"></string>

    <!-- Specifies the UTF-8 product model name of this device. If this value is not an empty
    string, it will be included in TXT (key is 'mn') value of the "_meshcop._udp" mDNS service as
    well as the Vendor Model TLV for network diagnostic. A non-empty string value must not exceed
    length of 24 UTF-8 bytes. A special value "ro.product.model" indicates this value should be
    derived from the `ro.product.model` system property.
    -->
    <string translatable="false" name="config_thread_model_name">ro.product.model</string>

    <!-- Specifies vendor-specific mDNS TXT entries which will be included in the "_meshcop._udp"
    service. The TXT entries list MUST conform to the format requirement in RFC 6763 section 6. For
    example, the key and value of each TXT entry MUST be separated with "=". If the value length is
    0, the trailing "=" may be omitted. Additionally, the TXT keys MUST start with "v" and be at
    least 2 characters.

    Note, do not include credentials in any of the TXT entries - they will be advertised on Wi-Fi
    or Ethernet link.

    An example config can be:
      <string-array name="config_thread_mdns_vendor_specific_txts">
        <item>vab=123</item>
        <item>vcd</item>
      </string-array>
    -->
    <string-array name="config_thread_mdns_vendor_specific_txts">
    </string-array>

    <!-- Whether to enable / start SRP server only when border routing is ready. SRP server and
    border routing are mandatory features required by a Thread Border Router, and it takes 10 to
    20 seconds to establish border routing. Starting SRP server earlier is useful for use cases
    where the user needs to know what are the devices in the network before actually needs to reach
    to the devices, or reaching to Thread end devices doesn't require border routing to work.
    -->
    <bool name="config_thread_srp_server_wait_for_border_routing_enabled">true</bool>

    <!-- Whether this border router will automatically join the previous connected network after
    device reboots. Setting this value to false can allow the user to control the lifecycle of
    the Thread border router state on this device.
    -->
    <bool name="config_thread_border_router_auto_join_enabled">true</bool>
</resources>
