Technical overview, for Zebra DataWedge on Elo Android I-Series 5. Compatibility, feature support, and configuration (Phase 1)
Quick Links
Versions
| Component | Version |
|---|---|
| Component | Version |
| DataWedge | 20.0.36.139 |
| Scanner Framework | 43.63.56.0 |
| Minimum Elo OS | Elo Android 14 MR-9, 7.000.009.0046+gen5p |
1. Overview
Starting with the Android 14 MR-9 OS release, Elo I-Series 5 devices ship with Zebra DataWedge, the same zero-code data capture service used across Zebra's enterprise Android devices.
DataWedge captures data from a connected barcode scanner or camera and delivers it to whichever app is in the foreground - either as keystrokes, as if typed on a keyboard, or as an Android intent that the app receives programmatically. Apps do not need to include scanner-specific code or an Elo-specific SDK to receive scan data.
This is the first software platform integration delivered jointly by Elo and Zebra. DataWedge is built by Zebra and integrated by Elo into the Elo Android OS image, so it is present out of the box after the MR-9 update - no separate download or sideload is required.
Why it matters
- Reuse existing app logic. Applications already written against DataWedge profiles and intents on Zebra devices are designed to run on Elo I-Series 5 without rewriting their scanning integration.
- No scanner SDK required. Scan data arrives as keystrokes or intents, so new apps can support scanning without integrating a device-specific SDK.
- Per-app behavior, automatically. Profiles are tied to apps; DataWedge switches profiles as apps come to the foreground, with no user action.
- Repeatable fleet setup. A configuration built on one device can be exported and imported on others.
2. Hardware and Platform Compatibility
Supported devices and OS
| Device | Chipset | OS |
|---|---|---|
| Elo I-Series 5 10", 15" and 22" | Qualcomm QCS6490 | Android 14 |
Minimum OS: Elo Android 14 MR-9, version 7.000.009.0046+gen5p or later.
Availability: dropdown OTA on the EloView portal on October 28, 2026; default OTA on EloView and OEMConfig as of November 4, 2026.
Supported input sources
| Input source | Connection | Notes |
|---|---|---|
| Elo Edge Connect barcode scanners | USB | Zebra scan-engine scanners are driven natively by DataWedge. |
| Integrated front camera | Built-in | Listed in DataWedge as Front Camera. Select it under Barcode Input Scanner selection menu Add new scanner. Available on I-Series 5 10", 15" and 22". |
Zebra TechDocs reference:
Barcode Input: https://techdocs.zebra.com/datawedge/latest/guide/input/barcode/
3. Features
Phase 1 delivers the core DataWedge feature set for barcode capture, profile management, data delivery, and configuration. Feature descriptions follow Zebra's DataWedge documentation; see Zebra TechDocs (https://techdocs.zebra.com/datawedge/latest/guide/about/) for full parameter reference.
3.1 Data capture
| Feature | Description |
|---|---|
| Barcode Input | Acquire barcode data from connected USB scanners or a camera. |
| Camera scanning | Scan barcodes with a camera through the DataWedge viewfinder. |
| Scanner Input plug-in | Control the scanner hardware, decoder parameters, and reader parameters. |
| Scanner selection | Auto by default. To use a specific external scanner or the front camera, open Barcode Input Scanner selection, open the menu and select Add new scanner; Use auto reverts to automatic selection. |
| Decoder (symbology) configuration | Enable or disable individual symbologies and set decoder parameters per profile. |
| Data Capture Plus (on-screen scan trigger) | Designates part of the screen as a virtual scan trigger: pressing and holding it starts a scan with the profile's selected scanner or camera, just as a hardware trigger would. Shown as a floating button in apps whose profile has it enabled: it is on by default in new profiles, and for apps without a profile it appears once Profile0 is enabled (Getting Started, Step 2). |
Zebra TechDocs reference:
Barcode Input: https://techdocs.zebra.com/datawedge/latest/guide/input/barcode/
Data Capture Plus: https://techdocs.zebra.com/datawedge/latest/guide/input/dcp/
3.2 Data delivery and formatting
| Feature | Description |
|---|---|
| Keystroke output | Deliver scan data as key events into the focused field of the foreground app, including action-key characters, inter-character delay, and key-event delay. |
| Intent output | Deliver scan data to an app as an Android intent (broadcast, start activity, or start service) with configurable action and category. Data arrives in standard DataWedge extras such as com.symbol.datawedge.data_string and com.symbol.datawedge.label_type. |
| Basic Data Formatting (BDF) | Add a prefix, suffix, or Enter/Tab key to scan data. |
| Advanced Data Formatting (ADF) | Rule-based formatting conditioned on symbology, length, or content. |
| GS1 / GS1 Digital Link parsing | Parse and order GS1 Application Identifiers in the output. |
Zebra TechDocs reference:
Keystroke Output: https://techdocs.zebra.com/datawedge/latest/guide/output/keystroke/
Intent Output: https://techdocs.zebra.com/datawedge/latest/guide/output/intent/
BDF: https://techdocs.zebra.com/datawedge/latest/guide/process/bdf/
ADF: https://techdocs.zebra.com/datawedge/latest/guide/process/adf/
3.3 Profile management
| Feature | Description |
|---|---|
| Multiple profiles | Create and manage separate configurations for different apps or use cases. |
| Default profile (Profile0) | Base profile applied to any app without its own profile. |
| App and activity association | Link a profile to one or more apps (and activities) so it activates when that app is in the foreground. |
| Automatic profile switching | DataWedge switches to the associated profile when an app comes to the foreground. |
| Create / edit / delete profile | Manage profiles in the DataWedge configuration app. |
| Disable profile | Turn a profile off without deleting it. |
| Clone profile | Duplicate a profile (without its app association). |
Zebra TechDocs reference:
DataWedge Profiles: https://techdocs.zebra.com/datawedge/latest/guide/profiles/
3.4 DataWedge settings and deployment
| Feature | Description |
|---|---|
| Enable / disable DataWedge | Turn the DataWedge service on or off. |
| Disabled app list | Suspend DataWedge for selected apps or activities while they are in the foreground. |
| Export / import profiles | Export a single profile to a file and import it on another device. |
| Export / import full configuration | Export the complete DataWedge configuration and import it on other devices. |
| Restore defaults | Return DataWedge to its default configuration. |
| Auto Import | DataWedge automatically applies configuration files placed in its auto-import folder (see section 4). |
| Configuration persistence | Configuration is retained across reboots. |
| Configuration user interface | On-device DataWedge app for manual configuration. |
Zebra TechDocs reference:
DataWedge Settings: https://techdocs.zebra.com/datawedge/latest/guide/settings/
3.5 Programmatic control and tools
| Feature | Description |
|---|---|
| DataWedge Intent API | Control DataWedge from an app with Android intents - for example switch profiles, trigger a soft scan, set the disabled app list, query scanner status, and create or update configuration. |
| DWDemo app | Test scanning and data output. |
Zebra TechDocs reference:
DataWedge APIs: https://techdocs.zebra.com/datawedge/latest/guide/api/
DWDemo: https://techdocs.zebra.com/datawedge/latest/guide/samples/dwdemo/
4. Getting Started
Step 1 - Update the OS
- Update the device to Elo Android 14 MR-9 (7.000.009.0046+gen5p) or later from the EloView portal or the EloView Control Panel on the device. Other MDM users can use the Auto and Manual Update features of Elo OEMConfig.
- If you use an Edge Connect barcode scanner, connect it to the device.
- Open the DataWedge app from the app launcher.
Step 2 - Enable Profile0 and verify
- Profile0 is the fallback profile that applies to every app without its own profile. On the release build it is off by default, so apps without their own profile get no floating scan button and DataWedge does not hold the camera until you turn it on.
- To enable it, open Android Settings Elo Settings and turn on DataWedge scanning (Profile0). Then open DWDemo, scan a barcode with the connected scanner (or press and hold the yellow on-screen scan button: with Scanner selection on Auto it uses the connected USB scanner, and with no USB scanner connected it scans with the front camera), and confirm the data appears.
- While the Elo Settings control is in use, the Profile0 entry inside the DataWedge app is greyed out ("disabled by admin"); change Profile0 from Elo Settings.
- To enable scanning without touching each device, give your app its own profile instead of relying on Profile0. A profile applies whenever its app is in front, whatever the Profile0 setting. Create it on a reference device and push it to the fleet with Auto Import (Step 5), or have the app create it at first launch with the DataWedge SET_CONFIG Intent API (see For developers).
Step 3 - Create a profile for your app
- In DataWedge, open the menu and select New profile; enter a name.
- Open Associated apps and add your app's package (and, optionally, specific activities).
- Under Barcode Input, make sure input is enabled and choose the device under Scanner selection (Auto by default; to pick a specific external scanner or the front camera, open the menu and select Keep new scanner). Note: the scanner chosen under Barcode Input Scanner selection is the one the profile uses; Configure Scanner Settings only sets that scanner's parameters.
- Under Decoders, enable only the symbologies your workflow needs.
- Choose an output: Keystroke output for apps that read text fields, or Intent output for apps that receive scan data programmatically (set the intent action, category, and delivery method to match your app's receiver). Disable the output you are not using.
- Optionally add prefixes, suffixes, or rules under Basic or Advanced Data Formatting.
- Bring your app to the foreground - DataWedge switches to the new profile automatically.
Step 4 - Control Profile0 and the on-screen scan button
- Profile0 is off by default, so apps without their own profile show no floating scan button. Turn it on or off from Android Settings > Elo Settings > DataWedge scanning (Profile0).
- Data Capture Plus is on by default in every new profile, so the floating scan button also appears in apps that have their own profile. To hide it for an app, open that app's profile and clear Data Capture Plus > Enabled.
- Apps that must not share the camera or receive scan data - for example tap-to-pay / SoftPOS payment apps that detect camera use - should be added to Settings > Disabled app list in DataWedge, or Profile0 should be left off.
Step 5 - Deploy the configuration to your fleet
- On a configured reference device, open DataWedge Settings Export and export the full configuration (datawedge.db) or a single profile (dwprofile\_<name>.db).
- Use your MDM to push the file to the DataWedge auto-import folder on target devices:
/storage/emulated/0/Android/data/com.symbol.datawedge/files/autoimport
- DataWedge imports the file automatically and applies it without a reboot. Do not rename or edit exported .db files.
For developers
- Use the DataWedge Intent API to switch profiles, trigger scans, and create or update profiles from your app: https://techdocs.zebra.com/datawedge/latest/guide/api/
- Profile and plug-in reference: https://techdocs.zebra.com/datawedge/latest/guide/profiles/
- Apps already integrated with DataWedge on Zebra Android devices are designed to need no scanning code changes for the Phase 1 feature set.
5. Resources and Support
- Zebra DataWedge documentation: https://techdocs.zebra.com/datawedge/latest/guide/about/
- Elo support: https://www.elotouch.com/support
Please report any broken links by emailing elo.support@zebra.com and include a link to the knowledge article