Since no one answer:

I have a solution.

I can already suspect that the BLE_API_Native seems to be limitated compare to the BLE_API regarding the advertising.

All example compiled with BLE_API show connect and bond correctly.

I also received a keyfob from Texas that I did not program and can be seen in any media.

Beside this below is my solution:

I made some change to GapAdvertisingData.h (which I hate but could not find a better solution) and in the GapAdvertisingData.cpp

The compiler did not like the type Flags and wanted an uint_8.

I am not a C++ super expert so it took me some time to understand the problem.

in the file GapAdvertisingData.h made the following changes:

line cancelled-> ble_error_t addFlags(Flags flag = LE_GENERAL_DISCOVERABLE);

replaced by this line -> ble_error_t addFlags(uint8_t flag = LE_GENERAL_DISCOVERABLE);

then in the main{} modified this line:

line canceled -> advData.addFlags(GapAdvertisingData::BREDR_NOT_SUPPORTED);

replaced by the line below->

advData.addFlags(GapAdvertisingData::BREDR_NOT_SUPPORTED | GapAdvertisingData::LE_GENERAL_DISCOVERABLE);

Need the following change also in GapAdvertisingData.cpp

ble_error_t GapAdvertisingData::addFlags(uint8_t flag) {

return addData(GapAdvertisingData::FLAGS, (uint8_t*)&flag, 1);

}

Basically the declaration uint_8 let us change the flags and make it discoverable.

Even if it was set by default it was not advertising it as such.

Finally I could make this work with the nRFToolbox and can see it from my PC and Phones WP and Android.

I suspect this to be a "soft" bug, but if someone could add some comment?

Jean-Marc