Data Field : Single Field (Legacy : Single Run Field)

*** LATEST VERSION : Single Field ***

Link: https://apps.garmin.com/en-US/apps/1d406424-eec1-4155-85f6-24de6c9611e4

Permission Requirements: User Profile (this is needed to get the HR zones), FIT Recording (used to record snacks earned)

Description: Review app store page for most recent and updated information about the field.


*** OLDER VERSIONS ***

NOTE: Legacy versions support devices which are still currently working and links are found here.

Single Field : https://apps.garmin.com/apps/640d46dd-12db-44d2-acfa-cb7eb9e840b7 (Legacy)

Single Run Field : https://apps.garmin.com/apps/a520cc32-75b2-4b19-a97d-1079b931dc3d (Legacy)


Please use this thread to discuss the single data fields. Links to other support resources for these data fields are listed here:

  • Former Member
    Former Member over 9 years ago
    The SDK at this point does not support this data but it has been requested quite a bit so I am sure they are aware people want it. If it becomes available I will add it as a selectable option but custom coding something isn't going to work due to memory constraints. I will add it to the list of known requests.


    Thanks for the explanation. It's much appreciated.
  • Heart Rate Zone colors based on Heart Rate Reserve

    Would it be possible to enter your resting heart rate and max heart so the zone colors can be based off of heart rate reserve instead of max heart rate?
  • Former Member
    Former Member over 9 years ago
    Apologies if this has been requested before, but.....ascent in feet. As a trail runner, would LOVE to have this. Preferably either at the top next to the time, or replace the "GPS" field at the bottom. Thanks for a great data field.
  • *** NOTICE *** : Upcoming HR Zone Changes

    *** NOTICE ***
    Due to all the variations that people want to see with heart rate ranges, the data field will be changing to use BPM defined ranges. This will require people with an already installed version to alter their settings. This hopefully will give people more flexibility when using the field and provide a way to guarantee it matches the ranges defined in Garmin Connect. Once installed, if anyone notices a issue comment back here since this required some code changes.
  • Former Member
    Former Member over 9 years ago
    Installation.

    This looks great, however I am having major problems trying to install. I only see one option for the layout and that's for 4 fields. Am I missing something? I'm using software version 6.9 on a Fenix 3.

    Thank you.
  • This looks great, however I am having major problems trying to install. I only see one option for the layout and that's for 4 fields. Am I missing something? I'm using software version 6.9 on a Fenix 3.

    Thank you.


    After the data field has been installed, it can be configured following these steps:

    Hold UP.
    Select Settings > Apps.
    Select the activity to customize.
    Select Data Screens.
    Select a data screen to customize.
    Select an option:
    Select Status to turn the data screen on or off.
    Select Layout to adjust the number of data fields on the data screen. <== on this screen scroll up/down till one field is shown
    Select a field to change the data that appears in the field
  • Former Member
    Former Member over 9 years ago
    "- activity timer or elapsed time based on user settings"

    What is the difference between the two?


    Btw data screen is great :)
  • "- activity timer or elapsed time based on user settings"

    What is the difference between the two?


    The explanation from the Garmin manual explains it best:

    Elapsed Time - The total time recorded. For example, if you start the timer and run for 10 minutes, then stop the timer for 5 minutes, then start the timer and run for 20 minutes, your elapsed time is 35 minutes.

    The activity timer value would not include the 5 minutes the recording was stopped for. Hope that helps explain it.
  • In the CIQ app world, here's the difference between elapsedTime and timerTime at the code level. You'll see this with real devices, but not in the simulator BTW!

    elapsedTime, is the time since the session was first created/started, and keeps incrementing even if you "stop" the recording (doing a "pause").

    timerTime is the time that the activity is recording and stops when the recording is "paused" and doesn't change until you "resume" (do a "start" again in the code) (this is how I detect a "pause" in a DF - timerTime doesn't change!). In Hike, I display them as "Elapsed Time" (elapsedTime) and "Recording Time" (timerTime)

    "moving time" in GC is a bit of a mystery to me, as it might be "movement while recording"....
  • Former Member
    Former Member over 9 years ago
    Ahh thanks, it should have been clear to me :D

    So elapsed time is better for races, to be sure in case if I stop it by accident, it happened before that I pushed stop button instead of lap button.
    And timer perhaps better for workouts.