Acknowledged
CIQQA-4769

fenix 9 Pro: GPS stops delivering positions to a Connect IQ app about 14 seconds into an activity

Summary

On the fenix 9 Pro, a Connect IQ device app that records an activity receives GPS positions for roughly 14 seconds and then none for the rest of the session. The FIT file written by the device shows the same: position fields stop at the same moment while the record messages continue with heart rate and altitude. The app keeps running normally (our 100 Hz accelerometer/gyroscope processing continues for the full hour). It happens in more than half of all sessions on the Pro 51mm and Pro 47mm, intermittently on the same watch, and it happens whether the app requests a SatIQ configuration or not.

Environment

  • Devices: fenix 9 Pro 51mm (006-B4954-00), fenix 9 Pro 47mm (006-B4953-00), fenix 9 Pro Solar 47mm/51mm, fenix 9 Pro 43mm. 
  • Firmware: 6.38, 6.48 and 6.49 all affected.
  • Connect IQ: 6.0.3. App built with SDK 9.2.0.
  • App: The Surfr. App (store app), version 4.1.4. Device app with ActivityRecording.createSession (sport kitesurfing), Position.enableLocationEvents(LOCATION_CONTINUOUS), and a 100 Hz Sensor.registerSensorDataListener for accelerometer and gyroscope.

Steps to reproduce

  1. Install the app from the store on a fenix 9 Pro.
  2. Start a session (this calls createSession, session.start(), enableLocationEvents(LOCATION_CONTINUOUS) and registers the 100 Hz sensor listener).
  3. Record for more than a minute while moving.
  4. Stop and save, then inspect the FIT file in Garmin Connect or with the FIT SDK.

We cannot force it: the same watch succeeds in some sessions and fails in others. Across our users since 1 September it fails in 56% of fenix 9 Pro sessions (120 of 214 sessions, 31 of 47 users affected at least once). 

Expected

Position updates for the whole activity, as on every other Garmin model running the same code.

Actual

Position updates arrive for about 14 seconds after the first fix and then stop. The FIT file written by the device confirms it is not only the app's callback: record messages lose their position fields at the same moment.

Example FIT file (fenix 9 Pro 51mm, firmware 6.49, app 4.1.4, 5 October 2026):
https://drive.google.com/file/d/1WMJ_1pWIFoaYnxRfg8MfVScQgK-KhsSz/view?usp=drive_link

  • Session length 6,354 s, 6,040 record messages.
  • Only 14 record messages carry latitude/longitude, from t+11 s to t+24 s.
  • From t+25 s onward, records continue every second with heart rate and altitude but no position or speed; distance stays frozen at 14 m.
  • Event messages: timer start at 0 and timer stop at the end. No pause, no stop in between.

Every failing session we have looked at (dozens) has this exact shape: 13 to 15 one-second positions, then nothing.

What we have tried

Since app 4.1.4 (3 October) the fenix 9 builds request a SatIQ configuration, following the reply in https://forums.garmin.com/developer/connect-iq/i/bug-reports/fenix-9-position-configuration_gps_xxxxx-not-supported, with the raw values because the constants are not in SDK 9.2.0:

try {
    var config = null;
    if (Position.hasConfigurationSupport(258 as Position.Configuration)) {        // SatIQ max accuracy
        config = 258;
    } else if (Position.hasConfigurationSupport(Position.CONFIGURATION_SAT_IQ)) {   // 255
        config = Position.CONFIGURATION_SAT_IQ;
    }
    if (config != null) {
        Position.enableLocationEvents({
            :acquisitionType => Position.LOCATION_CONTINUOUS,
            :configuration => config as Position.Configuration
        }, method(:onPosition));
        return;
    }
} catch (e) {}
Position.enableLocationEvents(Position.LOCATION_CONTINUOUS, method(:onPosition));

No change: in the first four days on 4.1.4, 13 of 14 sessions on the Pro 51mm and 6 of 20 on the Pro 47mm lost GPS, on the same watches that failed before. The attached FIT file was recorded with this code. We do not use :constellations. The simulator for fenix 9 Pro 51mm reports hasConfigurationSupport(255) true and hasConfigurationSupport(258) false, so on the simulator the app requests 255; we cannot tell which value the real device accepted.

What we can rule out

  • Not our stop/pause logic: the only LOCATION_DISABLE call in the app runs at session stop, and the FIT file has no pause or stop event before the end.
  • Not a fix problem: in several failing sessions the user was already moving at 8–10 m/s with good accuracy when positions stopped.

Questions

  1. Is the firmware turning GPS off for the CIQ app after a fixed time, for example when the app's state changes? The constant ~14 seconds suggests a timer rather than a signal condition.

We can supply more FIT files, a reduced test app, and session logs on request.


  • A follow-up to my comment of 9 November, with a reduced test case (fēnix 9 Pro 47 mm, firmware 6.74, Connect IQ 6.0.4). I have sent the test app, with its source and the FIT files, to [email protected].

    It reproduces in a swimming pool in under 3 minutes. The app asks for the GPS once at launch (LOCATION_CONTINUOUS, CONFIGURATION_SAT_IQ_MAX_ACCURACY) and records an activity on START. It never touches the GPS again. Then: 40 s with the wrist out of the water, 60 s with the wrist under water, 60 s out again, under open sky.

    One character per second from START. Top row: M a position with record field 107 = 1, m a position with 107 = 0, p a repeated position, . no position. Bottom row, FIT message 540: C (3,2), N (2,4), F (5,0).

        0 pMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMM..................
          CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCN
       60 ..........................................Mmmmmmmmmmmmmmm...
          NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNFFFF
      120 ......mMmmmmmmmmmmmmm...................
          FFFNNNNNNNNNNNNNNNNNFFFFFFFFFFFFFFFFFFFF
    • It starts in (3,2), the mode the native Surf activity keeps all the time.
    • At second 59, with the wrist under water, it changes to (2,4).
    • Out of the water (100 s) it never returns to (3,2): one position with 107 = 1, 14 with 107 = 0, then (5,0). It powers up again at second 3 of the next minute and does the same.

    What four more pool tests added:

    • The change from (3,2) to (2,4) comes at second 59 of a minute counted from START: 11 of 14 times (59, 179, 239, 299 s). It does not follow the signal: it also happened with open sky and a position with 107 = 1 every second.
    • A LOCATION_DISABLE and enable from the app brings (3,2) back every time, but only until the next second 59. Re-requesting right after second 59 lasted 3-4 s.
    • On dry land the same app stays in (3,2), and the native Surf activity always does.

    So an app can only win part of each minute back. Is this once-a-minute choice intended for Connect IQ apps that record, and is there a way for an app to keep the continuous mode?

  • fēnix 9 Pro: a recording Connect IQ app loses continuous GPS (the firmware switches it to a managed on/off mode); the native Surf activity keeps it (FIT message 540)

    Device: fēnix 9 Pro – inReach 47 mm (006-B4953-00), firmware 6.74, Connect IQ 6.0.4 (API 6.0.3), app built with SDK 9.3.0.

    App: a Connect IQ device app that records an activity (ActivityRecording, SPORT_SURFING) and calls Position.enableLocationEvents with LOCATION_CONTINUOUS and the configuration the watch accepts (SatIQ max accuracy).

    What happens: on 9 Nov 2026, at the same surf spot, the app got a position in 11 % of the seconds (434 of 3958). The native Surf activity, started 1 minute after the app's session ended, got one in 67 % (1210 of 1802).

    The FIT shows why, in the undocumented message 540 (GNSS mode):

    - Native Surf: (3,2), continuous, for the whole session.

    - Connect IQ app: (3,2) for the first 24 s after START, then (5,0), and from there 38 cycles alternating between (2,4) and (5,0). In (2,4) the first fix came after a median of 39 s, and 7 times there was no fix at all before it switched off again. There were gaps of up to 7 minutes without a position.

    The same pattern shows up in 8 earlier sea sessions of two different Connect IQ surf apps (ours and a third-party one): they always end up in (2,4)/(5,0) and never go back to (3,2). On land, a session started in (3,2) and dropped to (2,4) at 59 s without having lost the fix.

    Expected: a Connect IQ app that records an activity gets the same continuous GPS as the native activity profile. With the managed mode, a GPS-based wave counter misses most rides: on the native Surf FIT our detector finds 4 waves, but in the app's own session it could only validate 1.

    Same issue as this report (CIQQA-4769). I can share both FIT files privately.

  • Michael, can you provide the reduced test app (source) to [email protected]. Thanks!

  •  Same issue stops tracking, newest everything garmin fenix 9 pro solar inreach

  • I'm seeing the same issue. Would be great to get a fix from garmin for this.