nRF Connect Updated app - Not showing real Advertising data but default as FFFFFFF...

[Joel]

I can see for the same device on Android nRFconnect that the serial number in advertising data can be seen as here -->

The same device at same time on my iphone X with up to date nRF connect app shows FFFFFF...... -->

I am confused as to what is going on. The above two screenshots are from two phones at the same time but I'm using a nRF52DK.

Strangely I have a different custom board with same nRF52840 chip and I can see the data clearly advertised at same time. You can see this device in last pic above with 0xBA9999999995 in advertisement packet. All my devices use standard beacon and not ibeacon.

Please advise.

[Amanda Hsieh]

Hi, 

It seems like when you did not set a company identifier then it is filled with whatever was in the memory at the time of the initialization of 

ble_advdata_manuf_data_t manuf_specific_data;

You will see that you after the initialization of manuf_specific_data type the line:

memset(&manuf_specific_data, 0, sizeof(your_manuf_specific_data));

The two first bytes will be 0x00.

What do you want to do? Do you want to exclude the company identifier completely? What SDK do you use?

You could take a look at the advertising_init() in the Beacon Transmitter Sample Application example.

-Amanda H.

[Joel]

Thanks Amanda. I am using the same embedded code on both the devices (As seen in pic above under tasyl) and only difference is serial numbers. Why would the second device only show deafulat value i.e all F's? especially that using SES IDE and running debugger I can see the correct serial number in flash and advertisement data.

[Joel]

I can use the company identifier and use something unique there but is that mandatory or of any use? My main interest is in the advertisement custom data wherein I insert my serial number.

[Amanda Hsieh]

Hi,

You will have to get your own Company ID, i.e. become a member of the Bluetooth SIG. You need to at least be an adopter member of the Bluetooth SIG to get the company ID and the Adopter membership is a free level of membership.

-Amanda H.

[Joel]

Hi Amanda. I have now registered as a "Adopter" member and have a user ID but no company ID assigned. However I fail to understand as to why the advertisement data will be affected by Bluetooth SIG ID? It still doesn't explain as to why nRF Connect app is showing data as FFFFFF...... but my custom app is reading the advertisement data properly. Please advise. 

[Amanda Hsieh]

Hi Hermes,

Do you only see the issue with the iPhone X?

If yes, it could be a bug with either the iPhone or the nRF Connect for iOS app. From the screenshot, it seems like you are using the new v2 of the iOS app. It's pretty new, so there could be bugs.

Please kindly help us clarify the problem. Your reply will be useful. Thanks.

-Amanda H.

[Joel]

Hi Amanda,

Yes, it looks like a nRFconnect bug for iOS. As you can see in iOS screenshot (second screenshot with yellow highlighter), there are two TASYL devices. Both have the exact same embedded firmware (softdevice+app) and both have a custom adv data programmed. That data is the serial number. The first device where you can see the serial number 0xBA..... was programmed and scanned by old nRFconnect (iOS) app. After upgrading ios nrfconnect app I could see this first device with same adv data information which was good but now that I progarmmed a second nRF52 DK with same firmware and it was broadcasting then for thsi new device nRFconenct app was showing 0xFFF.... in adv packet. This is a bug I think. The reason I raised ticket was because I was not sure if it's a nRFconnect bug or if any of my iOS updates caused something to change by means of Apple policies,etc.   

[Amanda Hsieh]

Hi Hermes,

Thanks for the quick update. I have reported it into the development team. 

I will be back ASAP if I have the update. 

-Amanda H.

[Amanda Hsieh]

Hi, 

This was fixed in v2.1 that we changed the text shown when the Company ID in the Manufacturer Data is "No Company ID".

-Amanda H.