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

Disconnect on S130 v2, HCI Error 0x2A

Hello,

I've an issue with several smart-phone models when I use the softdevice S130 v2

I did tests with PCA10028 and the example "ble_app_bps".

I used softdevice S110, S130 V1, S130 V2.0.0, S130 V2.0.1

This work well with S110 and S130 V1, but this fails with S120 V2.x

When I connect with the smartphone inmediately the PCA10028 report a disconnect reason = 0x2A. This happens with some smarthphone, for example, Samsung Galaxy J1 ACE.

I need use the version S130 because our device has to connect to a smartphone and other peripherals simultaneously.

Could you help me? Do you have any idea about this issue?

Thanks & regards

S130 Trace (FAIL): s130_v2_fail.pcapng

S110 Trace (OK): s110_ok.pcapng

Full trace: trace_1.pcapng

Full Trace s110: trace_s110.pcapng

Parents
  • It seems that we haven't enforced the requirement as in Bluetooth spec in S110 v8.0 and S130v1.0. There is a good news that we will add a "compatibility mode" in the next release of the S132 to allow the connection to be kept when this situation happens. It will be released soon (in a few weeks). In the mean time I would suggest to continue your development with other Android phone. Most phones don't have this issue.

Reply
  • It seems that we haven't enforced the requirement as in Bluetooth spec in S110 v8.0 and S130v1.0. There is a good news that we will add a "compatibility mode" in the next release of the S132 to allow the connection to be kept when this situation happens. It will be released soon (in a few weeks). In the mean time I would suggest to continue your development with other Android phone. Most phones don't have this issue.

Children
No Data
Related