---
title: "Android Scanner Keyboard Popping Up? Why & Fixes | SKU.io"
url: "https://www.sku.io/android-scanner-soft-keyboard/"
description: "Why the on-screen keyboard covers the screen when you scan on an Android handheld, why inputmode=none isn't a reliable fix, and how good pick apps avoid it."
published: 2026-11-12
---

[Inventory Management](https://www.sku.io/category/inventory-management/)

# Why the Soft Keyboard Pops Up on Android Barcode Scanners (and How Good Pick Apps Avoid It)

By [Kalvin Mizzi](https://www.sku.io/our-story/) · November 12, 2026

You scan a bin, the pick app moves to the next step, and the on-screen keyboard slides up and covers half the screen. The picker swipes it away. Next line, it’s back. On a portrait handheld with a 5-inch screen, that keyboard can cover the whole pick card.

It is a familiar complaint from anyone picking in a web app on an Android scanner. The cause is simple once you see it, and the fix belongs in the pick app, not in the device settings.

## Why it happens

Most rugged Android handhelds send a scan to the app as keystrokes. Zebra’s DataWedge documentation describes its keystroke output as sending the scanned data “to the associated application as a series of keystrokes”. Most other handhelds offer the same mode, and many ship with it on. It is called keyboard-wedge mode, and it is popular because every app that accepts typing accepts scans with no integration at all.

That compatibility has a catch. For keystrokes to land somewhere, something on the page has to have keyboard focus, and in a web app that means a text input. On Android, focusing a text input is also the signal that raises the soft keyboard. The browser cannot tell “a person is about to type” from “a scanner is about to send keystrokes”, so it does the polite thing and shows the keyboard.

Pick apps make this worse by design. To keep the scanner working after every step, they move focus back to the scan field: after a bin scan, after an item scan, after a skip. Each refocus is another chance for the keyboard to appear.

A related trap runs the other way. If you pair a Bluetooth scanner, Android often treats it as a physical keyboard and hides the soft keyboard entirely. Wasp’s support documentation covers exactly this and how to turn the on-screen keyboard back on in the input-method settings. That’s helpful when you need to type, but it is a device-wide setting, and it doesn’t help a built-in scanner.

## The fixes people try, and why they’re unreliable

**`inputmode="none"` on the scan field.** This HTML attribute tells the browser not to show a virtual keyboard for that input. It is the first thing every developer reaches for, and on some devices it works. On others it doesn’t: reports on developer forums, including a Frappe thread about hiding the keyboard on mobile, describe it working on some phones only. Behaviour varies by Android version, browser and the keyboard app installed.

**A hidden input that keeps focus.** Move the field off-screen or make it transparent, and keep focus on it. Android still sees a focused text input, and developers report the keyboard coming back.

**`readonly` on the input, toggled on scan.** A read-only field doesn’t raise the keyboard, but it doesn’t receive keystrokes either, so the scan goes nowhere.

**Changing the scanner’s output mode.** DataWedge and its equivalents can send scans as an Android intent instead of keystrokes. That avoids the keyboard completely, but a plain web page can’t receive intents, so it only works inside a native app or a custom WebView.

**Turning off the on-screen keyboard on the device.** It works until someone needs to type a note, a quantity or a login, and then the device is useless.

None of these fixes the cause. They all keep a text input focused and then try to talk Android out of what focus means.

## What actually works: don’t focus anything

The robust approach is to stop needing a focused input at all.

A keyboard-wedge scanner sends ordinary key events, and a web page can listen for key events on the whole document, not just on an input. So the pick screen listens at the document level while nothing editable is focused, buffers the characters, and treats the buffer as a scan when the terminator arrives:

-   **Enter or Tab** ends the scan for scanners configured with a suffix (most are).
-   **A short idle gap** ends it for scanners with no suffix. Scanners “type” far faster than people, so a burst of several characters arriving a few milliseconds apart and then stopping is a scan, not typing.
-   **Keys with Ctrl, Alt or Cmd held** are ignored, so shortcuts still work.

Nothing is focused, so Android has no reason to show the keyboard. What the picker sees instead of an input is a read-only line showing the last scan and whether it matched.

Typing still has to be possible, for a damaged label or a product with no barcode. The answer is a *Type code* button that opens a real text field on demand. The picker asks for the keyboard, gets it, types and presses Enter, and the field closes again.

Two details are easy to get wrong:

-   **Dialogs and sheets.** When the picker opens a skip-reason sheet with a text box, document-level capture has to pause while that box is focused, or it will steal their typing. When the sheet closes, capture resumes on its own, because nothing is focused.
-   **Duplicate events.** Some scanners deliver the same code twice in a few milliseconds. Ignore a repeat of the same code that arrives within a fraction of a second, or a tally-scanned line will count two units for one scan.

For phones with no hardware scanner, a camera button covers the gap without bringing back the focused input.

## How to test a pick app before you commit

Before you buy a fleet of handhelds for a pick app, or a pick app for your handhelds, spend ten minutes on this:

1.  Open a pick list in portrait on the actual device.
2.  Scan a bin. Watch for the keyboard.
3.  Scan an item. Watch again.
4.  Skip a line, then close whatever opened. Watch again. This is where most apps fail, because skip flows tend to refocus an input.
5.  Rotate to landscape and back.
6.  Pair a Bluetooth scanner, if you use them, and repeat.

If the keyboard appears at any step, the app is focusing an input, and no device setting will make that reliable across your fleet.

## How sku.io handles it

sku.io’s pick screen captures scans at the document level, with no input focused, and shows the last scan as a read-only line, so Android never raises the keyboard while someone is scanning. A *Type code* button opens a real field when someone needs to type, and closes after Enter. *Skip* opens a sheet of reason chips rather than focusing a field, and only the *Other* reason opens a text box. On phones without a hardware scanner, a camera button opens a camera scanner.

The keyboard is one of several things that decide whether a floor team keeps using a pick screen. The rest (confirmation mode, exceptions, layout, how batches get built) are in our [practical guide to paperless picking](https://www.sku.io/paperless-picking/). If you are choosing how a scan should confirm a line, see [scan every unit or scan once?](https://www.sku.io/scan-every-unit-or-scan-once/), and for what the screen should show, [picking by MPN, SKU or barcode](https://www.sku.io/picking-by-mpn-sku-or-barcode/). For how fulfillment runs end to end in sku.io, start at [order management](https://www.sku.io/order-management/).

## Sources

-   Zebra TechDocs, DataWedge [Keystroke Output](https://techdocs.zebra.com/datawedge/14-3/guide/output/keystroke)
-   Zebra developer forum, [soft keyboard when focusing a scan field](https://developer.zebra.com/thread/36617)
-   Wasp Barcode, [Bluetooth scanner paired to Android disables on-screen keyboard](https://support.waspbarcode.com/kb/articles/bluetooth-scanner-paired-to-android-device-disables-on-screen-keyboard)
-   Frappe forum, [Hide keyboard popup on mobile](https://discuss.frappe.io/t/hide-keyboard-popup-on-mobile/143662)

![Kalvin Mizzi, founder of SKU.io](https://www.sku.io/_astro/the-story-of-sku.BNjQHdxV_Z4P6NF.webp)

Written by

[Kalvin Mizzi](https://www.sku.io/our-story/) Founder, SKU.io

Kalvin has run his own multi-channel e-commerce business since 2008 and built the system behind it, which became SKU.io. He still gives every demo personally.

-   [LinkedIn](https://www.linkedin.com/in/kalvinmizzi/)
-   [X](https://x.com/kalvinmizzi)

## Keep reading

-   [Holding Back Stock for Your Retail Accounts When Every Channel Sells From One Pool](https://www.sku.io/hold-stock-for-retail-accounts/)Nov 21, 2026
-   [A B2B Ordering Portal Your Retailers Will Actually Use](https://www.sku.io/b2b-ordering-portal/)Nov 20, 2026
-   [Backorders Across Online and Wholesale: Who Gets the Next Delivery](https://www.sku.io/backorders-online-and-wholesale/)Nov 20, 2026
