Skip to content

Latest commit

 

History

History
79 lines (64 loc) · 3.05 KB

Troubleshooting.md

File metadata and controls

79 lines (64 loc) · 3.05 KB
author Description title ms.author ms.date ms.topic ms.prod ms.technology
saraclay
Troubleshooting different commercialization-related issues.
Troubleshooting
saclayt
08/28/18
article
windows-hardware
windows-oem

Troubleshooting

This is an article that contains common troubleshooting issues that people have come across. To find something specific, use Ctrl+F to find a word or phrase. Have any insight you want to add? Create a PR for this documentation or provident content feedback below.

Note

This documentation is a work in progress.

ASUS Tinkerboard and Rockchip support

While the ASUS Tinkerboard and Rockchip are not officially supported by us, there are cases where Rockchip has worked with other third parties to get SoC working on Windows 10 IoT Core.

Issue when connecting a MBM device when roaming

There are two things to consider when enabling roaming:

  1. The profile.xml configures roaming and sets the behavior to automatically establish a connection to the cellular network. To set a profile for roaming please refer to this article.
  <!-- applicability to any combination of home carrier, partner MOs and non-partner MOs, except for HomeAndNonPartner -->
  <xs:simpleType name="roamApplicabilityType">
    <xs:restriction base="xs:token">
       <xs:enumeration value="NonPartnerOnly"/>
       <xs:enumeration value="PartnerOnly"/>
       <xs:enumeration value="HomeOnly"/>
       <xs:enumeration value="HomeAndPartner"/>
       <xs:enumeration value="PartnerAndNonpartner"/>
       <xs:enumeration value="AllRoaming"/>
    </xs:restriction>
  </xs:simpleType>
  
  <xs:simpleType name="roamControlType">
    <xs:restriction base="xs:token">
       <xs:enumeration value="AllRoamAllowed"/>
       <xs:enumeration value="PartnerRoamAllowed"/>
       <xs:enumeration value="NoRoamAllowed"/>
    </xs:restriction>
  </xs:simpleType>

To set a profile for automatic connection, select "auto":

<!-- Connection Mode, default is "manual" -->
    <xs:element name="ConnectionMode" minOccurs="0">
      <xs:simpleType>
        <xs:restriction base="xs:string">
          <!-- manual connect always -->
          <xs:enumeration value="manual" />
          <!-- auto connect always -->
          <xs:enumeration value="auto" />
          <!-- auto connect when not roaming -->
          <xs:enumeration value="auto-home"/>
        </xs:restriction>
      </xs:simpleType>
    </xs:element>
  1. Another factor is that the per-interface roaming policy must be satisfied. By default, that policy is set to FALSE ("home carrier only"). This can be queried and changed in command line via netsh mbn get/set dataroamcontrol.

Example:

    netsh mbn show dataroamcontrol int=*
    netsh mbn set dataroamcontrol interface=Cellular profileset=all state=all
    netsh mbn set dataroamcontrol help

You may get error 0x139f (ERROR_INVALID_STATE) in the case when the device is roaming but the roaming policy disallows data roaming - error on a connect request sent to wwansvc.