To be clear, I have registered the RemoteDeviceFound and RemoteNameUpdated signals against both "/org/bluez/hci0" AND "/hci0" (both
with "org.bluez.Adapter" interface). Signals for these signals always come back against "/org/bluez/hci0", and NOT against "/hci0"
(path retrieved with dbus_g_proxy_get_path).
DS
----- Original Message -----
From: "Marcel Holtmann" <[email protected]>
To: "BlueZ development" <[email protected]>
Sent: Monday, April 07, 2008 5:58 PM
Subject: Re: [Bluez-devel] UPDATE: org.bluez.Adapter Methods/Signals
Hi David,
> After installing *-3.30, when calling DiscoverDevices, with path "/
> hci0", RemoteDeviceFound and RemoteNameUpdated are STILL returned
> against path "/org/bluez/hci0", and not the originating path, "/hci0".
that is fine. On /hci0 you should see DeviceFound signals.
Regards
Marcel
Hi David,
> To be clear, I have registered the RemoteDeviceFound and
> RemoteNameUpdated signals against both "/org/bluez/hci0" AND "/
> hci0" (both
> with "org.bluez.Adapter" interface). Signals for these signals
> always come back against "/org/bluez/hci0", and NOT against "/hci0"
> (path retrieved with dbus_g_proxy_get_path).
why don't you actually read the API documentation. Nobody said that
you can expect RemoteDeviceFound and RemoteNameUpdated on /hci0 and
you really can't. They are not sent. You get a DeviceFound signal.
Regards
Marcel
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Register now and save $200. Hurry, offer ends at 11:59 p.m.,
Monday, April 7! Use priority code J8TLD2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
Bluez-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel