the saving proces can really take couple minutes if there are thousands points in recorded track. Anyway as usually we would need to simulate it. Could you see the "Working" progress when you clicked on the stop button?
Yes, "Working" progress appears, the loading line moves. After about 20 seconds, Locus exits (or minimalizes), and the recording icon is still on the notification bar, meaning it's not "lost", but perhaps Locus ignored the "stop" command. I cannot reproduce the issue, as luckily Locus finally managed to stop the recording, and I could save the track.
But I'm sure it will happen again when I'm recording a detailed/long track with 5-6000+ trackpoints.
Locus GIS was very likely really processing the points if there was a working dialog. On the other side, it shouldn't take hours but only minutes. Please test it or change the recording profile to reduce the number of recorded points (if possible to use less detailed recording)
Thank you for the bug report. What does exactly happen when you tap on the STOP button? Does dialog "App not responding" appear? If yes, would you tap on option wait?
To simulate saving of several thousands points: open menu > Settings > Track recording > tap on detailed profile:
- set Time Interval to 1s
- edit "Vertex recording condition" > and set option "Distance OR Time"
After that start recording of the new Line. You can put device close to window for an hour. It should record new point every second. Finally try to save the line.
After I tap on the Stop button, tracklog sidebar shifts back, and "Waiting" dialog ppears with the moving "loading" line. Then, after a few seconds, Locus disappears (or minimizes). Then I can reopen locus from notification bar again, but it seems like nothing happened, treacklog recording is still pending.
Thank you for the video you provided. We'll try to find some improvements.
I found this quite old but still not solved issue. Are you still facing mentioned troubles, please?
Issue "solved" . The problem was that my old device could not handle such huge amount of data to process, and freezed during saving. Using a more powerful device solved the issue. Thakns!
Ahh I see, thanks.