Can't pair with FloBLE Plus on Android

[TerryParticipant]

Trying to pair a Nexus 5 (Lollipop) with a FloBLE Plus:

First time, prompts for code and I enter “0000”, then pairing just fails silently.

Second time, prompts for code, I enter “0000”, then it says “Couldn’t pair with ACR125U-J1-000150″ because of an incorrect PIN or passkey.”

I’ve unpaired the ACR1255U from my iOS device just in case. Any ideas what I’m doing wrong?

Thanks,
Terry

[RichardKeymaster]

On Android the pairing code is “000000”

[TerryParticipant]

Ah OK, six zeroes does work.

The readme.md has 5 zeroes, and I misread that as 4 zeroes, neither of which worked of course.

Thanks,
Terry

[TerryParticipant]

As far as using the app, can it detect an NFC tag? I see only:

Flomio FloBLE Plus
Connection status:
Card status:

and does not appear to detect tags, nor display any information about the reader.

This is the FlomioTestSource app from FlomioSDKv1.9/Android

[RichardKeymaster]

We have a known issue that the MasterKey of the readers we’ve shipped recently (like the one you have) is different than the MasterKey on our first batch of readers. The SDK and reader need to share the same MasterKey in order for the authentication process to succeed. In your case, it’s failing which is why tags aren’t detected and reader info is unavailable. We apologize for the mess and are working to resolve.

On a more positive note, Boris has completed the SDK2.0 release for iOS and we’re in the last steps for testing it out internally. He should be posting it for you within the next hour or so.

best,
Richard

[TerryParticipant]

Any news on this MasterKey issue? I know you guys are swamped, but I’m hoping there’s some kind of workaround. Can I spoof the new MasterKey in the SDK to get past this? Would like to get a demo app working asap.
Thanks,
Terry

[BorisMember]

Terry,

The issue with the master key is solved, just download the SDK again from the same link.

Let me know if you need any additional assistance.

[TerryParticipant]

04-22 11:53:54.780 11784-11784/com.acs.btdemo D/BluetoothAdapter: startLeScan(): null
04-22 11:53:54.799 11784-11801/com.acs.btdemo D/BluetoothLeScanner: onClientRegistered() – status=0 clientIf=6
04-22 11:53:54.807 11784-11829/com.acs.btdemo D/OpenGLRenderer: Use EGL_SWAP_BEHAVIOR_PRESERVED: true
04-22 11:53:54.815 11784-11784/com.acs.btdemo D/Atlas: Validating map…
04-22 11:53:54.842 11784-11829/com.acs.btdemo I/Adreno-EGL: <qeglDrvAPI_eglInitialize:379>: QUALCOMM Build: 01/14/15, ab0075f, Id3510ff6dc
04-22 11:53:54.843 11784-11829/com.acs.btdemo I/OpenGLRenderer: Initialized EGL, version 1.4
04-22 11:53:54.865 11784-11829/com.acs.btdemo D/OpenGLRenderer: Enabling debug mode 0
04-22 11:53:54.931 11784-11784/com.acs.btdemo W/InputMethodManager: Ignoring onBind: cur seq=1026, given seq=1025
04-22 11:53:59.611 11784-11784/com.acs.btdemo D/BluetoothAdapter: stopLeScan()
04-22 11:53:59.738 11784-11784/com.acs.btdemo D/ReaderManager: locox
04-22 11:53:59.742 11784-11784/com.acs.btdemo D/BluetoothGatt: connect() – device: 68:C9:0B:0D:8A:44, auto: false
04-22 11:53:59.742 11784-11784/com.acs.btdemo D/BluetoothGatt: registerApp()
04-22 11:53:59.742 11784-11784/com.acs.btdemo D/BluetoothGatt: registerApp() – UUID=52e3453e-6c05-48b7-bc54-58274be81157
04-22 11:53:59.743 11784-11918/com.acs.btdemo D/BluetoothGatt: onClientRegistered() – status=0 clientIf=6
04-22 11:53:59.745 11784-11784/com.acs.btdemo I/ReaderActivity: onResume()
04-22 11:54:00.882 11784-11801/com.acs.btdemo D/BluetoothGatt: onClientConnectionState() – status=133 clientIf=6 device=68:C9:0B:0D:8A:44

It seems as though it detects the reader, but that’s as far as it gets. I have tried to debug the app but not clear what’s failing.

Here’s another try, with more Bluetooth information this time:

04-22 11:55:55.636 11784-11784/com.acs.btdemo D/ReaderManager: locox
04-22 11:55:55.636 11784-11784/com.acs.btdemo I/ReaderManager: Clear old GATT connection
04-22 11:55:55.636 11784-11784/com.acs.btdemo D/BluetoothGatt: cancelOpen() – device: 68:C9:0B:0D:8A:44
04-22 11:55:55.636 11784-11784/com.acs.btdemo D/BluetoothGatt: close()
04-22 11:55:55.637 11784-11784/com.acs.btdemo D/BluetoothGatt: unregisterApp() – mClientIf=6
04-22 11:55:55.639 11784-11784/com.acs.btdemo D/BluetoothGatt: connect() – device: 68:C9:0B:0D:8A:44, auto: false
04-22 11:55:55.639 11784-11784/com.acs.btdemo D/BluetoothGatt: registerApp()
04-22 11:55:55.639 11784-11784/com.acs.btdemo D/BluetoothGatt: registerApp() – UUID=f2e2b51d-0041-4101-91d0-949da26bc468
04-22 11:55:55.640 11784-11800/com.acs.btdemo D/BluetoothGatt: onClientRegistered() – status=0 clientIf=6
04-22 11:55:55.642 11784-11784/com.acs.btdemo I/ReaderActivity: onResume()
04-22 11:56:00.672 11784-11800/com.acs.btdemo D/BluetoothGatt: onClientConnectionState() – status=0 clientIf=6 device=68:C9:0B:0D:8A:44
04-22 11:56:00.672 11784-11800/com.acs.btdemo D/BluetoothGatt: discoverServices() – device: 68:C9:0B:0D:8A:44
04-22 11:56:00.679 11784-11800/com.acs.btdemo D/BluetoothGatt: onSearchComplete() = Device=68:C9:0B:0D:8A:44 Status=0
04-22 11:56:00.679 11784-11800/com.acs.btdemo V/ReaderManager: On Acr1255uj1Reader Detected.
04-22 11:56:00.679 11784-11800/com.acs.btdemo D/ReaderManager: Device Detected
04-22 11:56:00.679 11784-11800/com.acs.btdemo I/System.out: Notifying to all the subscribers when product became available
04-22 11:56:00.687 11784-11800/com.acs.btdemo D/BluetoothGatt: setCharacteristicNotification() – uuid: 00002a19-0000-1000-8000-00805f9b34fb enable: true
04-22 11:56:00.869 11784-11801/com.acs.btdemo D/BluetoothGatt: setCharacteristicNotification() – uuid: 0000fff2-0000-1000-8000-00805f9b34fb enable: true

NFC tags are not detected.

[TerryParticipant]

P.S. this is using a Nexus 5, running Android 5.1.1

ACR1255
P/N: ACR1255U-J1
S/N: RR330-000150

[RichardKeymaster]

Hey Terry, are you testing with the Test App we sent you via email or the SDK bundle and your own app?? I’m flying a little blind since we don’t have a Nexus 5 but we have tested the Test App on a Nexus 7 and Samsung Galaxy Zoom with success. We have experienced some of our team members getting tied up with having two different versions of the same Test App on their phones without realizing it. Also with trying to return to the first screen using the Back button…. which has an effect, but looks like its a crash. The actual way to return to the initial screen is to DISCONNECT from the menu bar.

In order to regain sanity, please remove all presence of the Test App on your Nexus 5. Then power cycle your device (extreme but to be safe). Then reinstall the test app we emailed you and launch. Scan for the ACR1255U-000150 device and select it from the list. You should immediately be prompted for Bluetooth pairing with this device. If you don’t there is a problem. Otherwise, enter the “000000” pin code and you should hear the beep from the reader confirming the pairing, authentication, and connection was successful. At this point you should be able to scan for tags.

best,
Richard

[TerryParticipant]

Hi Richard – can you re-send me the link to the test app? I don’t seem to have a recent link that might reflect the MasterKey fix.

Then I’ll give your instructions a try and see if we can get up and running.

Thanks,
Terry

[Author]

Posts