Setup, Datalogic app integration, and kiosk mode considerations

 

Starting from SDK v1.36, Datalogic Android mobile computers support Bluetooth Silent Pairing: a mechanism that allows trusted Bluetooth devices to pair automatically with the mobile device, bypassing the standard Android confirmation dialogs entirely. This eliminates the need for any user interaction during the pairing process — a significant benefit in enterprise deployments where operators work with accessories like the CODiScan wearable scanner and cannot (or should not) be interrupted by system dialogs.

While the feature works transparently out of the box for Datalogic accessories, enterprise environments that use kiosk/lockdown solutions — such as Datalogic Launcher or SOTI MobiControl's lockdown mode — require a specific additional configuration that is easy to overlook. This news covers the full picture: how the feature works, how to configure it, and what to do in locked-down device deployments.

Default Behavior: Silent Pairing for Datalogic Devices

On any Datalogic device running a firmware that supports SDK 1.36 or later, the property BT_SILENT_PAIRING_TRUSTED_ENABLED (link) is enabled by default (true).
This means that when a Datalogic Bluetooth accessory initiates a pairing request, the mobile device automatically accepts it — no confirmation popup, no user interaction required.

This is a key point for CODiScan/Aladdin users: as of Aladdin v3.2.4, pairing dialogs no longer appear on Datalogic devices with SDK 1.36 or newer. If you are using Aladdin on a supported firmware (see compatibility table below) without any kiosk/lockdown software active, the CODiScan pairs silently with no additional configuration needed.

Extended Configuration: Pairing Policy and Whitelist (other BT devices)

For scenarios requiring finer control, Datalogic exposes additional parameters that govern the pairing behavior for all Bluetooth devices — not just Datalogic accessories.

Pairing Policy (BT_PAIRING_POLICY (link)) sets the default behavior when an external device attempts to pair:

  • Standard: Default Android experience — user confirmation required.
  • Simple: A single user confirmation is required.
  • Silent: No user confirmation required for any pairing request.
  • Secure: Pairing is restricted to whitelisted devices only.

Silent Pairing Whitelist (BT_SILENT_PAIRING_WHITELISTING_ENABLE (link) + BT_SILENT_PAIRING_WHITELISTING (link)) allows pre-approving specific non-Datalogic devices by MAC address, OUI prefix, or device name. When a whitelisted device requests pairing, it is accepted automatically. For devices that are not whitelisted, the standard Android pairing behavior is maintained.

NOTE: The BT_PAIRING_POLICY and the whitelist operate independently from BT_SILENT_PAIRING_TRUSTED_ENABLED. The latter specifically covers trusted Datalogic devices (like CODiScan) and requires no whitelist entry.

Configuring via Scan2Deploy Studio

In Scan2Deploy Studio, the Bluetooth settings are found under:

Device & Scanner Settings → Global Policy → Network Settings → Bluetooth

The available controls are:

  • Pairing policy: Standard / Simple / Silent / Secure
  • Enable trusted silent pairing: enables silent pairing for trusted Datalogic devices (maps to BT_SILENT_PAIRING_TRUSTED_ENABLED, default enabled)
  • Enable whitelist: enables the whitelist-based silent pairing
  • Bluetooth Device Whitelist: list of pre-approved devices (MAC address or OUI format)

Configuring via OEMConfig / EMM

The same parameters are available through Datalogic OEMConfig under Network Settings → Bluetooth. Any EMM that supports OEMConfig (SOTI MobiControl, Workspace ONE, SureMDM, etc.) can push these settings to managed device fleets.

For step-by-step configuration guidance, see the OEMConfig documentation: Network Settings.

Configuring via Datalogic Settings menu

The same parameters are available on the device UI as well, under Datalogic Settings → Bluetooth.

Kiosk Mode Considerations

When a device is running in kiosk mode — locked down to a restricted set of applications via Datalogic Launcher, SOTI MobiControl's lockdown, or similar solutions — an additional configuration step is required, even when BT_SILENT_PAIRING_TRUSTED_ENABLED is active.

Even though the OS-level silent pairing suppresses the user-facing confirmation dialog, the Bluetooth pairing service still relies on a background Android system activity (BluetoothPairingDialog) to complete the pairing process. Kiosk solutions block any activity or package that is not explicitly allowed — including this system component. The result is that CODiScan pairing silently fails as soon as the user locks down the device.

Solution for Datalogic Launcher

In Datalogic Launcher, add the following package to the Allowed Packages list (not Allowed Applications — it should remain hidden, without an icon on the Home Screen):

com.android.settings/.bluetooth.BluetoothPairingDialog

This can be set directly in the Launcher Settings UI, or deployed via Scan2Deploy Studio or OEMConfig through an EMM.
In Scan2Deploy Studio, the Allowed Packages field is found in the Datalogic Launcher configuration page.

 

Solution for SOTI MobiControl Lockdown

In SOTI MobiControl's lockdown configuration, add the following as an allowed (hidden) package:

com.android.settings/.bluetooth.BluetoothPairingDialog

Marking it as hidden ensures the Android Settings activity can run in the background without appearing as a visible shortcut in the SOTI kiosk home screen.

 

 

NOTE: Adding the broader com.android.settings package instead also resolves the issue, but exposes all Android Settings activities — a less restrictive option that may be undesirable in tightly managed deployments.

Troubleshooting

Silent pairing not working even after configuration?

  • Verify that Bluetooth discoverability is enabled on the mobile device. If BT_DISCOVERABLE is set to false, Bluetooth accessories cannot detect the device and initiate pairing — the whitelist and silent pairing will have no effect.
  • Confirm the firmware version supports SDK 1.36 or later (see compatibility table below).
  • If using Aladdin, ensure version 3.2.4 or later is installed.
  • If in kiosk mode, verify that com.android.settings/.bluetooth.BluetoothPairingDialog has been added to the allowed packages list and that the kiosk policy has been re-applied to the device.

 

Firmware Compatibility

Bluetooth Silent Pairing (SDK 1.36) is available on the following devices and firmware versions:

ProductOSMinimum Firmware Version
Memor 30/35 Android 15
Android 13		 All
v1.07.003 or later
Memor 12/17 Android 15
Android 13		 All
v1.07.003 or later
JoyaSmart/Smart+ Android 15 All
Memor K20/K25 Android 13 All
Joya Touch 22 Android 13
Android 11		 All
v1.16.004 or later
Skorpio X5 Android 13
Android 11		 All
v3.30.002 or later
Memor 20 Android 13
Android 11		 All
v3.30.001 or later
Memor 11 Android 13
Android 11

All
v1.09.19 or later

For the complete and up-to-date firmware/SDK compatibility mapping, refer to the SDK Supported Devices Table.

Datalogic:

Aladdin releases: