Pausing/resuming now doesn't record?
I use Locus Pro mainly during the summer, because I like recording my hiking tracks. Some time ago I opened a ticket about pausing and resuming recording here:
https://help.locusmap.eu/topic/recordingpausing-incosistencies-between-app-and-notification
Two days ago, with Locus Pro 3.47.2 on the same system (Android 8.1 on a Samsung Note 9) I noticed that after a pause and a resume Locus told me on the notification it was recording but, as you can spot on the map below, when I opened the main UI I discovered that it didn't resume recording at all! There are missing segments...
It happened 2 times on 2 different days... On the linked thread the problem was (and always has been) a missed synchronization between widget/notification messages but I never missed parts of a track. I mean, tapping on the notification or on the widget always did the correct action, sometimes without reporting it correctly.
Locus is not battery optimized (I added an exception), is not killed by the system (I'm using Oreo, after all) and additionally it's running as a service, with the foreground notification. Using it extensively only during the summer, I cannot say which version broke the feature, but at the moment the only safe way to pause and resume a recording without losing part of a track is opening the main activity and tapping there.
That's not the most comfortable way in my opinion, especially when adding waypoint names or pausing/resuming frequently.
I don't remember now what caused the issue, but I think I paused the recording from the widget, resumed with the notification button and for sure I added a waypoint name from the widget (and that waypoint had the wrong position).
Hello,
interesting problem.
So, for my understanding, steps to reproduce:
Am I correct? Have to try it in the field.
Hello,
interesting problem.
So, for my understanding, steps to reproduce:
Am I correct? Have to try it in the field.
Replies have been locked on this page!