Kiosk Mode Deployment: Device-Specific Config Values, Navigation Lockdown, Wi-Fi Changes, and Scheduled Reboots

Android

Title: Kiosk mode configuration — device values, navigation, Wi-Fi, and reboots

When managing Android devices in kiosk mode, you may need to pass device-specific data to your app, suppress navigation gestures, update Wi-Fi credentials, or schedule automatic reboots — all without interrupting the locked-down user experience.

Pass device-specific configuration values to your kiosk app

Esper supports three methods for delivering per-device configuration values. Choose the one that matches your app architecture.

Option 1: Android Managed Configurations (recommended)

If your app declares a Managed Configuration schema in its manifest, Esper can push per-device key-value pairs directly to it. Your app retrieves these at runtime using RestrictionsManager.getApplicationRestrictions(). This is the standard Android Enterprise approach and requires no SDK integration.

1. Navigate to Apps & Configuration → Managed Configurations and select your kiosk app.
2. Define the key-value pairs for the target device.
3. Apply the configuration to the device via Devices & Groups → [Device Name] → Apps.
4. Deploy the configuration to a single test device first and confirm your app reads the correct values at launch before rolling out to your fleet.

Option 2: Esper Device SDK

If your app integrates the Esper Device SDK, it can query device-specific attributes and properties directly at runtime without requiring a separate configuration push.

Option 3: Esper API with device tags and custom properties

Set device metadata via the Esper API and have your app read it back at runtime, provided the app holds API access credentials scoped to that device. Navigate to Devices & Groups → [Device Name] → Device Tags to assign metadata values.

Verify: Launch your kiosk app on the test device and confirm it displays or acts on the expected device-specific value before pushing the configuration fleet-wide.

Suppress bottom navigation and swipe gestures in kiosk mode

On some devices, the navigation bar or gesture layer remains active even when kiosk mode is enabled. This lets users swipe out of the kiosk app. Hiding navigation at the Blueprint level prevents this.

1. Go to Blueprints → [Blueprint Name] → Device Settings → Navigation Bar.
2. Set the Navigation Bar to Hidden or Disabled.
3. If your devices run Android 10 or later with gesture navigation enabled, also set System Navigation to 3-Button Navigation. Gesture navigation on Android 10+ can allow edge swipes that bypass kiosk lockdown.
4. Apply the updated Blueprint to your devices. If the gesture layer still persists — common on certain MediaTek and Qualcomm devices — check whether the OEM exposes additional lockdown options via a system app or OEM-specific API, and apply those separately.

Verify: After the Blueprint is applied, attempt to swipe up from the bottom edge of the screen. No navigation controls or app-switcher should appear.

Update Wi-Fi networks on a kiosk device

Wi-Fi credentials are managed through Blueprints. You can add or change networks without disabling kiosk mode, as long as the device is online when the update is pushed.

1. Go to Blueprints → [Blueprint Name] → Network → Wi-Fi.
2. Add the new SSID and password. You can configure multiple networks; the device connects to available networks in priority order.
3. Apply the updated Blueprint by navigating to Devices & Groups → [Device Name] → Blueprint → Apply. The device receives and applies the new configuration over its existing connection, then connects to the new network when it is available. Kiosk mode remains active throughout.

If the device is offline when you push the Blueprint update, the configuration cannot be delivered remotely. In that case:

• Disable kiosk mode on the device locally.
• Start a Remote View session via Devices & Groups → [Device Name] → Remote View once the device reconnects, or update network settings on-device directly.
• Re-enable kiosk mode by re-applying the Blueprint.

Verify: After the Blueprint is applied, go to Devices & Groups → [Device Name] → Device Info and confirm the device shows the new network SSID under connected network. The device status should return to Online within 5 minutes.

Schedule automatic device reboots

Scheduled reboots help maintain device health on long-running kiosk deployments by clearing memory and applying pending system updates.

1. Go to Blueprints → [Blueprint Name] → Device Settings → Reboot.
2. Enable Scheduled Reboot and set the time and frequency that fits your deployment. Choose a window when the device is not in active use — for example, overnight or during a known low-traffic period.
3. Apply the updated Blueprint to your devices via Devices & Groups → [Device Name] → Blueprint → Apply.

Verify: Check Devices & Groups → [Device Name] → Activity Feed after the scheduled reboot window has passed. A reboot event should appear confirming the device restarted at the configured time. The device should return to the kiosk app automatically on boot.

If this doesn't resolve it

Before contacting support, collect the following:

• The device serial number and Esper Device ID, found in Devices & Groups → [Device Name] → Device Info.
• The Blueprint name and the timestamp of the last applied Blueprint.
• A screenshot or screen recording of the specific behavior (gesture bypass, incorrect config value, Wi-Fi not connecting, or reboot not occurring).
• The Android version and device model, visible in Devices & Groups → [Device Name] → Device Info → OS Version.

Contact Esper Support with these details to expedite resolution.

Still need help?

If you're still experiencing issues with kiosk mode configuration, device lockdown, or scheduled reboots, please submit a support ticket and include your device model, current kiosk mode settings, Wi-Fi configuration details, and any error messages you're encountering.