In gclue-location.c, commit d3893e6fac09064682e880c7972f2fcf82a6fb87 introduced a constant TIME_DIFF_THRESHOLD with value 60. In the summary of the commit this is said to be 60s, however it is compared to the output of g_date_time_difference, which is in microseconds. Therefore, if we want the threshold to correspond to 1 minute, TIME_DIFF_THRESHOLD should have value 60000000.
Created attachment 131817 [details] [review] This patch solves the bug
Oooh, good catch! Thanks.
Comment on attachment 131817 [details] [review] This patch solves the bug Patch applied with minor changes.
Thanks. On my laptop the gps receiver is always a few seconds ahead so the positions were reported as one day old and it made gnome-maps use the less accurate wifi-based location instead. I found the bug after digging on that problem. Hopefully my gnome-maps will use gps, now!
(In reply to Valentin Blot from comment #4) > Thanks. On my laptop the gps receiver is always a few seconds ahead so the > positions were reported as one day old and it made gnome-maps use the less > accurate wifi-based location instead. I found the bug after digging on that > problem. Hopefully my gnome-maps will use gps, now! Cool, this probably also explains the times when maps won't pick up my location updates. Is this a standalone GPS device and are you using gps-share?
No, this is a 3G modem with integrated GPS (modem is sierra gobi 3000, default modem on thinkpad X230), and I'm not using gps-share.
(In reply to Valentin Blot from comment #6) > No, this is a 3G modem with integrated GPS (modem is sierra gobi 3000, > default modem on thinkpad X230), and I'm not using gps-share. Ah OK, thanks. :)
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.