https://devzone.nordicsemi.com/f/nordic-q-a/34390/nrf52-cannot-connect-to-ble-4-1-phone-nexus-6-with-android-7-1-1Hi, We are developing a wireless sensor for research purpose using NRF52. I was always develop under Bluetooth 5.0 environments. The phone i am always using is Xiaomi MI 6, which supports Bluetooth 5. We are using data length extension for higher dataen-USTelligent Community 13Thu, 17 May 2018 16:54:48 GMThttps://devzone.nordicsemi.com/thread/132437?ContentTypeID=1Thu, 17 May 2018 16:54:48 GMT137ad170-7792-4731-bb38-c0d22fbe4515:76d6cd0c-838c-4c1f-a28f-b24ad2f1fb45aircheese<p>Hi, thanks for reply, I am testing with the Nexus 6 today. I am monitoring the results in NRF52 side, it seems like Nexus 6 is accepting the MTU change to 247 event it is not suppose to have anything bigger than 23. The connection then fail after this.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/132289?ContentTypeID=1Wed, 16 May 2018 13:01:04 GMT137ad170-7792-4731-bb38-c0d22fbe4515:01c15d57-9d75-470a-bfa7-19fe927ed431Einar Thorsrud<p>Hi&nbsp;Jianjia,</p> <p>It is difficult to know what to make of the sniffer trace. All the packets from #362-#379 are tagged with invalid CRC, which would then result in them being correctly discarded by the SoftDevice (which in turn times out). It does not look right tough, as Wireshark seems to find the CRC field too early in the packet, which in turn is strangely long (length field is 31).</p> <p>Do you have another sniffer you can compare with to see if the problem is with the sniffer or the phone?</p><div style="clear:both;"></div>