Developer hub / public basics / Technical article

Kiosk and MDM provisioning checklist

Build a repeatable dedicated-device rollout using SUNMI Kiosk APIs, OEMConfig, the selected MDM and an explicit recovery owner.

Discuss your project

Build a repeatable dedicated-device rollout using SUNMI Kiosk APIs, OEMConfig, the selected MDM and an explicit recovery owner.

v1.0.0 / Technical articleSources checked: 2026-08-30

Model scope: K2 or another named SUNMI device with a selected MDM, ownership mode and approved kiosk profile. K2 is documented with Android 7.1, 9 or 13 depending on configuration and batch.
Android version: K2 has multiple documented Android versions by configuration. V2s and V2s PLUS are listed as Android 11; L2s PRO as Android 12. Confirm the actual batch before policy design.
Firmware: Record the exact SUNMI OS or firmware because Kiosk, System UI, OEMConfig and software-management availability can be scope-dependent.
SDK / interface: SUNMI Kiosk Management, System UI Management, Software Management, Customer API and OEMConfig; Android managed configurations and dedicated-device policy provide the platform context.
Application build: Record the exact project build and hardware environment before deployment.

What the vendor documentation covers

SUNMI documents Kiosk, System UI and Software Management modules with device or financial-scope qualifications for some APIs.
SUNMI OEMConfig exposes managed settings for device, network, printer, scanner and kiosk behavior through an MDM path.
Android documents dedicated-device and managed-configuration concepts that must be combined with the selected MDM and device owner model.

API surface

SUNMI Customer API service connection and module-specific AAR interfaces
Kiosk list, enable or disable, exit control, navigation-bar and status-bar policy APIs
Software Management install, uninstall, enable or disable and default-app operations
SUNMI OEMConfig managed configuration keys
Android managed configurations and dedicated-device policy

Scope and prerequisites

Named device batch, Android version and firmware revision.
MDM provider, enrollment owner, ownership mode and support escalation.
Signed package, package hash, update channel and recovery image or process.
Kiosk policy, managed-configuration values, network profile and accessory profile.

Permissions and ownership

Customer API and management modules can require local AAR distribution, package visibility and device or policy authority; obtain them through the authorized channel.
Kiosk exit control, system UI and silent software operations are high-privilege functions and must be approved by the device owner.
Never publish exit passwords, MDM tokens, signing keys, default credentials or customer package names.

Error handling

Plan for enrollment failure, policy drift, unsupported key, package signature mismatch, offline boot, failed update, app crash, kiosk exit recovery, factory reset and replacement-device handover.

Known limitations

SUNMI marks some Customer API capabilities for financial or specific device scopes; the module name alone does not guarantee availability.
OEMConfig capability depends on the selected MDM, app version, device model and firmware.
Zero-touch and reseller documentation describes a deployment route; it does not establish UnitWeave reseller status or service entitlement.
This guide is a fleet-rollout planning baseline; a deployment conclusion belongs to a named project record.

Implementation path

01
Choose the ownership and enrollment model first: MDM device owner, zero-touch or a controlled staging path. Record who owns the device, signing key, MDM tenant and recovery process.
02
Confirm the actual Android version and SUNMI OS for every target batch. Do not design a single K2 policy around one Android version because the official matrix lists 7.1, 9 and 13 variants.
03
Define the signed application package, update channel, default launch behavior, navigation and status-bar policy, network configuration and allowed peripherals.
04
Use OEMConfig for settings exposed by the selected device and MDM. Treat an SOTI example in the vendor documentation as a process reference, not proof that every MDM platform or model has identical support.
05
Use SUNMI Kiosk and System UI APIs only where the target ownership mode and firmware authorize them. Keep a local administrative recovery route owned by the project administrator.
06
Use Android managed-configuration and dedicated-device guidance for app configuration, boot, lock task, update and failure behavior. Keep policy values separate from application secrets.
07
Stage a small batch, verify enrollment and rollback, then freeze a handover record containing the package hash, policy revision, device naming rule and exception list.

Verification checklist

Record model, batch, Android version, SUNMI OS or firmware, MDM provider and policy revision.
Enroll a clean device and verify package installation, configuration delivery, default launch and kiosk lock behavior.
Test network loss, server outage, app crash, update failure, factory reset and replacement-device recovery.
Verify that the administrative exit path is controlled by the project owner and is not present as a public credential or screenshot.
Verify navigation, status bar, notification, orientation, printer and scanner policies on every Android variant in the batch.
Record staging exceptions and the rollback owner before approving volume deployment.

Publication gate

A published note must link a public source, keep claims within that source, show a named acceptance result and exclude private or customer material.

At least one public source is linked and its retrieval date is recorded.
Implementation claims stay within the named model, API and vendor-documentation scope.
UnitWeave test status is shown separately from manufacturer documentation status.
No private SDK, credential, customer binary, serial number or production data is included.
A project-specific compatibility or acceptance conclusion still requires a named test record.

License and provenance

Original UnitWeave editorial synthesis with source provenance. No vendor AAR, SO, APK, private SDK, customer binary or production data is redistributed.

Sample reference

No MDM tenant, package, token or recovery credential is published. Use the public SUNMI and Android references to build a redacted project-specific staging record.

Source basis

Source provenance

Sources checked: 2026-08-30

The implementation content is maintained here in UnitWeave structure and wording. Source URLs remain in the provenance record for attribution and version checking; they are not a substitute for the guide.

Kiosk Management ModuleSUNMI / Kiosk application list, enablement, navigation policy and exit-control concepts. / Sources checked: 2026-08-30
External SUNMI documentation. API availability and device ownership requirements vary by device scope; never publish exit passwords or customer package names.
Open reference
System UI Management ModuleSUNMI / Documented controls for navigation bar, status bar and notification UI. / Sources checked: 2026-08-30
External SUNMI documentation. Link to the current vendor page; do not redistribute vendor SDK binaries or assume every model shares the same implementation.
Open reference
Software Management ModuleSUNMI / Documented software management operations such as install, uninstall, enablement and default-app policy. / Sources checked: 2026-08-30
External SUNMI documentation. These are high-privilege operations; signing, ownership and policy prerequisites must be confirmed for the target project.
Open reference
SUNMI OEMConfigSUNMI / Managed configuration controls for device, display, network, printer, scanner and kiosk policy. / Sources checked: 2026-08-30
External SUNMI documentation. Link to the current vendor page; do not redistribute vendor SDK binaries or assume every model shares the same implementation.
Open reference
Android Enterprise Reseller / Zero-touchSUNMI / SUNMI-described Android Enterprise zero-touch and reseller deployment path. / Sources checked: 2026-08-30
External SUNMI documentation. This reference does not establish that UnitWeave is a Google reseller or provide zero-touch enrollment services without a separate authorization record.
Open reference
Overview of SUNMI Customer API SDKSUNMI / Customer API modules, asynchronous service connection and model or device-scope boundaries. / Sources checked: 2026-08-30
External SUNMI documentation. Link to the current vendor page; do not redistribute vendor SDK binaries or assume every model shares the same implementation.
Open reference
SUNMI Device's Android VersionSUNMI / Model-specific Android version information; some models have multiple versions or configurations. / Sources checked: 2026-08-30
External SUNMI documentation. Link to the current vendor page; do not redistribute vendor SDK binaries or assume every model shares the same implementation.
Open reference
Managed configurationsAndroid Developers / Android Enterprise managed application configuration model. / Sources checked: 2026-08-30
External Android documentation. Apply the guidance to the target Android API level and device policy.
Open reference
Dedicated devices cookbookAndroid Developers / Dedicated-device and kiosk deployment concepts. / Sources checked: 2026-08-30
External Android documentation. Apply the guidance to the target Android API level and device policy.
Open reference