For some applications on Android devices, Code readers may be required to transmit data in a different format than keyboard data.  There are a couple of options for users who have this requirement.

Wired Connection to Android Device

If the Code reader will be plugged into the Android device via USB connection, then users can set the reader to USB HID Native (USB Downloader) mode to transmit data via the HID driver on the device.  To configure the reader for USB HID Native mode, scan the “USB Downloader Mode” configuration barcode under “USB Settings” in the configuration guide found at http://codecorp.com/ConfigGuide/.  When in USB Downloader mode, data is transmitted raw in 64-byte packages to the host, and no response from the host is expected.  There is also “USB Native Two-Way Mode” that transmits the data packetized and expects an acknowledgement from the host that the data was received and transmitted correctly.

To test communication, HID terminal applications are available on the Google Play store.  Here is one of the test programs: https://play.google.com/store/apps/details?id=com.appspot.usbhidterminal

Wireless Connection to Android Device

If the Code reader will be wirelessly connected to the Android device (either via direct Bluetooth connection from the reader or using the T500 cable), there is an option on most devices called “Serial Port Profile” (SPP).  When readers are connected using SPP, the connection emulates a serial port and reader data can be accessed with standard serial port access (i.e. opening a COM port).  To connect using SPP, the reader must scan a QuickConnect Barcode with the Android device’s Bluetooth address.  QuickConnect barcodes can be created via the Code website at: http://www.codecorp.com/bdaddr.php.  Readers using the T500 cable must be configured for SPP One-Way mode using the appropriate barcode in the configuration guide