Quick answer: On x86 kiosk PCs built from one cloned image, Android gives every machine the same ID. The Kiosk app therefore makes its own 16-character ID per machine and keeps it, so each kiosk shows up as a separate device.
The special ID is used only for the Kiosk app (package co.abacus.kiosk) on x86 or x86_64 devices. Every other device uses the normal Android ID.
How the ID is chosen, in order
An ID already saved in the app's private storage (SAVED).
A real hardware ID, if the device provides one (managed configuration keys hardware_id, abacus_hardware_id or device_serial, or a vendor property). Placeholder values such as "To be filled by O.E.M." and all zeros are ignored (HARDWARE).
An ID saved earlier in Documents/Abacus/kiosk_device_id, so it survives a reinstall (SHARED).
Otherwise a new random ID (GENERATED).
The ID is 16 lowercase hex characters with no dash.
On Android 11 and later, the shared copy in Documents is written only if the app has all-files storage access.
What support should do
If a cloned kiosk still shows a duplicate ID: on the clone, clear the Nomni Kiosk app data and delete the file Documents/Abacus/kiosk_device_id. The kiosk then uses its own hardware ID or makes a new one.
Fixed in Nomni Kiosk v1.0.77.
Need help?
Email support@nomni.ai or call 1300 445 483.