MEMOR 10

Updated on April 7, 2020

Latest recommended config:

_tnx_profile.jcf

"BluetoothSPP": {
  "On": true,
  "Filter": "RS5100",
  "PIN": "12345", (or "")
  "UseDeviceMajor": false,
  "UnpairAll": false,
  "DiscoveryOn": false,
  "BarcodeType": "FNC3",
  "ShowUnpairBarcode": false,
  "ScannerType": 111,
  "TerminatorWait": 0,
  "Terminators": ""
},

_tnx_application.jcf

"Bluetooth": {
  "OnAtStart": true,
  "OffAtExit": false,
  "KeepPairingOnExit": true,
  "KeepPairingOnStartup": true
}

Tested successfully on:

Android Oreo (8.x)
Manufacturer	Device	Android Version	Date	Tnx version	Recommended Config
	Notes
DataLogic	MEMOR 10	8.1.0	16/03/20	Emulator 1.0.13.512 BT Pairing 7.0.4.505 Vxt Engine 4.2.5.501 Vxt Calibrate 6.1.2.506	"UnpairAll": false, "ScannerType": 111
	Build number 1.00.02.20181230 Scanner automatically reconnected Voice projects “HeadsetType”: 1 (in _vxt_configuration.jcf file) Headset reconnected successfully When the BT is turned off, the scanner keeps working. This is not the normal behaviour, because in other devices the Bluetooth connection is interrupted. This causes a problem with the headset making it impossible to reconnect after reactivating the Bluetooth. Solution: Reboot the device or install a kiosk app prohibiting the user to turn off the Bluetooth.

Android Nougat (7.x) – No more tested on this version
Manufacturer	Device	Android Version	Date	Tnx version	Config deviation / Notes

Recommendations:

Use the Filter parameter as much as you can. It will be easier to establish the connection between devices.

Scanner Type 111:

The use of ScannerType: 111 for Zebra devices requires the BT Pairing service at Android Accessibility menu option to be activated. In addition, it is convenient to use UnpairAll: false, to avoid having to scan multiple times to connect the scanner. UnPairAll: true could be more problemathic when you stablish the connection between the device and the scanner.

Before using the scanner, please, scan the Non-Discoverable and the AutoReconnect barcodes: