已知問題
透過集合功能整理內容
你可以依據偏好儲存及分類內容。
零接觸機制適用於所有搭載 Android 9.0 以上版本的裝置，但部分裝置會因軟體不相容而無法使用這項機制。下表列出據報無法正常運作零接觸註冊的裝置。
Google 正與製造商合作解決問題，這些裝置的後續軟體版本可能就能正常使用零接觸註冊功能。在某些情況下，問題可能與特定國家/地區或電信業者版本的裝置有關。購買前請先洽詢裝置經銷商。
| 製造商 |
模型 |
附註 |
| 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) |
安裝 OTA 更新即可解決問題。 |
| Samsung |
SM-P610 (Galaxy Tab S6 Lite) |
安裝 OTA 更新即可解決問題。 |
| Samsung |
SM-T500 (Samsung Galaxy Tab A7 10.4) |
安裝 OTA 更新即可解決問題。 |
| Unihertz |
Titan |
|
| Urovo |
DT50W |
|
| Vivo |
various |
由於設定精靈進行了修改，零接觸註冊機制無法在大多數 Vivo Android 9 和 Android 10 機型上運作。Vivo 裝置的 Android 11 機型支援零接觸註冊機制。 |
| ZTE (Telstra) |
T86 (Tough Max 3) |
|
Samsung 專屬問題
Wi-Fi AP：如果使用者收到「無法登入 Wi-Fi AP。這部裝置已在未經授權的情況下恢復原廠設定。「無法存取登入畫面」，建議使用未採用強制回應入口網站的 Wi-Fi AP，例如在移除 KME (Knox 行動註冊) 後將裝置恢復原廠設定時。如果從伺服器移除 KME，裝置也必須更新 KME 刪除資訊，這時需要 Wi-Fi 連線。如果將強制回應入口網站設為 Wi-Fi，系統就會顯示錯誤訊息。
裝置設定：不建議在同一部裝置上設定零接觸註冊和 KME。在兩個服務中設定裝置可能會導致設定不同步，進而造成混淆，如果裝置發生其他問題，也很難進行偵錯。
雙 SIM 卡裝置問題
雙 SIM 卡裝置搭載兩個獨立數據機，且具備兩個 IMEI 號碼。經銷商可以註冊兩個 IMEI，但如果只註冊一個，建議選擇數值最低的 IMEI 號碼，因為零接觸註冊機制使用最低的 IMEI 時，運作會更可靠。
或者，經銷商也可以依序號、製造商和型號註冊所有裝置。
沒有電話功能的行動裝置
如果裝置具備行動網路連線功能，但沒有電話功能 (例如支援數據連線的平板電腦)，且符合下列條件，即可略過零接觸註冊：
- 預先載入的 Google Play 服務版本介於
23.13.12
和 23.39.18之間。
- 且只會以 IMEI 註冊。
以下提供兩種可能的解決方法：
- 照常設定裝置，並等待裝置收到恢復原廠設定通知。此時，零接觸註冊會註冊更可靠的 ID，因此日後嘗試佈建時會成功。
- 註冊裝置序號、製造商、型號和 IMEI。
除非另有註明，否則本頁面中的內容是採用創用 CC 姓名標示 4.0 授權，程式碼範例則為阿帕契 2.0 授權。詳情請參閱《Google Developers 網站政策》。Java 是 Oracle 和/或其關聯企業的註冊商標。
上次更新時間：2025-07-25 (世界標準時間)。
[null,null,["上次更新時間：2025-07-25 (世界標準時間)。"],[[["\u003cp\u003eZero-touch enrollment, while designed for Android 9.0 and higher, may not function correctly on some devices due to software incompatibilities, as detailed in the provided table.\u003c/p\u003e\n"],["\u003cp\u003eGoogle is actively collaborating with manufacturers to resolve these incompatibility issues, and later software versions might enable zero-touch on previously affected devices, although country or carrier variants may have specific issues.\u003c/p\u003e\n"],["\u003cp\u003eFor Samsung devices experiencing Wi-Fi issues, it's advised to use a Wi-Fi access point without a captive portal, especially after removing Knox Mobile Enrolment (KME).\u003c/p\u003e\n"],["\u003cp\u003eIt is not recommended to configure both zero-touch and Knox Mobile Enrolment (KME) on the same Samsung device due to potential configuration conflicts that are difficult to debug.\u003c/p\u003e\n"],["\u003cp\u003eOn dual-SIM devices, resellers should preferably register the numerically lowest IMEI number for more reliable zero-touch enrollment, or register by serial number, manufacturer and model as an alternative.\u003c/p\u003e\n"]]],["Zero-touch enrollment fails on specific devices: ALLDOCUBE iPlay 7T, Multilaser M10_4G_PRO, OnePlus 6, Realme 6i/XT, Unihertz Titan, Urovo DT50W, and ZTE T86. Most Vivo Android 9/10 models also experience issues. Samsung Galaxy A20, Tab S6 Lite, and Tab A7 10.4 require OTA updates. For Wi-Fi issues on Samsung devices, avoid captive portals. Do not configure zero-touch and KME simultaneously on the same device. For dual-SIM devices register the numerically lowest IMEI. Cellular devices without telephony can skip zero-touch if they meet the specific requirements.\n"],null,["# Known issues\n\nWhile zero-touch is designed to work with all devices running Android 9.0 and\nhigher, there are some devices where zero-touch is blocked due to software\nincompatibility. The following table lists those devices which were reported\nto have had zero-touch failing to work correctly.\n\nWhere possible, Google is working with the manufacturers to address the issues,\nand zero-touch may work correctly in later software versions of these devices.\nIn some cases, the issue may be specific to a particular country or carrier\nvariant of the device. Check with your device reseller before purchasing.\n\n| Manufacturer | Model | Notes |\n|---------------|--------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| ALLDOCUBE | iPlay 7T (T701) | |\n| Multilaser | M10_4G_PRO (Multilaser M10 4G Pro) | |\n| OnePlus | A6003 (OnePlus 6) | |\n| Realme | Realme 6i | |\n| Realme | Realme XT | |\n| Samsung | SM-A205F (Samsung Galaxy A20) | Installing OTA update resolves the issue. |\n| Samsung | SM-P610 (Galaxy Tab S6 Lite) | Installing OTA update resolves the issue. |\n| Samsung | SM-T500 (Samsung Galaxy Tab A7 10.4) | Installing OTA update resolves the issue. |\n| Unihertz | Titan | |\n| Urovo | DT50W | |\n| 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. |\n| ZTE (Telstra) | T86 (Tough Max 3) | |\n\nSamsung specific issues\n-----------------------\n\n**Wi-Fi AP:** For users who experience the error message *\"Unable to sign in to\nWi-Fi AP. An unauthorised factory reset has been performed on this device. The\nsign in screen cannot be accessed.\"*, it is recommended to use a Wi-Fi AP that\ndoes not use a captive portal, like in the case of the device being factory\nreset after removing the KME (Knox Mobile Enrolment). If the KME is removed\nfrom the server, the KME deletion information must be updated on the device\nalso for which Wi-Fi connection is required. If the captive portal is set to\nWi-Fi, the error message appears.\n\n**Device Configuration:** It is not recommended to configure zero-touch and KME\non the same device. Configuring the device in both services is likely to cause\nconfusion as the configurations can be out of sync, which is difficult to debug\nif the device experiences further issues.\n\nDual SIM device issues\n----------------------\n\nA dual-SIM device includes two discrete modems and has two IMEI numbers.\nResellers can register both IMEIs, but if registering just one, prefer the\nnumerically lowest IMEI number as zero-touch enrollment works more reliably with\nthe lowest IMEI.\n\nAlternatively resellers are also able to register all devices by serial number,\nmanufacturer and model.\n\nCellular devices without telephony\n----------------------------------\n\nDevices that have mobile network connectivity but no telephony features, such as\ndata-enabled tablets, can skip zero-touch if the following conditions apply:\n\n- They are preloaded with a Google Play services version between `23.13.12` and `23.39.18`.\n- They are registered by only their IMEI.\n\nThere are two possible workarounds:\n\n- 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.\n- Register the device serial number, manufacturer, model, and IMEI."]]
