Hi, and thank you for the answer. Appreciated! I see there is QT Bluetooth module since 5.2. I'll be looking into this to see what is possible. There is also a kde package bluez-qt which can be also useful, but I did not have time to look closer. It just looks like that a lot needs to be reworked to make it right. At the moment I don't know how far this has been integrated in Sailfish. My experience with audio and sync is very disappointing.
And thanks for the repos. Exactly there I've been looking. The best would be to use QT Bluetooth consistently if possible. Who can provide more information on the topic? I found this wiki which gives an overview of packages but not on relations and I'm not sure how up to date it is: https://wiki.merproject.org/wiki/SailfishOSS thanks and regards Chris Adams wrote: > Hi, > > Yes, I suspect that the Buteo plugins weren't updated when the rest of the > stack was upgraded to BlueZ 5. > I assume that you can simply update the code in that repository to use the > appropriate interfaces and APIs to begin the porting effort. I don't > believe that we mean to keep BlueZ 4 support working, so no need to have > two separate codepaths with ifdefs depending on version, instead can just > port directly to BlueZ 5 APIs. > > The two repositories with code that will probably need to be updated are: > https://git.merproject.org/mer-core/buteo-syncfw/ > https://git.merproject.org/mer-core/buteo-sync-plugins/ > > Regarding patterns-sailfish-mw - I believe that patterns can be thought of > as "meta packages" which simply define a whole set of packages which > should be installed. So in itself, it is not a specific package, but will > include a variety of packages which need to be installed. (I may be > incorrect, if so perhaps David can correct me.) > I don't know where the patterns are specified, but they are probably > internal currently. If you have a new package which you believe should be > added to the core middleware pattern, I suggest you ping lbt on IRC to > discuss. > > Best regards, > Chris. > > ________________________________________ > From: Devel [devel-boun...@lists.sailfishos.org] on behalf of deloptes > [delop...@gmail.com] Sent: Wednesday, June 05, 2019 6:06 PM > To: devel@lists.sailfishos.org > Subject: Re: [SailfishDevel] SyncML topic revived > > deloptes wrote: > > >> Another question is where do I find source or documentation around >> patterns-sailfish-mw package. It looks like it is the right place to >> integrate such a plugin. >> > > No one answered about patterns-sailfish-mw. > > I was digging deeper and found out that in > libbuteosyncfw/profile/BtHelper.cpp the interface definitions are bluez4 > > > const QString BT::BLUEZ_DEST = "org.bluez"; > const QString BT::BLUEZ_MANAGER_INTERFACE = "org.bluez.Manager"; > const QString BT::BLUEZ_ADAPTER_INTERFACE = "org.bluez.Adapter"; > const QString BT::BLUEZ_DEVICE_INTERFACE = "org.bluez.Device"; > const QString BT::GET_DEFAULT_ADAPTER = "DefaultAdapter"; > const QString BT::FIND_DEVICE = "FindDevice"; > const QString BT::DISCOVERSERVICES = "DiscoverServices"; > const QString BT::GETPROPERTIES = "GetProperties"; > > Where can I address this issue? My impression is that this is related to > syncml and never updated when Jolla updated to bluez5 in Sailfish. > > @Chris Adams - can you advise pls? You've helped me so far. > > Thanks in advance > > > _______________________________________________ > SailfishOS.org Devel mailing list > To unsubscribe, please send a mail to > devel-unsubscr...@lists.sailfishos.org > _______________________________________________ SailfishOS.org Devel > mailing list To unsubscribe, please send a mail to > devel-unsubscr...@lists.sailfishos.org _______________________________________________ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
