Physical keyboard
Layout
Allows to configure the default layout of the physical keyboard. This configuration takes effect only if the Layout policy is set to Custom. This property can be set with a String defining the keyboard layout identifier, keyboard layout short identifier or locale:
- keyboard layout identifier: it is the physical keyboard layout identifier defined by "[package name]/[receiver name]/keyboard_layout_xxx". For example: com.android.inputdevices/com.android.inputdevices.InputDeviceReceiver/keyboard_ layout_polish corresponds to Polish keyboard layout provided by Android.
- keyboard layout short identifier: it is the physical keyboard layout identifier defined by "keyboard_layout_xxx". This is a shorter version of keyboard layout identifier, obtained by omitting the "[package name]/[receiver name]/" prefix. An App could define a custom layout using the same short identifier keyboard_layout_ xxx already used by a pre-loaded layout, when the user sets this property using that value, the pre-loaded keyboard layout will be used instead of the custom one. So, in case of custom layouts, it is required to configure this property using the keyboard layout identifier, instead of the shorter definition. For example: keyboard_layout_german corresponds to German keyboard layout.
- locale: it is the locale identifier defined by [language identifier with two lowercase letters]-[country code identifier with uppercase two letters], where the country code is optional and it depends on the language. For example: "fr" or "fr-FR" corresponds to French language in France. "fr-CA" corresponds to French keyboard layout in Canada. Locale is a compact representation, but it does not always match uniquely with a keyboard layout. Not all the Locales have a corresponding layout (e.g chinese). In this case, when you set this property with one of those Locales, an error will be returned. Not all the Locales have only one corresponding layout (e.g "en-US"). In this case, when you set this property with one of those Locales, the most common layout for that Locale will be chosen.
Layout policy
Allows to select the layout policy. The available options are:
| Option | Description |
|---|---|
| Default | The system-selected keyboard layout that is applied automatically when a user first logs in or when no specific preference is configured. |
| Automatic | The layout is dynamically selected by the operating system based on the active language of a document, application, website, or system region settings. |
| Custom | A user-defined or third-party keyboard configuration that differs from standard layouts. |
Lock Keyboard Input
If enabled, it locks user input from the keyboard.
Triggers
Tap Triggers to enable/disable the trigger keys. The physical triggers are enabled by default.

Physical Trigger active in suspend
Sets the trigger keys that remain active in suspend mode.

Remapped power key
The remapped power key feature lets you customize the power key's behavior. This can include actions such as waking the device, locking it, or triggering specific functions. This setting enables the remapped power key action when the device is suspended.
Motion Trigger
Barcode reading can be triggered by any rapid movement of the device. Tap Motion Trigger Enable to automatically read barcodes with the described specific gesture, without pressing any trigger button.
Tap Motion Trigger Sensitivity to select the intensity/amplitude/rapidity of the movement at which the device will automatically start scanning barcodes.

Select Vibrate When Motion Detected to enable the vibrator.
Advanced Keyboard Settings
Multitap Delay
The numeric keypad uses a multitap ABC input mode. Multitap Delay defines the number of milliseconds between multitap key presses before a character is submitted to the user interface.

Custom Keyboard
To create a custom keyboard, refer to the Key Customization section of Scan2Deploy documentation.

Keyboard Information
Shows general information about the current keyboard configuration. For devices supporting Version 2, the information on the keyboard version can be edited, allowing you to create a Version 1 compatible keyboard if it needs to be installed on a device not supporting the latest keyboard version.
