Hi Arman, On Tue, Sep 16, 2014, Arman Uguray wrote: > > have you looked at the the Add Device management command with the > > 0x00 Action. That will just send out Device Found events for devices > > in range and uses passive scanning. > > > > In addition if you are paired with a device and actually want to > > connect to it, you can use Action 0x02 to allow for background > > connection. This is currently in use for LE HID devices. > > This still only sends one Device Found event though right? In Jakub's > case, a mgmt event is desired to let the userspace know every time a > new advertisement packet is received, with the updated RSSI and > TxPower and so on. It should send as many Device Found events as there are advertising reports from the controller. We're enabling duplicate filtering in the hci_req_add_le_passive_scan() function in hci_core.c so maybe that's your issue? Some HW (like Broadcom) tend to be more conservative in how many events they send when filtering is enabled whereas others (like CSR) will give you many more of them (at least one whenever RSSI changes). > I think this ties in with some of the previous conversations on the > list about adding a device scan API that is geared towards > applications (rather than OS UI). That is, not only a mgmt API that > enables these kinds of use cases but also (probably) a high-level API > exposed from bluetoothd that allows applications to scan for devices > filtered by service UUIDs, contents of the manufacturer data field, > and so on. > > As for the Add Device command, does bluetoothd currently use this somehow? Yes, this feature (action 0x02 for Add Device) takes over the entire LE background scanning and auto-connection mechanism from 3.17 kernel onwards since BlueZ 5.22 (which was mentioned in our release notes btw). This is much better than the active scanning based auto-connections that have until now been done using Start/Stop Discovery. Johan -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
