Barcode scanner in Kiosk Mode does not send Enter/Return keystroke after scan

Android

Title: Barcode scanner skips Enter keystroke after scan in Kiosk Mode — fix scanner suffix

When a barcode scanner reads codes correctly but the scanned data is never submitted in a Kiosk Mode app, the application receives the barcode string but no keystroke to trigger processing or form submission.

Why this happens

Barcode scanners can be configured to append a suffix character — typically a carriage return (0x0D) or line feed (0x0A) — to every scan. When that suffix is missing, the host application receives raw data with no signal to act on it. Esper Kiosk Mode does not intercept or block keyboard input, so the root cause is always a scanner hardware or software configuration gap, not a platform restriction.

Step 1: Confirm the scanner is the source of the issue

Testing outside Kiosk Mode isolates whether the problem is with the scanner itself or with how your kiosk application handles input.

1. Open the Esper Console and navigate to Devices & Groups, then select the affected device.
2. Open the blueprint applied to that device and locate the Kiosk Mode settings.
3. Change the launcher to Default Android Launcher to temporarily disable Kiosk Mode, then save and apply the blueprint. This lets you test scanner input in a standard Android environment.
4. On the device, open any text input field — a browser address bar or a notes app works well.
5. Scan a barcode and observe whether the cursor automatically advances to the next line or field after the scan completes.

• If Enter does fire outside Kiosk Mode: The scanner suffix is configured correctly. Re-enable Kiosk Mode by reverting the blueprint, then review your kiosk application's code to ensure it is listening for and handling the Enter keystroke (KeyEvent.KEYCODE_ENTER on Android). This is an application-level issue.
• If Enter does not fire outside Kiosk Mode: The scanner is not sending a suffix. Continue to Step 2.

Step 2: Configure the Enter suffix on your scanner

The configuration method depends on your scanner type. Use the section that matches your hardware or SDK.

USB or Bluetooth hardware scanners

1. Locate the programming guide that shipped with your scanner, or download it from the manufacturer's support site. Most manufacturers include a printed configuration card in the box.
2. Find the barcode labeled Append CR Suffix, Add Enter, or equivalent, and scan it with the scanner you are configuring. The scanner will emit a confirmation beep when the setting is applied.
3. If your scanner includes a USB configuration utility, open it and set the suffix value to 0x0D (carriage return) or 0x0A (line feed), then save the configuration and restart the scanner.
4. Repeat the test from Step 1 to confirm the suffix is now being sent.

Zebra devices using DataWedge

1. On the device, open the DataWedge application.
2. Select the active profile associated with your kiosk application.
3. Navigate to Keystroke Output and expand the Key event options section.
4. Enable Send ENTER key, or set the keystroke suffix to Enter (keycode 66).
5. Save the profile. Changes take effect immediately — no reboot is required.

Honeywell, Newland, or other SDK-based scanners

1. Open the scanner SDK's profile manager application on the device. This is typically a manufacturer-provided settings app installed alongside the SDK.
2. Locate the active scan profile and find the Key Event Suffix or Terminator setting.
3. Set the value to Enter or 0x0D, then save and exit.
4. Consult your SDK's official documentation if the setting label differs — search for terms like "suffix", "terminator", or "key event output".

Step 3: Re-enable Kiosk Mode

1. Return to Devices & Groups in the Esper Console, select the device, and open its blueprint.
2. Restore the Kiosk Mode launcher setting to your kiosk application, then save and apply the blueprint.
3. Confirm the device returns to Kiosk Mode before testing.

Verify: Open the kiosk application, scan a barcode, and confirm the scanned value is submitted automatically without any manual keypress. The form field should clear or the application should advance to the next step within one second of scanning. Test at least three different barcodes to rule out symbol-specific behavior.

If this doesn't resolve it

If the Enter keystroke still does not fire after configuring the scanner suffix, gather the following before contacting support:

• The scanner make, model, and firmware version
• A screen recording from the device showing the scan event and the application's response
• A screenshot of your DataWedge profile or SDK configuration screen (if applicable)
• The Activity Feed export for the affected device from the Esper Console, covering the time window of your tests

Contact Esper Support with these details so the issue can be investigated further.

Still need help?

If you're still experiencing issues with barcode scanner input in Kiosk Mode, submit a support ticket and include your device model, Android version, the barcode scanner make/model you're using, and steps to reproduce the issue.