Hilfe - Alle Produkte & Anleitungen

Kiosk - Set Up Device Owner

Set Up Device Owner (Technician Guide)

What is Device Owner and why do we need it?

The kiosk app can update itself automatically (APK updates are downloaded from our server). Normally, Android shows a confirmation dialog for every installation — the user has to tap "Install".

The problem: Our kiosk devices often have no keyboard and no mouse. Nobody can confirm the dialog, and the update gets stuck.

The solution: When the app is set up as Device Owner, it can install updates without a confirmation dialog ("silent install"). The device then updates completely automatically.

Without Device Owner

With Device Owner

Update installation

Manual — confirmation dialog must be accepted

Automatic — no dialog needed

Display in the app

"Manual (no Device Owner)"

"Automatic (Device Owner)"

Suitable for kiosk?

No

Yes


Prerequisites

  • Windows PC (or laptop) with internet access

  • USB cable (USB-A to USB-C or Micro-USB, depending on the device)

  • Kiosk device (Sunmi or similar) with the kiosk app installed

  • The device must be powered on and unlocked


Step 1: Install ADB (Windows)

ADB (Android Debug Bridge) is a tool that allows you to control Android devices from your PC.

1.1 Download

Download the Android Platform Tools:

Download SDK Platform-Tools for Windows

Click "Download SDK Platform-Tools for Windows" and accept the license terms.

1.2 Extract

  1. Create the folder C:\adb\

  2. Extract the downloaded ZIP file there

  3. After extraction, the file C:\adb\platform-tools\adb.exe should exist

1.3 Set PATH (optional but recommended)

So you can run adb from anywhere in the command line:

  1. Press the Windows key, type "Environment Variables" and open "Edit the system environment variables"

  2. Click "Environment Variables..."

  3. Under "System variables", select "Path" and click "Edit..."

  4. Click "New" and add: C:\adb\platform-tools

  5. Confirm all dialogs with OK

1.4 Test

Open a new Command Prompt (Windows key > cmd > Enter) and type:

adb version

Expected output (version number may vary):

Android Debug Bridge version 1.0.41

If the command is not found: Check the PATH or navigate directly to the folder:

cd C:\adb\platform-tools
adb version


Step 2: Enable USB Debugging on the Kiosk

2.1 Unlock Developer Options

  1. Open Android Settings on the kiosk device

  2. Go to "About device" (or "About phone")

  3. Tap 7 times quickly on "Build number"

  4. A message appears: "You are now a developer"

Sunmi note: On Sunmi devices, you can find the build number under Settings > About device > Build number. If a password is required, contact Sunmi support.

2.2 Enable USB Debugging

  1. Go back to Android Settings

  2. Open "Developer options" (should now be visible)

  3. Enable "USB Debugging"

  4. Confirm the security prompt with OK


Step 3: Connect the Kiosk via USB

  1. Connect the kiosk device to the Windows PC with a USB cable

  2. A dialog appears on the kiosk device: "Allow USB debugging?"

  3. Check "Always allow from this computer"

  4. Tap "OK" or "Allow"

Verify the connection

Open the Command Prompt on the PC and type:

adb devices

Expected output:

List of devices attached
XXXXXXXX    device

Where XXXXXXXX is the serial number of the device.

Error cases:

  • Empty list: Check USB cable, re-enable USB debugging, try a different cable

  • unauthorized: Accept the confirmation dialog on the device

  • offline: Disconnect and reconnect the USB cable


Step 4: Remove Existing Accounts

Device Owner can only be set if no Google accounts are configured on the device. If accounts exist, they must be removed first.

Check and remove accounts

  1. Open Android Settings on the kiosk device

  2. Go to "Accounts" (or "Users & accounts")

  3. If Google accounts are listed:Tap on the accountTap **"Remove account"**Confirm with "Remove account"

  4. Repeat for all Google accounts

Important: Only Google accounts need to be removed. Other accounts (e.g., manufacturer accounts) can remain.


Step 5: Set Device Owner

5.1 Find the package name

The package name depends on the installed app variant. You can find it in the app:

  1. Open the kiosk app on the device

  2. Go to Settings (gear icon)

  3. Scroll to the "APK Update" section

  4. If there is a hint "For automatic updates...", the ADB command with the correct package name is displayed

The package name has the format: at.meisterwork.kiosk.<variant>

5.2 Run the ADB command

Run the following command in the Command Prompt (replace <package-name> with the package name from the app):

adb shell dpm set-device-owner <package-name>/com.loyalty.apkupdate.KioskDeviceAdminReceiver

Example (for the treuepass variant):

adb shell dpm set-device-owner at.meisterwork.kiosk.treuepass/com.loyalty.apkupdate.KioskDeviceAdminReceiver

5.3 Success message

On success, you will see:

Success: Device owner set to package at.meisterwork.kiosk.<variant>
Active admin set to component {at.meisterwork.kiosk.<variant>/com.loyalty.apkupdate.KioskDeviceAdminReceiver}


Step 6: Verify

  1. Open the kiosk app on the device

  2. Go to Settings (gear icon)

  3. Scroll to the "APK Update" section

  4. The installation mode should now show: "Automatic (Device Owner)"

If it still shows "Manual (no Device Owner)", restart the app and check again.


Troubleshooting

"Not allowed to set the device owner because there are already some accounts on the device"

Cause: There are still Google accounts configured on the device.

Solution: Remove all Google accounts (see Step 4) and run the command again.

If the account cannot be removed through Settings, try:

adb shell pm remove-user 0

Warning: If this also doesn't work, the device must be factory reset. All data will be lost!


"Device is already provisioned"

Cause: The device has already been set up (e.g., through a setup wizard or MDM system).

Solution: Factory reset the device and set it up again:

  1. Settings > System > Reset options > Erase all data

  2. After restart: Skip the Google account setup

  3. Enable USB debugging (Step 2)

  4. Run the Device Owner command (Step 5)


ADB cannot find the device

Symptom: adb devices shows an empty list.

Possible causes and solutions:

  1. USB debugging not enabled: Check Step 2

  2. Wrong USB cable: Some cables are charge-only without data connection — use a different cable

  3. USB drivers missing: Install the USB drivers from the device manufacturer (for Sunmi: Sunmi drivers from the Sunmi website)

  4. USB port defective: Try a different USB port on the PC

  5. ADB server stuck: Restart the ADB server:

adb kill-server
adb start-server
adb devices


Remove Device Owner

If the Device Owner needs to be removed:

adb shell dpm remove-active-admin <package-name>/com.loyalty.apkupdate.KioskDeviceAdminReceiver

Alternatively, the device can be factory reset.