Has anyone else noticed that Position.hasConfigurationSupport always returns false for Fenix 9 series in the simulator?
Has anyone else noticed that Position.hasConfigurationSupport always returns false for Fenix 9 series in the simulator?
Yes, I found the same thing, I changed my code a bit and now I'm waiting for someone with a real f9 to see what happens there.
Came here to see if there were reports of the same thing. Yes, even though (Position has :hasConfigurationSupport) is true the actual .hasConfigurationSupport is returning false on all the config enumerations and resulting (for me) in a IQ stack error on my glance using the pro-forma code to establish a .enableLocationEvents() callback.
Workaround with a final else to set the lowest options = Position.LOCATION_ONE_SHOT
however, any apps set to auto-update to new device support will get caught out ?
I did read in the5krunner review of the Fenix9 series that GNSS on-device configuration was now not a user-config and it was just set to SatIQ but the API in the SIM at least is not recognising/reporting the right returns here
Speedy work Garmin SIM engineering - there are updates to the Fenix 9 series today in the device manager that add the missing SATIQ and change the other ID's ...
now returns true.

Hi Jim, did you receive any feedback on Fenix 9 behaviour?
Thanks Jim,
I'm assuming that a new SDK/Simulator version will be required to map to the new 'constellationConfiguration' values and that Position.CONFIGURATION_SAT_IQ is working because that mapping remains unchanged.
See Fenix 9 Position.CONFIGURATION_GPS_xxxxx not supported
Brandon.ConnectIQ posted info there about the change and while it's not working in the current sim (Brandon said there was an SDK update coming), it is working as he stated with a sideload on an f9.
New device downloads all round today in the SDK manager - no SDK yet but next week is the 2nd week in the quarter.
Device XML gives clue to a new API call but no indication of new constants as indicated in link above.
The devices were actually updated a few days back. Depending how how you implement this you may not even need new constants. What Brandon posted, the values from 255 to 258 is all you may need. That's the case for me.
You cant test this in the sim for the f9 devices yet - it only "knows" 255. But with println calls and a side load/device (yous or a friend's) you can do some testing/debugging. For example with something like
for(var c=250;c<260;c++) {
System.println(c+" "+Position.hasConfigurationSupport(c));
}
With a sideload and log file, I see 255 to 258 as "true"
---
The fenix 9 series of devices only supports SatIQ and won't allow you to set select configurations like you've been able to do in the past. We have an upcoming SDK release that will have some additional mode constants that the fenix 9 firmware already supports. Here's a preview:
CONFIGURATION_SAT_IQ_NORMAL - 255, Dynamic SatIQ Normal Mode. Balance between accuracy and battery life, and equivalent to the current CONFIGURATION_SAT_IQ.
CONFIGURATION_SAT_IQ_EXTENDED_BATTERY - 256, Dynamic SatIQ Extended Battery Mode. Longer battery life with good accuracy.
CONFIGURATION_SAT_IQ_MAX_BATTERY - 257, Dynamic SatIQ Max Battery Mode. Longest battery life, but lower accuracy.
CONFIGURATION_SAT_IQ_MAX_ACCURACY - 258, Dynamic SatIQ Max Accuracy Mode. Best accuracy, but higher battery consumption.
There are more specifics in the API docs indicating which configurations are available on which products. Apologies for the confusion and the delay in SDK support on this feature!