While zero-touch is designed to work with all devices running Android 9.0 and higher, there are some devices where zero-touch is blocked due to software incompatibility. The following table lists those devices which were reported to have had zero-touch failing to work correctly.
Where possible, Google is working with the manufacturers to address the issues, and zero-touch may work correctly in later software versions of these devices. In some cases, the issue may be specific to a particular country or carrier variant of the device. Check with your device reseller before purchasing.
| Manufacturer | Model | Notes |
|---|---|---|
| ALLDOCUBE | iPlay 7T (T701) | |
| Multilaser | M10_4G_PRO (Multilaser M10 4G Pro) | |
| OnePlus | A6003 (OnePlus 6) | |
| Realme | Realme 6i | |
| Realme | Realme XT | |
| Samsung | SM-A205F (Samsung Galaxy A20) | Installing OTA update resolves the issue. |
| Samsung | SM-P610 (Galaxy Tab S6 Lite) | Installing OTA update resolves the issue. |
| Samsung | SM-T500 (Samsung Galaxy Tab A7 10.4) | Installing OTA update resolves the issue. |
| Unihertz | Titan | |
| Urovo | DT50W | |
| Vivo | various | Due to modifications made in the setup wizard, zero-touch is blocked from working in most Vivo Android 9 and Android 10 models. Vivo are supporting zero-touch in Android 11 models. |
| ZTE (Telstra) | T86 (Tough Max 3) |
Samsung specific issues
Wi-Fi AP: For users who experience the error message "Unable to sign in to Wi-Fi AP. An unauthorised factory reset has been performed on this device. The sign in screen cannot be accessed.", it is recommended to use a Wi-Fi AP that does not use a captive portal, like in the case of the device being factory reset after removing the KME (Knox Mobile Enrolment). If the KME is removed from the server, the KME deletion information must be updated on the device also for which Wi-Fi connection is required. If the captive portal is set to Wi-Fi, the error message appears.
Device Configuration: It is not recommended to configure zero-touch and KME on the same device. Configuring the device in both services is likely to cause confusion as the configurations can be out of sync, which is difficult to debug if the device experiences further issues.
Dual SIM device issues
Resellers and OEMs need to do the following in order for zero-touch to work reliably on dual-sim devices:
- Resellers need to register the devices using the numerically lowest IMEI (dual-sim devices come with two discrete modems and two IMEI numbers).
- OEMs need to pre-install on devices a version of Google Play services higher than 24.07.12.
Once the user boots up the device, it gets detected by zero-touch and goes through the enrollment process.
Cellular devices without telephony
Devices that have mobile network connectivity but no telephony features, such as data-enabled tablets, can skip zero-touch if the following conditions apply:
- They are preloaded with a Google Play services version between
23.13.12and23.39.18. - They are registered by only their IMEI.
There are two possible workarounds:
- Set up the device as normal, and wait until it receives a factory reset notification. At this point, zero-touch registers a more reliable identifier, so future attempts to provision it will succeed.
- Register the device serial number, manufacturer, model, and IMEI. This is only possible by registering two devices: one containing the IMEI and one containing the serial number, manufacturer, and model.