This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Firmware 18.54 Affected Backcountry Ski Activity

I know, I know, the first gen Instinct/Solar doesn't come with the Backcountry Ski activity. This is a travesty. There's no reason Garmin can't release this for the OG Instinct. Leaves a bad taste in my mouth for sure.

However, I got the file over the summer and dropped it into the appropriate folder on my watch. Did a test, worked fine. Did a tour in November, worked fine. Did the update to 18.54 over the holidays. Went out to tour today and it was acting wonky. I'd go for a bit and all of the sudden, distance and vertical would get hung up. Time was still running, HR still working, but distance and vertical were stuck. Once, I saw it adjust, but for the most part, just stuck. Very similar to what's being described here: https://forums.garmin.com/outdoor-recreation/outdoor-recreation/f/fenix-6-series/255346/strange-elevation-profile---ski-touring-activity

Just tried taking the file off the watch and reloading. We'll see if that works next time I get out. Really, Garmin just needs to make the activity available on the gen 1 Instinct and support it in future firmware updates.

  • The Instinct/Instinct Solar - both watches are part of the first generation for the Instinct series and were released 5+ years ago. Their memory was designed around what was commonly found across our current generation outdoor watches at the time. The reason you won't see all of the APPS that are included in the Instinct 2 series, is due to their 16MB of memory in the 1st generation vs. 32MB in the Instinct 2 series generation.

  • Any ideas as to why it worked pre 18.54 update vs after? Or if it's a memory issue, can I delete other activities I don't need/want?

  • There is more to an activity than only the APP profile name itself. IE: There are unique OHR algorithms that will sometimes be part of an activity. It is complicated.

    I am sorry, but there is no answer when a workaround is used since our engineering team has not thoroughly tested what happens when a newer generation series APP is copied to an older series. We can make no promises or guarantees on the behavior that will result.