New Topic

Locus Map - help desk Topic Problem Locus Map (Android)

This object is in archive!

Category Locus Map (Android)

Tags Recording

Comments 6

Subscribers 3

Votes 2

Pausing/resuming now doesn't record?

virtualdj shared this problem ago

Solved

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).

The same problem 0

Replies (1)

Menion ●

Hello,

interesting problem.

So, for my understanding, steps to reproduce:

start track recording over the application
put the app on the background
after some time, pause recording over the widget
after some time, resume also after the widget
when later stoped, saved, the result should be like on your screen

Am I correct? Have to try it in the field.

URL

virtualdj ●

Yes, exactly. I never opened the main app activity to watch the map but I'm pretty sure after resuming the notification said "recording" and not "paused". After saving the track I discovered the bad news :-(

URL

Menion ●

Oki. This probably won't be a problem that app is still in some "pause" mode (because I'm sure it works correctly). It may be more a problem that the app simply does not enable GPS when needed again.

You may, for now, try if my theory is correct by Settings > GPS & sensors > GPS ON for track recording - and keep this setting enabled. This should keep GPS enabled even if the recording is paused.

I'll try to simulate it on my own device, thanks for now.

Menion

URL

virtualdj ●

Hi, I couldn't test earlier because I couldn't "risk" my tracks so I tried today.

First note: I was able to replicate the issue on the first try, but with these steps (slightly different from yours):

Place the widget on the home page
Start recording from the widget, without opening Locus main UI: the notification confirms the recording state
Start to walk and after a while pause the recording from the widget: the notification confirms it's pause
Continue to walk and after a couple of seconds "unpause"/resume from the widget: the notification says it is recording but it's not true. The number of points saved doesn't increment while the time does. Only after opening the main Locus UI the recording is actually resumed.

I was able to capture a screen recording where all those things are visible (keep an eye on the number of points) and as the max attachment size here is only 2 MB I have to put a Dropbox link:

20200829_095329.mp4

Enabling "GPS ON for track recording" as you suggested does work as a workaround, but of course this eats more battery on pauses. I can confirm that the same device with the same Android OS version worked well in the past (apart from the widget sync issue) so resuming the GPS recording should work and I think this "bug" might be a regression.

Thank you very much.

URL

Menion ●

Hello,

I've finally looked on this problem. Indeed, you were perfectly correct! GPS was not enabled when resuming recording over widget!

Perfecet, will be fixed in next 3.48.1 version.

Menion

URL

virtualdj ●

Great! Thank you very much!

URL