Fenix 9 Position.CONFIGURATION_GPS_xxxxx not supported

Never interested in that topic and now tried to use 9.3 SDK with Sim fenix 9, MARQ 3, etc.

It does not reflect device properties still.

Everything I touch is either unfinished, broken, or causes crashes. Couldn't you just hire some students to go through these properties—like a bunch of monkeys—and simply compare what’s actually in the hardware against what’s in your simulator’s list?

Mark my words: I’m about to go check the flashlight (Attention.hasFlashlightColor crash), and I’ll probably run into that old bug with the green color again (though I really hope not—hope dies last, after all).

fenix 9x Sim:

=== hasConfigurationSupport AVAILABLE ===
CONFIGURATION_GPS exists, supported=false
CONFIGURATION_GPS_GLONASS exists, supported=false
CONFIGURATION_GPS_GALILEO exists, supported=false
CONFIGURATION_GPS_BEIDOU exists, supported=false
CONFIGURATION_GPS_GLONASS_GALILEO_BEIDOU_L1 exists, supported=false
CONFIGURATION_GPS_GLONASS_GALILEO_BEIDOU_L1_L5 exists, supported=false
CONFIGURATION_SAT_IQ exists, supported=true
CONFIGURATION_SAT_IQ_NORMAL exists, supported=true
CONFIGURATION_SAT_IQ_EXTENDED_BATTERY exists, supported=false
CONFIGURATION_SAT_IQ_MAX_BATTERY exists, supported=false
CONFIGURATION_SAT_IQ_MAX_ACCURACY exists, supported=false
=== RAW VALUES 250-260 ===
value 250 supported=false
value 251 supported=false
value 252 supported=false
value 253 supported=false
value 254 supported=false
value 255 supported=true
value 256 supported=false
value 257 supported=false
value 258 supported=false
value 259 supported=false

We don't use :constellations. Since our latest release the Fenix 9 builds request a SatIQ configuration exactly as Brandon described, with the raw values because the constants aren't in SDK 9.2.0. All other watches still use the plain enableLocationEvents(LOCATION_CONTINUOUS, ...) call.

The problem is unchanged with this code. Over the first four days of 4.1.4 we have 37 Fenix 9 sessions; on the Fenix 9 Pro 51mm, 13 of 14 lost GPS, on the Pro 47mm 6 of 20. It is the same riders and the same watches that failed before the change, now on firmware 6.49.

The failure is always the same. Attached is a FIT file from a Fenix 9 Pro 51mm on firmware 6.49 recorded with 4.1.4: a 106-minute session with 6,040 record messages, of which only 14 carry a position (from second 11 to second 24). After that the records continue every second with heart rate and altitude but no position, and the distance freezes at 14 metres. There is no pause or stop event in between; the session was recorded with ActivityRecording.createSession and the only events are the start at 0 and the stop at the end. Our own position callback stops receiving fixes at the same moment.

So in our case the configuration request does not appear to be the cause, or it is not being honoured. Is there any way to tell from the device which configuration was actually applied, and whether the firmware is turning GPS off for the CIQ app after about 14 seconds?

Here the fit: https://drive.google.com/file/d/1WMJ_1pWIFoaYnxRfg8MfVScQgK-KhsSz/view?usp=sharing 

----

function start(reader) as Void {
self.reader = reader;
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) {
// fall through to the plain call
}
Position.enableLocationEvents(Position.LOCATION_CONTINUOUS, method(:onPosition));
}

What do you have for configurations in Position.  You don't want to use constellations.

As Brandon posted, I use the configurations 255 through 258 (the constants aren't in the current SDK)

Hi Brandon, we get many complaints from our users that our activity tracking app stops tracking GPS after few seconds into the activity. Only on fenix 9. I assume this is related.It looks like that GPS tracking for Connect IQ apps is not reliably possible on the Fenix 9.

So the same as what Brandon posted.  My Hike2 in the store now supports these too.  Start the app (on the f9) and long press the middle button (menu).  Scroll down the menu to "GPS Mode", and use select to scroll through the choices.  This was a bit hard to test in the sim as there, only 255 is valid.

If you use something like another fenix or forerunner, you see the options available on that device.  If you try older watch. (pre configurations) you see the basic 3.