Phone does not decode advert packet properly

RE: Phone does not decode advert packet properly

run_ar — Fri, 12 Apr 2019 13:00:56 GMT

That is strange, could depend on the bit sequence. I suppose the traces will show that the advertiser is advertising what it should. Would be interesting to see how the phone actually decodes the packages, but unfortunately we just have to guess what is happening on that end.

Note that we have limited staffing during the Easter holidays (next week). And will probably not be able to respond in a timely manner. I am sorry for the inconvenience.

RE: Phone does not decode advert packet properly

Jonathan — Thu, 11 Apr 2019 06:18:34 GMT

We haven't found a real correlation. Some longer names worked fine, and for instance, default "Nordic_Blinky" causes no problem unlike shorter "LP-KEYFOB". We thought maybe some "special" characters so we replaced "-" with "_", and then also removed it. Did not fix the issue.

I'll try obtaining captures.

RE: Phone does not decode advert packet properly

run_ar — Wed, 10 Apr 2019 19:47:19 GMT

Would it be a solution to avoid the advertisement names that causes problems with the phones? Is there a particular length that causes the problem? I.e. have you tried to gradually increase the length of the advertisement name to see when it fails?

It would still be interesting to get a sniffer log so I can see what is happening on air.

RE: Phone does not decode advert packet properly

Jonathan — Mon, 08 Apr 2019 13:39:45 GMT

Yes, that's actually what I described in the report: taking the example from latest SDK, and changing the device causes the issue (on SOME phones, which have all been determined to be international imports, typically from countries where they are cheaper)

RE: Phone does not decode advert packet properly

run_ar — Wed, 27 Mar 2019 13:56:34 GMT

Ok, so the blinky example that works also have the chsel bit? Can you try to change the device name in this example to see if it still works.

As for sniffer. If you have an extra DK or a dongle you could use this: https://www.nordicsemi.com/Software-and-Tools/Development-Tools/nRF-Sniffer

RE: Phone does not decode advert packet properly

Jonathan — Wed, 27 Mar 2019 06:33:29 GMT

What type of sniffer trace would you consider? All I have available is Ubertooth. I doubt the changes with Bluetooth 5 would be causing the issue, as said, the original Blinky works fine, then simply change a few characters and it tursn complete wrong.

RE: Phone does not decode advert packet properly

run_ar — Tue, 26 Mar 2019 15:00:33 GMT

Hi,

I would recommend that you capture a sniffer trace so we can see what is happening on air. If you capture one trace of each, both working and non working so you can compare these to find the difference.

Note that in Bluetooth 5.0 a new field was added to the PDU, so it might be that the phone you are using is decoding this erroneously: