Blueprint not published causes BLE pairing dialog to be auto-dismissed on managed device; offline device locked in Kiosk Mode requires factory reset

Android

This article covers two separate issues you may encounter on managed Samsung devices: BLE pairing dialogs being automatically dismissed, and devices becoming locked in Kiosk Mode without connectivity. Both issues have specific solutions outlined below.

Understanding the BLE pairing dialog issue

On fully-managed Samsung devices (particularly the SM-X110 with Knox active), you may find that the Android system Bluetooth pairing confirmation dialog ("Pair?" prompt) for a BLE peripheral automatically dismisses within a few seconds. This causes bonding to fail, and your app cannot complete the connection to devices like heart-rate sensors or other BLE peripherals that require pairing confirmation.

Note that plain BLE connections without pairing (such as EEG streaming devices) are not affected — only BLE peripherals requiring Android's system pairing dialog are impacted.

How to fix BLE pairing failure

BLE pairing dialogs are often auto-dismissed because your Blueprint has been created but not yet published. An unpublished Blueprint cannot be applied to your devices, so they continue operating under their previous or default policy.

In the Esper Console, go to Blueprints and locate the Blueprint you want to use.
Click Publish to move the Blueprint out of draft state.
Navigate to Devices & Groups and select the affected device or devices.
Click Actions → Converge to push the published Blueprint to your devices.
Wait a few moments for convergence to complete, then attempt to pair your BLE peripheral again. The pairing dialog should now remain visible long enough for you to accept it.

To verify the correct Blueprint was applied, navigate to Devices & Groups → [Device Name] → Blueprint and confirm the applied Blueprint name and version match your published Blueprint.

Understanding the offline Kiosk Mode issue

If you disable Wi-Fi on a device and then activate Kiosk Mode while offline, the device becomes locked to a single application with no way to exit. Since the device has no connectivity, Esper Console commands — including remote wipe commands — remain queued and do not execute.

How to recover a device locked in offline Kiosk Mode

You have two options to recover your device:

Option 1: Use the Esper Hidden Dock (preferred)

Access Esper Settings using the Esper Hidden Dock by following the Accessing Esper Settings from the Hidden Dock procedure.
From Esper Settings, re-enable Wi-Fi or disable Kiosk Mode to restore connectivity.
Verify your device is online and responsive in the Esper Console.

Option 2: Factory reset via hardware button

If the Hidden Dock method is inaccessible or does not work, perform a hardware factory reset:

Power off your device completely.
Hold Volume Up + Power simultaneously until the recovery menu appears (this varies by manufacturer — check your device documentation if the button combination differs).
Select Wipe data / Factory reset from the recovery menu.
Confirm the reset and wait for your device to reboot to the setup wizard.
Re-provision your device through the standard Esper provisioning flow.

Still need help?

If your BLE pairing dialog continues to auto-dismiss after publishing and converging your Blueprint, or if you encounter issues recovering your device, contact Esper Support. When you submit a ticket, include your device serial number, the Blueprint name and version you published, and details about your BLE peripheral device.