API 5.0.0

I'm confused. I don't see any Garmin devices that support API 5.0.0. What am I missing?

developer.garmin.com/.../

Top Replies

All Replies

  • That developer page clearly hasn’t been updated.

    API 5 is System 7, and it seems that more or all of the System 6 (API 4) devices are getting it. The devices in the SDK haven’t been updated either, but physical watches such as Forerunner 955 have received an update with CIQ 5.0.0.

    If you’re wondering why the SDK devices haven’t been updated yet, I’d imagine that they’re waiting either until there’s a reasonable chance that “everyone” (or as many people as possible) have the update, or they’re waiting to see if there’s any bugs in the field. Remember, once an SDK device is updated with a new firmware/CIQ version, then any app you build for that device will require that firmware at a *minimum* (meaning people who still have CIQ 4.x would have to update.)

    https://forums.garmin.com/developer/connect-iq/b/news-announcements/posts/connect-iq-sdk-7-1-0-is-now-available

    System 7 APIs are available in the following devices:

    • D2 Mach 1
    • Edge® 1040 Series
    • Edge 540
    • Edge 840
    • Epix (Gen 2) Series
    • Epix (Gen 2) Pro Series
    • Enduro 2 Series
    • fēnix® 7 Series
    • fēnix 7 Pro Series
    • MARQ 2 Series
    • Forerunner 165 series
    • Forerunner® 255 series
    • Forerunner 265 series
    • Forerunner 955 series
    • Forerunner 965
    • Venu® 3
    • Vivoactive® 5

    Venu 2 series, Venu 2 Plus, and Venu Sq 2 Series will be getting API 5.0.0 in a future update. Get the Connect IQ 7.1.0 SDK from the SDK Manager today.

    You might take issue with the wording of this announcement, given that the sdk devices haven’t been updated yet. I guess they can weasel out of it by saying that the actual devices have API 5, and you can still build an app that uses API 5 features (I think), you just can’t set the minApiVersion to 5 otherwise you won’t be able to build for any device (which might be a problem for someone who wants to make an app which *only* works on CIQ 5 devices.)

  • There were new deice files a few days back with the System 7/CIQ 5 devices.  Be forewarned, some folks have run into issues using the new device files and the 6.4.x SDK.  So maybe save off the device folder before you get the updates with the SDKmanager  I'm fully switched to the 7.1.0 SDK.

    When I run an app for the 965 in the sim with the new device files, I see this on the top line:

    I see the same thing for other watches, like the fr955. And edge devices like the 540/840

    Device files for some of the devices that will get System7 haven't been released yet.  Could be that production FW for those devices with CIQ 5 hasn't  been released, only beta FW.

  • Oh my mistake. I did hear that some ppl got the 5.0.0 devices in the forums, but I hadn’t received the updates myself. Sorry for the misinformation.

    In that case, the devices page in the online documentation should def be updated.

  • Indeed. For example if you use Menu2 and compile with old SDK (6.4.2) and run on a 5.0.0 device in the simulator then it crashes

  • Thanks. Just need to reconcile API 5 and System 7 and SDK 7 and CIQ 5. Sounds like these are all the same. My immediate issue is I'm running out of BG memory for a large JSON packet. I can't pass it into Background.exit(data), and I can't Storage.setValue("data",data). Out of memory. So I was hoping my Target Devices like an EDGE 1030, 820, etc, would now be able to to handle COMM in the foreground under API 5.

  • Older edge devices like the 520,820,530,830,1030 are CIQ 3 and will not be getting CIQ 5, so this will not help you with those.

  • Is there an easy way / summary to see all the new functions in 5.0.0 ? E.g. stress score is now in ActivityMonitor.Info

  • There is the System 7 announcement, and also in each SDK is a readme file with all the Release notes back to version 0.0.1 of the SDK

  • I don't see this specific change (stress score) documented in either of those places. I'm guessing there might be more things that were added and it would be nice to know what they are.

  • There are times that it's just a matter of going through the API doc (yes, it can be a pain), but imagine a doc that listed this for each version of the SDK over the last 9 years.