https://devzone.nordicsemi.com/f/nordic-q-a/37808/problem-with-ble_hci_different_transaction_collision-using-nrf52840-sdk-v15-0-0-s140-v6-0-0Hello, I have got a quick question regarding a potential workaround-setting for the BLE_HCI_DIFFERENT_TRANSACTION_COLLISION-error. Here is what I am currently seeing: 1.) Results from testing the att_max_mtu_throughput-example from SDK v15.0.0 withen-USTelligent Community 13Mon, 27 Aug 2018 08:35:10 GMThttps://devzone.nordicsemi.com/thread/145845?ContentTypeID=1Mon, 27 Aug 2018 08:35:10 GMT137ad170-7792-4731-bb38-c0d22fbe4515:a112dbc1-88e3-49cf-a992-5a89c8842facrun_ar<p>Hi,</p> <p>Can you capture a sniffer trace so we can see what is happening on air?</p> <p>Most likely this is a known issue with samsung phones, where they are breaking the core spec by starting two LL procedures that contains an instant. Unfortunately the spec states that we have to disconnect when this happens, so you end up loosing the connection. The suggested workaround for now is not to change phy right after the connection is established (which is the case with SDK 15.x). Instead you should wait for some time before trying to update the phy (unfortunately, there is no way of knowing if this will work or not), but in case you are disconnected if you try to change PHY early on; add a timer to try later in the connection when the peer reconnects.</p><div style="clear:both;"></div>