BT or FW issue

[Steven Allen]

Hi,

We believe we have either a BT communication issue for Nordic Semiconductor ASA    NRF52832-QFAB-R 

https://www.digikey.com/products/en?keywords=1490-1055-1-ND

The problem phone can connect to our IOT device, but can't get any command from it or read/write any gatt characteristics values. After 20-30 seconds the connection is lost. You can check this behavior using a problem phone and any bluetooth scanner from google play. Problem phones incude the following: samsung a1 with android 7.0, samsung galaxy s6 edge with android 7.0. So, I think that the common pattern here is that the problem phones are samsung with android 7.0.

Anyone else experiencing this issue or does the manufacturer have any advice on this as a BT issue?

[Einar Thorsrud]

Hi,

I do not recall any problems specifically with those devices. Do you have a sniffer trace of the communication sowing what happens on air? That is usually the best place to start in such cases.

[Steven Allen]

We tried to sniff traffic between the problem device and our IOT product using WireShark and we have logs. These logs contain our IOT products interactions with a mobile phone on which errors do not occur and the logs of interaction with a problem telephone. Unfortunately, we are a expert in low-level communication. I have files I can send via e-mail they are zip files.

[Steven Allen]

 I have files I can send via e-mail they are zip files. I do not see how to upload them. If I forward them to you, may I ask you to load them here. They need not be private. 

[Steven Allen]

 I have files can I forward them via e-mail they are zip files?

[Einar Thorsrud]

Hi,

You can upload the zip file(s) as shown here:

[Steven Allen]

Hoping this link works:

https://www.getthedefender.com/wp-content/uploads/2019/10/Defender-BLE-logs.zip

[Einar Thorsrud]

Hi,

Thanks, I got the files. Uploading here as well for completeness (Defender BLE logs.zip), and changed the filenames to pcapng). I see some disconnects (reason 0x13), but nothing that obviously is an error. Can you point to the problem in these HCI logs? Also, do you have logs from the nRF side or normal sniffer traces (showing traffic on air)?

I have not found any indications that there should be a problem with Android 7 or Galaxy S6 Edge in general, so therefore it would be good to know what is happening in your peripheral device as well.