Disconnect on S130 v2, HCI Error 0x2A

RE: Disconnect on S130 v2, HCI Error 0x2A

gabitoyacu — Wed, 07 Dec 2016 15:03:18 GMT

Sorry, Argentina, Cordoba

RE: Disconnect on S130 v2, HCI Error 0x2A

Hung Bui — Wed, 07 Dec 2016 14:53:58 GMT

Please let me know your area (country/state) I will send you the contact.

RE: Disconnect on S130 v2, HCI Error 0x2A

gabitoyacu — Wed, 07 Dec 2016 14:38:21 GMT

I don't have a contact, we made the purchase at a distributor. Now, we can detect this issue with Samsung Galaxy J1 ACE, android 5.1. Previously I had the same type of anomaly, but I don't remember the model, this has android 5.x

RE: Disconnect on S130 v2, HCI Error 0x2A

Hung Bui — Wed, 07 Dec 2016 14:25:02 GMT

I would suggest you send your request through our sale representative. If you don't have a contact please let me know your area.

Could you let me know the detail about the phones that you found the problem ? Phone name, Android version ?

RE: Disconnect on S130 v2, HCI Error 0x2A

gabitoyacu — Wed, 07 Dec 2016 13:40:30 GMT

We have our production with nrf51822, at the moment isn't possible to move to NRF52. Is it feasible that you apply this compatibility to S130? Does this require a lot of work?

RE: Disconnect on S130 v2, HCI Error 0x2A

Hung Bui — Wed, 07 Dec 2016 12:51:23 GMT

Unfortunately no. And S132v3.1 with exactly the option you want is just released today. Check out the release note:

A new compatibility mode has been added to enable interoperability with central devices that may initiate version exchange and feature exchange control procedures in parallel (DRGN-8232).

You may want to move to the NRF52.

RE: Disconnect on S130 v2, HCI Error 0x2A

gabitoyacu — Tue, 06 Dec 2016 23:22:16 GMT

S132 isn't compatible with nrf51822, rigth?

RE: Disconnect on S130 v2, HCI Error 0x2A

Hung Bui — Tue, 06 Dec 2016 13:42:18 GMT

I am afraid there would be no release/update soon for S130.

RE: Disconnect on S130 v2, HCI Error 0x2A

gabitoyacu — Mon, 05 Dec 2016 18:08:22 GMT

Our hardware uses the nrf51 chip, will this feature be implemented to S130?

RE: Disconnect on S130 v2, HCI Error 0x2A

gabitoyacu — Mon, 05 Dec 2016 15:54:53 GMT

Great & thanks for your support

RE: Disconnect on S130 v2, HCI Error 0x2A

Hung Bui — Mon, 05 Dec 2016 15:19:37 GMT

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.

RE: Disconnect on S130 v2, HCI Error 0x2A

gabitoyacu — Mon, 05 Dec 2016 14:28:39 GMT

Hello, please check the full trace s110

RE: Disconnect on S130 v2, HCI Error 0x2A

Hung Bui — Mon, 05 Dec 2016 08:18:02 GMT

Could you try to record a trace with S110 and S130v1 ? I believe it would have the same behavior as S130v2. Maybe I'm wrong.

Do you have the issue every time the phone connect to S130v2 ?

But anyway, it comes from a violation of the spec from Android side. I don't think we can do anything with that.

RE: Disconnect on S130 v2, HCI Error 0x2A

gabitoyacu — Fri, 02 Dec 2016 15:40:08 GMT

PCA10028 V1.1.0 and our own board, the fail is present with both boards, but these boards work fine with others smart-phone. In addition, the softdevice s110 and s130 V1 work without drawbacks

RE: Disconnect on S130 v2, HCI Error 0x2A

Hung Bui — Fri, 02 Dec 2016 15:29:07 GMT

Hi Gabi,

Thanks for the trace.

I can clearly see why this happens. At packet #103 and #104 the phone sent LL_VERSION_IND and we haven't answered yet. The phone should wait but it didn't and send LL_FEATURE_REQ. This is not allowed. There should be only one LL command packets at a time. When we have 2 request at the same time we will disconnect and throw out 0x2A because link layer protocol is violated

You can see that we advertise after that. There are 2 -3 connection request attempt failed after that, but it's not related to the software, simply the connect request was not received by the chip. This could be due to interference or bad RF circuit on the board.

Which board are you testing with ?

RE: Disconnect on S130 v2, HCI Error 0x2A

gabitoyacu — Fri, 02 Dec 2016 14:46:25 GMT

Attached full trace, look at this

RE: Disconnect on S130 v2, HCI Error 0x2A

Hung Bui — Fri, 02 Dec 2016 13:28:29 GMT

@gabitoyacu: The sniffer is not complete, only 3-4 packets in the trace. Did you modify it or smth ? It should include advertising packets, and other data packets when in connection. Please try again

RE: Disconnect on S130 v2, HCI Error 0x2A

gabitoyacu — Fri, 02 Dec 2016 01:34:18 GMT

Look at files s130_v2_fail.pcapng & s110_ok.pcapng. These are with the same smart-phone

RE: Disconnect on S130 v2, HCI Error 0x2A

gabitoyacu — Thu, 01 Dec 2016 22:49:50 GMT

I don't have any trace, my kit doesn't work with sniffer firmware. I've done tests with our hardware (I've manufactured prototypes) and our firmware, but the problem persists.

The S130 V2.x works with samsung note, motorola moto x

I'll try to use our hardware as sniffer.

RE: Disconnect on S130 v2, HCI Error 0x2A

Hung Bui — Thu, 01 Dec 2016 11:21:46 GMT

It's pretty rare to see BLE_HCI_DIFFERENT_TRANSACTION_COLLISION (0x2A). There is smth wrong with the link layer. We would need to have a sniffer trace to really tell what happened.

Could you provide one ?

Which other phones did you test with ?

Do you see the problem when you test with other examples ?