Hi Hannu, I have fixed Qt Bluetooth like you described and it's working, a new rpm is under way.
It's in my fork on github for those interested : https://github.com/lainwir3d/qtconnectivity/commit/5f42edc7ce404db1a9fe95087bf6c0866df40771 Thanks again for the help ! Richard On Thu, Mar 5, 2015 at 7:41 AM, Hannu Mallat <hannu.mal...@jolla.com> wrote: > Hi Richard, > > we recently made certain BlueZ D-Bus methods restricted to the > privileged group. This was done because some operations, like > creating or removing pairings, should happen only via the OS bluetooth > UI. The method you noticed, org.bluez.Adapter.CreateDevice, is also in > this list. > > Since you need a device object path to be able to call > org.bluez.Device.DiscoverServices a non-privileged app can retrieve > service records over D-Bus for a device that has already been created, > but not for one that hasn't. > > Unfortunately checking the Qt code shows that it always calls > CreateDevice, even if the device already exists... and only proceeds > with FindDevice if the returned error for that is AlreadyExists. So > that will stop you even if the headset has been paired already. > > We'll review what is the best way to correct this. The plan is of > course to check all issues like this before officially allowing Qt > Bluetooth API as a shared library in harbour... > > In the meanwhile, you should be able to work around this by patching > your copy of Qt Bluetooth to call CreateDevice only after FindDevice, > and then service discovery should work for paired devices. > > BR, > H. > _______________________________________________ > SailfishOS.org Devel mailing list > To unsubscribe, please send a mail to > devel-unsubscr...@lists.sailfishos.org > -- Richard Rondu Responsable de projet EIREL 33, av. Claude Debussy 92588 Clichy Cedex Tél: 0141401263 Fax: 0141400238
_______________________________________________ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
