Hi,
I currently did many test with BLE our new devices, and i am stuck on this probleme since days. The goal of those test are to have internal too for validation process, and production on PC, but will also influence the decision of the futur component we will use in our next devices.
The scan sent me BLE_GAP_EVT_ADV_REPORT like in the sample "heart_rate_collector" but the data in p_ble_gap_evt->params.adv_report.data don't contain the name ( using : adv_report_parse with BLE_GAP_AD_TYPE_COMPLETE_LOCAL_NAME or BLE_GAP_AD_TYPE_SHORT_LOCAL_NAME ) .
if i look directly in memory, i only get 4 data value :
- BLE_GAP_AD_TYPE_16BIT_SERVICE_UUID_MORE_AVAILABLE
- BLE_GAP_AD_TYPE_APPEARANCE
- BLE_GAP_AD_TYPE_TX_POWER_LEVEL
- BLE_GAP_AD_TYPE_128BIT_SERVICE_UUID_COMPLETE and it could be suffisent, but not ...
If i do the same test with an ESP32 I get the same 4 value in the same order with 2 more :
- BLE_GAP_AD_TYPE_16BIT_SERVICE_UUID_MORE_AVAILABLE
- BLE_GAP_AD_TYPE_APPEARANCE
- BLE_GAP_AD_TYPE_TX_POWER_LEVEL
- BLE_GAP_AD_TYPE_128BIT_SERVICE_UUID_COMPLETE
- BLE_GAP_AD_TYPE_COMPLETE_LOCAL_NAME
- BLE_GAP_AD_TYPE_MANUFACTURER_SPECIFIC_DATA
So with ESP32 (Bluedroid BLE stack) i got exactly what i was looking for and i did not find the way to do with your BT stack ... did i forgot to do something or you have a bug somewhere ?
Regards,
Nicolas PERRET.