Topics

Hi all,

I currently have a new phone I'm trying out - Cubot King Kong Mini 2 Pro. I installed Locus Pro 3.70.0 and took the phone for a couple of runs using Locus' tracking. The first run went fine, but today's outing left me somewhat surprised: after a certain point (roughly 2:30h into the run), the track started diverging significantly from the 'real' one, while it was spot-on before. I have attached the recorded track and the true one - the latter drawn in Viking for simplicity. Also note that the elevation data of the recorded track is totally off - nope, that town is not 790m below sea level ;-)

Any ideas what the problem could be?

Cheers,
r.

Hi all,

I've been using Locus Pro to track my runs for more than 12 years now. For Ultras longer than 12h, I'm using an old phone with interchangeable battery. With old versions of Locus, I usually stopped recording when my battery was low, changed battery and started a new recording after the phone was powered back on.

I was very (!) excited to see that with current Locus versions (mine is 3.68.2), after the phone shut down (once due to dropping it, another time because it ran out of battery) Locus resumed track recording after the phone was powered back on.

Now my question is: how would I best do this on purpose? Pause recording, shut down the phone and resume after powering back on?


Your suggestions will be much appreciated!
r.