Released with v2.6.6

When provisioning a device using our provisioning app your device is locked down in the most secure way possible. Kiosk Browser becomes the "device owner" meaning that it is granted more permissions vs a standard Kiosk Browser installation.

Key Features:
Streamlined setup process (embed licence keys or remote management registration key)
Automatically grant majority of permissions
Set the default launcher programmatically without user intervention
Hide home button and recents button (Android 6.0 or higher)
Block access to the status bar (top of the screen) using official methods, rather than workaround
Update applications (Update Manager via remote management) or via our JavaScript interface, Android 6.0 or higher
Reboot device on schedule (Android 7.0 or higher)
Disable lock screen programatically
Block launching of applications not in app drawer (apps launched from JavaScript unaffected)
Disable booting into safe mode (Android 6.0 or higher)

Samsung specific features can be configured with our Security Module for Samsung Devices, however the only additional feature offered is full device screenshots (unless running lower than Android 7.0 in which case the security module is required for rebooting devices).

Android 6.0 or higher is supported, Android 5.0 works but has various issues relating to app pinning.
To start the provisioning process your device (the target device you want to install Kiosk Browser on) either needs to be brand new out of the box or factory reset.

Method 1. NFC
Google introduced the provisioning method when Android 5.0 was released, it was generally designed to use NFC to provision. NFC is required on both devices used in the process.
Install Kiosk Browser Provisioner on a device that will not be running Kiosk Browser (source device).
Launch Kiosk Browser Provisioner
Select target Android version
Change APK Url if using a custom build (otherwise leave default)
Select the locale you wish the target device to use (default is probably correct)
Enter optional parameters such as registration key or licence key
Tap compute checksum and wait for the checksum to be returned
Boot up your new device (factory reset or new out of the box)
Bump both devices together until you hear the "bump/nfc sound"
Follow the on-screen steps
Repeat steps for each device by bumping the devices together

NFC Provisioning

Method 2. QR Code (Android 7.0)
The QR code method was introduced in Android 7.0, it requires that your device has a camera.
Boot up your new / factory reset device
Tap the welcome screen 6 times until the QR wizard starts
Connect to your WiFi network
Scan the QR code from the Provisioner App or create a custom QR Code for your deployment
Your device will then download and install Kiosk Browser
Follow the on-screen steps

QR Code Provisioning

Method 3. ADB (set device owner via ADB command)
Only use if the previous options are not possible.
This option is complicated and long winded, BUT at the end of it your device will be running Kiosk Browser in device owner mode and you will benefit from all the features. Only for advanced users who know how to communicate with a device via ADB.

Boot up your new / factory reset device
Follow the setup wizard but DO NOT add a Google Account at this stage, otherwise provisioning will fail
Install Kiosk Browser via APK
Enable USB debugging on your device
Connect the device via USB cable
Execute the following command: adb shell dpm set-device-owner com.procoit.kioskbrowser/.receiver.AdminReceiver
If using a custom build use the following command adb shell dpm set-device-owner com.mycompany.browser/com.procoit.kioskbrowser.receiver.AdminReceiver and replace com.mycompany.browser with your custom package name.
Once the command has executed it should state success or failure, if successful Kiosk Browser is now provisioned

If you have purchased a custom build you will need to change com.procoit.kioskbrowser to your package name i.e. com.mycompany.browser, if unsure please contact us.
Was this article helpful?
Thank you!