New Forerunner 920XT Version 3.03 Public Beta

Our FR920XT team released a new public beta today, available here:

http://www8.garmin.com/support/download_details.jsp?id=7627

I know most of you have been waiting for gesture support, and this release makes it available!

Another nice feature that we've made added is CIQ logging, which can help you with debugging on the device. Here's how you use it:

  • Create /GARMIN/APPS/LOGS on the device
  • Inside the LOGS directory make a CIQ_LOG.txt file

This will log out console messages to the CIQ_LOG.txt file. You can also create a separate log file for each app, where any Sys.println statements called within the app will be written. For example, if your app is called MYAPP.PRG, just create a MYAPP.TXT in /GARMIN/APPS/LOGS.

Have fun!

-The Connect IQ Team
  • Technically, this would work for any PRG as long as the author includes System.println() statements in the app. I would generally discourage leaving this "debug" code in published versions of your app, but it would do what you want. The purpose behind the println logging feature is to provide an additional resource for debugging during development, and it may be something that is only included in our beta builds. The println logging specifically can cause apps to perform poorly (the UI can be choppy or exhibit lag), and we'd prefer customers avoid that experience. :) We're looking at providing ways to write custom data to be written to FIT files, which will be a better solution for what you intend.
  • Thanks, understood. I will wait and hope that eventually data fields will be able to write custom data to FIT files.
  • Former Member
    Former Member over 10 years ago
    We're looking at providing ways to write custom data to be written to FIT files


    Does that include making that information viewable in Garmin Connect, or does a developer than need to build another application for a user to be able to view it and spend $5000,- for a license to get the info to that other application?
  • Is there a way to disable 'exit low power mode'?

    Also what difference does having the exit low power mode make typically to the battery life?
  • Former Member
    Former Member over 10 years ago
    Does that include making that information viewable in Garmin Connect, or does a developer than need to build another application for a user to be able to view it and spend $5000,- for a license to get the info to that other application?


    The goal would be to allow custom data to be written to the files, and display it on Garmin Connect. There are, however, a lot of pieces we need to work out to make that happen, so this isn't a "next release" kind of feature.

    I am not an expert on how the GC license works, but I believe the primary feature of the license is having direct access to your users FIT data. (i.e. The FIT files are uploaded directly to your own web service instead of to GC.)
  • Former Member
    Former Member over 10 years ago
    Is there a way to disable 'exit low power mode'?

    Also what difference does having the exit low power mode make typically to the battery life?


    At this time, it is not possible to disable the exit low power gesture on watch faces. The impact on battery life depends on use, but should be negligible for typical use. If the user looks at their watch every 10 seconds and forces the device to be perpetually awake, it will impact battery life significantly.

    Impact will be kept to a minimum if you do not use timers and animations during the wake time.
  • Brian, Any clues about when we can expect to have a release with the Communications module enabled for the 920xt?
  • At this time, it is not possible to disable the exit low power gesture on watch faces. The impact on battery life depends on use, but should be negligible for typical use. If the user looks at their watch every 10 seconds and forces the device to be perpetually awake, it will impact battery life significantly.

    Impact will be kept to a minimum if you do not use timers and animations during the wake time.


    Ok, but I have to redraw whole watch face if I want to avoid residues of popups and so no. There should be any flag in View API - for example isSuppressHighPowerMode()..
  • I apologize for any ambiguity about app and widget support availability in 3.03. Since these devices are in the hands of customers already, we didn't want people thinking apps and widgets are good to go--but I confirmed with the 920 team this morning, and we do want you developers testing out the apps and widgets. There are already some issues we have identified, but please report anything you believe is a bug.

    The fact that the connect IQ store now has apps and widgets available, and reports them as compatible with the 920XT will make people think they are good to go now. I only found out to the contrary when I downloaded an app and a widget and could not find how to access them. I posted a forum comment and was told that I needed the 3.03 beta firmware in order for them to work. This is certainly not clear anywhere, and even the beta firmware post itself and the description of the changes makes no mention of this. Given other peoples comments, I do not think I am alone.
  • The fact that the connect IQ store now has apps and widgets available, and reports them as compatible with the 920XT will make people think they are good to go now. I only found out to the contrary when I downloaded an app and a widget and could not find how to access them. I posted a forum comment and was told that I needed the 3.03 beta firmware in order for them to work. This is certainly not clear anywhere, and even the beta firmware post itself and the description of the changes makes no mention of this. Given other peoples comments, I do not think I am alone.


    Please release new 920XT firmware with App and Widget support as soon as possible... We really, really need it...