DataFields : 367 RunFields

Update 2015-09-15

Have started to upload V2 of the 367Bike and RunFields to the App store.
367BikeFields is Live.
367RunFields is Live

The new version adds TimerTime, also adds the seconds on the timer once you reach > 1hr. (I'm told that seeing seconds is especially important for runners)

Note for all : Please refer to the app store for the latest in the NEW direction the app/datafield is going.
Go PRO! GO UnLimited!!

  • TOD (Time Of Day)
  • Timer Time
  • Pace 10s / Current Speed (in KM or Miles)
  • Cad
  • HR
  • Dist (either Miles or KM)
  • Avg Pace / Avg Speed


Many Thanks to SimonMcMullen for his code guidance.
Many Thanks to TORSTEINVH for his guidance on how to make an moving average (tho it's still a hack and not pretty code)


367RunFields-VA - http://apps.garmin.com/en-US/apps/0d38cc9d-78d9-46e1-85d4-9b4b2742a4bc
367RunFields-F3 - http://apps.garmin.com/en-US/apps/01ff5476-3b6a-499f-9253-404724f5d642
367RunFields-920 -http://apps.garmin.com/en-US/apps/f7daa40d-bc9d-4456-ad12-65cf43e5782c


367BikeFields-VA - https://apps.garmin.com/en-US/apps/8469d7cf-07af-4046-9a5e-c9c6345b219a
367BikeFields-F3 - https://apps.garmin.com/en-US/apps/617b1adc-c42e-46e2-aac9-1ab56618971e
367BikeFields-920 - https://apps.garmin.com/en-US/apps/e2e00ba3-452b-4798-8b5d-f272fc7cbe63


For Full configurability of all the fields in the 4 datascreens offered, take a look at these apps
F3 : https://apps.garmin.com/en-US/apps/b...9-2fcfefdf466d
VA: https://apps.garmin.com/en-US/apps/1...1-937d99f95fea
920: https://apps.garmin.com/en-US/apps/0...b-35c893b25356

Also has :
Time in zone.
Virtual partner

Generic Recorder: - for other activity profiles which are not Weight Lifting / Running and Biking
https://apps.garmin.com/en-US/apps/b...a-23afd94009c4
  • Thank you for your input.
    I am working within the confines and terms of the Garmin App Store.

    We're nkt even allowed to talk donations or payment here.
  • Hi - I've updated the apps on the store to show an additional line on remaining session time for the F3 and 920 & Epix. I have not found a way to do it on the VA as there is severe space constraint.

    From an updating perspective, as I believe you auto-updated, none of the app's description would be visible. (In addition to that, experience has shown that not many people actually read the descriptions until something drastic happens)

    Datafields are limited to 16kb of memory and thus severely limits what can be shown (UI wise) w/o adding more code size (and memory).
    (I've had to rework the EPIX one multiple times just to get it to function honestly)

    The developer's email is there to facilitate further queries for items as stated in that line.
    I am doing what I can to navigate the terms of the store and the forums

    Thank you for your time. I apologise for any inconvenience it may have caused.
  • Just poor form....

    I loved this data field, but making it for pay and not announcing that you are crippling it if people don't pay you just seems inappropriate. It doesn't matter what you charge, making it ransomware is lame....gonna stop using it. The right thing to have done would have been to request donations if people like the product -- NOT shutting it down for longer runs.

    Sorry. You should always be upfront and honest.

    That's my opinion.

    Bests,
    T
  • hi,

    I'm sorry for the inconvenience. It was in the App Store description ( did u miss that?)

    I also presume you liked the product? If you were the <10 donators of the >55,000 people who uses this, you would have gotten the email to get the PRO version at no cost.
  • Poor form

    Well, it's not going to stay at 55,000 users for long I predict. The cost isn't the issue. Would gladly pay for it. It's a great field. It's that without paying for it you get crippled software that dies on you mid run without notice (at least that's what happened to a few people it seems)...that alone would upset lot of people. I think that's a pretty awful thing to do. It's about the approach, really. Again, just my $0.02. If you had said something like "I put a lot of work into making this a great product, and if you use it I would really appreciate a donation"...it might have gotten you more $$ or it might not, but it would not have upset your user base.
  • Hi,

    Thank you for your input. It is very appreciative.
    I am working based on the confines of what's currently I can achieve on this platform and its SDK and the 16kb memory available.

    Thank you for your patronage and you are right. I did put in an absolute lot of work in this product which netted 10 donators who would have gotten the email on the PRO upgrade and the announcement. (And we are not allowed to also solicit or talk about payment or donations on the forums)

    As stated in the App Store description, we have no means to communicate to users beside the store descriptions.

    Again - I apologize for the inconvenience. Do read the App Store description as that is the only form of communication to end users.
  • Former Member
    Former Member over 9 years ago
    Finkelt, this developer is working within the constraints provided by Garmin. I too was a little annoyed when I reached the "usage limit" after just a few miles into a run. I would recommend maybe extending the max session time a little. Anyhow I was able to quickly activate other data screens (Garmin still provides access to menus during a run), the watch continued to record, and no data was lost. So it was just a minor inconvenience. Garmin hasn't given him any way to communicate with us, other than the app page. I believe if you had the version which has a limit you would have had to have visited that page. Unfortunately you chose not to read what's there (as probably many others will), but I believe the app developer is just trying to work with the tools Garmin has given him.

    FWIW I missed it too. A suggestion to the developer: put "limited" or "trial" in the app title.
  • How can I upgrade to pro version? Can anybody tell me? Thanks!
  • Unfortunately you chose not to read what's there (as probably many others will), but I believe the app developer is just trying to work with the tools Garmin has given him.

    FWIW I missed it too. A suggestion to the developer: put "limited" or "trial" in the app title.


    I've change it all to show up as TRIAL.
    Also spent the last 10hours debugging and trying to get the session ending time on the VA. Darn datafield. Keep on giving out of memory errors on 1.1.4 SDK. And there's no attention module that can be used on this datafield, I can't signal to the user either thru a tone or a vibrationl that the session end time is nearing it's end. And to ensure things are OK, I need to keep the simulator running until the session times out.

    So many negative comments. Maybe I'll go jump into the river.