Did Garmin give up on SDK?

Nice summary and I had wondered the same … it definitely looks like the quarterly 9.3.0 missed the release window that approximates to the 2nd week of the quarter. But it’s not the first time… see also the list of  SDK dates from the SDK manager which shows the 7.3.0 was also unreleased.

In actual devices CIQ 6.0.3 started to come out in the summer and I just saw the first betas with 6.0.4 this weekend on Tactix8… the same firmware version had a massive changelog in the beta forum but didn’t mention the CIQ bump.

So on-device SDK capabilities are being increasingly versioned and some diff-ing of the SIM device files against older/backup versions might (but I wouldn’t as it’s probably against the T’s and Cs) reveal the change to the 6.0.3/9.3.0 … and why do that if not planning a SDK release.

What is it you are looking for in the next SDK?

For me, there seem to be some issues with BLE with 9.2.  For example, the NordicThingy52 samples in the SDK don't work.  But then again  I may be one of the few people that has a Thingy52 but I only use it in some testing

Also, the constants for the new GPS configurations on the f9 series need to be added. Once those 4 values were posted, I had it working in a short time

On real devices, a bump in CIQ is almost never mentioned, and charges are at most "various CIQ fixes"

Also, if there are new thing comin in CIQ. Garmin tries to get them into production FW before the SDK is released, so devs can test on devices right awa. 

jim_m_58 said:

What is it you are looking for in the next SDK?

Lots of people could answer this, it’s a shame there isn’t a “uservoice” forum where things can get listed and voted on, but how about for starters…

• access to new speaker (not tone) playback sounds
• access to the new “hey Garmin” for on-device voice commands
• System access to the state of a connected BLE so apps know if there is 4G connectivity, not just BLE to phone
• some access to the state of the shared graphics pool to not call high impact functions that currently sometimes issue outofmemory exceptions
• fix/increment the makeWebRequest callback for JSON to include top level arrays (which it does, but not in the prototype so breaks strict typechecking)
• allow access to on-device course/route information via the persisted storage - access the actual location data
• allow access to the sync model for Garmin Connect to retrieve (for the current user, on-device) other data

I’d add tone playing ability and gps polling rate