Resume later - backpacking

Former Member
Former Member
I am planing on taking my fenix5 on a multi day backpacking trip. I will create a route before the trip and load it on the watch.

Will it be better to pause the activity each day and do resume later. When I wake up the next day, I can resume the activity. Any issues with this? It doesn't get lost with so much time in between?

Or is it better to create a route for each day, and save each day separately?
Or if I have one course and save each day separately will it know where I am at along the course each day?

I would rather have a single activity for simplicity's sake in garmin connect.
  • It is just my preference, but I would go with one route for whole trip and separated track records for each day. Regarding the route, you load it up every day and watch will catch up from your current position. And for tracks, I suppose you spend some time camping, so I would really record just the actual activity. It can be merged together with a proper SW anyway, if you would like to see it as a whole.
  • I would be careful with activity resume, unless you tested, that it is working as expected. With my Fenix 3, I lost the rest of the GPS data after resuming for some trips. You have been warned.
  • As I reported in the F5X forum the Resume Later is a problem with loaded courses. When you resume the activity the Fenix does not pick up the course route where you left off but tries to reset to the begiining; that is the lower information field instead of saying distance to end (or next waypoint) gives you distance to the begining.

    You can of course still see the course track but all TBTs and waypoint information will not show, just that ever increasing distance away from the start. It is a bug that has been reported.

    Despite the navigation feature failing on resumeing an activity the activity itself is recorded correctly.

    The only way around this for now (until Garmin fix the bug) is to have a number of course tracks for ech part of your whole route and record each as a seperate actviity. You can always merge them later with tools available on the web.
  • The only way around this for now (until Garmin fix the bug) is to have a number of course tracks for ech part of your whole route and record each as a seperate actviity. You can always merge them later with tools available on the web.
    You should not have to have a separate course for each part. My experience is that if you start a course and are part way along, it simply jumps to that position rather than expecting you to start at the start.
  • You should not have to have a separate course for each part. My experience is that if you start a course and are part way along, it simply jumps to that position rather than expecting you to start at the start.

    Is that your experience with the 5 series? If so which one?

    My Fenix 3 certainly did jump to the point on the course where I was located.

    But as I said, with the Fenix 5X it does not; it tries to send you back to the start.
    I would be surprised if this was not true of other 5 series Fenix.
    Hopefully this bug will be fixed soon.
  • Former Member
    0 Former Member over 7 years ago
    Sounds like I should not use the resume later function then. I will have to test, but Im hearing it correctly that I can have the entire trip as one course loaded on the watch and end and save the activity every day, and the next day start the same course again and it knows where I am on that course?
  • Sounds like I should not use the resume later function then. I will have to test, but Im hearing it correctly that I can have the entire trip as one course loaded on the watch and end and save the activity every day, and the next day start the same course again and it knows where I am on that course?

    Not quite.

    If you have the entire multi-day course as one on the watch then no, with this current version bug (on my F5X and I assume all 5 series) when you resume the activity or even if you start a new activity each day then it will not pick up the route where you left off and restart. It tries to send you back to the start; that is your navigation fields and TBTs are screwed; although it will not effect your activity recording and you can still see the pre-loaded course track.

    If it were me (and Garmin have not fixed the bug before embarking) and I know where I was ending each day, then I would compile a course for each day. So then I would start course navigation for each of these days and save each day activity as a seperate record.

    During the day I would stop the activity (for lunch or whatever) but not resume later, just leave paused (making my stops less than 15 minutes to avoid autosave, or resume and pause again until ready to restart).

    If I wanted to have a single track of the whole multi-day I would just merge those multiple fits with the fit compiler in FIT File Tools (https://www.fitfiletools.com/#/top).

    Good luck.
  • Former Member
    0 Former Member over 7 years ago
    I see. thanks. Hope they fix that bug asap
  • I haven't tested it on the F5, but I remember on my Edge 800, when I follow a route and if I interrupt it somewhere in the middle and later start a new activity it sometimes sends me in the opposite direction (back to start). But once I move several tens/hundreds meters in desired direction it starts to show correct navigation instructions and all data fields are fine too.

    Couldn't be that the case for F5 too?
  • I haven't tested it on the F5, but I remember on my Edge 800, when I follow a route and if I interrupt it somewhere in the middle and later start a new activity it sometimes sends me in the opposite direction (back to start). But once I move several tens/hundreds meters in desired direction it starts to show correct navigation instructions and all data fields are fine too.

    Couldn't be that the case for F5 too?

    I have stopped navigation in response to this bug, the last time on a 9 mile hike after I resumed later after stopping for refreshments. I can't recall after how long, perhaps 1.5 miles. I will see next time I go out but if it does resume the correct track direction after some interval that is still unacceptable behaviour. This certainltly is not the case with the Fenix 3 so they can get the coding correct. With luck that will be in the next sw release.