Receiving onclientconnectionstate() - status=133 on custom Android BLE app that uses NUS service

RE: Receiving onclientconnectionstate() - status=133 on custom Android BLE app that uses NUS service

bjorn-spockeli — Tue, 25 Apr 2017 14:18:51 GMT

@vivek: Yes, the source code for the nRF-Toolbox application for Android containt the nRF UART app which connects with the ble_app_uart example and uses the TX and RX characteristics in the Nordic UART Service.

RE: Receiving onclientconnectionstate() - status=133 on custom Android BLE app that uses NUS service

Vivek — Mon, 24 Apr 2017 08:40:51 GMT

@Bjørn Spockeli: Sir, I have used following sources for my application:

profile: -BleManager, -BleManagerCallbacks, -BleProfileService
uart: -UARTService -UARTManager, -UARTManagerCallbacks, -UARTInterface

The above source code i have taken from nRF-Toolbox . So i wanted to know is these source are enough for ble Connection, RX and TX services.?

I will be waiting for your feedback on this.. Thank you

RE: Receiving onclientconnectionstate() - status=133 on custom Android BLE app that uses NUS service

Vivek — Fri, 21 Apr 2017 12:01:33 GMT

Yes I'm able to connect with other phones except Mi phones with OS version higher than 5.0 . As these control is already available in nRF Toolbox source code. I have used Android-nRF-Blinky as a base for my application.

Is there any solution to fix issue in connection with reference to Mi phones.?

RE: Receiving onclientconnectionstate() - status=133 on custom Android BLE app that uses NUS service

bjorn-spockeli — Fri, 21 Apr 2017 11:23:44 GMT

AFIK you should be able to connect without scanning first if you use getRemoteDevice(String address) with the MAC address as the argument and then you'll get the BluetoothDevice and then you can call connectGatt() to connect.

RE: Receiving onclientconnectionstate() - status=133 on custom Android BLE app that uses NUS service

Anjali — Fri, 21 Apr 2017 11:22:26 GMT

Another inputs, by referrring nrf blinky's source, we also enabled scanning on modified app but we have the same results.

RE: Receiving onclientconnectionstate() - status=133 on custom Android BLE app that uses NUS service

Anjali — Fri, 21 Apr 2017 07:26:40 GMT

When I first try to pair with the device, it sends connect req but it immediately disconnects after that with error code 13 shown on pca10040, maybe because it was Bluetooth connection without Gatt not actual BLE. nrf-Toolbox unmodified code connects to the device with no problem.

One more thing, we have disabled scanning in our modified app because we have the MAC address of the device available. So do we still have to scan?

RE: Receiving onclientconnectionstate() - status=133 on custom Android BLE app that uses NUS service

bjorn-spockeli — Fri, 21 Apr 2017 07:20:22 GMT

Just to clarify, if you first try to pair with the device, which is not supported by the device, through the phones settings, then you're able to successfully connect? Yes, please try with the unmodified nRF Toolbox app and see if you also have to try to pair before you can successfully connect.

RE: Receiving onclientconnectionstate() - status=133 on custom Android BLE app that uses NUS service

Anjali — Fri, 21 Apr 2017 07:13:14 GMT

I will again check with the nrf-Toolbox unmodified app

RE: Receiving onclientconnectionstate() - status=133 on custom Android BLE app that uses NUS service

Anjali — Fri, 21 Apr 2017 06:58:08 GMT

I connected through the app we built on top of nrf-toobox, obtained from here

RE: Receiving onclientconnectionstate() - status=133 on custom Android BLE app that uses NUS service

bjorn-spockeli — Fri, 21 Apr 2017 06:51:57 GMT

@Anjali: When you say we tried connecting to the board through the app, then it connects succesfully, do you mean that you used the unaltered nRF Toolbox application (either Google Play or unmodified source from GitHub?

RE: Receiving onclientconnectionstate() - status=133 on custom Android BLE app that uses NUS service

Anjali — Fri, 21 Apr 2017 06:35:02 GMT

We are observing this issue on another phone as well. We can add the logs out of it shortly. But my point is if this is not limited to only a single phone, then is there any way there is missed out something from the BLE_manager? We are using the uart manager from nrf_toolbox, so whatever is managed from uart mnanger to ble manager, we haven't looked at it.

RE: Receiving onclientconnectionstate() - status=133 on custom Android BLE app that uses NUS service

Anjali — Fri, 21 Apr 2017 06:30:01 GMT

Hi, I am adding the observations on Vivek's behalf:

I have put logs in function on_ble_event(), in cases BLE_GAP_EVT_CONNECTED and BLE_GAP_EVT_DISCONNECTED, but I do not receive those logs in the case I do not see the connect request on sniffer. So as you suggested the problem might be in the phone; But that is not all.

We went into the phone's settings, we tried to pair the pca10040 fromthere manually (which will fail ofcourse), and after that we tried connecting to the board through the app, then it connects succesfully. We observed all the logs in sniffer as well as on pca10040 according to the working phones sniffer I have attached. We have tried this multiple times, and it is confirmed that if we try to pair manually in device's settings, and then try to connect through the app, it works.

RE: Receiving onclientconnectionstate() - status=133 on custom Android BLE app that uses NUS service

bjorn-spockeli — Fri, 21 Apr 2017 06:18:13 GMT

Yes, if you do not get any BLE events from the SoftDevice while you attempt to connect using the Mi Redme 3s phone in addition to the fact that you do not see any connection request on the sniffer trace, then it suggests that the issue lies with the Mi Redme 3s phone.

RE: Receiving onclientconnectionstate() - status=133 on custom Android BLE app that uses NUS service

Vivek — Thu, 20 Apr 2017 19:27:27 GMT

Yes that's true it should show up in the sniffer log, but the main problem is Mi phone is not able to send connection request, whereas others phone sends connection request..! I will post the logs by debugging on pca10040 shortly

RE: Receiving onclientconnectionstate() - status=133 on custom Android BLE app that uses NUS service

bjorn-spockeli — Thu, 20 Apr 2017 14:32:28 GMT

If the Mi Redme 3s is sending a connection request, then it should show up in the sniffer log like the other phones. Do you have access to a Frontline/Elisys sniffer or similar? That way we could verify that the connection request is actually sent. Are you able to debug the application on the PCA10040 board? If yes, are any BLE events propagated to the application, e.g. BLE_GAP_EVT_CONNECTED or BLE_GAP_EVT_DISCONNECTED?

RE: Receiving onclientconnectionstate() - status=133 on custom Android BLE app that uses NUS service

Vivek — Thu, 20 Apr 2017 11:39:15 GMT

Hi Bjorn, Thanks for your prompt reply. As you correctly mentioned we are not able to see connection request being send when we try it through Mi phone. When we are executing Same thing from some other phone, We are able to see connection request packet. So we are not sure why it is showing different behavior as far as Mi phone is concerned. Any help and guidance on this is appreciated.

RE: Receiving onclientconnectionstate() - status=133 on custom Android BLE app that uses NUS service

bjorn-spockeli — Thu, 20 Apr 2017 11:24:29 GMT

@anjali: I cannot see any connection request in the mi_logs.zip capture, its only advertisment packets and scan requests/responses. Are you sure that you captured the connection attempt?

RE: Receiving onclientconnectionstate() - status=133 on custom Android BLE app that uses NUS service

Anjali — Thu, 20 Apr 2017 10:31:59 GMT

I have edited the question with logs obtained from sniffer on windows machine.

RE: Receiving onclientconnectionstate() - status=133 on custom Android BLE app that uses NUS service

Vivek — Thu, 20 Apr 2017 08:09:10 GMT

I am sorry to say this but nrf Sniffer is the most painful tool I have tried to work with. I have a linux machine so I followed the tutorial posted on: devzone.nordicsemi.com/.../

But after installation connection to sniffer is not successful: Could not find device Sniffer device list[]:

So I also tried the link: github.com/.../BLESniffer_Python Which is posted in one of the comments. But the error it throws is: Sniffer board is not responding. Do you have any pointers on how to make this work on Linux?

RE: Receiving onclientconnectionstate() - status=133 on custom Android BLE app that uses NUS service

bjorn-spockeli — Wed, 19 Apr 2017 10:52:51 GMT

Can you provide a sniffer trace of the communication between the nRF52 and the Xiaomi phone?