Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Lost the last part of a (local not online) recorded track #21831

Open
RealVegOs opened this issue Jan 30, 2025 · 6 comments
Open

Lost the last part of a (local not online) recorded track #21831

RealVegOs opened this issue Jan 30, 2025 · 6 comments
Labels
Observed Needs more clarification, feedback, or research

Comments

@RealVegOs
Copy link

Description

I'm new to OsmAnd and it is hard despite experiences with other navigation apps. For the third time, I lost the last part of a recorded track. It was the part from the last indicated stop. I would like to disable the display of stops, but the loss is the bigger issue. The track was shown completely, before I stopped the recording. Perhaps the last part disappeared when I edited the file name. I'm not sure. Is there any local buffer file? Sorry for this poor report. I have not figured out yet, how this happens. Thanks anyway.

Steps to reproduce

Record a track with track visibility enabled.

Actual result

Last part from last stop is missing in track.

Expected result

Get the complete recording as you see on the screen until last part disappeared.

Your Environment (required)

WARNING Crash-Logs MAY contain information you deem sensitive.
Review this CAREFULLY before posting your issue!

OsmAnd Version: 4.9.10
Android version: 13
Device model: Lenovo Tab M 8 (4th Gen)
Crash-Logs: ?
@sonora
Copy link
Member

sonora commented Jan 30, 2025

There is a switch in the Trip recording Plugin's Settings called "Auto-split recordings after gaps", perhaps that's what you mean by "disable the display of stops".

Regarding incomplete recordings: The track is written to a database, force-stopping and restarting the app may make the track complete.

Sounds like an elusive bug, though, have not succeeded to reproduce yet. Perhaps it is related to the above gap setting, I usually have it to 'off'.

@RealVegOs
Copy link
Author

THX! I never activated splitting after gaps. Will try your suggestion to stop the app as workaround. With "display of stops" I mean that an icon is shown where I stopped. I would like not to show an icon. This could be extremely annoying on a photo tour. Beside that my SLR camera writes GPS data into each shot. If I find out more about the disappearance of the last part, I'll let you know here. Good to know that there is a database and waypoints are not lost.

@yuriiurshuliak yuriiurshuliak added the Observed Needs more clarification, feedback, or research label Jan 31, 2025
@RealVegOs
Copy link
Author

I can confirm that no waypoints are lost when the the end of track or the whole (if short) suddenly vaporizes. The track comes back by forcing the app to stop as suggested above or by playing with views. E.g. "show track on map" etc. Still don't know, what triggers the disappearance. Perhaps it is ending recording even without editing the file name but it happens randomly.

If street names flicker is this a hint to update maps?

@sonora
Copy link
Member

sonora commented Feb 1, 2025

Flickering street names,seems worth a separate issue. You can also try changing the 'Map rendering engine', a setting in "OsmAnd settings", probably you are using Version 2 (which is capable of 3D view), but I find that on many devices Version 1 works better. Perhaps this also solves the track appearance issue at hand.

Related: It seems that we enable "Auto-split recordings after gaps" by default these days? Several users are annoyed to see all these icons in their recording, I suggest we may want to change the installation default for this setting to "off"?

@RealVegOs
Copy link
Author

I used rendering engine 1 first, but I think 2 works better for me. With 1 the recorded track was not displayed when the starting point was out of the screen. There is already an issue filed by somebody. Your hint to force the app to stop helped me a lot. Now I do not try to use the editor to complete the track. I always export tracks and view and save them on my pc. For me this is a glitch but no big issue.

@sonora
Copy link
Member

sonora commented Feb 2, 2025

The 'starting point outside viewport' related glitch has meanwhile been fixed, will be gone in next release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Observed Needs more clarification, feedback, or research
Projects
None yet
Development

No branches or pull requests

3 participants