Fields of gold

Great job! Thank you!

How many bars are shown in the graph? Wouldn't it be possible to set the visible time for the hole graph instead the seconds for one bar? Nearly the same for the Virtual runner. It is ok tho set the pace in s/km but it would be much nicer to set it in min:s/km.

In the settings I found a little mistake - two settings have the same text "Sixth Field". I think the first of them should have the name "Fifth Field"?!

@WEBVAN: I think the field you choose by "Pace" instead of "Average Pace"

Nice field, thanks ! Looking forward to being able to replace "Average Pace" by Garmin's standard "Current Pace" (I saw your explanations about it.

Also the name of the Field is a bit odd, ah now I see it's been updated to "Fields of Gold" now ;-) I'm getting a CIQ crash though when I select it on my FR235 now?

HI Webvan,

It should work on a FR235 (it is basically a 230 with an optical HR and it is really well tested with the 230). What may happen here is that I detected a problem whem the application is set up from Garmin Connect Mobile. I've uploaded a new version that should solve that (it solves it on my 230).

If it still crashes, please let me know. Debugging for the real hardware on this platform is not very developer-friendly.

Best,
Kurt.-

Great job! Thank you!

How many bars are shown in the graph? Wouldn't it be possible to set the visible time for the hole graph instead the seconds for one bar? Nearly the same for the Virtual runner. It is ok tho set the pace in s/km but it would be much nicer to set it in min:s/km.

In the settings I found a little mistake - two settings have the same text "Sixth Field". I think the first of them should have the name "Fifth Field"?!

@WEBVAN: I think the field you choose by "Pace" instead of "Average Pace"

Hi Cluni,

Glad that you are enjoying it.

The graph is showing 54 bars. Yes, it would be possible to set the visible time for the hole graph, but it has to be a multiple of 54 :). I could put a select with 54s, 1m48s, 2m 42s and so on.... but maybe it would look a bit weird. I will think about it. What do you think?

Definitely it would be nicer to set the pace in s/km (or s/mile I have to implement support for miles). I will try to do that in next version. The fact is that I am pushing the limits with this apps. There are only 16 Kb of memory for data and code, and there is almost no space left for doing anything more but I think that something like that is not going to take much more.

You are right about the wrong "Sixth Field". I will fix it in the next version. Thanks for reporting.

Best,
Kurt.-

HI Webvan,

It should work on a FR235 (it is basically a 230 with an optical HR and it is really well tested with the 230). What may happen here is that I detected a problem whem the application is set up from Garmin Connect Mobile. I've uploaded a new version that should solve that (it solves it on my 230).

If it still crashes, please let me know. Debugging for the real hardware on this platform is not very developer-friendly.

Best,
Kurt.-

Did the update but it's even worse now as the watch reboots when I select the FOG datafield!

Did the update but it's even worse now as the watch reboots when I select the FOG datafield!

I am sorry to hear that. I have also another report that is not working on 235 (as well as Fenix 3). I can say that it works on 23 (because I try it myself), and also it is reported to work on 630. Unfortunately in the simulator everything works fine for any model, but seems that each hardware behaves a bit differently than the others and this makes the development notably difficult and cumbersome, specially if I have no way to test it on real hardware.

I assume you are using the last firmware for your watch and the last Garmin Connect Mobile version available (otherwise there is any guarantee that the app is going to work).

The only thing I can do, because I don't own every single model of Garmin watches (and I don't pretend to) is to send you a version of the app with debugging information for you to try and then send me back the log file. If you agree (or anybody else with a 235 or Fenix 3 that wants to collaborate), let me know in a private message where I can send you the file (the form don't allow me to attach files of that type). For now I will retire the app for 235s.

Best,
Kurt.-

I installed the latest version via Garmin Express actually as I've seen problems in the past with GCM.

Would be happy to help to get it working on the FR235 (it did work ok 2 versions ago), feel free to send me a PM and I'll give you my email.

I installed the latest version via Garmin Express actually as I've seen problems in the past with GCM.

Would be happy to help to get it working on the FR235 (it did work ok 2 versions ago), feel free to send me a PM and I'll give you my email.

I just answered your email (and thanks for the help)... but reading this, If I understood correctly, the app was working ok two versions ago (0.9.0 or 0.9.1?) and now is rebooting your watch? It is important for me to know that because up to this moment I only have negative reports on 235 (unfortunately people usually don't tell me when the app works) so I thought that it was not working on ANY 235.

It is not easy debug an app on this platform. I have a report of reboots on a 230. I have a 230 and it works flawlessly. If the watch crashes it does not generate logs, so I am clueless here. I think that when an app crashes it has hit a bug on the host platform (my guess is that apps run sandboxed, they can crash but should not take down the entire system) and that should be addressed by Garmin, because I have no tools to fix that.

Best,
Kurt.-

Yes, two versions ago it worked on the FR235 then the following version crashed and the latest one reboots the FR235 :-(

Yes, two versions ago it worked on the FR235 then the following version crashed and the latest one reboots the FR235 :-(

Mmm... weird. Today I got a report of someone who happily runs the data field on a FR235, so I really am clueless on what's going on. It seems that some people (probably an small percentage) have problems running the app and the watch reboots.

Probably the version that were working on your watch was the first one.The first one was compiled against SDK 1.2.2 while the rest are compiled against 1.2.3, or the last one against 1.2.4. Don't know if that can be relevant. The first version only supported semiround watches (230, 235 and 630) and then I added support for round watches, but anyway the app seemed not to work on Fenix 3 so I retired it but support for round layout is still compiled (and that takes precious memory).

In a future version (coming soon) I will remove any support for round watches and add some goodies (support for imperial units and some fields more). Maybe then it will work in your watch. I will let you know.

Best,
Kurt.-