Comment by rinigus
No, I don't know. I think you could look into the src of createDefaultSource and check it out there. In this respect, it should be the same for Flatpak and standalone install. Also, if it is your own...
View ArticleComment by Woidboy
Again, the problem is that the KDE Platform has three plugins available, viz., geoclue2, geoclue and positionpoll, where geoclue2 is the default one. Changing the code to use geoclue instead has one...
View ArticleComment by Woidboy
I've solved the problem. So far, I've initialized the GPS source with source = QGeoPositionInfoSource::createDefaultSource(this); which chooses Geoclue v2 by default. I've checked the KDE flatpak...
View ArticleComment by rinigus
I guess you will have to dig deeper. In particular, how to enable other geoclue version in Qt. As you opened dbus (system+session), it probably is somewhere in configs of Qt...
View ArticleComment by Woidboy
Hi Rinigus, thanks for the comment. Actually, I'm not forced to use Geoclue v2 due to my app but I thought that flatpak is restricted to it. I think that I misunderstood your answer on talk.maemo.org...
View ArticleComment by rinigus
Geoclue 2 you probably need for Gtk. For Qt, there maybe some way to get geoclue 0.x working as well. See https://doc.qt.io/qt-5/qtpositioning-plugins.html . I don't know the used protocol, whether...
View ArticleAre there any plans to update Geoclue?
As far as I know, Sailfish OS still uses Geoclue1, however, if you would like to have access to GPS within a flatpak app (thanks for supporting this way of installing apps by the way, this is awesome),...
View Article
