Acknowledged
CIQQA-4660

Firmware applies Auto Pause to a CIQ ActivityRecording session (fenix 8 SW 22.41, Forerunner 570 SW 17.33)

Environment

- Devices: fenix 8 - 51mm AMOLED (006-B4536-00), firmware 22.41, paired with iOS. Forerunner 570 - 42mm (006-B4574-00), firmware 17.33, paired with Android.
- App: UDisc (watch-app), UUID 51d01a6a-272a-4750-af48-10bf0de983fd, minApiLevel 3.3.0, installed from the Connect IQ store.
- SDK: Connect IQ 9.2.0. Editor: VS Code with the Monkey C extension.

Description

Our app records disc golf activities with the ActivityRecording API. On the devices above, the firmware applies Auto Pause to the session. The FIT files contain timer stop and start events with timer_trigger = auto. Our app does not send these events. Connect IQ has no API to control Auto Pause.

The result for the user: low distance, low step count, and gaps in the GPS track. One auto pause continued for almost 15 minutes.

The auto_pause setting in the affected FIT files is "when stopped".I contacted a developer who helped with the version of ConnectIQ app. He confirmed that in FIT files from unaffected devices, the same setting is "off". He also told us that a CIQ generic activity must record this setting as invalid, which the device reads as disabled. Support directed us to this forum.

Our analysis of the speed data shows this pattern: the timer pauses after 2 seconds below 0.447 m/s (1.0 mph). The timer resumes only above 1.35 m/s. A normal disc golf walking pace stays between these two values. In the sample files, 82% to 89% of the discarded movement occurred in walk segments that did not restart the timer.

Code sample

_session = ActivityRecording.createSession({
:name => "Disc Golf @ " + courseName,
:sport => Activity.SPORT_DISC_GOLF,
:subSport => Activity.SUB_SPORT_GENERIC
});
_session.start();

We call start() one time. We do not call stop() until the round ends.

Steps to reproduce

* In theory, I have not been able to reproduce this myself since I do not have these devices.

1. Install UDisc from the Connect IQ store on a fenix 8 (22.41) or Forerunner 570 (17.33).
2. Start a round with activity recording on.
3. Walk a disc golf round. Stop at each tee and basket, as normal play requires.
4. Save the round and open the activity in Garmin Connect.
5. Compare the recorded distance with the phone's GPS track. Examine the timer events in the FIT file.

Attachments

    

We also have two FIT files from an affected user. The files contain user GPS data. Didn't want to attach for privacy reasons but can share in a private channel.

Question

Why does the firmware set auto_pause to "when stopped" for this CIQ session? Is there a workaround from the CIQ layer?

  • Same issue on fenix 8 47mm AMOLED, firmware 23.40 - Connect IQ padel watch-app (SPORT_RACKET / SUB_SPORT_PADEL)

    I'm seeing the same behaviour with my own watch-app, built with SDK 9.2.0, minApiLevel 5.0.0.

    - Session created with :sport => Activity.SPORT_RACKET, :subSport => Activity.SUB_SPORT_PADEL; start() is called once, stop() only when the user pauses via the START button. The app never sends pause events.

    - After a few minutes of play, the watch plays the pause tone and Activity.getActivityInfo().timerState becomes TIMER_STATE_PAUSED. Padel involves short, slow movements, so with the thresholds reported above the timer practically never resumes on its own.

    - There is no Auto Pause option for the app, and the native Padel activity has no Auto Pause setting either (and it is not enabled), so there is nothing the user can turn off.

    - It does not happen when standing still from the start; it starts after some movement.

    As a temporary workaround, the app now detects TIMER_STATE_PAUSED while the user hasn't paused and calls stop()/start() to restart the timer. A proper fix (or an API to opt out of Auto Pause) would be much appreciated.

  • This reminds me another bug:

    I have the "Hiker App" and the "Hiker DF" datafield. When I add the datafield to the Walk activity, and then I run the App with Walk activity type then on some devices I see that in the fit file there are records not only from the Hiker App (which is what is the expected behaviour) but also from the Hiker DF. In other words it looks like when a watch-app starts a session with a sport and subSport combination that otherwise does exist on the watch, then that activitiy's settings are also applied to the session.

    So if you had Auto Pause enabled in the built-in Walk activity, and now you start a session with the same sport and subSport as Walk, then the Auto-Pause might be applied.

    But, even that wouldn't explain what happens, as obviously the Auto Pause on the activities has also Auto Resume, so once the user continues to walk/run/ride it should've resumed the session. So there must be then 2 bugs.

  • I'm not sure either. The behavior we're experiencing may be intentional, thus having to do with the type of activity `:sport` or `:subSport` config options? It could also be an unintentional intermittent issue at some layer of the activity recording system. Or something else, haha Shrug

  • I don't understand. Is there any way a CIQ app can set this? Isn't this something the firmware does (or should do) for every session recorded by a watch-app?

  • EDIT: 

    I contacted a developer at Garmin, who helped with the initial release of the UDisc ConnectIQ app He confirmed that in FIT files from unaffected devices, the same `auto_pause` setting is "off". He also told me that a CIQ generic activity must record this setting as invalid, which the device reads as disabled. He suggested that I post in this forum.

    And thanks again to all the Garmin developers who have helped us with the UDisc ConnectIQ app, so far!!