Tracklog lost
-
Hi, today after a ride of over 300 km during which I had started the tracklog, once I reached my destination I, as usual, stopped the tracklog and clicked on the save icon. However, an error appeared stating that it was not possible to save the tracklog due to lack of connectivity (which was actually available and working properly) or because the file was missing.
I tried 3–4 times but always got the same negative result. Then, about 10 minutes later, when I opened the app again to try saving it once more, the tracklog had disappeared!Is there any way to recover it? There were uncharted roads in it that I need for an event.
Thanks. -
Hi, today after a ride of over 300 km during which I had started the tracklog, once I reached my destination I, as usual, stopped the tracklog and clicked on the save icon. However, an error appeared stating that it was not possible to save the tracklog due to lack of connectivity (which was actually available and working properly) or because the file was missing.
I tried 3–4 times but always got the same negative result. Then, about 10 minutes later, when I opened the app again to try saving it once more, the tracklog had disappeared!Is there any way to recover it? There were uncharted roads in it that I need for an event.
Thanks.@Manzo91 You could check to see if it is in Uploaded tracklogs. Go to your account page and scroll down to Uploaded tracklogs, if it isn't there then sadly it is gone forever.
Always willing to help if I can.
Triumph Tiger 1200 XRT called Tina.
MRA Navigation Next and SilverFox BJ8 -
@Manzo91 You could check to see if it is in Uploaded tracklogs. Go to your account page and scroll down to Uploaded tracklogs, if it isn't there then sadly it is gone forever.
@Nick-Carthew i check, but there isn't. oh damn, i hope it's the only time that ths appens, otherwise it's a big problem.
but what file it's missing? -
Hi, today after a ride of over 300 km during which I had started the tracklog, once I reached my destination I, as usual, stopped the tracklog and clicked on the save icon. However, an error appeared stating that it was not possible to save the tracklog due to lack of connectivity (which was actually available and working properly) or because the file was missing.
I tried 3–4 times but always got the same negative result. Then, about 10 minutes later, when I opened the app again to try saving it once more, the tracklog had disappeared!Is there any way to recover it? There were uncharted roads in it that I need for an event.
Thanks.@Manzo91 did you check the upload queue in settings in "Uploaded tracklogs"?
Sometimes, if the Internet connection is bad or absent, the track couldn't be uploaded. You will see it in the upload queue indicated by special icon: arrow as circle...Nothing is impossible ;-)
In past: GARMIN Zumo 210->GARMIN Zumo 395->GARMIN XT=> now: DMD T865-X + MyRoute-App, LocusMaps, OsmAnd.
In past: GARMIN MapSource ->GARMIN BaseCamp->Tyre->Kurviger->Calimoto=> now: MRA-Routplanner. -
@Manzo91 did you check the upload queue in settings in "Uploaded tracklogs"?
Sometimes, if the Internet connection is bad or absent, the track couldn't be uploaded. You will see it in the upload queue indicated by special icon: arrow as circle...@Guzzist nope, the list is empty now...
-
bad luck
-
That's why I would like the option to automatically save track logs to local memory independently of any action on the screen. It could work like video recorders do: for example 10 files could be stored in memory and the oldest ones could be overwritten.
-
That's why I would like the option to automatically save track logs to local memory independently of any action on the screen. It could work like video recorders do: for example 10 files could be stored in memory and the oldest ones could be overwritten.
@Stanisław great idea! so there would be no risk of losing the tracks just recorded.. I hope that the developer implement this option.
-
That's why I would like the option to automatically save track logs to local memory independently of any action on the screen. It could work like video recorders do: for example 10 files could be stored in memory and the oldest ones could be overwritten.
I too lost my tracklog today. It was a long track, with photos taken during the ride. Not uploaded for some reason, and not in queue in the app.
@Stanisław said in Tracklog lost:
That's why I would like the option to automatically save track logs to local memory independently of any action on the screen.
Yes, The app needs this in order to be trusted. Just discarding data because of some temporary Internet connectivity problem is a call for improvement.
-
Maybe it would be better if it auto saved as it was recording and not leave it till the end and be internet dependant ....
-
Maybe it would be better if it auto saved as it was recording and not leave it till the end and be internet dependant ....
@HighPeakRider the purpose of such a log is that you've got the whole trip. Do it must be at the end and by design with an active internet connection. No worries is that's nog available it will stay in the upload queue
-
no point it being the whole trip if the system loses the data as people are indicating!!!!!
Other apps perform saves as they go so the data isn’t lost, it’s basic end to end application design….You wouldn’t write a document and leave the saving till the end and risk losing what you wrote, you would save your work as you go……
-
no point it being the whole trip if the system loses the data as people are indicating!!!!!
Other apps perform saves as they go so the data isn’t lost, it’s basic end to end application design….You wouldn’t write a document and leave the saving till the end and risk losing what you wrote, you would save your work as you go……
@HighPeakRider I have seen odd behaviours at the end of a trip & messages that there are problems with the log.
Fortunately I have not lost any as I navigate in offline mode all logs have still been in the upload queMy feeling is that the log problem is secondary to an issue of the navigation failing at the end of the trip & crashing the app.
I think the root problem may be to do with the introduction of the stop navigation switch at the end of journey.
The log issue never used to happen.
