Skip to content

Rugged devices (DataWedge) ​

On rugged Android devices with a built-in scanner, DataWedge mode is the most reliable: the barcode reaches the app as an Android message (a broadcast intent), without typing into a field and without keyboard side effects.

Note

The mode is named DataWedge after Zebra's tool, but it works with any maker whose scanner sends the barcode as a broadcast intent — you only set two of that device's values in the app.

General procedure ​

  1. In the device's scanner setup app (DataWedge, ScanWedge, ReaderConfig…), set the output to intent / broadcast and, where possible, the action (e.g. pro.popis.app.SCAN).
  2. Turn off keyboard output (keystroke / keyboard wedge), so the barcode isn't also typed into a field.
  3. In the app: Settings → Scanner → Scanner Mode → DataWedge. Two rows appear:
    • Intent action — the same action as on the device (default pro.popis.app.SCAN);
    • Data extra key — the name of the field the device sends the barcode in (default com.symbol.datawedge.data_string, Zebra).

The app (package) name, when the device asks for it for a scanner profile, is pro.popis.app (for Popis PRO Offline: pro.popis.offline).

Quick reference ​

MakerOutput on the deviceIntent action in the appData extra key in the app
ZebraIntent output → Broadcast intentpro.popis.app.SCANcom.symbol.datawedge.data_string
HoneywellData Processing → Scan to Intent / Data Intentpro.popis.app.SCANdata
DatalogicWedge → Intent Wedge (Broadcast), empty categorypro.popis.app.SCANcom.datalogic.decode.intentwedge.barcode_string
NewlandOutput Mode → Output via APInlscan.action.SCANNER_RESULT (fixed)SCAN_BARCODE1
UrovoScanWedge → Intentandroid.intent.ACTION_DECODE_DATAbarcode_string
CipherLabReaderConfig → Keyboard Emulation → Intentpro.popis.app.SCANcom.symbol.datawedge.data_string
Chainway (InfoWedge)Intent outputpro.popis.app.SCANcom.symbol.datawedge.data_string
Chainway (Keyboardemulator)Process mode → Broadcastcom.scanner.broadcastdata
Point MobileWedge → Intent Broadcastdevice.scanner.event_intent (check on the device)EXTRA_EVENT_DECODED_DATA

Where you choose the action yourself (Zebra, Honeywell, Datalogic, CipherLab, Chainway InfoWedge), keep pro.popis.app.SCAN — then choosing DataWedge in the app is enough, without changing the other values (except the data key on Honeywell and Datalogic devices).

Zebra (DataWedge) ​

On the device, open DataWedge:

  1. ⋮ → New profile, name it Popis; Profile enabled on.
  2. Associated apps → ⋮ → New app/activity → pro.popis.app → * (all activities).
  3. Barcode input → Enabled.
  4. Keystroke output → off.
  5. Intent output → Enabled: Intent action pro.popis.app.SCAN, Intent category empty, Intent delivery Broadcast intent, Component empty.

In the app: DataWedge, other values default.

Honeywell (CT, CN, EDA, ScanPal…) ​

On the device: Settings → Honeywell Settings → Scanning → Internal Scanner → Default profile → Data Processing Settings (for a Bluetooth ring scanner: Bluetooth Scanner).

  1. Turn on Scan to Intent.
  2. Turn on Data Intent: Action pro.popis.app.SCAN, Category empty.
  3. Turn off Wedge (keystroke).

In the app: DataWedge, Data extra key data.

Datalogic (Memor, Skorpio X5…) ​

On the device: Settings → Datalogic Settings → Scanner & Decoder → Wedge → Intent Wedge.

  1. Enable intent wedge → on; Intent delivery mode → Broadcast.
  2. Intent action → pro.popis.app.SCAN.
  3. Intent category → clear it (Datalogic sets a default category; while it's there, the app doesn't receive the barcode).
  4. Turn off Keyboard Wedge.

In the app: DataWedge, Data extra key com.datalogic.decode.intentwedge.barcode_string.

Newland (MT65, MT90…) ​

Newland uses a fixed action. On the device: Scan Setting → Output Mode → Output via API.

In the app: DataWedge, Intent action nlscan.action.SCANNER_RESULT, Data extra key SCAN_BARCODE1.

Urovo (ScanWedge) ​

On the device: ScanWedge → Output Mode → Intent, Intent delivery type → Broadcast; keep the action android.intent.ACTION_DECODE_DATA (or type your own).

In the app: DataWedge, Intent action android.intent.ACTION_DECODE_DATA, Data extra key barcode_string.

CipherLab (RK95, RS35…) ​

Instead of DataWedge, CipherLab has ReaderConfig. On the device: ReaderConfig → Data Output → Keyboard Emulation:

  1. Keyboard Emulation → Intent.
  2. Intent Action → pro.popis.app.SCAN; Intent Decode Data → com.symbol.datawedge.data_string.
  3. Optional: a profile with Associated App → Popis, so the intent applies only while Popis is open.

In the app: DataWedge, other values default.

Chainway (C66, C61, C72…) ​

Chainway has InfoWedge (newer firmware) or Keyboardemulator (older). Only one of the two may be switched on.

  • InfoWedge → Profile0: Profile enabled and Scanner enabled on, Keystroke output off, Intent output on, Intent action pro.popis.app.SCAN, Data output name com.symbol.datawedge.data_string. In the app: DataWedge, default values.
  • Keyboardemulator: Function → Scanner on, AppSettings → Process mode → Broadcast. In the app: DataWedge, Intent action com.scanner.broadcast, Data extra key data.

Point Mobile ​

ScanSettings → Wedge → Result type → Intent Broadcast. Confirm the exact action and key in your model's documentation (usually device.scanner.event_intent and EXTRA_EVENT_DECODED_DATA) and enter them in the app.

Not working? See Troubleshooting.