This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

BLE Disconnects immediately after connection - disconnect reason 0x2A

I am using nRF 52 DK with Softdevice s132 v4.0.2 and app ble_app_uart from sdk 13.0.0

When i try to connect using nRF Toobox running from my Nexus 6p Android phone Segger traces from the DK shows device connected event followed by immediate "device disconnected event".

0> APP:INFO:UART Start!
0> APP:INFO:Connected
0> APP:INFO:Data len is set to 0x3D(61)
0> APP:INFO:Disconnected

When i step through, in the disconnected event the reason is showing 0x2A - BLE_HCI_DIFFERENT_TRANSACTION_COLLISION

the same setup works flawlessly with iPad Air and i can send messages back and forth. Please suggest how to fix this with my phone

Adding more information - WHen i use s132 v3.1.0 with SDK v12.2.0 the ble_app_uart application works fine with my Nexus 6P. So, something added in softdevice v4.0.2 is causing this issue

Parents Reply Children
No Data
Related