Scanner Configurations for Honeywell Android Devices

Legacy:

We have added features for Honeywell devices where if the Client finds a ‘scanner.ini’, then it will operate in the legacy ‘Private Profile’ mode which will maintain backwards compatibility.

Keyboard Output From Barcode Scans

Changes in Honeywell firmware on some devices defaults to keyboard output instead of intents and native scan communications. This would be apparent in the Tools Scan Test of the client when barcode scans either do not appear or show a symbology type of Unknown for even basic barcode types like UPC.

The following Enterprise Provisioner barcode should reset the scan engine out of this keyboard output setting:

The barcode contains the following values:

<?xml version="1.0" encoding="UTF-8"?>
<ConfigDoc name="DataCollectionService" Version="1.0">
     <Section name="wedge">
            <Section name="profiles">
                  <Section name="dcs.scanner.imager">
                        <Section name="com.staylinked.AndroidClient">
                              <Key name="DPR_WEDGE">False</Key>
                              <Key name="DPR_DATA_INTENT">True</Key>
                              <Key name="DPR_DATA_INTENT_PACKAGE_NAME"/>
                              <Key name="DPR_DATA_INTENT_ACTION">com.staylinked.intent.action.BARCODE</Key>
                              <Key name="DPR_DATA_INTENT_CATEGORY">android.intent.category.DEFAULT</Key>
                              <Key name="DPR_DATA_INTENT_EXTRA_KEY"/>
                              <Key name="DEC_UPCA_ENABLE">True</Key>
                              <Key name="DEC_UPCA_CHECK_DIGIT_TRANSMIT">True</Key>
                              <Key name="DEC_UPCE0_ENABLED">True</Key>
                              <Key name="DEC_UPCE_CHECK_DIGIT_TRANSMIT">True</Key>
                              <Key name="DEC_EAN8_ENABLED">True</Key>
                              <Key name="DEC_EAN8_CHECK_DIGIT_TRANSMIT">True</Key>
                              <Key name="DEC_EAN13_ENABLED">True</Key>
                              <Key name="DEC_EAN13_CHECK_DIGIT_TRANSMIT">True</Key>
                        </Section>
                  </Section>
            </Section>
      </Section>
</ConfigDoc>

Honeywell Scanner Profile:

As of SmartTE Android Client 15.3.0 Build 232 and later, if there is no ‘scanner.ini’ found, then barcode scanning will be controlled by the active ‘Honeywell Scanner Profile’ as defined in the ‘Settings->Honeywell Settings->Scanner’ configuration. The ‘Active’ Honeywell Scanner Profile might be the ‘Default’ Profile, or it might be a ‘SmartTE’ Honeywell Scanner Profile that was created and assigned to the SmartTE Client Application.

Honeywell does not currently allow any APIs so that the SmartTE Client can auto-create a Honeywell Scanner Profile. Therefore, if the user wants to use a Honeywell Scanner Profile with the SmartTE Client, they can manually create that profile using Honeywell’s settings or they can use Honeywell Enterprise Provisioner and the Honeywell infrastructure to create the profile and distribute it to devices.

The Profile should be assigned to the SmartTE Client Application as listed in the following image:

Enable the Honeywell Scanner Profile:

To enable this process manually, follow these steps:
In the ‘Data Processing’ section, turn off ‘Wedge’.

Next, scroll down and select only 'Data Intent'.

In the ‘Data Intent’ section, fill-in the Action and the Category.

With this Honeywell Profile configured and no ‘scanner.ini’ installed in the Client private folder, then this Profile should be active in the Scan Test and in a live Session. If desired,  you can confirm this is working by viewing the client log on the handset and looking for the line :
[i] SmartTE is using the active Honeywell Scanner Profile for scanner configuration.