PositionSource onPositionChanged SIGNAL slow

[ekkescorner]

just did some first work with PositionSource on Android / iOS
it works - I'm getting the correct location

for this App I only need single update

starting the App, the PositionSource immediately gets a PositionUpdate (seems to be the last one cached by the OS)
this is fine, so I can display the coordinates together with position timestamp and user can decide to use this one or to refresh the coordinates

starting a new update() is very slow
it took around 2 minutes before getting the positionChanged SIGNAL,
but the reported timestamp is only 2 secs after doing the update()
per ex
15:13:08 doing update() on PositionSource
15:15:08 getting positionChanged SIGNAL: Coordinates together with Timestamp 15:13:10

tried to set updateInterval to 5000, but this interval only should be needed if using start() and continuous reading updates

supported and preffered methods are Satellite and Non-Satellite

any ideas ?

[ekkescorner]

just found a workaround:

setting updateInterval to 5000

doing start() instead of update()

and first time getting a positionUpdate() doing stop()

should I report a bug or did I something wrong with update() before ?

[Schluchti]

Experienced the same behavior a few weeks ago. I did the same as you, I am also using start and stop instead of update. Don't know why, but as you already said, it performs way faster than update.

[ekkescorner]

@Schluchti thx confirming this. will open a bug report

[Schluchti]

@ekkescorner Thanks! Could you maybe post the ticket number here afterwards? Would like to subscribe to the ticket, in order to stay up to date :)

[ekkescorner]

@Schluchti here's the bugreport https://bugreports.qt.io/browse/QTBUG-57104

[Schluchti]

Thanks a lot :)