Data field: Snapshot

Yup, as soon as a setting is changed and 'done'd, it crashes.
Edit: there is a (double) post with all requested info waiting to be approved...

Yup, as soon as a setting is changed and 'done'd, it crashes.
Edit: there is a (double) post with all requested info waiting to be approved...

OK thanks for letting me know and the info. Let me check and i'll figure it out. It may be that i'll need to update the SDK compiler version for v3.30 on the watch.

Yup, as soon as a setting is changed and 'done'd, it crashes.
Edit: there is a (double) post with all requested info waiting to be approved...

Hi NeonPigeon. I'm not able to reproduce the crash, which is frustrating. What i've done is recompile the field with the latest (non-beta) SDK, since there might be something in the 3.3 firmware that depends on having the latest SDK that i'm unaware of.

Have a look for the update and let me know if this fixes things.

Otherwise i'll have to did deeper, although i'm not sure what else i can do. There's been you and one other report the crash, yet 400+ downloads (although admittedly only a fraction of these are probably using the field regularly). The problem might be a corrupted file on your watch which would require a reset of your user settings. Although i certainly don't want to recommend that right now.

Anyway, let me know if the re-compile helps. Hopefully.

Awesome datafield! Thanks.
Could you possibly ad option of custom pace (1-30sec)?

For me, a datafield with: current pace, lap pace, avg pace, custom pace, hr, distance, tod and elapsed time would be a dream come true.

Keep up the great work!

Hi NeonPigeon. I'm not able to reproduce the crash, which is frustrating. What i've done is recompile the field with the latest (non-beta) SDK, since there might be something in the 3.3 firmware that depends on having the latest SDK that i'm unaware of.

Have a look for the update and let me know if this fixes things.

Otherwise i'll have to did deeper, although i'm not sure what else i can do. There's been you and one other report the crash, yet 400+ downloads (although admittedly only a fraction of these are probably using the field regularly). The problem might be a corrupted file on your watch which would require a reset of your user settings. Although i certainly don't want to recommend that right now.

Anyway, let me know if the re-compile helps. Hopefully.

Yes - unfortunately very few downloads translate to reviews, let alone people actually knowing they can change settings, let alone going on to a forum. If the problem is confined to a single model - you might only get a couple of comments.

Thanks for the update - but it still has the same issue. It crashes differently now though. Previously, as soon as you went back to the layout preview (after changing a setting), it would give the crash screen. Now, when you first reopen the layout view - it looks like it would before the settings are changed (I tried to change the inversion and the lap pace to current pace) - i.e. nothing seems to happen.When you select something else (e.g. snapshot 2) and then re-select the snapshot 1 field, it immediately reverts to the default timer field. If you do the re-selection again, you get to see the crash screen.

All other similar data fields, apps and faces are working normally.

Ha! The settings can be changed without issue in the express program. The issue is only in the phone connect app. Don't know if that helps...

Thanks!

Ha! The settings can be changed without issue in the express program. The issue is only in the phone connect app. Don't know if that helps...

Thanks David. There's actually been a major SDK update recently and i've recompiled the field for it. However the update is so significant that it's quite unstable right now (lots of developers are having issues with it breaking their watch faces, fields, etc). As soon as they've smoothed that out i'll be pushing a new version of Snapshot that i'm hoping will fix the settings issue once and f

An alternative (which i can't test because it all seems to work for me) is to identify the settings file on the watch itself (once mounted on your computer) in /Garmin/APPS/SETTINGS/ (may have a different name on each watch, not obvious), then uninstall the field. Check to see if the settings file was also removed. If not, delete it. Then reinstall the field.

If that works it will confirm my theory that for some people the settings file itself has become corrupted and needs to be manually removed.

Unfortunately, the data fields are not working on the 735xt with the current or previous version of the garmin software (since late June). It does not matter if the settings are not altered or not. Or if I use the PC or phone app. The field displays the error IQ warning after the activity is started.

The settings files are removed after removing the field. The error returns once the field is loaded again.

Unfortunately, the data fields are not working on the 735xt with the current or previous version of the garmin software (since late June). It does not matter if the settings are not altered or not. Or if I use the PC or phone app. The field displays the error IQ warning after the activity is started.

The settings files are removed after removing the field. The error returns once the field is loaded again.

Hi David.

Sorry to hear you're having problems. The field works fine on my watch and i've heard no other reports of problems, so this seems to be something unique to your situation it seems. The first thing i'd suggest is to remove and reinstall it, then power cycle the watch. But you've already done that without success. :(

All i can think of is that perhaps you have a corrupt settings file (or similar) on the watch that doesn't get deleted when the app is removed (something a little more hidden?). You could try a factory reset to totally clear these out (googling should direct you to the relevant information). It sucks that this may be the only solution for you though. But outside of that I'm not sure what else i can do to help.

Please feel free to contact me through the "contact developer" button on the app webpage and perhaps we can troubleshoot it further.

Regardless, let me know how you go.
Darren

The relevant settings file definitely disappears when 'uninstalling' the app. Will try a factory reset sometimes. The dual apps are great.