Hi Simon,

On Wed, Sep 6, 2017 at 5:06 AM, Simon Ratner <[email protected]> wrote:
>
> Hi devs,
>
> I am seeing a change in behaviour when performing active scan, compared to
> pre-1.1. Previously, BLE_GAP_EVENT_DISC event would be reported for both
> the original advertising packet (BLE_HCI_ADV_RPT_EVTYPE_ADV_IND), and the
> scan response (BLE_HCI_ADV_RPT_EVTYPE_SCAN_RSP), in close succession.
>
> With 1_2_0_dev, I no longer see the advertising packet data, only the scan
> responses.
>
> This is my scan parameters:
>
> const struct ble_gap_disc_params scan_params_dflt = {
>   .itvl = 0, /* use default */
>   .window = 0, /* use default */
>   .filter_policy = BLE_HCI_SCAN_FILT_NO_WL,
>   .filter_duplicates = 0,
>   .limited = 0,
>   .passive = 0,
> };
>
> Is this an intentional change, and if so, any way to get at the actual adv
> packet data?

I'm not aware of any change in this code, but I've just done a quick
test using bletiny and for me it works just fine:

[08:50:23:504] 093668 received advertisement; event_type=0 <cut> fields:
[08:50:23:600] 093672 flags=0x1a:
[08:50:23:600] 093672 General discoverable mode
[08:50:23:600] 093673 tx_pwr_lvl=-7
[08:50:23:600] 093674
[08:50:23:600] 093674 received advertisement; event_type=4 <cut> fields:
[08:50:23:600] 093680 uuids16(complete)=0x180d
[08:50:23:600] 093681 name(complete)=andk xperia z5

I used 'b scan' which uses default parameters so the same as you quoted.

Can you see the advertising reports in HCI trace? If so, can you show
them perhaps to check if they are correct?

Best regards,
Andrzej

Reply via email to