15.09.2017 16:46, Luiz Augusto von Dentz пишет:
Ive just a set of patches adressing race condition with StartDiscovery
and StopDiscovery, please have a try. Also it is not a good idea to
mix usage of D-Bus with btmgmt, they might not play well together
especially when it comes to discovery.
Thank you, I add "patch v2 adapter: Refactor code around discovery" to
source bluez-5.47 and compile it.
My test results:
1. btmgmt after "find" command NOT set org.bluez.Adapter1
string:Discovering =1 . But the Discovery process is already running,
why he does not do it? btmgmt not use dbus for managment?
2. If i send method StartDiscovery via dbus-send command, i see
org.bluez.Adapter1 string:Discovering =1 status. But I can not stop the
process, method StopDiscovery - has no effect.
"btmgmt stop-find" - has no effect, in therminal i see:
hci0 type 7 discovering off
hci0 type 7 discovering on
hci0 type 7 discovering off
hci0 type 7 discovering on
hci0 type 7 discovering off
hci0 type 7 discovering on
after btmgmt power off and btmgmt power on
org.bluez.Adapter1 string:Discovering =0
I assume that the method StopDiscovery must completely terminate the
process StartDiscovery, regardless of the way the scan was started
(btmgmt, dbus-send, hcitool, bluetoothctl or more other).
--
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
