App: Hiking

https://apps.garmin.com/en-US/apps/39d3b5e8-67db-4517-93a8-5ec485269635

For the vivoactive, FR230, FR235, and FR630 (I don't plan support for other devices)

Please use this thread for questions, etc!

"Hike" records an activity as a hike or walk in Garmin Connect. It also allows you to mark "waypoints" (they show up as lap marks in Garmin connect, so you can see them on that map).

When hike starts, it waits for GPS, and looks for an available HRM and Tempe. At this point, with the up/down key or a screen swipe, you can switch between "hike" and "walk". Then, press "start" to start recording.

The current time, HR and temp (if the sensors are available) is displayed on all screens. While recording, pressing "back" marks a waypoint. To pause or end, press "start again", and you are given the options of "resume", "save", and "discard".

When you hit the start button and get the resume/save/discard menu, you can hit the back button. The menu goes away, and the recording remains paused (it's indicated next to the clock time on all pages). But you can scroll trough the data pages at the time. That way, if you're taking a break, you can sit and look at the current data.

When "paused" is displayed with the time, pressing start again resumes the recording.

There are 5 data screens that you can see when recording (up/down button, or swipe right/left on touch devices) (some not shown here due to forum limits)

The first screen is basic recording info: The time for the activity, the time that recording was active (when paused, this doesn't increase), the distance, and the number of waypoints marked

The second screen shows pace, avg pace, speed, and avg speed.

The third page shows the waypoints you marked. They are shown 5 at a time, and rotate every 7 seconds. They closest waypoint is shown in green.

The fourth page shows elevation data. This is GPS based, and sometime may be off. Elevation, total Ascent, and total Descent is shown.

The fifth page is location information. Your current lat/lon and heading, as well as your starting location lat/lon and the direction and distance back to start. GPS quality is also show, both in text and colors (green is usable or better)




Changes in version 0.12: see https://forums.garmin.com/showthread.php?335082-App-Hiking&p=765691#post765691
  • 6.20? You mean 2.60 of Sensor Hub? (it came out with the 4.20 FW). Have you powered off and on your watch after that? (something weird here and that might help)

    If you did update Hike, go into app settings for Hike on your phone and uncheck the boxes for the HRM and Tempe for now, and see if it then runs.
  • 6.20? You mean 2.60 of Sensor Hub? (it came out with the 4.20 FW). Have you powered off and on your watch after that? (something weird here and that might help)

    If you did update Hike, go into app settings for Hike on your phone and uncheck the boxes for the HRM and Tempe for now, and see if it then runs.


    You were right
    *) 4.20 of course (& 2.60 oHR)
    *) reboot -> everything is fine
    *) w/o disabeling anything

    THANK YOU! I'll do a test-walk during lunchbreak,
  • Former Member
    Former Member over 8 years ago
    Hey,

    I love the app but recently I've been having issues with it when it saves the data. It doesn't track the steps and although it keeps all the GPS and pace etc it seems to be saving it as running. Never had a problem until the last update on the 235 and it isn't all the time it does it.
  • KaiNinaste -

    Make sure you are running 0.14g (you'll see that on the top line of the display), as what you describe sounds like the crash reported by another user. If there's a crash, when it boots back up you are given the resume/save/discard, but for "running" (that's the way the FW works, as "hike" isn't a native app)
  • I've had a couple of reviews that mention a crash on the 23x devices.

    But in reviews, I can't respond or ask questions, so if anyone sees this, let me know in this thread.

    First, check that you are running 0.14g by looking at the top line on the screen (the current version in the store). What can happen is that the update is on queued for you by the store, but may not have yet been installed on the watch. (I had a crash problem in 0.14f)

    If you see the crash, please let me know the FW you are running on the watch, and if you are using a HRM or Tempe (if HRM, is it a band or the OHRM).

    Also, what you were doing when the crash occurred. For example, was when it when you were trying to pause or save a hike?

    When you see a crash, is it a screen that has "IQ!" (hike crashed) or does the watch reboot? (goes back to the garmin logo)

    Thanks in advance!
  • I have a 235 running the 4.20 system version, and using the 0.14g version of Hike.

    I have had 3 crashes with the application, all at the point of attempting to save when finished. The outcome of the crash has always been a reboot of the watch.

    I do have the HRM capture enabled in the settings for Hike, and that would be the built in HRM of the 235. I have not deselected the Tempe option in settings, however I do not have one paired.

    Let me know if I can try anything else out to help with this.

    John
  • Thanks John! I suspected it to be related to the menu and been looking at things the last couple days. I should be posting an update to hike later today that resolves this.
  • 0.14i is in the app store

    Hopefully, this fully fixes the memory crash some have seen on 23x devices!

    There is one new feature. With this version when you are "paused", by default, the watch will vibrate every 5 minutes. This is meant as a reminder, so if you start moving again and forget to "resume", you'll look at your watch to see why it vibrated, and resume.

    You can change it to every 10 minutes, or "never" with app settings.
  • Hopefully, this fully fixes the memory crash some have seen on 23x devices!

    There is one new feature. With this version when you are "paused", by default, the watch will vibrate every 5 minutes. This is meant as a reminder, so if you start moving again and forget to "resume", you'll look at your watch to see why it vibrated, and resume.

    You can change it to every 10 minutes, or "never" with app settings.


    Had two "walk"s today with this new version. and it didn't crash. thank you.
    FR635, fw4.2, gps3.00, oHR2.60, but no tempe today, had to wear my "other" shoes.
  • Glonass

    Is there any way to turn on GLONASS to get at more accurate fix?