It can't be compatible, it seems it needs at least CIQ 2.4.2. It's sad they release a 7.x firmware with the older CIQ 2.4.1 at this point of time.
I don't know about that. My North American 935 is running 7.60 (beta), but the CIQ version is 2.4.1 and Running Power works. Maybe the real problem is the app developers (Garmin) have not added the necessary information to the SDK which is used to build the app. My understanding is that for a device to be supported by an app for a given CIQ version (e.g. 2.4.1), the device of course has to have the correct CIQ version, but the SDK also has to know that the device supports that CIQ.
In other words, your watch may have CIQ 2.4.1, but the SDK that built the app doesn't know that.
Looking at the latest Connect IQ 2.4.2 SDK -- devices.xml -- this seems to be the case:
You can see that the first 935 part number, which seems to be the worldwide version of the watch, is listed as supporting 2.4.1, but the part number for APAC is still listed as supporting 2.3.4.
I believe that other devs have had a similar problem with their app on APAC devices. The device supported the necessary CIQ, but the SDK did not have the correct support. Theoretically it would've worked, if only the store would let them download the app to their device. They had to wait for a newer SDK to come out and rebuild their app.
If I'm not mistaken, this is something Garmin needs to fix on their end, by building their own running apps with a newer version of their SDK with up-to-date info on the CIQ that 935 supports. Either that or they need to fix the same info on the store's end (I'm not 100% sure how it works, tbh). This is clearly one of the issues that arises when they use their own 3rd-party app ecosystem to add a feature to their own watch. #whoops
Maybe this will provide some impetus to improve things. (Like having more than 2 CIQ data fields per activity...)
I don't know about that. My North American 935 is running 7.60 (beta), but the CIQ version is 2.4.1 and Running Power works. Maybe the real problem is the app developers (Garmin) have not added the necessary information to the SDK which is used to build the app. My understanding is that for a device to be supported by an app for a given CIQ version (e.g. 2.4.1), the device of course has to have the correct CIQ version, but the SDK also has to know that the device supports that CIQ.
In other words, your watch may have CIQ 2.4.1, but the SDK that built the app doesn't know that.
Looking at the latest Connect IQ 2.4.2 SDK -- devices.xml -- this seems to be the case:
You can see that the first 935 part number, which seems to be the worldwide version of the watch, is listed as supporting 2.4.1, but the part number for APAC is still listed as supporting 2.3.4.
I believe that other devs have had a similar problem with their app on APAC devices. The device supported the necessary CIQ, but the SDK did not have the correct support. Theoretically it would've worked, if only the store would let them download the app to their device. They had to wait for a newer SDK to come out and rebuild their app.
If I'm not mistaken, this is something Garmin needs to fix on their end, by building their own running apps with a newer version of their SDK with up-to-date info on the CIQ that 935 supports. Either that or they need to fix the same info on the store's end (I'm not 100% sure how it works, tbh). This is clearly one of the issues that arises when they use their own 3rd-party app ecosystem to add a feature to their own watch. #whoops
Maybe this will provide some impetus to improve things. (Like having more than 2 CIQ data fields per activity...)
Great info! I'm not familiar with the SDK at all, but I'm kind of surprised the CIQ versions are hard coded into the SDK release for every device. Does that mean we have to wait for Garmin to update their SDK so they can download it themselves, rebuild the data fields and release them?
I have an issue with LAST LAP POWER. everything shows, but last lap power does not show in combo power or in the single data field. any help will be great,
maybe i am missing something when isntalling the apps
This will be my last Garmin I bought here in Singapore. I don't see the point in paying the full price and having to deal with an ecosystem that's always ~3 months behind.
I agree. I will likely never bother with Garmin again. Certainly I will never be so foolish to purchase an APAC unit. Their handling and response to this issue has been arrogant and inconsiderate. At the very least there should be a disclaimer on the product, clearly visible, so folk know what they are entering into. It's stunning they think they can charge the same price as a ROW unit and then provide an different and inferior post purchase experience. I have expressed this opinion directly on various forums like 5Krunner and DC Rainmaker, GARMIN facebook etc. Hopefully a few will read and reconsider because if I had known about this experience I may well have chosen to purchase through Clever Training etc and worn the duties.
are you sure your splits in the top match laps in the bottom? Is the bottom excel generated directly from fit file data or some other data? There is not enough info to check this out really. Perhaps you can post a link to the activity on Garmin Connect
The problem of importing current .fit files into ST3 lies with ST3. It’s for them to ‘maintain’ the software to cope with developments in file structure. That they don’t illustrates their lack of desire to maintain ST3 so that it remains current. Post a comment to the ongoing thread in the ST forums on the ST site.
