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 HzSensor.registerSensorDataListenerfor accelerometer and gyroscope.
Steps to reproduce
- Install the app from the store on a fenix 9 Pro.
- Start a session (this calls
createSession,session.start(),enableLocationEvents(LOCATION_CONTINUOUS)and registers the 100 Hz sensor listener). - Record for more than a minute while moving.
- 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_DISABLEcall 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
- 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.