GPS track recording initialisation issue
Dear Locus Team,
I am a happy Locus Map Pro user for several years.
Up to versions 3.46 the track recoding in the Locus app started out from the already captured actual GPS position and simply continued to capture the position data smoothly.
From version 3.47 on the track recoding systematically reinitializes the GPS at the beginning of each track recording, even if a valid GPS signal was already available, which has the consequence that an inital transient from the new GPS signal capturing is also included at the very beginning of the track, generating jumps, peaks and biasing recorded values (e.g. max speeds sometimes >100 km/h). After this init phase the track recording runs otherwise as normal, but this intial transient is very disturbing in the recorded data.
Please consider restoring the earlier approach not to reinitialize the GPS at the beginning of track recording.
Best regards,
Laszlo
Samsung A6 (2018), Android 10, Battery optimization disabled for Locus
Hello,
I'm surprised that such a) you noticed such tiny change and mainly b) that has an effect on the start of recorded track. Anyway, this was made to perform some background checks and validated that the app has correct "location" permission. I've improved this so, in the next version 3.48, this won't be happening anymore in case, permission is already correctly set.
Thanks, Menion
Hello,
I'm surprised that such a) you noticed such tiny change and mainly b) that has an effect on the start of recorded track. Anyway, this was made to perform some background checks and validated that the app has correct "location" permission. I've improved this so, in the next version 3.48, this won't be happening anymore in case, permission is already correctly set.
Thanks, Menion
Replies have been locked on this page!