Turn Your Android Phone into a Kiosk Device with Lock Task Mode

Why use Lock Task Mode for a kiosk?

Lock Task Mode (sometimes called screen pinning for developers) lets a device run a single app while disabling system navigation, status bar, and most settings. It’s the official way Android supports public‑facing kiosks, digital signage, or any scenario where you want to hand a phone to a user without exposing the rest of the OS.

Unlike rooting or custom ROMs, Lock Task Mode works on stock Android 5.0+ and requires only a few ADB commands. The device remains fully update‑able and secure, and you can revert the changes at any time.

Before you start

• Back up any important data. Setting a device‑owner will factory‑reset the device on most devices because the command can only be run on a “clean” device (no Google account, no existing device owner).
• Charge the phone to at least 60 % and keep it connected to power during the process.
• Enable Developer options → USB debugging. On most phones: Settings > About phone > Build number (tap 7 times) then Settings > System > Developer options > USB debugging.
• Install Android Platform‑Tools (ADB) on your computer.
• Have a stable USB cable and a PC running Windows, macOS, or Linux.

Step 1 – Choose a kiosk‑ready app

Lock Task Mode can only be started by an app that has been granted the android:lockTaskMode permission and is set as a device‑owner. Several free apps on the Play Store already include the required device‑admin receiver, for example:

• SureLock Kiosk Lockdown (free tier)
• Fully Kiosk Browser (basic version)
• Kiosk Mode – Lockdown (open‑source)

For this tutorial we’ll use **SureLock** because it provides a simple UI to enable lock task mode and its package name is stable.

After installation the app will request Device admin permission. Grant it by tapping Activate → Allow in the system dialog.

Step 2 – Prepare the device for a device‑owner assignment

Android only allows dpm set-device-owner on a device that has no Google account and no existing device owner. The safest way is to perform a factory reset after you have backed up your data.

To factory‑reset:

Once the device restarts, enable USB debugging again (see the “Before you start” list).

Step 3 – Set SureLock as the device owner via ADB

Connect the phone to your computer with the USB cable. Open a terminal (or Command Prompt) and verify the connection:

adb devices

You should see a device ID with the word device. If it shows unauthorized, check the phone for a prompt asking to allow USB debugging and tap Allow.

Now run the device‑owner command. The exact component name for SureLock is:

adb shell dpm set-device-owner com.surelock.kiosk/.DeviceAdminReceiver

Replace com.surelock.kiosk/.DeviceAdminReceiver with the actual receiver class if the app updates its package structure (you can find it in the app’s AndroidManifest.xml via APKTool if needed). For most versions the above works.

At this point the device recognises SureLock as the privileged “device owner”. This status grants the app permission to start Lock Task Mode without user interaction.

Step 4 – Enable Lock Task Mode inside SureLock

Open the SureLock app. Navigate to Settings > Lock Task Mode (the exact path may vary by version, but look for “Kiosk Mode” or “Lock task” options).

• Toggle Enable Lock Task Mode to On.
• Select the activity you want to lock – typically com.surelock.kiosk/.MainActivity. This tells Android which screen should stay in the foreground.
• Save the configuration.

After saving, tap the Start Kiosk button inside the app. The device will immediately hide the navigation bar, status bar, and the recent‑apps button. Only the SureLock interface remains visible.

Step 5 – Exiting Lock Task Mode safely

Because the device is now locked, you need a reliable way to exit for maintenance:

• Via ADB: Run adb shell am stopservice -n com.surelock.kiosk/.KioskService (replace the service name if different) or simply adb shell am clear-task com.surelock.kiosk.
• Via a hidden admin shortcut: Some kiosk apps expose a secret gesture (e.g., long‑press the back button three times). Check SureLock’s help page for the exact sequence.
• Factory reset: As a last resort, boot into recovery (Power + Volume Down) and wipe data.

After exiting, you can remove the device‑owner status if you ever want to return the phone to normal use:

adb shell dpm remove-active-admin com.surelock.kiosk/.DeviceAdminReceiver

Note that removing the admin does not automatically clear the lock‑task configuration; you may need to open the app once more and disable the lock‑task toggle.

Alternative: Using Android’s built‑in Screen Pinning

If a factory reset is not an option, Android’s Screen Pinning offers a lightweight, user‑initiated kiosk‑like experience:

Screen Pinning does not hide the status bar, and users can still exit with the button combination, but it requires no ADB or device‑owner setup.

Troubleshooting common issues

Safety and privacy considerations

• Data loss: Setting a device owner forces a factory reset on most devices. Back up contacts, photos, and any app data beforehand.
• Account removal: Do not add a Google account until after the device‑owner is set; otherwise the command will fail.
• Future updates: System OTA updates will still install, but a major Android version change may reset the device‑owner status. Re‑apply the steps after a major update.
• Security: A device‑owner can enforce security policies (e.g., disable USB debugging). Review the kiosk app’s permissions to ensure it does not expose unnecessary data.

Wrapping up

By following the steps above you have turned a regular Android phone into a dedicated kiosk that runs a single app, hides system UI, and prevents users from leaving the intended experience—all without rooting or flashing custom ROMs. The setup is reversible, works on most modern Android devices, and gives you a solid foundation for public displays, point‑of‑sale terminals, or classroom devices.

Remember to keep a backup of the ADB commands and the device‑owner package name in a secure place. If you ever need to repurpose the device, the removal command and a simple factory reset will restore full Android functionality.