On Mon, 2018-07-30 at 09:44 +0300, Luiz Augusto von Dentz wrote: > From: Luiz Augusto von Dentz <luiz.von.dentz@xxxxxxxxx> > > This adds discoverable command to scan menu which can be used to set > if adapter should become discoverable while scanning: > > [bluetooth]# scan.discoverable on > [bluetooth]# scan on > SetDiscoveryFilter success > [CHG] Controller XX:XX:XX:XX:XX:XX Discoverable: yes > Discovery started > [CHG] Controller XX:XX:XX:XX:XX:XX Discovering: yes > [bluetooth]# scan off > Discovery stopped > [CHG] Controller XX:XX:XX:XX:XX:XX Discoverable: no This doesn't call SetDiscoverFilter() when the scan as already started, meaning that my earlier test still fails. > As mentioned on IRC, this does not work if the Discoverable filter is > set after the discovery has started. So: > discoverable off > scan on > scan.discoverable on > show <- this will show "Discoverable" still off. Doing a quick "scan off" / "scan on" will show "SetDiscoveryFilter success" appearing, this should also appear when the filter is changed while scanning is on-going. If you don't want to change the currently filter, it might be good for the client to show a "Filter change queued" or similar message that would show that the setting hasn't been applied, but would be for the next run. Cheers -- 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
