1. Compatible Devices | Connect IQ | Garmin Developers
   URL: https://developer.garmin.com/connect-iq/compatible-devices
   Compatible Devices | Connect IQ | Garmin Developers

MenuCompatible Devices

×

Device Type:

AllWatches/WearablesOutdoor HandheldsEdge

Supported CIQ Version:

All

- All
- 1.2
- 1.4
- 2.4
- 3.0
- 3.1
- 3.2
- 3.3
- 3.4
- 5.0
- 5.1
- 5.2
- 6.0

| Watches/Wearables | Screen Resolution | Screen Shape | Screen Technology | API Level |
| --- | --- | --- | --- | --- |
| Approach® S50 info | 390 x 390 | round | AMOLED | 5.1 |
| Approach® S60 info | 240 x 240 | round | Memory-In-Pixel (64 colors) | 2.4 |
| Approach® S62 info | 260 x 260 | round | Memory-In-Pixel (64 colors) | 3.0 |
| Approach® S70 42mm info | 390 x 390 | round | AMOLED | 5.1 |
| Approach® S70 47mm info | 454 x 454 | round | AMOLED | 5.1 |
| Captain Marvel info | 218 x 218 | round | Memory-In-Pixel (64 colors) | 3.3 |
| D2™ Air info | 390 x 390 | round | AMOLED | 3.2 |
| D2™ Air X10 info | 416 x 416 | round | AMOLED | 5.0 |
| D2™ Bravo info | 218 x 218 | round | Memory-In-Pixel (16 colors) | 1.4 |
| D2™ Bravo Titanium info | 218 x 218 | round | Memory-In-Pixel (16 colors) | 1.4 |
| D2™ Charlie info | 240 x 240 | round | Memory-In-Pixel (64 colors) | 3.0 |
| D2™ Delta info | 240 x 240 | round | Memory-In-Pixel (64 colors) | 3.1 |
| D2™ Delta PX info | 240 x 240 | round | Memory-In-Pixel (64 colors) | 3.1 |
| D2™ Delta S info | 240 x 240 | round | Memory-In-Pixel (64 colors) | 3.1 |
| D2™ Mach 1 info | 416 x 416 | round | AMOLED | 5.2 |
| D2™ Mach 2 info | 454 x 454 | round | AMOLED | 5.2 |
| D2™ Mach 2 Pro info | 454 x 454 | round | AMOLED | 6.0 |
| Darth Vader™ info | 260 x 260 | round | Memory-In-Pixel (64 colors) | 3.3 |
| Descent™ G1 / G1 Solar info | 176 x 176 | semi-octagon | Memory-In-Pixel (2 colors) | 3.4 |
| Descent™ G2 info | 390 x 390 | round | AMOLED | 5.1 |
| Descent™ Mk1 info | 240 x 240 | round | Memory-In-Pixel (64 colors) | 3.1 |
| Descent™ Mk2 / Mk2i info | 280 x 280 | round | Memory-In-Pixel (64 colors) | 3.4 |
| Descent™ Mk2 S info | 240 x 240 | round | Memory-In-Pixel (64 colors) | 3.4 |
| Descent™ Mk3 43mm / Mk3i 43mm info | 390 x 390 | round | AMOLED | 5.1 |
| Descent™ Mk3i 51mm info | 454 x 454 | round | AMOLED | 5.1 |
| Enduro™ info | 280 x 280 | round | Memory-In-Pixel (64 colors) | 3.4 |
| Enduro™ 3 info | 280 x 280 | round | Memory-In-Pixel (64 colors) | 6.0 |
| epix™ info | 205 x 148 | rectangle | Memory-In-Pixel (64 colors) | 1.2 |
| epix™ (Gen 2) / quatix® 7 Sapphire info | 416 x 416 | round | AMOLED | 5.2 |
| epix™ Pro (Gen 2) 42mm info | 390 x 390 | round | AMOLED | 5.2 |
| epix™ Pro (Gen 2) 47mm / quatix® 7 Pro info | 416 x 416 | round | AMOLED | 5.2 |
| epix™ Pro (Gen 2) 51mm / D2™ Mach 1 Pro / tactix® 7 – AMOLED Edition info | 454 x 454 | round | AMOLED | 5.2 |
| fēnix® 3 / tactix® Bravo / quatix® 3 info | 218 x 218 | round | Memory-In-Pixel (16 colors) | 1.4 |
| fēnix® 3 HR info | 218 x 218 | round | Memory-In-Pixel (16 colors) | 1.4 |
| fēnix® 5 / quatix® 5 info | 240 x 240 | round | Memory-In-Pixel (64 colors) | 3.1 |
| fēnix® 5 Plus info | 240 x 240 | round | Memory-In-Pixel (64 colors) | 3.3 |
| fēnix® 5S info | 218 x 218 | round | Memory-In-Pixel (64 colors) | 3.1 |
| fēnix® 5S Plus info | 240 x 240 | round | Memory-In-Pixel (64 colors) | 3.3 |
| fēnix® 5X / tactix® Charlie info | 240 x 240 | round | Memory-In-Pixel (64 colors) | 3.1 |
| fēnix® 5X Plus info | 240 x 240 | round | Memory-In-Pixel (64 colors) | 3.3 |
| fēnix® 6 / 6 Solar / 6 Dual Power info | 260 x 260 | round | Memory-In-Pixel (64 colors) | 3.4 |
| fēnix® 6 Pro / 6 Sapphire / 6 Pro Solar / 6 Pro Dual Power / quatix® 6 info | 260 x 260 | round | Memory-In-Pixel (64 colors) | 3.4 |
| fēnix® 6S / 6S Solar / 6S Dual Power info | 240 x 240 | round | Memory-In-Pixel (64 colors) | 3.4 |
| fēnix® 6S Pro / 6S Sapphire / 6S Pro Solar / 6S Pro Dual Power info | 240 x 240 | round | Memory-In-Pixel (64 colors) | 3.4 |
| fēnix® 6X Pro / 6X Sapphire / 6X Pro Solar / tactix® Delta Sapphire / Delta Solar / Delta Solar - Ballistics Edition / quatix® 6X / 6X Solar / 6X Dual Power info | 280 x 280 | round | Memory-In-Pixel (64 colors) | 3.4 |
| fēnix® 7 / quatix® 7 info | 260 x 260 | round | Memory-In-Pixel (64 colors) | 5.2 |
| fēnix® 7 Pro info | 260 x 260 | round | Memory-In-Pixel (64 colors) | 5.2 |
| fēnix® 7 Pro - Solar Edition (no Wi-Fi) info | 260 x 260 | round | Memory-In-Pixel (64 colors) | 5.2 |
| fēnix® 7S info | 240 x 240 | round | Memory-In-Pixel (64 colors) | 5.2 |
| fēnix® 7S Pro info | 240 x 240 | round | Memory-In-Pixel (64 colors) | 5.2 |
| fēnix® 7X / tactix® 7 / quatix® 7X Solar / Enduro™ 2 info | 280 x 280 | round | Memory-In-Pixel (64 colors) | 5.2 |
| fēnix® 7X Pro info | 280 x 280 | round | Memory-In-Pixel (64 colors) | 5.2 |
| fēnix® 7X Pro - Solar Edition (no Wi-Fi) info | 280 x 280 | round | Memory-In-Pixel (64 colors) | 5.2 |
| fēnix® 8 43mm info | 416 x 416 | round | AMOLED | 6.0 |
| fēnix® 8 47mm / 51mm / tactix® 8 47mm / 51mm / quatix® 8 47mm / 51mm info | 454 x 454 | round | AMOLED | 6.0 |
| fēnix® 8 Pro 47mm / 51mm / MicroLED / quatix® 8 Pro 47mm / 51mm info | 454 x 454 | round | AMOLED | 6.0 |
| fēnix® 8 Solar 47mm info | 260 x 260 | round | Memory-In-Pixel (64 colors) | 6.0 |
| fēnix® 8 Solar 51mm / tactix® 8 Solar 51mm info | 280 x 280 | round | Memory-In-Pixel (64 colors) | 6.0 |
| fēnix® Chronos info | 218 x 218 | round | Memory-In-Pixel (64 colors) | 3.1 |
| fēnix® E info | 416 x 416 | round | AMOLED | 6.0 |
| First Avenger info | 260 x 260 | round | Memory-In-Pixel (64 colors) | 3.3 |
| Forerunner® 165 info | 390 x 390 | round | AMOLED | 5.2 |
| Forerunner® 165 Music info | 390 x 390 | round | AMOLED | 5.2 |
| Forerunner® 170 info | 390 x 390 | round | AMOLED | 6.0 |
| Forerunner® 170 Music info | 390 x 390 | round | AMOLED | 6.0 |
| Forerunner® 230 info | 215 x 180 | semi-round | Memory-In-Pixel (16 colors) | 1.4 |
| Forerunner® 235 info | 215 x 180 | semi-round | Memory-In-Pixel (16 colors) | 1.4 |
| Forerunner® 245 info | 240 x 240 | round | Memory-In-Pixel (64 colors) | 3.3 |
| Forerunner® 245 Music info | 240 x 240 | round | Memory-In-Pixel (64 colors) | 3.3 |
| Forerunner® 255 info | 260 x 260 | round | Memory-In-Pixel (64 colors) | 5.2 |
| Forerunner® 255 Music info | 260 x 260 | round | Memory-In-Pixel (64 colors) | 5.2 |
| Forerunner® 255s info | 218 x 218 | round | Memory-In-Pixel (64 colors) | 5.2 |
| Forerunner® 255s Music info | 218 x 218 | round | Memory-In-Pixel (64 colors) | 5.2 |
| Forerunner® 265 info | 416 x 416 | round | AMOLED | 5.2 |
| Forerunner® 265s info | 360 x 360 | round | AMOLED | 5.2 |
| Forerunner® 45 info | 208 x 208 | round | Memory-In-Pixel (8 colors) | 1.4 |
| Forerunner® 55 info | 208 x 208 | round | Memory-In-Pixel (8 colors) | 3.4 |
| Forerunner® 570 42mm info | 390 x 390 | round | AMOLED | 6.0 |
| Forerunner® 570 47mm info | 454 x 454 | round | AMOLED | 6.0 |
| Forerunner® 630 info | 215 x 180 | semi-round | Memory-In-Pixel (16 colors) | 1.4 |
| Forerunner® 645 info | 240 x 240 | round | Memory-In-Pixel (64 colors) | 3.1 |
| Forerunner® 645 Music info | 240 x 240 | round | Memory-In-Pixel (64 colors) | 3.2 |
| Forerunner® 70 info | 390 x 390 | round | AMOLED | 6.0 |
| Forerunner® 735xt info | 215 x 180 | semi-round | Memory-In-Pixel (16 colors) | 2.4 |
| Forerunner® 745 info | 240 x 240 | round | Memory-In-Pixel (64 colors) | 3.3 |
| Forerunner® 920XT info | 205 x 148 | rectangle | Memory-In-Pixel (16 colors) | 1.4 |
| Forerunner® 935 info | 240 x 240 | round | Memory-In-Pixel (64 colors) | 3.1 |
| Forerunner® 945 info | 240 x 240 | round | Memory-In-Pixel (64 colors) | 3.3 |
| Forerunner® 945 LTE info | 240 x 240 | round | Memory-In-Pixel (64 colors) | 3.4 |
| Forerunner® 955 / Solar info | 260 x 260 | round | Memory-In-Pixel (64 colors) | 5.2 |
| Forerunner® 965 info | 454 x 454 | round | AMOLED | 5.2 |
| Forerunner® 970 info | 454 x 454 | round | AMOLED | 6.0 |
| Garmin Swim™ 2 info | 208 x 208 | round | Memory-In-Pixel (8 colors) | 1.4 |
| Instinct® 2 / Solar / Dual Power / dēzl Edition info | 176 x 176 | semi-octagon | Memory-In-Pixel (2 colors) | 3.4 |
| Instinct® 2S / Solar / Dual Power info | 163 x 156 | semi-octagon | Memory-In-Pixel (2 colors) | 3.4 |
| Instinct® 2X Solar info | 176 x 176 | semi-octagon | Memory-In-Pixel (2 colors) | 3.4 |
| Instinct® 3 AMOLED 45mm info | 390 x 390 | round | AMOLED | 5.1 |
| Instinct® 3 AMOLED 50mm info | 416 x 416 | round | AMOLED | 5.1 |
| Instinct® 3 Solar 45mm / 50mm info | 176 x 176 | semi-octagon | Memory-In-Pixel (2 colors) | 5.1 |
| Instinct® Crossover info | 176 x 176 | semi-octagon | Memory-In-Pixel (2 colors) | 3.4 |
| Instinct® Crossover AMOLED info | 390 x 390 | round | AMOLED | 5.1 |
| Instinct® E 40mm info | 166 x 166 | semi-octagon | Memory-In-Pixel (2 colors) | 5.1 |
| Instinct® E 45mm info | 176 x 176 | semi-octagon | Memory-In-Pixel (2 colors) | 5.1 |
| MARQ® (Gen 2) Athlete / Adventurer / Captain / Golfer / Carbon Edition / Commander - Carbon Edition info | 390 x 390 | round | AMOLED | 5.2 |
| MARQ® (Gen 2) Aviator info | 390 x 390 | round | AMOLED | 5.2 |
| MARQ® Adventurer info | 240 x 240 | round | Memory-In-Pixel (64 colors) | 3.4 |
| MARQ® Athlete info | 240 x 240 | round | Memory-In-Pixel (64 colors) | 3.4 |
| MARQ® Aviator info | 240 x 240 | round | Memory-In-Pixel (64 colors) | 3.4 |
| MARQ® Captain / MARQ® Captain: American Magic Edition info | 240 x 240 | round | Memory-In-Pixel (64 colors) | 3.4 |
| MARQ® Commander info | 240 x 240 | round | Memory-In-Pixel (64 colors) | 3.4 |
| MARQ® Driver info | 240 x 240 | round | Memory-In-Pixel (64 colors) | 3.4 |
| MARQ® Expedition info | 240 x 240 | round | Memory-In-Pixel (64 colors) | 3.4 |
| MARQ® Golfer info | 240 x 240 | round | Memory-In-Pixel (64 colors) | 3.4 |
| Rey™ info | 218 x 218 | round | Memory-In-Pixel (64 colors) | 3.3 |
| Venu® info | 390 x 390 | round | AMOLED | 3.3 |
| Venu® 2 info | 416 x 416 | round | AMOLED | 5.0 |
| Venu® 2 Plus info | 416 x 416 | round | AMOLED | 5.0 |
| Venu® 2S info | 360 x 360 | round | AMOLED | 5.0 |
| Venu® 3 info | 454 x 454 | round | AMOLED | 5.2 |
| Venu® 3S info | 390 x 390 | round | AMOLED | 5.2 |
| Venu® 4 41mm info | 390 x 390 | round | AMOLED | 6.0 |
| Venu® 4 45mm / D2™ Air X15 info | 454 x 454 | round | AMOLED | 6.0 |
| Venu® Mercedes-Benz® Collection info | 390 x 390 | round | AMOLED | 3.3 |
| Venu® Sq info | 240 x 240 | rectangle | Transflective Liquid-Crystal (High Color) | 3.3 |
| Venu® Sq 2 info | 320 x 360 | rectangle | AMOLED | 5.0 |
| Venu® Sq 2 Music info | 320 x 360 | rectangle | AMOLED | 5.0 |
| Venu® Sq. Music Edition info | 240 x 240 | rectangle | Transflective Liquid-Crystal (High Color) | 3.3 |
| Venu® X1 info | 448 x 486 | rectangle | AMOLED | 6.0 |
| vívoactive® info | 205 x 148 | rectangle | Memory-In-Pixel (64 colors) | 1.4 |
| vívoactive® 3 info | 240 x 240 | round | Memory-In-Pixel (64 colors) | 3.1 |
| vívoactive® 3 Mercedes-Benz® Collection info | 240 x 240 | round | Memory-In-Pixel (64 colors) | 3.0 |
| vívoactive® 3 Music info | 240 x 240 | round | Memory-In-Pixel (64 colors) | 3.2 |
| vívoactive® 3 Music LTE info | 240 x 240 | round | Memory-In-Pixel (64 colors) | 3.1 |
| vívoactive® 4 info | 260 x 260 | round | Memory-In-Pixel (64 colors) | 3.3 |
| vívoactive® 4S info | 218 x 218 | round | Memory-In-Pixel (64 colors) | 3.3 |
| vívoactive® 5 info | 390 x 390 | round | AMOLED | 5.2 |
| vívoactive® 6 info | 390 x 390 | round | AMOLED | 6.0 |
| vívoactive® HR info | 148 x 205 | rectangle | Memory-In-Pixel (64 colors) | 2.4 |

| Outdoor Handhelds | Screen Resolution | Screen Shape | Screen Technology | API Level |
| --- | --- | --- | --- | --- |
| eTrex® Touch info | 240 x 400 | rectangle | Transflective Liquid-Crystal (High Color) | 5.1 |
| GPSMAP® 66s / 66i / 66sr / 66st info | 240 x 400 | rectangle | Transflective Liquid-Crystal (High Color) | 3.1 |
| GPSMAP® 67 / 67i info | 240 x 400 | rectangle | Transflective Liquid-Crystal (High Color) | 3.2 |
| GPSMAP® 86s / 86sc / 86i / 86sci info | 240 x 400 | rectangle | Transflective Liquid-Crystal (High Color) | 3.0 |
| GPSMAP® H1 / H1i Plus info | 282 x 470 | rectangle | Transflective Liquid-Crystal (High Color) | 5.0 |
| Montana® 7 Series info | 480 x 800 | rectangle | Transflective Liquid-Crystal (High Color) | 3.2 |
| Oregon® 7 Series info | 240 x 400 | rectangle | Transflective Liquid-Crystal (High Color) | 3.0 |
| Rino® 7 Series info | 240 x 400 | rectangle | Transflective Liquid-Crystal (High Color) | 3.0 |

| Edge | Screen Resolution | Screen Shape | Screen Technology | API Level |
| --- | --- | --- | --- | --- |
| Edge® 1000 / Explore info | 240 x 400 | rectangle | Transflective Liquid-Crystal (High Color) | 2.4 |
| Edge® 1030 info | 282 x 470 | rectangle | Transflective Liquid-Crystal (High Color) | 3.3 |
| Edge® 1030 / Bontrager info | 282 x 470 | rectangle | Transflective Liquid-Crystal (High Color) | 3.3 |
| Edge® 1030 Plus info | 282 x 470 | rectangle | Transflective Liquid-Crystal (High Color) | 3.3 |
| Edge® 1040 / 1040 Solar info | 282 x 470 | rectangle | Transflective Liquid-Crystal (High Color) | 6.0 |
| Edge® 1050 info | 480 x 800 | rectangle | Transflective Liquid-Crystal (High Color) | 6.0 |
| Edge® 130 info | 230 x 303 | rectangle | Transflective Liquid-Crystal (Single Color) | 3.1 |
| Edge® 130 Plus info | 230 x 303 | rectangle | Transflective Liquid-Crystal (Single Color) | 3.2 |
| Edge® 520 info | 200 x 265 | rectangle | Transflective Liquid-Crystal (High Color) | 2.4 |
| Edge® 520 Plus info | 200 x 265 | rectangle | Transflective Liquid-Crystal (High Color) | 3.1 |
| Edge® 530 info | 246 x 322 | rectangle | Transflective Liquid-Crystal (High Color) | 3.3 |
| Edge® 540 / 540 Solar info | 246 x 322 | rectangle | Transflective Liquid-Crystal (High Color) | 6.0 |
| Edge® 550 info | 420 x 600 | rectangle | Transflective Liquid-Crystal (High Color) | 6.0 |
| Edge® 820 / Explore info | 200 x 265 | rectangle | Transflective Liquid-Crystal (High Color) | 3.1 |
| Edge® 830 info | 246 x 322 | rectangle | Transflective Liquid-Crystal (High Color) | 3.3 |
| Edge® 840 / 840 Solar info | 246 x 322 | rectangle | Transflective Liquid-Crystal (High Color) | 6.0 |
| Edge® 850 info | 420 x 600 | rectangle | Transflective Liquid-Crystal (High Color) | 6.0 |
| Edge® Explore info | 240 x 400 | rectangle | Transflective Liquid-Crystal (High Color) | 3.1 |
| Edge® Explore 2 info | 240 x 400 | rectangle | Transflective Liquid-Crystal (High Color) | 5.1 |
| Edge® MTB info | 240 x 320 | rectangle | Transflective Liquid-Crystal (High Color) | 6.0 |

2. How to determine devices compatibility with a watchface - Connect IQ App Development Discussion - Connect IQ - Garmin Forums
   URL: https://forums.garmin.com/developer/connect-iq/f/discussion/257847/how-to-determine-devices-compatibility-with-a-watchface
   How to determine devices compatibility with a watchface - Connect IQ App Development Discussion - Connect IQ - Garmin Forums

- Apps & Software
- Outdoor Recreation
- Sports & Fitness
- Pilots
- Developer
- Beta Program
- German Forum
- More
- Cancel

- State Not Answered
- Replies 5 replies
- Subscribers 19 subscribers
- Views 1239 views
- Users 0 members are here

- devices compatibility

Options

- Share
- More
- Cancel

Related

# How to determine devices compatibility with a watchface

Hello,

As a part of my tests I have tried to run my watchface of some simulated devices, and interestingly found that it would e.g. run on VA4 and Fenix 6, but not on Fenix 5;

I know I have some code, which requires/uses SDK 3.2.x (e.g. Toybox.Weather), and with that in mind, looked around and found that:

- as per https://developer.garmin.com/connect-iq/compatible-devices/ VA4/Fenix5/Fenix6 are all 3.0 compatible (note no minor version)

- as per their compiler.xml, VA4/Fenix5/Fenix6 all have "connectIQVersion": "3.1.6"

And yet, while I can build-for/sim VA4/Fenix6, for Fenix5 I get "BUILD: ERROR: Device 'fenix5' does not support SDK version '3.2.0'".

Could anyone advise ?

Further, the bigger question in this context, is how to define compatible devices when I publish, given the limitations are:

- min sdk 3.2.0

- round face

- Sign in to reply
- Cancel

## Top Replies

RxC said:

- as per https://developer.garmin.com/connect-iq/compatible-devices/ VA4/Fenix5/Fenix6 are all 3.0 compatible (note no minor version)

That table isn't always up-to-date. The best way to find out…

- Round watches is easy. Out of all the watches with CIQ 3 or greater, the Venu Sq is the only one that's not round.for 3.2, understand it's not the same on everything. For instance, the f5+ devices…
- Another thing to consider is the fr245/m is round, runs CIQ 3.2 (with weather), but doesn't have a baro so you can't show floor, elevation history, temperature history and a few other things. So…

## All Replies

Round watches is easy. Out of all the watches with CIQ 3 or greater, the Venu Sq is the only one that's not round.

for 3.2, understand it's not the same on everything. For instance, the f5+ devices have 3.2, but don't support weather. If in doubt, "has" protect your code.

When you look in the device json files, remember that is the min CIQ version supported, so even if you see something like 3.1.6, devices could have 3.2.x. In the sim, you can tell by looking at the run config in eclipse and see if you can select 3.2.x

Another thing to consider is the fr245/m is round, runs CIQ 3.2 (with weather), but doesn't have a baro so you can't show floor, elevation history, temperature history and a few other things. So there's other things to consider when adding new targets.

RxC said:

- as per https://developer.garmin.com/connect-iq/compatible-devices/ VA4/Fenix5/Fenix6 are all 3.0 compatible (note no minor version)

That table isn't always up-to-date. The best way to find out what version is supported by a device is to look at the simulator configuration files . If you are using a recent SDK on windows look in C:\Users\ \AppData\Roaming\Garmin\ConnectIQ\Devices\**\compiler.json. You will see that vva4 has ConnectIQ 3.2 support and fenix5 is only 3.1.6.

RxC said:

And yet, while I can build-for/sim VA4/Fenix6, for Fenix5 I get "BUILD: ERROR: Device 'fenix5' does not support SDK version '3.2.0'".

As I mentioned above, the fenix5 device only has 3.1.6 support. It sounds like your manifest file has a minSdkVersion attribute that is set to 3.2.0, but you've enabled support for a device that doesn't have 3.2.0 support. The manifest editor in eclipse should make this difficult to do. When you set the minSdkVersion it should not allow you to select devices that don't have support.

Thank you,

Indeed, overlooked the fact VA4 compiler.xml actually contains a second connectIQVersion w/ "3.2.0".

Travis.ConnectIQ said:

The manifest editor in eclipse should make this difficult to do. When you set the minSdkVersion it should not allow you to select devices that don't have support.

As recently mentioned in this forum, the Eclipse manifest editor has a bug where the increasing the minSdkVersion only greys out the checkboxes for the devices which are no longer available, but does not uncheck any such devices which were already selected. This is also reflected in the fact that manifest.xml still has an entry for these devices.

e.g.

1) Create app with min SDK version of 1.3

2) Select a bunch of devices including FR230 (CIQ 2)

3) Change min SDK version to 3.x

4) Note that FR230 is still checked (but greyed out) and still appears in manifest.xml

3. Device API levels - Connect IQ App Development Discussion - Connect IQ - Garmin Forums
   URL: https://forums.garmin.com/developer/connect-iq/f/discussion/354168/device-api-levels
   Device API levels - Connect IQ App Development Discussion - Connect IQ - Garmin Forums

- State Not Answered
- Replies 9 replies
- Subscribers 20 subscribers
- Views 5007 views
- Users 0 members are here

- apilevel

Options

- Share
- More
- Cancel

Related

# Device API levels

Is there any way to know when and which version is available to devices?

The "Compatible Devices" page seems to be way behind? As I understand it

the API level shown there is the max level. E.g. the devices with the most recent API

(4.2) is still showing 4.2.0 there, when 4.2.1 was reported at least as early as June to

be working on a number of devices ...

Cheers

- Sign in to reply
- Cancel

## Top Replies

- TL;DR for any given device, compiler.json in the SDK device folder has the minimum required CIQ version for that device, which is also the maximum expected CIQ version for the app dev.--Open the SDK…

## All Replies

TL;DR for any given device, compiler.json in the SDK device folder has the minimum required CIQ version for that device, which is also the maximum expected CIQ version for the app dev.

--

Open the SDK's devices folder, and navigate to compiler.json for the device of interest.

On Windows, the devices folder is at %appdata%\garmin\connectiq\devices. This folder contains a separate folder for each device (e.g. fr265).

Each device folder has several files, including compiler.json, has a partNumbers array containing information about each part number (this is not the same part number that's shown on the box or listed on the website).

Newer devices may only have one part number, while older devices may have different part numbers for worldwide (WW) and Asia-Pacific (APAC) devices. The value for worldWidePartNumber will indicate which partNumber is WW (which means that its CIQ version will always be newer or equal to the APAC CIQ version.)

Each partNumbers element has the following fields:

connectIQVersion: e.g. "4.2.3"

firmwareVersion: e.g. 1616

number: the actual part number e.g. "006-B4257-00"

connectIqVersion and firmwareVersion are actually the minimum versions an app built with device file can expect to see when deployed to a device. This is enforced when the user tries to download the app - if the device has a lower CIQ or firmware version than the minimum, the user will be prompted to updated.

Since those are the minimum required versions for the user, they are also the maximum expected versions for the app dev. e.g. If we know every user has 4.2.3 or higher, then we can't assume they have anything higher than 4.2.3.

Thanks,

So ... do the compiler.json files represent what's been pushed out to actual devices?

It's the minimum api level that the device can have to install an app, not what may be on the device today.

Also note that you may see multiple part numbers in the same file, with the common case being APAC and Word Wide devices, where the APAC version may be lower than the WW version.

Look at using "has" to see if something is supported or not

No, and you're welcome to vote on this "feature" (documentation) request: forums.garmin.com/.../improve-documentation-add-api-levels-and-system-levels-to-device-reference

I'll add that any "available" information (documentation, compiler.json) only has information about what would be the max api level if a certain kind of device was upgraded to the latest available firmware. There's no information on the minimum possible. Even when you think you have that information it's not really that. When you look at a certain device family, and then split it by part numbers then you'll only know what would be the minimum api level of that device family if all the devices would be ugraded to the latest firmware version. The problem is that once there is a new FW version the json is updated to indicate the CURRENT minimum version, but if a device doesn't upgrade the FW then they still have an older CIQ with older api versions... And I am not aware of any official documentation that would tell what would be the lowest version of a part number if the FW wasn't upgraded since the 1st item that came out of the factory.

BTW I made some effort to collect the data, and it may be correct for devices that came out since I started the project (but not necessarily, because it depends on the json files in the devices directory, that might or might not be correct, and more importantly I am not checking every day if there are new versions of the devices in the sdk manager so I might have skipped/missed some) The idea is that I have a script that scans the device files and extracts the min, max CIQ version for the devices, and it ADDS the newly available versions to a list, but also KEEPS the older versions in the csv files: https://github.com/flocsy/garmin-dev-tools(look at the files under csv/)

Interesting, thanks.

So I am drawing the conclusion that when the ciq version is updated in the compiler.json, then it's also possible for users to update real devices (timing difference between sdk update and real device update, earlier or later)?

Devices can. and often do, get a CIQ version update before you see it in compiler.json. The last digit (the "3" in 4.2.3 for example) can just indicate a bug fix level. It might still show as 4.2.1 in compiler.json. as that's the minimum level a user needs to have to install your app. If the user has a level less that 4.2.1, they will be told they need a firmware update to install your app, but they don't need to have 4.2.3 -just 4.2.1 or later..

flocsy🤠 said:

I'll add that any "available" information (documentation, compiler.json) only has information about what would be the max api level if a certain kind of device was upgraded to the latest available firmware. There's no information on the minimum possible. Even when you think you have that information it's not really that.

I don't agree with this. Based on other threads and personal experience, if an app is built against a given device file, then the user will not be able to install it unless their device has the CIQ API version and firmware version specified in the device file, at a minimum. You will see that the exported .IQ file (zip archive) contains a manifest XML file which has the CIQ/firmware version for each device (and the naming scheme is something like "minApiVersion" which indeed suggests it's the minimum version.)

This means a device file does indeed specify the minimum possible CIQ version (*) for any given device, for apps that are built against that version of the device file. The only use case which isn't covered by looking at the latest device files is when you have an *old* app which hasn't been built again the latest device files. In this case, if you have a copy of the exported IQ file, you should be able to look at manifest to determine the minimum CIQ/firmware versions for that version of the app.

(* which is also the maximum CIQ version that you can safely *assume* is present)

Some anecdotal evidence: look at all the threads complaining that users can't install Spotify on their device because it has old firmware. There's also another thread that directly addresses this topic, but I don't have a link to it at the moment.

You can also test this for yourself by hand-editing a device file to increase the API version or firmware version to be greater than what's installed on your real device, uploading a beta app built against that device file, and observing what happens when you try to install it.

By the way, as far as what's in the manifest.xml file, this is what I pretty much always have:

minApiLevel="1.2.0"

if an app is only for devices with 3.x or higher, that is determined by what targets I add for the app. I just don't include any CIQ 1 or CIQ 2 devices.

The TL;DR is that the firmware version and CIQ version in a device's compiler.json are in fact the minimum versions your app will see on the device, when your app is built against that version of the device file; if the device doesn't have those versions, the store will prevent the user from installing the app.

This is the cause of the infamous complaints about being unable to install Spotify (for example) without a device update.

But yes, it is possible for a device to have a lower or higher version. If the version is lower, then they will be asked to update their app. If the version is higher, the app will install without any problems.

4. Connect IQ 3.1 Now Available! - News & Announcements - Connect IQ - Garmin Forums
   URL: https://forums.garmin.com/developer/connect-iq/b/news-announcements/posts/connect-iq-3-1-now-available
   Connect IQ 3.1 Now Available! - News & Announcements - Connect IQ - Garmin Forums

- Connect IQ Developers
- SDK Release

- Share
- Subscribe by email
- More
- Cancel

Related

Recommended

Sep 9, 2019

At long last Connect IQ 3.1 is here! Here are some of the new features it brings to the table:

- Exception Reporting: Access crash logs from the field and fix issues faster
- Animations: Use the new Monkey Motion tool to add animated clips to your apps
- Bluetooth Low Energy: Write apps that communicate with Bluetooth Low Energy (BLE) peripherals
- Relative Positions in Layouts: Use percentages in layouts for coordinates to make layouts that scale across a range of products
- Expanded Storage: Store more information on device.
- Wi-Fi in Device Apps: Use the new Communications.SyncDelegate to download content over Wi-Fi
- ANT+ Manufacturer Pages: Access manufacturer pages of connected ANT+ peripherals

You may have noticed we also launched some products the past few weeks. I’d like to take a moment to talk you through some of the products and new features.

vívoactive® 4/4S – The vívoactive 4 and 4S are the natural continuation of the vívoactive line. There are two sizes (small and regular) both of which have the latest Elevate sensors and support music. The one button version has been updated to have two buttons on the right side; one for start/stop and another for back.

fēnix® 6S/6 – The fēnix 6s/6 are successors to the fēnix 5 series. There are two sizes (small and regular) with the latest Elevate sensors.

fēnix 6S/6/6X Pro – The fēnix 6s/6/6X Pro are successors to the fēnix 5 Plus series. There are three sizes (small, regular, and Shaq) with the latest Elevate sensors and all support music. The 6X Pro Solar adds a solar cell to allow charging while operating outside.

Venu – The Venu is a new variant of the vívoactive 4. In addition to the latest Elevate sensors and music, the Venu is the first Garmin wearable to feature an AMOLED screen. This is the most beautiful screen ever on a Garmin watch but introduces new considerations for your apps.

Legacy Series – These are vívoactive 4 and 4s units branded with Marvel content. For all intents and purposes consider them vívoactive 4 and 4s units.

Here is a technical breakdown of the devices:

| Feature | vívoactive 4S | vívoactive 4 | fēnix 6S | fēnix 6S Pro | fēnix 6 | fēnix 6 Pro | fēnix 6X Pro | Venu |
| --- | --- | --- | --- | --- | --- | --- | --- | --- |
| Screen | MIP | MIP | MIP | MIP | MIP | MIP | MIP | AMOLED |
| Resolution | 218x218 | 260x260 | 240x240 | 240x240 | 260x260 | 260x260 | 280x280 | 390x390 |
| Icon | 36x36 | 43x43 | 40x40 | 40x40 | 40x40 | 40x40 | 40x40 | 40x40 |
| Colors | 64 | 64 | 64 | 64 | 64 | 64 | 64 | 16 BPP |
| Music | Yes | Yes | No | Yes | No | Yes | Yes | Yes |
| Maps | No | No | No | Yes | No | Yes | Yes | No |
| Inputs | Touchscreen | Touchscreen | Buttons | Buttons | Buttons | Buttons | Buttons | Touchscreen |
| Widget Glances | No | No | Yes | Yes | Yes | Yes | Yes | No |
| Watch Face RAM | 96K | 96K | 96 KB | 96K | 96 KB | 96K | 96K | 512 KB |
| Data Field RAM | 32 KB | 32 KB | 32 KB | 128 KB | 32 KB | 128 KB | 128 KB | 32 KB |
| Widget RAM | 512 KB | 512 KB | 64 KB | 1 MB | 64 KB | 1 MB | 1 MB | 512 KB |
| App RAM | 1 MB | 1 MB | 128 KB | 1.25 MB | 128 KB | 1.25 MB | 1.25 MB | 1 MB |
| Music RAM | 512 KB | 512 KB | N/A | 512 KB | N/A | 512 KB | 512 KB | 512 KB |
| Glance RAM | N/A | N/A | 32 KB | 64 KB | 32 KB | 64 KB | 64 KB | N/A |
| Background RAM | 64 KB | 32 KB | 32 KB | 32 KB | 32 KB | 32 KB | 32 KB | 64 KB |

The fēnix 6 and Venu introduce some features we did not cover at Connect IQ summit that are only available in the 3.1 SDK. Lets talk about them briefly.

## Widget Glances

The fēnix 6 series introduces some changes for widgets that will permeate across the Connect IQ ecosystem. The widget loop is converting from a carousel to a list presentation, which will make it much faster for users to navigate their information. When the user clicks on your glance, it will launch into the foreground.

To support this new behavior, CIQ is introducing in 3.1 a new glance background type that allows your widget to update its glance presentation behind the scenes.

1. Implement getGlanceView in your Application.AppBase instance
2. Implement an instance of GlanceView that renders the base view
3. Adapt your first page on Fenix 6 products to be the click in page instead of the base page.

## AMOLED

The Venu is the first Garmin watch with an AMOLED screen. Your apps now can have breathtaking presentations of information and gorgeous imagery, while still retaining days of battery life. However, now that we have given you all these gorgeous colors, could you, like, not use them?

Please?

Here is the challenge with AMOLED – every pixel draws power. If you want your apps to fall within the regular amount of battery life, you want to have as much black on screen as possible, especially in screens that are showing activity information. You’ll notice that with most of the native applications, black is the new black. It’s okay to work a periodic splash screen or gradient into your apps – make the app look great! – but for screens that are supposed to show constantly updating data, the blacker the better. Also, if you have header and footer gradients, try to have the darker parts at the outer edges.

Just remember this handy guide when doing app layouts for Venu:

### AMOLED Always On Watch Faces

Always On watch faces behave differently from MIP to AMOLED. With MIP screens, you can use View.onPartialUpdate to update a portion of the screen every second. With AMOLED screen, this is no longer allowed. Instead, when WatchUi.onEnterSleep is called, you are allowed to render a watch face that must obey the rules of the AMOLED burn-inprotector:

- No more than 10% screen pixels can be on
- No pixel can be on longer than 3 mins

Ways you can prevent burn in are by drawing the time with a thin font, shifting the time every minute as not to repeatedly leave the same pixels on, and not having static tick marks that leave the same pixels on.

Note that watch faces can detect whether a product has screen protection enforced by checking the value of DeviceSettings.requiresBurnInProtection.

### Note about AMOLED Resources

The default color depth for the Venu is 16 bits per pixel, similar to Edge products. If you do not use the option when importing resources, be aware that your images will grow in file size, and by proxy take a lot longer to download to the device. You can also add the attribute compress="true" to your image resources, with the trade offs that images may take longer to load and compression is not available on Connect IQ 1.x products.

## Start Today

New Features. Better Tools. New Devices. Get the SDK today and make your apps dance and sing.

5. Fenix 5 plus api version? - Connect IQ App Development Discussion - Connect IQ - Garmin Forums
   URL: https://forums.garmin.com/developer/connect-iq/f/discussion/340738/fenix-5-plus-api-version
   Fenix 5 plus api version? - Connect IQ App Development Discussion - Connect IQ - Garmin Forums

- Cancel
- More
- German Forum
- Beta Program
- Developer
- Pilots
- Sports & Fitness
- Outdoor Recreation
- Apps & Software

- Users 0 members are here
- Views 460 views
- Subscribers 17 subscribers
- Replies 1 reply
- State Not Answered

Options

- Cancel
- More
- Share

Related

# Fenix 5 plus api version?

What API version does Phoenix 5 Plus have? The site says 3.3.0, and when programming, all the functionality is from 3.1.0

- Cancel
- Sign in to reply

What are you trying to do? When you look at the API doc, you'll see "Since API Level" but you also want to check "Supported devices". In the case of the fenix5+, It may be 3.3.3 , and Toybox.Weather is "Since API Level 3.2.0", but the fenix5+ isn't listed as a Supported Device for example. The Fenix5+ doesn't have the weather API...

6.
   URL: https://the5krunner.com/2021/10/13/garmin-ciq-level-5-inbound-for-2022-what-is-it/
   Skip to content

Garmin Insider News Technology

Yes it does say Edge 1040 – Some other slightly out-of-date info is updated in the table further below

# Garmin CIQ System 5 Is Coming

News today of some of the details that will be supported in CIQ next year. We will probably see this in System 5 (CIQ 3, API Level 3.3?). Which you might see (incorrectly?) referred to as CIQ 5.

Whilst this is a feature that will initially be of interest to developers it will affect the capabilities of many Garmin devices and some new ones in 2022.

## App Store on the Watch

Garmin’s CIQ store was initially only available through a browser but the addition of a smartphone app made it much easier to choose and install those extra bits of ‘must have’ functionality on your Garmin watches and bike computers. Well both of those versions of the CIQ store (web, smartphone) will be revamped.

Better still, taking a leaf out of Google’s Wear OS, the app store will also be accessible on the watch. Super cool!

It also looks like the Wi-Fi enabled devices will be able to download CIQ apps and their updates over your home WiFi as well as enable you to tinker with some of their settings on the watch.

Very Nice.

## Compatability

Check out the first image at the top and compare it to the one immediately above.

It looks like most devices that support CIQ System 4 will also support the new CIQ System 5 where hardware permits.

## Also New

We will see new analytics and new metrics that can be incorporated into CIQ, including Stress Data, VO2max and Body Battery.

## Take Out

Perhaps not as big a leap forward as in previous years but there are some tantalising hints at continued improvements from Garmin, especially to new devices next year.

If you want to read more technical detail then check out the Garmin Developer’s report on this same subject. Elsewhere, Ray Maker points out that some of the wording used by Garmin suggests that AMOLED is the chosen way forward for its high-end, high-resolution devices.

## More Info – Currently Supported API Level

| Watches/Wearables | API Level | Screen Resolution | Screen Shape | Screen Technology |
| --- | --- | --- | --- | --- |
| Approach® S60 | 2.4.0 | 240 x 240 | round | Memory-In-Pixel (64 colors) |
| Approach® S62 | 3.0.0 | 260 x 260 | round | Memory-In-Pixel (64 colors) |
| Captain Marvel | 3.2.0 | 218 x 218 | round | Memory-In-Pixel (64 colors) |
| D2™ Air | 3.2.0 | 390 x 390 | round | AMOLED |
| D2™ Bravo | 1.4.0 | 218 x 218 | round | Memory-In-Pixel (16 colors) |
| D2™ Bravo Titanium | 1.4.0 | 218 x 218 | round | Memory-In-Pixel (16 colors) |
| D2™ Charlie | 3.0.0 | 240 x 240 | round | Memory-In-Pixel (64 colors) |
| D2™ Delta | 3.1.0 | 240 x 240 | round | Memory-In-Pixel (64 colors) |
| D2™ Delta PX | 3.1.0 | 240 x 240 | round | Memory-In-Pixel (64 colors) |
| D2™ Delta S | 3.1.0 | 240 x 240 | round | Memory-In-Pixel (64 colors) |
| Darth Vader™ | 3.2.0 | 260 x 260 | round | Memory-In-Pixel (64 colors) |
| Descent™ Mk1 | 3.0.0 | 240 x 240 | round | Memory-In-Pixel (64 colors) |
| Descent™ Mk2 / Descent™ Mk2i | 3.2.0 | 280 x 280 | round | Memory-In-Pixel (64 colors) |
| Descent™ Mk2 S | 3.2.0 | 240 x 240 | round | Memory-In-Pixel (64 colors) |
| Enduro™ | 3.2. 0 | 280 x 280 | round | Memory-In-Pixel (64 colors) |
| epix™ | 1.2.0 | 205 x 148 | rectangle | Memory-In-Pixel (64 colors) |
| fēnix® 3 / tactix® Bravo / quatix® 3 | 1.4.0 | 218 x 218 | round | Memory-In-Pixel (16 colors) |
| fēnix® 3 HR | 1.4.0 | 218 x 218 | round | Memory-In-Pixel (16 colors) |
| fēnix® 5 / quatix® 5 | 3.1.0 | 240 x 240 | round | Memory-In-Pixel (64 colors) |
| fēnix® 5 Plus | 3.2.0 | 240 x 240 | round | Memory-In-Pixel (64 colors) |
| fēnix® 5S | 3.1.0 | 218 x 218 | round | Memory-In-Pixel (64 colors) |
| fēnix® 5S Plus | 3.2.0 | 240 x 240 | round | Memory-In-Pixel (64 colors) |
| fēnix® 5X / tactix® Charlie | 3.1.0 | 240 x 240 | round | Memory-In-Pixel (64 colors) |
| fēnix® 5X Plus | 3.2.0 | 240 x 240 | round | Memory-In-Pixel (64 colors) |
| fēnix® 6 / 6 Solar / 6 Dual Power | 3.2.0 | 260 x 260 | round | Memory-In-Pixel (64 colors) |
| fēnix® 6 Pro / 6 Sapphire / 6 Pro Solar / 6 Pro Dual Power / quatix® 6 | 3.2.0 | 260 x 260 | round | Memory-In-Pixel (64 colors) |
| fēnix® 6S / 6S Solar / 6S Dual Power | 3.2.0 | 240 x 240 | round | Memory-In-Pixel (64 colors) |
| fēnix® 6S Pro / 6S Sapphire / 6S Pro Solar / 6S Pro Dual Power | 3.2.0 | 240 x 240 | round | Memory-In-Pixel (64 colors) |
| fēnix® 6X Pro / 6X Sapphire / 6X Pro Solar / tactix® Delta Sapphire / Delta Solar / Delta Solar – Ballistics Edition / quatix® 6X / 6X Solar / 6X Dual Power | 3.2.0 | 280 x 280 | round | Memory-In-Pixel (64 colors) |
| fēnix® Chronos | 3.1.0 | 218 x 218 | round | Memory-In-Pixel (64 colors) |
| First Avenger | 3.2.0 | 260 x 260 | round | Memory-In-Pixel (64 colors) |
| Forerunner® 230 | 1.4.0 | 215 x 180 | semi-round | Memory-In-Pixel (16 colors) |
| Forerunner® 235 | 1.4.0 | 215 x 180 | semi-round | Memory-In-Pixel (16 colors) |
| Forerunner® 245 | 3.2.0 | 240 x 240 | round | Memory-In-Pixel (64 colors) |
| Forerunner® 245 Music | 3.2.0 | 240 x 240 | round | Memory-In-Pixel (64 colors) |
| Forerunner® 45 | 1.4.0 | 208 x 208 | round | Memory-In-Pixel (8 colors) |
| Forerunner® 55 | 3.2.0 | 208 x 208 | round | Memory-In-Pixel (8 colors) |
| Forerunner® 630 | 1.4.0 | 215 x 180 | semi-round | Memory-In-Pixel (16 colors) |
| Forerunner® 645 | 3.1.0 | 240 x 240 | round | Memory-In-Pixel (64 colors) |
| Forerunner® 645 Music | 3.2.0 | 240 x 240 | round | Memory-In-Pixel (64 colors) |
| Forerunner® 735xt | 2.4.0 | 215 x 180 | semi-round | Memory-In-Pixel (16 colors) |
| Forerunner® 745 | 3.2.0 | 240 x 240 | round | Memory-In-Pixel (64 colors) |
| Forerunner® 920XT | 1.4.0 | 205 x 148 | rectangle | Memory-In-Pixel (16 colors) |
| Forerunner® 935 | 3.1.0 | 240 x 240 | round | Memory-In-Pixel (64 colors) |
| Forerunner® 945 | 3.2.0 | 240 x 240 | round | Memory-In-Pixel (64 colors) |
| Forerunner® 945 LTE | 3.2.0 | 240 x 240 | round | Memory-In-Pixel (64 colors) |
| Garmin Swim™ 2 | 1.4.0 | 208 x 208 | round | Memory-In-Pixel (8 colors) |
| MARQ® Adventurer | 3.2.0 | 240 x 240 | round | Memory-In-Pixel (64 colors) |
| MARQ® Athlete | 3.2.0 | 240 x 240 | round | Memory-In-Pixel (64 colors) |
| MARQ® Aviator | 3.2.0 | 240 x 240 | round | Memory-In-Pixel (64 colors) |
| MARQ® Captain / MARQ® Captain: American Magic Edition | 3.2.0 | 240 x 240 | round | Memory-In-Pixel (64 colors) |
| MARQ® Commander | 3.2.0 | 240 x 240 | round | Memory-In-Pixel (64 colors) |
| MARQ® Driver | 3.2.0 | 240 x 240 | round | Memory-In-Pixel (64 colors) |
| MARQ® Expedition | 3.2.0 | 240 x 240 | round | Memory-In-Pixel (64 colors) |
| MARQ® Golfer | 3.2.0 | 240 x 240 | round | Memory-In-Pixel (64 colors) |
| Rey™ | 3.2.0 | 218 x 218 | round | Memory-In-Pixel (64 colors) |
| Venu® Sq | 3.2.0 | 240 x 240 | rectangle | Transflective Liquid-Crystal (High Color) |
| Venu® Sq. Music Edition | 3.2.0 | 240 x 240 | rectangle | Transflective Liquid-Crystal (High Color) |
| Venu™ | 3.2.0 | 390 x 390 | round | AMOLED |
| Venu™ 2 | 4.0.0 | 416 x 416 | round | AMOLED |
| Venu™ 2S | 4.0.0 | 360 x 360 | round | AMOLED |
| Venu™ Mercedes-Benz® Collection | 3.2.0 | 390 x 390 | round | AMOLED |
| vívoactive® | 1.4.0 | 205 x 148 | rectangle | Memory-In-Pixel (64 colors) |
| vívoactive® 3 | 3.1.0 | 240 x 240 | round | Memory-In-Pixel (64 colors) |
| vívoactive® 3 Mercedes-Benz® Collection | 3.0.0 | 240 x 240 | round | Memory-In-Pixel (64 colors) |
| vívoactive® 3 Music | 3.2.0 | 240 x 240 | round | Memory-In-Pixel (64 colors) |
| vívoactive® 3 Music LTE | 3.1.0 | 240 x 240 | round | Memory-In-Pixel (64 colors) |
| vívoactive® 4 | 3.2.0 | 260 x 260 | round | Memory-In-Pixel (64 colors) |
| vívoactive® 4S | 3.2.0 | 218 x 218 | round | Memory-In-Pixel (64 colors) |
| vívoactive® HR | 2.4.0 | 148 x 205 | rectangle | Memory-In-Pixel (64 colors) |
| Edge | API Level | Screen Resolution | Screen Shape | Screen Technology |
| Edge® 1000 / Explore | 2.4.0 | 240 x 400 | rectangle | Transflective Liquid-Crystal (High Color) |
| Edge® 1030 | 3.2.0 | 282 x 470 | rectangle | Transflective Liquid-Crystal (High Color) |
| Edge® 1030 / Bontrager | 3.2.0 | 282 x 470 | rectangle | Transflective Liquid-Crystal (High Color) |
| Edge® 1030 Plus | 3.2.0 | 282 x 470 | rectangle | Transflective Liquid-Crystal (High Color) |
| Edge® 130 | 3.1.0 | 230 x 303 | rectangle | Transflective Liquid-Crystal (Single Color) |
| Edge® 130 Plus | 3.2.0 | 230 x 303 | rectangle | Transflective Liquid-Crystal (Single Color) |
| Edge® 520 | 2.4.0 | 200 x 265 | rectangle | Transflective Liquid-Crystal (High Color) |
| Edge® 520 Plus | 3.1.0 | 200 x 265 | rectangle | Transflective Liquid-Crystal (High Color) |
| Edge® 530 | 3.2.0 | 246 x 322 | rectangle | Transflective Liquid-Crystal (High Color) |
| Edge® 820 / Explore | 3.1.0 | 200 x 265 | rectangle | Transflective Liquid-Crystal (High Color) |
| Edge® 830 | 3.2.0 | 246 x 322 | rectangle | Transflective Liquid-Crystal (High Color) |
| Edge® Explore | 3.1.0 | 240 x 400 | rectangle | Transflective Liquid-Crystal (High Color) |
| Outdoor Handhelds | API Level | Screen Resolution | Screen Shape | Screen Technology |
| GPSMAP® 66s / 66sr / 66st | 3.0.0 | 240 x 400 | rectangle | Transflective Liquid-Crystal (High Color) |
| GPSMAP® 86s / 86sc / 86i / 86sci | 3.0.0 | 240 x 400 | rectangle | Transflective Liquid-Crystal (High Color) |
| Montana® 7 Series | 3.1.0 | 480 x 800 | rectangle | Transflective Liquid-Crystal (High Color) |
| Oregon® 7 Series | 3.0.0 | 240 x 400 | rectangle | Transflective Liquid-Crystal (High Color) |
| Rino® 7 Series | 3.0.0 | 240 x 400 | rectangle | Transflective Liquid-Crystal (High Color) |

Last Updated on 25 January 2026 by the5krunner

---

### My favourite kit and nutrition

- Injinji – Runners protect your toes. Avoid discomfort and minor injury. Run more. Run faster. I use them.
- Garmin 90-degree charging adapter — The small adapter that keeps your charging cables tidy. Essential for race day. I use one.
- Garmin charging puck — the fastest and most reliable way to top up your Garmin before a session. I use one.
- Ravemen FR300 — Front light that mounts directly under your Garmin or Wahoo head unit. Keeps your bars clean and your beam pointed where it matters. I use one.
- Body Glide – The blue anti-chafe stick that all swimmers and many runners use. I use it.
- Maurten — The race nutrition trusted by elite athletes. Gels and drink mixes engineered to be easy on the stomach. I use them.
- Garmin Varia RTL515 — A radar rear light that alerts you to vehicles approaching from behind. Pairs with your Edge or Garmin watch. I use this model.
- Favero Assioma Pro RS2 — The power-meter pedals most serious cyclists choose. Accurate, easy to move between bikes. I use this model.
- Garmin Forerunner 970 — A serious choice for a pro-grade triathlon watch. I use this.
- Polar H10 — My daily driver for accurate, waking HRV readings.
- Wahoo ELEMNT Roam 3 — The bike computer that has the feature Garmin lacks: usability. I use mine on most rides.

---

---

### Reader-Powered Content

This content is not sponsored. It’s mostly me behind the labour of love, which is this site, and I appreciate everyone who supports it.

Support the site: Follow (free, fewer ads) · Subscribe (paid, ad-free) · Buy Me A Coffee ❤

All articles are written by real people, fact-checked, and verified for originality. See the Editorial Policy. FTC: Affiliate Disclosure — some links pay commission. As an Amazon Associate, I earn from qualifying purchases.

the5krunner

tfk is the founder and author of the5krunner, an independent endurance sports technology publication. With 20 years of hands-on testing of GPS watches and wearables, and competing in triathlons at an international age-group level, tfk provides in-depth expert analysis of fitness technology for serious athletes and endurance sport competitors. ID

### Share this:

- Share on WhatsApp (Opens in new window) WhatsApp
- Share on X (Opens in new window) X
- Email a link to a friend (Opens in new window) Email
- Share on Facebook (Opens in new window) Facebook
- Share on Reddit (Opens in new window) Reddit
- Share on LinkedIn (Opens in new window) LinkedIn
- Share on Pinterest (Opens in new window) Pinterest
- More
- Share on Nextdoor (Opens in new window) Nextdoor
- Share on Mastodon (Opens in new window) Mastodon
- Print (Opens in new window) Print
- Share on X (Opens in new window) X
- Share on Tumblr (Opens in new window) Tumblr
- Share on Threads (Opens in new window) Threads
- Share on Bluesky (Opens in new window) Bluesky
- Share on Telegram (Opens in new window) Telegram

## 13 thoughts on “Garmin CIQ System 5 Inbound for 2022 – What is it !”

1. Well well WELL. This makes the choice between getting what I need now (a new watch) and waiting for the Fenix 7 (which looks like it’ll add the new HR sensor, LTE and maybe the Enduro battery, which I won’t really need) a lot harder.
2. The 1030/Plus could have been rounded upwards.
3. it could but there is other info where some of the Garmin app code has both the edge 1030+ and 1040 in the same doc. (but still could be a leftover)

```
1. Ciq on the watch, is a huge step forward, not just for Garmin, that’s a major sector step forward to the unified smart/sport watch that’s the best of both worlds.
  Now they just have to be the definitive Wrist OHM leader and then maybe they’ll have me looking to return to the fold. Not that I rely on ohr for anything but 24/7, but if you’ve proven this thing can be near exact to a chest strap during high intensity, sign me up.

```

1. The top image is out of date, the Fenix 5 Plus series ended up receiving 3.2.x so are in System 4 (as well as the upcoming 5).
Connect IQ 4.0 only showed up on the Venu 2/2s and most of the differences from 3.2.x are in graphics, so it is not surprising that they’d arrive on a unit with a fancy screen. The other difference was Super Apps which merged apps and widgets and allowed the device to run more than one at a time. Whether that is making any difference to anyone but the coders I don’t know.
2. ty Dom much appreciated for that info
1. I’ll try to annotate the image and update
2. so does ciq 4.0 get System 5?
3. Super apps – do you have any more info about those or where it can be gleaned? I thought there were also other super app capabilities eg running an app as a screen in a sport profile

```
1. 2\. Yes, the beta SDK has a preview for the Venu 2 and one for the F6 Pro, and one of the new features is an update to the Amoled always-on watch face system. The only thing I’ve seen that’s restricted to future devices is the on-device app store.
  3\. I don’t, no. If you rebuild a widget for a 4.0 device, the same code will generate a super app which shows in the widget loop as a glance, so in UI terms it’s pretty similar to a 3.2.x device with the widget loop set to show glances. I have yet to see anybody doing anything that really exploits simultaneous apps, or launching an app from within another app. Maybe I’m looking in the wrong places, maybe the Venu 2 market is just too small for the devs to be exploiting it much so far; certainly, if anyone had done anything significant you’d expect it to pop up in the developer awards, and that hasn’t happened. The most detailed discussion I found was on Ray’s Venu 2 review, and a lot of that was you and me spitballing 🙂
  The most obvious application, for me, would be something like Komoot letting you download and follow a route while you’re already out running/cycling.

  1. is there an emoji for spitballing? (Not wholly sure what it is but I can guess…UK here!)
        the usage for me would be to put the STRYD app into the running profile. then i get the zone alerts from the app and have the ability to view the page layouts that I normally use
        I’m guessing if it could be done stryd will be very much onto that right now
  2. I shudder to think… I’m UK as well, no idea where I picked up that bit of US slang from!
        Yup that sounds like another good use for it – I use the pod a lot but always with data fields.

```

1. Hi,
Maybe you can update your “great” table 🙂
Fenix 6 Pro is listed at the developper site with API Level 3.3.x for System 5 Preview
https://developer.garmin.com/connect-iq/compatible-devices/
2. hi
it’s impossible to keep blog posts up to date as time passes.
thank you for that link. Garmin has significantly more resources than me to keep their link up to date 😉

```
1. You are an impressive ressource 🙂
  You can update your data/table for a next post … later … when you want 🙂

  1. i’ve used your link 😉

```

Comments are closed.

```json
{"@context":"https:\/\/schema.org","@graph":[{"@type":"NewsArticle","@id":"https:\/\/the5krunner.com\/2021\/10\/13\/garmin-ciq-level-5-inbound-for-2022-what-is-it\/#article","isPartOf":{"@id":"https:\/\/the5krunner.com\/2021\/10\/13\/garmin-ciq-level-5-inbound-for-2022-what-is-it\/"},"author":{"name":"the5krunner","@id":"https:\/\/the5krunner.com\/#\/schema\/person\/57c7543a6bf35d49370a052a0be81b43"},"headline":"Garmin CIQ System 5 Inbound for 2022 – What is it !","datePublished":"2021-10-13T20:31:37+00:00","dateModified":"2026-01-25T05:42:32+00:00","mainEntityOfPage":{"@id":"https:\/\/the5krunner.com\/2021\/10\/13\/garmin-ciq-level-5-inbound-for-2022-what-is-it\/"},"wordCount":1033,"commentCount":13,"publisher":{"@id":"https:\/\/the5krunner.com\/#organization"},"image":{"@id":"https:\/\/the5krunner.com\/2021\/10\/13\/garmin-ciq-level-5-inbound-for-2022-what-is-it\/#primaryimage"},"thumbnailUrl":"https:\/\/imagedelivery.net\/_jGo7Cp8DLHLbI9FzBn6-Q\/the5krunner.com\/2021\/10\/p1.jpg\/w=320,h=162","keywords":["ciq level 5","ciq5","Garmin"],"articleSection":["Garmin Insider","News","Technology"],"inLanguage":"en-GB","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/the5krunner.com\/2021\/10\/13\/garmin-ciq-level-5-inbound-for-2022-what-is-it\/#respond"]}],"copyrightYear":"2021","copyrightHolder":{"@id":"https:\/\/the5krunner.com\/#organization"}},{"@type":"WebPage","@id":"https:\/\/the5krunner.com\/2021\/10\/13\/garmin-ciq-level-5-inbound-for-2022-what-is-it\/","url":"https:\/\/the5krunner.com\/2021\/10\/13\/garmin-ciq-level-5-inbound-for-2022-what-is-it\/","name":"Garmin CIQ System 5 Inbound for 2022 - What is it !","isPartOf":{"@id":"https:\/\/the5krunner.com\/#website"},"primaryImageOfPage":{"@id":"https:\/\/the5krunner.com\/2021\/10\/13\/garmin-ciq-level-5-inbound-for-2022-what-is-it\/#primaryimage"},"image":{"@id":"https:\/\/the5krunner.com\/2021\/10\/13\/garmin-ciq-level-5-inbound-for-2022-what-is-it\/#primaryimage"},"thumbnailUrl":"https:\/\/imagedelivery.net\/_jGo7Cp8DLHLbI9FzBn6-Q\/the5krunner.com\/2021\/10\/p1.jpg\/w=320,h=162","datePublished":"2021-10-13T20:31:37+00:00","dateModified":"2026-01-25T05:42:32+00:00","breadcrumb":{"@id":"https:\/\/the5krunner.com\/2021\/10\/13\/garmin-ciq-level-5-inbound-for-2022-what-is-it\/#breadcrumb"},"inLanguage":"en-GB","potentialAction":[{"@type":"ReadAction","target":["https:\/\/the5krunner.com\/2021\/10\/13\/garmin-ciq-level-5-inbound-for-2022-what-is-it\/"]}]},{"@type":"ImageObject","inLanguage":"en-GB","@id":"https:\/\/the5krunner.com\/2021\/10\/13\/garmin-ciq-level-5-inbound-for-2022-what-is-it\/#primaryimage","url":"https:\/\/imagedelivery.net\/_jGo7Cp8DLHLbI9FzBn6-Q\/the5krunner.com\/2021\/10\/p1.jpg\/w=320,h=162","contentUrl":"https:\/\/imagedelivery.net\/_jGo7Cp8DLHLbI9FzBn6-Q\/the5krunner.com\/2021\/10\/p1.jpg\/w=320,h=162","width":320,"height":162,"caption":"Garmin Ciq System 5 Inbound For 2022 - What Is It !"},{"@type":"BreadcrumbList","@id":"https:\/\/the5krunner.com\/2021\/10\/13\/garmin-ciq-level-5-inbound-for-2022-what-is-it\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/the5krunner.com\/"},{"@type":"ListItem","position":2,"name":"News","item":"https:\/\/the5krunner.com\/category\/news\/"},{"@type":"ListItem","position":3,"name":"Garmin Insider","item":"https:\/\/the5krunner.com\/category\/news\/garmin\/"},{"@type":"ListItem","position":4,"name":"Garmin CIQ System 5 Inbound for 2022 – What is it !"}]},{"@type":"WebSite","@id":"https:\/\/the5krunner.com\/#website","url":"https:\/\/the5krunner.com\/","name":"the5krunner","description":"Endurance & performance tech: news & opinion","publisher":{"@id":"https:\/\/the5krunner.com\/#organization"},"alternateName":"the5krunner.com","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/the5krunner.com\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-GB"},{"@type":"Organization","@id":"https:\/\/the5krunner.com\/#organization","name":"the5krunner","alternateName":["the 5k runner","5krunner","the 5krunner","5k runner","the5k runner"],"url":"https:\/\/the5krunner.com\/","logo":{"@type":"ImageObject","inLanguage":"en-GB","@id":"https:\/\/the5krunner.com\/#\/schema\/logo\/image\/","url":"https:\/\/imagedelivery.net\/_jGo7Cp8DLHLbI9FzBn6-Q\/10a31787-22fc-43ac-2aa3-08c4968e3400\/w=512,h=512,fit=crop","contentUrl":"https:\/\/imagedelivery.net\/_jGo7Cp8DLHLbI9FzBn6-Q\/10a31787-22fc-43ac-2aa3-08c4968e3400\/w=512,h=512,fit=crop","width":512,"height":512,"caption":"the5krunner"},"image":{"@id":"https:\/\/the5krunner.com\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/facebook.com\/the5krunner","https:\/\/x.com\/the5krunner","https:\/\/www.instagram.com\/the5krunner\/","https:\/\/the5krunner.substack.com\/","https:\/\/www.pinterest.com\/the5krunner\/","https:\/\/www.youtube.com\/@the5krunner","https:\/\/www.reddit.com\/r\/the5krunner","https:\/\/bsky.app\/profile\/the5krunner.bsky.social","https:\/\/open.spotify.com\/show\/0AXgizeE1GfXN9UBmcweNQ","https:\/\/www.threads.com\/@the5krunner","https:\/\/www.linkedin.com\/company\/94350433","https:\/\/podcasts.apple.com\/gb\/podcast\/the-deep-dive-podcast-sports-tech-performance-for\/id1815583227","https:\/\/www.wikidata.org\/wiki\/Q138416924"],"description":"the5krunner is an independent endurance sports technology publication covering GPS watches, fitness trackers, cycling computers and performance wearables. Founded and written by tfk, an international age-group triathlete with 20 years of hands-on testing experience.","publishingPrinciples":"https:\/\/the5krunner.com\/editorial-policy\/"},{"@type":"Person","@id":"https:\/\/the5krunner.com\/#\/schema\/person\/57c7543a6bf35d49370a052a0be81b43","name":"the5krunner","image":{"@type":"ImageObject","inLanguage":"en-GB","@id":"https:\/\/secure.gravatar.com\/avatar\/d510ef1e30484ff64d8418ed3e9637954fa2808f1e1ffd1c03c43e319ec22592?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/d510ef1e30484ff64d8418ed3e9637954fa2808f1e1ffd1c03c43e319ec22592?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/d510ef1e30484ff64d8418ed3e9637954fa2808f1e1ffd1c03c43e319ec22592?s=96&d=mm&r=g","caption":"the5krunner"},"description":"tfk is the founder and author of the5krunner, an independent endurance sports technology publication. With 20 years of hands-on testing of GPS watches and wearables, and competing in triathlons at an international age-group level, tfk provides in-depth expert analysis of fitness technology for serious athletes and endurance sport competitors. ID","sameAs":["https:\/\/the5krunner.com","https:\/\/facebook.com\/the5krunner","https:\/\/www.instagram.com\/the5krunner\/","https:\/\/www.linkedin.com\/in\/the5krunner\/","https:\/\/www.pinterest.com\/the5krunner\/","https:\/\/x.com\/the5krunner","https:\/\/www.youtube.com\/@the5krunner","https:\/\/www.wikidata.org\/wiki\/Q138417140","https:\/\/orcid.org\/0009-0001-8619-2642","https:\/\/muckrack.com\/tfk-the5krunner"],"knowsAbout":["GPS watches","fitness trackers","triathlon","running","cycling","wearable technology"],"knowsLanguage":["English"],"jobTitle":"Endurance Sports Technology Reviewer","worksFor":"the5krunner","alternateName":["the5krunner","the 5k runner","5krunner","the 5krunner","5k runner","Duathlon Champ","the5k runner","Race Leader"]}]}
{"@context":"https:\/\/schema.org\/","@type":"CreativeWork","dateModified":"2026-01-25T05:42:32+00:00","headline":"Garmin CIQ System 5 Inbound for 2022 - What is it !","description":"Yes it does say Edge 1040 – Some other slightly out-of-date info is updated in the table further below Garmin CIQ System 5 Is Coming   News today of some of the details that will be supported in CIQ next year. We will probably see this in System 5 (CIQ 3, API Level 3.3?). Which you might see (incorrectly?) referred","mainEntityOfPage":{"@type":"WebPage","@id":"https:\/\/the5krunner.com\/2021\/10\/13\/garmin-ciq-level-5-inbound-for-2022-what-is-it\/"},"author":{"@type":"Person","name":"the5krunner","url":"https:\/\/the5krunner.com\/author\/the5krunner2\/","description":""}}
{"@context":"https:\/\/schema.org\/","@type":"NewsArticle","@id":"https:\/\/the5krunner.com\/2021\/10\/13\/garmin-ciq-level-5-inbound-for-2022-what-is-it\/#newsarticle","url":"https:\/\/the5krunner.com\/2021\/10\/13\/garmin-ciq-level-5-inbound-for-2022-what-is-it\/","image":{"@type":"ImageObject","url":"https:\/\/imagedelivery.net\/_jGo7Cp8DLHLbI9FzBn6-Q\/the5krunner.com\/2021\/10\/p1.jpg\/w=300,h=300,fit=crop","width":300,"height":162},"headline":"Garmin CIQ System 5 Inbound for 2022 – What is it !","mainEntityOfPage":"https:\/\/the5krunner.com\/2021\/10\/13\/garmin-ciq-level-5-inbound-for-2022-what-is-it\/","datePublished":"2021-10-13T21:31:37+01:00","dateModified":"2026-01-25T05:42:32+00:00","description":"Garmin CIQ System 5 Is Coming   News today of some of the details that will be supported in CIQ next year. We will probably see this in System 5","articleSection":"Technology","articleBody":"[caption id=\"\" align=\"alignnone\" width=\"871\"] Yes it does say Edge 1040 - Some other slightly out-of-date info is updated in the table further below[\/caption]\r\nGarmin CIQ System 5 Is Coming\r\n \r\n\r\nNews today of some of the details that will be supported in CIQ next year. We will probably see this in System 5 (CIQ 3, API Level 3.3?). Which you might see (incorrectly?) referred to as CIQ 5.\r\n\r\nWhilst this is a feature that will initially be of interest to developers it will affect the capabilities of many Garmin devices and some new ones in 2022.\r\n\r\n[gallery type=\"rectangular\" size=\"medium\" ids=\"66768,66770,66769\"]\r\nApp Store on the Watch\r\nGarmin's CIQ store was initially only available through a browser but the addition of a smartphone app made it much easier to choose and install those extra bits of 'must have' functionality on your Garmin watches and bike computers. Well both of those versions of the CIQ store (web, smartphone) will be revamped.\r\n\r\nBetter still, taking a leaf out of Google's Wear OS, the app store will also be accessible on the watch. Super cool!\r\n\r\nIt also looks like the Wi-Fi enabled devices will be able to download CIQ apps and their updates over your home WiFi as well as enable you to tinker with some of their settings on the watch.\r\n\r\nVery Nice.\r\nCompatability\r\nCheck out the first image at the top and compare it to the one immediately above.\r\n\r\nIt looks like most devices that support CIQ System 4 will also support the new CIQ System 5 where hardware permits.\r\nAlso New\r\nWe will see new analytics and new metrics that can be incorporated into CIQ, including Stress Data, VO2max and Body Battery.\r\n\r\n \r\nTake Out\r\nPerhaps not as big a leap forward as in previous years but there are some tantalising hints at continued improvements from Garmin, especially to new devices next year.\r\n\r\nIf you want to read more technical detail then check out the Garmin Developer's report on this same subject. Elsewhere, Ray Maker points out that some of the wording used by Garmin suggests that AMOLED is the chosen way forward for its high-end, high-resolution devices.\r\n\r\n \r\nMore Info - Currently Supported API Level\r\n \r\n\r\n\r\n\r\nWatches\/Wearables\r\nAPI Level\r\nScreen Resolution\r\nScreen Shape\r\nScreen Technology\r\n\r\n\r\nApproach\u00ae S60\r\n2.4.0\r\n240 x 240\r\nround\r\nMemory-In-Pixel (64 colors)\r\n\r\n\r\nApproach\u00ae S62\r\n3.0.0\r\n260 x 260\r\nround\r\nMemory-In-Pixel (64 colors)\r\n\r\n\r\nCaptain Marvel\r\n3.2.0\r\n218 x 218\r\nround\r\nMemory-In-Pixel (64 colors)\r\n\r\n\r\nD2\u2122 Air\r\n3.2.0\r\n390 x 390\r\nround\r\nAMOLED\r\n\r\n\r\nD2\u2122 Bravo\r\n1.4.0\r\n218 x 218\r\nround\r\nMemory-In-Pixel (16 colors)\r\n\r\n\r\nD2\u2122 Bravo Titanium\r\n1.4.0\r\n218 x 218\r\nround\r\nMemory-In-Pixel (16 colors)\r\n\r\n\r\nD2\u2122 Charlie\r\n3.0.0\r\n240 x 240\r\nround\r\nMemory-In-Pixel (64 colors)\r\n\r\n\r\nD2\u2122 Delta\r\n3.1.0\r\n240 x 240\r\nround\r\nMemory-In-Pixel (64 colors)\r\n\r\n\r\nD2\u2122 Delta PX\r\n3.1.0\r\n240 x 240\r\nround\r\nMemory-In-Pixel (64 colors)\r\n\r\n\r\nD2\u2122 Delta S\r\n3.1.0\r\n240 x 240\r\nround\r\nMemory-In-Pixel (64 colors)\r\n\r\n\r\nDarth Vader\u2122\r\n3.2.0\r\n260 x 260\r\nround\r\nMemory-In-Pixel (64 colors)\r\n\r\n\r\nDescent\u2122 Mk1\r\n3.0.0\r\n240 x 240\r\nround\r\nMemory-In-Pixel (64 colors)\r\n\r\n\r\nDescent\u2122 Mk2 \/ Descent\u2122 Mk2i\r\n3.2.0\r\n280 x 280\r\nround\r\nMemory-In-Pixel (64 colors)\r\n\r\n\r\nDescent\u2122 Mk2 S\r\n3.2.0\r\n240 x 240\r\nround\r\nMemory-In-Pixel (64 colors)\r\n\r\n\r\nEnduro\u2122\r\n3.2.0\r\n280 x 280\r\nround\r\nMemory-In-Pixel (64 colors)\r\n\r\n\r\nepix\u2122\r\n1.2.0\r\n205 x 148\r\nrectangle\r\nMemory-In-Pixel (64 colors)\r\n\r\n\r\nf\u0113nix\u00ae 3 \/ tactix\u00ae Bravo \/ quatix\u00ae 3\r\n1.4.0\r\n218 x 218\r\nround\r\nMemory-In-Pixel (16 colors)\r\n\r\n\r\nf\u0113nix\u00ae 3 HR\r\n1.4.0\r\n218 x 218\r\nround\r\nMemory-In-Pixel (16 colors)\r\n\r\n\r\nf\u0113nix\u00ae 5 \/ quatix\u00ae 5\r\n3.1.0\r\n240 x 240\r\nround\r\nMemory-In-Pixel (64 colors)\r\n\r\n\r\nf\u0113nix\u00ae 5 Plus\r\n3.2.0\r\n240 x 240\r\nround\r\nMemory-In-Pixel (64 colors)\r\n\r\n\r\nf\u0113nix\u00ae 5S\r\n3.1.0\r\n218 x 218\r\nround\r\nMemory-In-Pixel (64 colors)\r\n\r\n\r\nf\u0113nix\u00ae 5S Plus\r\n3.2.0\r\n240 x 240\r\nround\r\nMemory-In-Pixel (64 colors)\r\n\r\n\r\nf\u0113nix\u00ae 5X \/ tactix\u00ae Charlie\r\n3.1.0\r\n240 x 240\r\nround\r\nMemory-In-Pixel (64 colors)\r\n\r\n\r\nf\u0113nix\u00ae 5X Plus\r\n3.2.0\r\n240 x 240\r\nround\r\nMemory-In-Pixel (64 colors)\r\n\r\n\r\nf\u0113nix\u00ae 6 \/ 6 Solar \/ 6 Dual Power\r\n3.2.0\r\n260 x 260\r\nround\r\nMemory-In-Pixel (64 colors)\r\n\r\n\r\nf\u0113nix\u00ae 6 Pro \/ 6 Sapphire \/ 6 Pro Solar \/ 6 Pro Dual Power \/ quatix\u00ae 6\r\n3.2.0\r\n260 x 260\r\nround\r\nMemory-In-Pixel (64 colors)\r\n\r\n\r\nf\u0113nix\u00ae 6S \/ 6S Solar \/ 6S Dual Power\r\n3.2.0\r\n240 x 240\r\nround\r\nMemory-In-Pixel (64 colors)\r\n\r\n\r\nf\u0113nix\u00ae 6S Pro \/ 6S Sapphire \/ 6S Pro Solar \/ 6S Pro Dual Power\r\n3.2.0\r\n240 x 240\r\nround\r\nMemory-In-Pixel (64 colors)\r\n\r\n\r\nf\u0113nix\u00ae 6X Pro \/ 6X Sapphire \/ 6X Pro Solar \/ tactix\u00ae Delta Sapphire \/ Delta Solar \/ Delta Solar - Ballistics Edition \/ quatix\u00ae 6X \/ 6X Solar \/ 6X Dual Power\r\n3.2.0\r\n280 x 280\r\nround\r\nMemory-In-Pixel (64 colors)\r\n\r\n\r\nf\u0113nix\u00ae Chronos\r\n3.1.0\r\n218 x 218\r\nround\r\nMemory-In-Pixel (64 colors)\r\n\r\n\r\nFirst Avenger\r\n3.2.0\r\n260 x 260\r\nround\r\nMemory-In-Pixel (64 colors)\r\n\r\n\r\nForerunner\u00ae 230\r\n1.4.0\r\n215 x 180\r\nsemi-round\r\nMemory-In-Pixel (16 colors)\r\n\r\n\r\nForerunner\u00ae 235\r\n1.4.0\r\n215 x 180\r\nsemi-round\r\nMemory-In-Pixel (16 colors)\r\n\r\n\r\nForerunner\u00ae 245\r\n3.2.0\r\n240 x 240\r\nround\r\nMemory-In-Pixel (64 colors)\r\n\r\n\r\nForerunner\u00ae 245 Music\r\n3.2.0\r\n240 x 240\r\nround\r\nMemory-In-Pixel (64 colors)\r\n\r\n\r\nForerunner\u00ae 45\r\n1.4.0\r\n208 x 208\r\nround\r\nMemory-In-Pixel (8 colors)\r\n\r\n\r\nForerunner\u00ae 55\r\n3.2.0\r\n208 x 208\r\nround\r\nMemory-In-Pixel (8 colors)\r\n\r\n\r\nForerunner\u00ae 630\r\n1.4.0\r\n215 x 180\r\nsemi-round\r\nMemory-In-Pixel (16 colors)\r\n\r\n\r\nForerunner\u00ae 645\r\n3.1.0\r\n240 x 240\r\nround\r\nMemory-In-Pixel (64 colors)\r\n\r\n\r\nForerunner\u00ae 645 Music\r\n3.2.0\r\n240 x 240\r\nround\r\nMemory-In-Pixel (64 colors)\r\n\r\n\r\nForerunner\u00ae 735xt\r\n2.4.0\r\n215 x 180\r\nsemi-round\r\nMemory-In-Pixel (16 colors)\r\n\r\n\r\nForerunner\u00ae 745\r\n3.2.0\r\n240 x 240\r\nround\r\nMemory-In-Pixel (64 colors)\r\n\r\n\r\nForerunner\u00ae 920XT\r\n1.4.0\r\n205 x 148\r\nrectangle\r\nMemory-In-Pixel (16 colors)\r\n\r\n\r\nForerunner\u00ae 935\r\n3.1.0\r\n240 x 240\r\nround\r\nMemory-In-Pixel (64 colors)\r\n\r\n\r\nForerunner\u00ae 945\r\n3.2.0\r\n240 x 240\r\nround\r\nMemory-In-Pixel (64 colors)\r\n\r\n\r\nForerunner\u00ae 945 LTE\r\n3.2.0\r\n240 x 240\r\nround\r\nMemory-In-Pixel (64 colors)\r\n\r\n\r\nGarmin Swim\u2122 2\r\n1.4.0\r\n208 x 208\r\nround\r\nMemory-In-Pixel (8 colors)\r\n\r\n\r\nMARQ\u00ae Adventurer\r\n3.2.0\r\n240 x 240\r\nround\r\nMemory-In-Pixel (64 colors)\r\n\r\n\r\nMARQ\u00ae Athlete\r\n3.2.0\r\n240 x 240\r\nround\r\nMemory-In-Pixel (64 colors)\r\n\r\n\r\nMARQ\u00ae Aviator\r\n3.2.0\r\n240 x 240\r\nround\r\nMemory-In-Pixel (64 colors)\r\n\r\n\r\nMARQ\u00ae Captain \/ MARQ\u00ae Captain: American Magic Edition\r\n3.2.0\r\n240 x 240\r\nround\r\nMemory-In-Pixel (64 colors)\r\n\r\n\r\nMARQ\u00ae Commander\r\n3.2.0\r\n240 x 240\r\nround\r\nMemory-In-Pixel (64 colors)\r\n\r\n\r\nMARQ\u00ae Driver\r\n3.2.0\r\n240 x 240\r\nround\r\nMemory-In-Pixel (64 colors)\r\n\r\n\r\nMARQ\u00ae Expedition\r\n3.2.0\r\n240 x 240\r\nround\r\nMemory-In-Pixel (64 colors)\r\n\r\n\r\nMARQ\u00ae Golfer\r\n3.2.0\r\n240 x 240\r\nround\r\nMemory-In-Pixel (64 colors)\r\n\r\n\r\nRey\u2122\r\n3.2.0\r\n218 x 218\r\nround\r\nMemory-In-Pixel (64 colors)\r\n\r\n\r\nVenu\u00ae Sq\r\n3.2.0\r\n240 x 240\r\nrectangle\r\nTransflective Liquid-Crystal (High Color)\r\n\r\n\r\nVenu\u00ae Sq. Music Edition\r\n3.2.0\r\n240 x 240\r\nrectangle\r\nTransflective Liquid-Crystal (High Color)\r\n\r\n\r\nVenu\u2122\r\n3.2.0\r\n390 x 390\r\nround\r\nAMOLED\r\n\r\n\r\nVenu\u2122 2\r\n4.0.0\r\n416 x 416\r\nround\r\nAMOLED\r\n\r\n\r\nVenu\u2122 2S\r\n4.0.0\r\n360 x 360\r\nround\r\nAMOLED\r\n\r\n\r\nVenu\u2122 Mercedes-Benz\u00ae Collection\r\n3.2.0\r\n390 x 390\r\nround\r\nAMOLED\r\n\r\n\r\nv\u00edvoactive\u00ae\r\n1.4.0\r\n205 x 148\r\nrectangle\r\nMemory-In-Pixel (64 colors)\r\n\r\n\r\nv\u00edvoactive\u00ae 3\r\n3.1.0\r\n240 x 240\r\nround\r\nMemory-In-Pixel (64 colors)\r\n\r\n\r\nv\u00edvoactive\u00ae 3 Mercedes-Benz\u00ae Collection\r\n3.0.0\r\n240 x 240\r\nround\r\nMemory-In-Pixel (64 colors)\r\n\r\n\r\nv\u00edvoactive\u00ae 3 Music\r\n3.2.0\r\n240 x 240\r\nround\r\nMemory-In-Pixel (64 colors)\r\n\r\n\r\nv\u00edvoactive\u00ae 3 Music LTE\r\n3.1.0\r\n240 x 240\r\nround\r\nMemory-In-Pixel (64 colors)\r\n\r\n\r\nv\u00edvoactive\u00ae 4\r\n3.2.0\r\n260 x 260\r\nround\r\nMemory-In-Pixel (64 colors)\r\n\r\n\r\nv\u00edvoactive\u00ae 4S\r\n3.2.0\r\n218 x 218\r\nround\r\nMemory-In-Pixel (64 colors)\r\n\r\n\r\nv\u00edvoactive\u00ae HR\r\n2.4.0\r\n148 x 205\r\nrectangle\r\nMemory-In-Pixel (64 colors)\r\n\r\n\r\nEdge\r\nAPI Level\r\nScreen Resolution\r\nScreen Shape\r\nScreen Technology\r\n\r\n\r\nEdge\u00ae 1000 \/ Explore\r\n2.4.0\r\n240 x 400\r\nrectangle\r\nTransflective Liquid-Crystal (High Color)\r\n\r\n\r\nEdge\u00ae 1030\r\n3.2.0\r\n282 x 470\r\nrectangle\r\nTransflective Liquid-Crystal (High Color)\r\n\r\n\r\nEdge\u00ae 1030 \/ Bontrager\r\n3.2.0\r\n282 x 470\r\nrectangle\r\nTransflective Liquid-Crystal (High Color)\r\n\r\n\r\nEdge\u00ae 1030 Plus\r\n3.2.0\r\n282 x 470\r\nrectangle\r\nTransflective Liquid-Crystal (High Color)\r\n\r\n\r\nEdge\u00ae 130\r\n3.1.0\r\n230 x 303\r\nrectangle\r\nTransflective Liquid-Crystal (Single Color)\r\n\r\n\r\nEdge\u00ae 130 Plus\r\n3.2.0\r\n230 x 303\r\nrectangle\r\nTransflective Liquid-Crystal (Single Color)\r\n\r\n\r\nEdge\u00ae 520\r\n2.4.0\r\n200 x 265\r\nrectangle\r\nTransflective Liquid-Crystal (High Color)\r\n\r\n\r\nEdge\u00ae 520 Plus\r\n3.1.0\r\n200 x 265\r\nrectangle\r\nTransflective Liquid-Crystal (High Color)\r\n\r\n\r\nEdge\u00ae 530\r\n3.2.0\r\n246 x 322\r\nrectangle\r\nTransflective Liquid-Crystal (High Color)\r\n\r\n\r\nEdge\u00ae 820 \/ Explore\r\n3.1.0\r\n200 x 265\r\nrectangle\r\nTransflective Liquid-Crystal (High Color)\r\n\r\n\r\nEdge\u00ae 830\r\n3.2.0\r\n246 x 322\r\nrectangle\r\nTransflective Liquid-Crystal (High Color)\r\n\r\n\r\nEdge\u00ae Explore\r\n3.1.0\r\n240 x 400\r\nrectangle\r\nTransflective Liquid-Crystal (High Color)\r\n\r\n\r\nOutdoor Handhelds\r\nAPI Level\r\nScreen Resolution\r\nScreen Shape\r\nScreen Technology\r\n\r\n\r\nGPSMAP\u00ae 66s \/ 66sr \/ 66st\r\n3.0.0\r\n240 x 400\r\nrectangle\r\nTransflective Liquid-Crystal (High Color)\r\n\r\n\r\nGPSMAP\u00ae 86s \/ 86sc \/ 86i \/ 86sci\r\n3.0.0\r\n240 x 400\r\nrectangle\r\nTransflective Liquid-Crystal (High Color)\r\n\r\n\r\nMontana\u00ae 7 Series\r\n3.1.0\r\n480 x 800\r\nrectangle\r\nTransflective Liquid-Crystal (High Color)\r\n\r\n\r\nOregon\u00ae 7 Series\r\n3.0.0\r\n240 x 400\r\nrectangle\r\nTransflective Liquid-Crystal (High Color)\r\n\r\n\r\nRino\u00ae 7 Series\r\n3.0.0\r\n240 x 400\r\nrectangle\r\nTransflective Liquid-Crystal (High Color)\r\n\r\n\r\n\r\n \r\n\r\n ","keywords":"ciq level 5, ciq5, Garmin, ","name":"Garmin CIQ System 5 Inbound for 2022 – What is it !","thumbnailUrl":"https:\/\/imagedelivery.net\/_jGo7Cp8DLHLbI9FzBn6-Q\/the5krunner.com\/2021\/10\/p1.jpg\/w=300,h=300,fit=crop","wordCount":933,"timeRequired":"PT4M8S","mainEntity":{"@type":"WebPage","@id":"https:\/\/the5krunner.com\/2021\/10\/13\/garmin-ciq-level-5-inbound-for-2022-what-is-it\/"},"author":{"@type":"Person","name":"the5krunner","description":"tfk is the founder and author of the5krunner, an independent endurance sports technology publication. With 20 years of hands-on testing of GPS watches and wearables, and competing in triathlons at an international age-group level, tfk provides in-depth expert analysis of fitness technology for serious athletes and endurance sport competitors. ID","url":"https:\/\/the5krunner.com\/author\/admin\/","sameAs":["https:\/\/the5krunner.com","https:\/\/facebook.com\/the5krunner","the5krunner","https:\/\/www.instagram.com\/the5krunner\/","https:\/\/www.linkedin.com\/in\/the5krunner\/","https:\/\/www.pinterest.com\/the5krunner\/","https:\/\/www.youtube.com\/@the5krunner"],"image":{"@type":"ImageObject","url":"https:\/\/secure.gravatar.com\/avatar\/d510ef1e30484ff64d8418ed3e9637954fa2808f1e1ffd1c03c43e319ec22592?s=96&d=mm&r=g","height":96,"width":96}},"editor":{"@type":"Person","name":"the5krunner","description":"tfk is the founder and author of the5krunner, an independent endurance sports technology publication. With 20 years of hands-on testing of GPS watches and wearables, and competing in triathlons at an international age-group level, tfk provides in-depth expert analysis of fitness technology for serious athletes and endurance sport competitors. ID","url":"https:\/\/the5krunner.com\/author\/admin\/","sameAs":["https:\/\/the5krunner.com","https:\/\/facebook.com\/the5krunner","the5krunner","https:\/\/www.instagram.com\/the5krunner\/","https:\/\/www.linkedin.com\/in\/the5krunner\/","https:\/\/www.pinterest.com\/the5krunner\/","https:\/\/www.youtube.com\/@the5krunner"],"image":{"@type":"ImageObject","url":"https:\/\/secure.gravatar.com\/avatar\/d510ef1e30484ff64d8418ed3e9637954fa2808f1e1ffd1c03c43e319ec22592?s=96&d=mm&r=g","height":96,"width":96}}}

```

7. Device Reference
   URL: https://developer.garmin.com/connect-iq/device-reference/fenix5plus/
   Device Reference

MenuDevice Reference

Device Reference
[Garmin Developers](https://developer.garmin.com/)
#
* [Overview](https://developer.garmin.com/connect-iq/overview/)
*
* [Compatible Devices](https://developer.garmin.com/connect-iq/compatible-devices/)
*
* [API Docs](https://developer.garmin.com/connect-iq/api-docs/)
*
* [Get the SDK](https://developer.garmin.com/connect-iq/sdk/)
*
* [Submit an App](https://developer.garmin.com/connect-iq/submit-an-app/)
*
* [Stay Informed](https://developer.garmin.com/connect-iq/stay-informed/)
*
* [Connect IQ Basics](https://developer.garmin.com/connect-iq/connect-iq-basics/)
*
* [Monkey C](https://developer.garmin.com/connect-iq/monkey-c/)
*
* [Core Topics](https://developer.garmin.com/connect-iq/core-topics/)
*
* [User Experience Guidelines](https://developer.garmin.com/connect-iq/user-experience-guidelines/)
*
* [Personality Library](https://developer.garmin.com/connect-iq/personality-library/)
*
* [Connect IQ FAQ](https://developer.garmin.com/connect-iq/connect-iq-faq/)
*
* [Reference Guides](https://developer.garmin.com/connect-iq/reference-guides/)
*
* [App Review Guidelines](https://developer.garmin.com/connect-iq/app-review-guidelines/)
*
* [Monetization](https://developer.garmin.com/connect-iq/monetization/)
*
* [Device Reference](https://developer.garmin.com/connect-iq/device-reference/)
*
* [Approach® S50](https://developer.garmin.com/connect-iq/device-reference/approachs50/)
* [Approach® S60](https://developer.garmin.com/connect-iq/device-reference/approachs60/)
* [Approach® S62](https://developer.garmin.com/connect-iq/device-reference/approachs62/)
* [Approach® S70 42mm](https://developer.garmin.com/connect-iq/device-reference/approachs7042mm/)
* [Approach® S70 47mm](https://developer.garmin.com/connect-iq/device-reference/approachs7047mm/)
* [D2™ Air](https://developer.garmin.com/connect-iq/device-reference/d2air/)
* [D2™ Air X10](https://developer.garmin.com/connect-iq/device-reference/d2airx10/)
* [D2™ Bravo](https://developer.garmin.com/connect-iq/device-reference/d2bravo/)
* [D2™ Bravo Titanium](https://developer.garmin.com/connect-iq/device-reference/d2bravo-titanium/)
* [D2™ Charlie](https://developer.garmin.com/connect-iq/device-reference/d2charlie/)
* [D2™ Delta](https://developer.garmin.com/connect-iq/device-reference/d2delta/)
* [D2™ Delta PX](https://developer.garmin.com/connect-iq/device-reference/d2deltapx/)
* [D2™ Delta S](https://developer.garmin.com/connect-iq/device-reference/d2deltas/)
* [D2™ Mach 1](https://developer.garmin.com/connect-iq/device-reference/d2mach1/)
* [D2™ Mach 2](https://developer.garmin.com/connect-iq/device-reference/d2mach2/)
* [D2™ Mach 2 Pro](https://developer.garmin.com/connect-iq/device-reference/d2mach2pro/)
* [Descent™ G1 / G1 Solar](https://developer.garmin.com/connect-iq/device-reference/descentg1/)
* [Descent™ G2](https://developer.garmin.com/connect-iq/device-reference/descentg2/)
* [Descent™ Mk1](https://developer.garmin.com/connect-iq/device-reference/descentmk1/)
* [Descent™ Mk2 / Mk2i](https://developer.garmin.com/connect-iq/device-reference/descentmk2/)
* [Descent™ Mk2 S](https://developer.garmin.com/connect-iq/device-reference/descentmk2s/)
* [Descent™ Mk3 43mm / Mk3i 43mm](https://developer.garmin.com/connect-iq/device-reference/descentmk343mm/)
* [Descent™ Mk3i 51mm](https://developer.garmin.com/connect-iq/device-reference/descentmk351mm/)
* [Edge® 1030](https://developer.garmin.com/connect-iq/device-reference/edge1030/)
* [Edge® 1030 / Bontrager](https://developer.garmin.com/connect-iq/device-reference/edge1030bontrager/)
* [Edge® 1030 Plus](https://developer.garmin.com/connect-iq/device-reference/edge1030plus/)
* [Edge® 1040 / 1040 Solar](https://developer.garmin.com/connect-iq/device-reference/edge1040/)
* [Edge® 1050](https://developer.garmin.com/connect-iq/device-reference/edge1050/)
* [Edge® 130](https://developer.garmin.com/connect-iq/device-reference/edge130/)
* [Edge® 130 Plus](https://developer.garmin.com/connect-iq/device-reference/edge130plus/)
* [Edge® 520 Plus](https://developer.garmin.com/connect-iq/device-reference/edge520plus/)
* [Edge® 530](https://developer.garmin.com/connect-iq/device-reference/edge530/)
* [Edge® 540 / 540 Solar](https://developer.garmin.com/connect-iq/device-reference/edge540/)
* [Edge® 550](https://developer.garmin.com/connect-iq/device-reference/edge550/)
* [Edge® 820 / Explore](https://developer.garmin.com/connect-iq/device-reference/edge820/)
* [Edge® 830](https://developer.garmin.com/connect-iq/device-reference/edge830/)
* [Edge® 840 / 840 Solar](https://developer.garmin.com/connect-iq/device-reference/edge840/)
* [Edge® 850](https://developer.garmin.com/connect-iq/device-reference/edge850/)
* [Edge® 1000 / Explore](https://developer.garmin.com/connect-iq/device-reference/edge-1000/)
* [Edge® 520](https://developer.garmin.com/connect-iq/device-reference/edge-520/)
* [Edge® Explore](https://developer.garmin.com/connect-iq/device-reference/edgeexplore/)
* [Edge® Explore 2](https://developer.garmin.com/connect-iq/device-reference/edgeexplore2/)
* [Edge® MTB](https://developer.garmin.com/connect-iq/device-reference/edgemtb/)
* [Enduro™](https://developer.garmin.com/connect-iq/device-reference/enduro/)
* [Enduro™ 3](https://developer.garmin.com/connect-iq/device-reference/enduro3/)
* [epix™](https://developer.garmin.com/connect-iq/device-reference/epix/)
* [epix™ (Gen 2) / quatix® 7 Sapphire](https://developer.garmin.com/connect-iq/device-reference/epix2/)
* [epix™ Pro (Gen 2) 42mm](https://developer.garmin.com/connect-iq/device-reference/epix2pro42mm/)
* [epix™ Pro (Gen 2) 47mm / quatix® 7 Pro](https://developer.garmin.com/connect-iq/device-reference/epix2pro47mm/)
* [epix™ Pro (Gen 2) 51mm / D2™ Mach 1 Pro / tactix® 7 – AMOLED Edition](https://developer.garmin.com/connect-iq/device-reference/epix2pro51mm/)
* [eTrex® Touch](https://developer.garmin.com/connect-iq/device-reference/etrextouch/)
* [fēnix® 3 / tactix® Bravo / quatix® 3](https://developer.garmin.com/connect-iq/device-reference/fenix3/)
* [fēnix® 3 HR](https://developer.garmin.com/connect-iq/device-reference/fenix3-hr/)
* [fēnix® 5 / quatix® 5](https://developer.garmin.com/connect-iq/device-reference/fenix5/)
* [fēnix® 5 Plus](https://developer.garmin.com/connect-iq/device-reference/fenix5plus/)
* [fēnix® 5S](https://developer.garmin.com/connect-iq/device-reference/fenix5s/)
* [fēnix® 5S Plus](https://developer.garmin.com/connect-iq/device-reference/fenix5splus/)
* [fēnix® 5X / tactix® Charlie](https://developer.garmin.com/connect-iq/device-reference/fenix5x/)
* [fēnix® 5X Plus](https://developer.garmin.com/connect-iq/device-reference/fenix5xplus/)
* [fēnix® 6 / 6 Solar / 6 Dual Power](https://developer.garmin.com/connect-iq/device-reference/fenix6/)
* [fēnix® 6 Pro / 6 Sapphire / 6 Pro Solar / 6 Pro Dual Power / quatix® 6](https://developer.garmin.com/connect-iq/device-reference/fenix6pro/)
* [fēnix® 6S / 6S Solar / 6S Dual Power](https://developer.garmin.com/connect-iq/device-reference/fenix6s/)
* [fēnix® 6S Pro / 6S Sapphire / 6S Pro Solar / 6S Pro Dual Power](https://developer.garmin.com/connect-iq/device-reference/fenix6spro/)
* [fēnix® 6X Pro / 6X Sapphire / 6X Pro Solar / tactix® Delta Sapphire / Delta Solar / Delta Solar - Ballistics Edition / quatix® 6X / 6X Solar / 6X Dual Power](https://developer.garmin.com/connect-iq/device-reference/fenix6xpro/)
* [fēnix® 7 / quatix® 7](https://developer.garmin.com/connect-iq/device-reference/fenix7/)
* [fēnix® 7 Pro](https://developer.garmin.com/connect-iq/device-reference/fenix7pro/)
* [fēnix® 7 Pro - Solar Edition (no Wi-Fi)](https://developer.garmin.com/connect-iq/device-reference/fenix7pronowifi/)
* [fēnix® 7S](https://developer.garmin.com/connect-iq/device-reference/fenix7s/)
* [fēnix® 7S Pro](https://developer.garmin.com/connect-iq/device-reference/fenix7spro/)
* [fēnix® 7X / tactix® 7 / quatix® 7X Solar / Enduro™ 2](https://developer.garmin.com/connect-iq/device-reference/fenix7x/)
* [fēnix® 7X Pro](https://developer.garmin.com/connect-iq/device-reference/fenix7xpro/)
* [fēnix® 7X Pro - Solar Edition (no Wi-Fi)](https://developer.garmin.com/connect-iq/device-reference/fenix7xpronowifi/)
* [fēnix® 8 43mm](https://developer.garmin.com/connect-iq/device-reference/fenix843mm/)
* [fēnix® 8 47mm / 51mm / tactix® 8 47mm / 51mm / quatix® 8 47mm / 51mm](https://developer.garmin.com/connect-iq/device-reference/fenix847mm/)
* [fēnix® 8 Pro 47mm / 51mm / MicroLED / quatix® 8 Pro 47mm / 51mm](https://developer.garmin.com/connect-iq/device-reference/fenix8pro47mm/)
* [fēnix® 8 Solar 47mm](https://developer.garmin.com/connect-iq/device-reference/fenix8solar47mm/)
* [fēnix® 8 Solar 51mm / tactix® 8 Solar 51mm](https://developer.garmin.com/connect-iq/device-reference/fenix8solar51mm/)
* [fēnix® Chronos](https://developer.garmin.com/connect-iq/device-reference/fenixchronos/)
* [fēnix® E](https://developer.garmin.com/connect-iq/device-reference/fenixe/)
* [Forerunner® 165](https://developer.garmin.com/connect-iq/device-reference/fr165/)
* [Forerunner® 165 Music](https://developer.garmin.com/connect-iq/device-reference/fr165m/)
* [Forerunner® 170](https://developer.garmin.com/connect-iq/device-reference/fr170/)
* [Forerunner® 170 Music](https://developer.garmin.com/connect-iq/device-reference/fr170m/)
* [Forerunner® 230](https://developer.garmin.com/connect-iq/device-reference/fr230/)
* [Forerunner® 235](https://developer.garmin.com/connect-iq/device-reference/fr235/)
* [Forerunner® 245](https://developer.garmin.com/connect-iq/device-reference/fr245/)
* [Forerunner® 245 Music](https://developer.garmin.com/connect-iq/device-reference/fr245m/)
* [Forerunner® 255](https://developer.garmin.com/connect-iq/device-reference/fr255/)
* [Forerunner® 255 Music](https://developer.garmin.com/connect-iq/device-reference/fr255m/)
* [Forerunner® 255s](https://developer.garmin.com/connect-iq/device-reference/fr255s/)
* [Forerunner® 255s Music](https://developer.garmin.com/connect-iq/device-reference/fr255sm/)
* [Forerunner® 265](https://developer.garmin.com/connect-iq/device-reference/fr265/)
* [Forerunner® 265s](https://developer.garmin.com/connect-iq/device-reference/fr265s/)
* [Forerunner® 45](https://developer.garmin.com/connect-iq/device-reference/fr45/)
* [Forerunner® 55](https://developer.garmin.com/connect-iq/device-reference/fr55/)
* [Forerunner® 570 42mm](https://developer.garmin.com/connect-iq/device-reference/fr57042mm/)
* [Forerunner® 570 47mm](https://developer.garmin.com/connect-iq/device-reference/fr57047mm/)
* [Forerunner® 630](https://developer.garmin.com/connect-iq/device-reference/fr630/)
* [Forerunner® 645](https://developer.garmin.com/connect-iq/device-reference/fr645/)
* [Forerunner® 645 Music](https://developer.garmin.com/connect-iq/device-reference/fr645m/)
* [Forerunner® 70](https://developer.garmin.com/connect-iq/device-reference/fr70/)
* [Forerunner® 735xt](https://developer.garmin.com/connect-iq/device-reference/fr735xt/)
* [Forerunner® 745](https://developer.garmin.com/connect-iq/device-reference/fr745/)
* [Forerunner® 920XT](https://developer.garmin.com/connect-iq/device-reference/fr920xt/)
* [Forerunner® 935](https://developer.garmin.com/connect-iq/device-reference/fr935/)
* [Forerunner® 945](https://developer.garmin.com/connect-iq/device-reference/fr945/)
* [Forerunner® 945 LTE](https://developer.garmin.com/connect-iq/device-reference/fr945lte/)
* [Forerunner® 955 / Solar](https://developer.garmin.com/connect-iq/device-reference/fr955/)
* [Forerunner® 965](https://developer.garmin.com/connect-iq/device-reference/fr965/)
* [Forerunner® 970](https://developer.garmin.com/connect-iq/device-reference/fr970/)
* [Garmin Swim™ 2](https://developer.garmin.com/connect-iq/device-reference/garminswim2/)
* [GPSMAP® 66s / 66i / 66sr / 66st](https://developer.garmin.com/connect-iq/device-reference/gpsmap66/)
* [GPSMAP® 67 / 67i](https://developer.garmin.com/connect-iq/device-reference/gpsmap67/)
* [GPSMAP® 86s / 86sc / 86i / 86sci](https://developer.garmin.com/connect-iq/device-reference/gpsmap86/)
* [GPSMAP® H1 / H1i Plus](https://developer.garmin.com/connect-iq/device-reference/gpsmaph1/)
* [Instinct® 2 / Solar / Dual Power / dēzl Edition](https://developer.garmin.com/connect-iq/device-reference/instinct2/)
* [Instinct® 2S / Solar / Dual Power](https://developer.garmin.com/connect-iq/device-reference/instinct2s/)
* [Instinct® 2X Solar](https://developer.garmin.com/connect-iq/device-reference/instinct2x/)
* [Instinct® 3 AMOLED 45mm](https://developer.garmin.com/connect-iq/device-reference/instinct3amoled45mm/)
* [Instinct® 3 AMOLED 50mm](https://developer.garmin.com/connect-iq/device-reference/instinct3amoled50mm/)
* [Instinct® 3 Solar 45mm / 50mm](https://developer.garmin.com/connect-iq/device-reference/instinct3solar45mm/)
* [Instinct® Crossover](https://developer.garmin.com/connect-iq/device-reference/instinctcrossover/)
* [Instinct® Crossover AMOLED](https://developer.garmin.com/connect-iq/device-reference/instinctcrossoveramoled/)
* [Instinct® E 40mm](https://developer.garmin.com/connect-iq/device-reference/instincte40mm/)
* [Instinct® E 45mm](https://developer.garmin.com/connect-iq/device-reference/instincte45mm/)
* [Captain Marvel](https://developer.garmin.com/connect-iq/device-reference/legacyherocaptainmarvel/)
* [First Avenger](https://developer.garmin.com/connect-iq/device-reference/legacyherofirstavenger/)
* [Darth Vader™](https://developer.garmin.com/connect-iq/device-reference/legacysagadarthvader/)
* [Rey™](https://developer.garmin.com/connect-iq/device-reference/legacysagarey/)
* [MARQ® (Gen 2) Athlete / Adventurer / Captain / Golfer / Carbon Edition / Commander - Carbon Edition](https://developer.garmin.com/connect-iq/device-reference/marq2/)
* [MARQ® (Gen 2) Aviator](https://developer.garmin.com/connect-iq/device-reference/marq2aviator/)
* [MARQ® Adventurer](https://developer.garmin.com/connect-iq/device-reference/marqadventurer/)
* [MARQ® Athlete](https://developer.garmin.com/connect-iq/device-reference/marqathlete/)
* [MARQ® Aviator](https://developer.garmin.com/connect-iq/device-reference/marqaviator/)
* [MARQ® Captain / MARQ® Captain: American Magic Edition](https://developer.garmin.com/connect-iq/device-reference/marqcaptain/)
* [MARQ® Commander](https://developer.garmin.com/connect-iq/device-reference/marqcommander/)
* [MARQ® Driver](https://developer.garmin.com/connect-iq/device-reference/marqdriver/)
* [MARQ® Expedition](https://developer.garmin.com/connect-iq/device-reference/marqexpedition/)
* [MARQ® Golfer](https://developer.garmin.com/connect-iq/device-reference/marqgolfer/)
* [Montana® 7 Series](https://developer.garmin.com/connect-iq/device-reference/montana7xx/)
* [Oregon® 7 Series](https://developer.garmin.com/connect-iq/device-reference/oregon7xx/)
* [Rino® 7 Series](https://developer.garmin.com/connect-iq/device-reference/rino7xx/)
* [Venu®](https://developer.garmin.com/connect-iq/device-reference/venu/)
* [Venu® 2](https://developer.garmin.com/connect-iq/device-reference/venu2/)
* [Venu® 2 Plus](https://developer.garmin.com/connect-iq/device-reference/venu2plus/)
* [Venu® 2S](https://developer.garmin.com/connect-iq/device-reference/venu2s/)
* [Venu® 3](https://developer.garmin.com/connect-iq/device-reference/venu3/)
* [Venu® 3S](https://developer.garmin.com/connect-iq/device-reference/venu3s/)
* [Venu® 4 41mm](https://developer.garmin.com/connect-iq/device-reference/venu441mm/)
* [Venu® 4 45mm / D2™ Air X15](https://developer.garmin.com/connect-iq/device-reference/venu445mm/)
* [Venu® Mercedes-Benz® Collection](https://developer.garmin.com/connect-iq/device-reference/venud/)
* [Venu® Sq](https://developer.garmin.com/connect-iq/device-reference/venusq/)
* [Venu® Sq 2](https://developer.garmin.com/connect-iq/device-reference/venusq2/)
* [Venu® Sq 2 Music](https://developer.garmin.com/connect-iq/device-reference/venusq2m/)
* [Venu® Sq. Music Edition](https://developer.garmin.com/connect-iq/device-reference/venusqm/)
* [Venu® X1](https://developer.garmin.com/connect-iq/device-reference/venux1/)
* [vívoactive®](https://developer.garmin.com/connect-iq/device-reference/vivoactive/)
* [vívoactive® 3](https://developer.garmin.com/connect-iq/device-reference/vivoactive3/)
* [vívoactive® 3 Mercedes-Benz® Collection](https://developer.garmin.com/connect-iq/device-reference/vivoactive3d/)
* [vívoactive® 3 Music](https://developer.garmin.com/connect-iq/device-reference/vivoactive3m/)
* [vívoactive® 3 Music LTE](https://developer.garmin.com/connect-iq/device-reference/vivoactive3mlte/)
* [vívoactive® 4](https://developer.garmin.com/connect-iq/device-reference/vivoactive4/)
* [vívoactive® 4S](https://developer.garmin.com/connect-iq/device-reference/vivoactive4s/)
* [vívoactive® 5](https://developer.garmin.com/connect-iq/device-reference/vivoactive5/)
* [vívoactive® 6](https://developer.garmin.com/connect-iq/device-reference/vivoactive6/)
* [vívoactive® HR](https://developer.garmin.com/connect-iq/device-reference/vivoactive-hr/)
MenuDevice Reference

8. SDK Release 3.1.5 - News & Announcements - Connect IQ - Garmin Forums
   URL: https://forums.garmin.com/developer/connect-iq/b/news-announcements/posts/sdk-release-3-1-5
   SDK Release 3.1.5 - News & Announcements - Connect IQ - Garmin Forums

- Share
- Subscribe by email
- More
- Cancel

Related

Recommended

Oct 3, 2019

Hello,

We've released SDK 3.1.5 which includes device support and version changes, as well as some minor updates. Here is a list of some of the changes and updates:

General Changes

- Add support for the MARQ Adventurer and MARQ Commander.
- Update minimum firmware and supported connect IQ version for the vívoactive® 3 / music / LTE devices
- Update minimum firmware and supported connect IQ version for the MARQ and fēnix® series devices.
- Fix MapTrackView.setMapVisibleArea to update the map everytime it is called.
- Add new DeviceSettings API isGlanceModeEnabled to determine if widget glances are enabled.

Simulator Changes

- Fix issue that prevented WiFi/LTE connection info from being provided on devices that did not have audio content provider app support.
- Fix a few simulator crashes that can occur when pairing BLE sensors.
- Fix incorrect data field layouts for the GPSMAP® 66 and 86 devices.
- Fix issue with fēnix® 6 series fonts being slightly different from device.
- Fix incorrect supported connect IQ API version listed for the vívoactive® 4 / 4s and Venu.

Compiler Changes

- Fix a crash that can occur in when compiling an animation from a GIF with frame delays set to 0.
- Fix the app memory limit check for background / glance apps, which should not be checked when a device does not support the app type.

9. Difference between CIQ and API version - Connect IQ App Development Discussion - Connect IQ - Garmin Forums
   URL: https://forums.garmin.com/developer/connect-iq/f/discussion/420567/difference-between-ciq-and-api-version
   Difference between CIQ and API version - Connect IQ App Development Discussion - Connect IQ - Garmin Forums

- State Not Answered
- Replies 6 replies
- Subscribers 18 subscribers
- Views 887 views
- Users 0 members are here

Options

Related

# Difference between CIQ and API version

Just wondering, in the compiler.json file for each device, there is a "connectIQVersion" with a version number. In the https://developer.garmin.com/connect-iq/compatible-devices/ page, it shows a API level that is somewhat but not always the same as the CIQ version. I assume the "connectIQVersion" means the exact CIQ version the device has the API is what the device is compatible with, right? However, some devices like the VenuD (Mercedes, I believe), has a CIQ of 3.2.6 and yet its API is 3.3, Shouldn't be API 3.2?

Also, what happens to CIQ 4? All I see with that CIQ level are System6 and System7 "previews". Anybody knows why?

- Sign in to reply
- Cancel

CIQ version and API version mean the same thing. [*]

However, the compatible devices page you linked only shows the first two version components (e.g. 3.2) and not all three components (e.g. 3.2.6).

To answer your other questions quickly:

- venud (the ciq device) isn't in the compatible devices page. venu is though.

Ofc it's hard to tell from that page, but you'll note that venud is indeed a Mercedes-Benz variant of Venu (1st gen), yet the compatible devices page doesn't have the phrase "Mercedes-Benz" in the description for Venu.

Also note that display name for venu/compiler.json is "Venu®" , which *exactly* matches what's on the compatible devices page.

- All CIQ 4 devices have been upgraded to at least CIQ 5.0

---

[*] There was actually a time when the SDK version was in sync with the CIQ/API version, which is why minApiLevel in manifest.xml used to be called minSdkVersion, and why ConnectIQ/SDKs/SDK_VERSION/bin/compilerinfo.xml has an element called targetSdkVersions, but it really means targetApiVersions. Btw you can look at compilerinfo.xml:targetSdkVersions to see the "official" mapping from system level to API level.

Iirc, when the SDK and CIQ versions were in sync, there wasn't even a concept of API level. That was only introduced once the SDK version went out of sync with the CIQ version. Possibly at the exact same time that the concept of System Levels was introduced. The reason for system levels was to support both CIQ 3 devices and CIQ 4 devices at the same time, with new CIQ versions and features. CIQ 3 devices wouldn't get all the new features, but they would get some new features. (To be clear, the rule was that no CIQ 3 device would ever get CIQ 4; CIQ 4 was only for newer devices. But Garmin wished to continue to support CIQ 3 devices with new CIQ releases)

So when CIQ 4.0 was released (for new devices only), Garmin needed a way to group that with existing CIQ 3 devices, which would be receiving a CIQ 3.2 update, with some new features. So they invented the system level concept and defined System 4 as CIQ 3.2 for CIQ 3 devices, and CIQ 4.0 for newer devices.

System 5 was CIQ 3.3 / 4.1.

System 6 was CIQ 3.4 / 4.2.

But System 7 is CIQ 5.0 only. All CIQ 4 devices received CIQ 5.0 and CIQ 3 devices were left behind.

System 8 is CIQ 5.1

Ofc Garmin doesn't explain any of this. And they rarely explained what each system level meant. There was a lot of confusion amongst bloggers, users and devs around this topic, even devs who thought they understood.

You'll also note that it isn't possible to select a system level (for levels 4, 5 and 6) using minApiLevel in manifest.xml.

For example, say you wanted to target System 6 when it was new. You couldn't use minApiLevel of 4.2, as that would incorrectly exclude CIQ 3.4 devices. But you couldn't use minApiLevel of CIQ 3.4, because that would incorrectly include CIQ 4.1 devices. This is kind of a moot and abstract point, as CIQ 3 and 4 devices were mostly being updated to the latest CIQ (for their respective branches) anyway, although we can can see from the compatible devices page / compiler.json that not all of them have the latest. It really has been made moot since all previously CIQ 4 devices are now on CIQ 5, so you really can use a min API level of CIQ 3.4 now, to target system 6 (or higher).

This is also a problem for the docs - if a doc says something like available since CIQ 3.4, that really means available since CIQ 3.4 (for CIQ 3 devices) and available since 4.2 (for CIQ 4 devices) but that isn't explained anywhere. This is also a moot point now.

I assume the "connectIQVersion" means the exact CIQ version the device has the API is what the device is compatible with, right?

I assume you are referring to "connectIQVersion" in the partNumbers array in ConnectIQ/Devices/DEVICE_ID/compiler.json

The "connectIQVersion" / "firmwareVersion" for a given part number isn't the exact CIQ version for that part number has. Users aren't forced to update their firmware, so it's impossible for Garmin to guarantee that.

Furthermore, some users have beta firmware, so they may have a newer [for that device *] version of Connect IQ which isn't widely released yet.

[* here when I say device, I speak of a generic customer-facing device/model, not a specific CIQ device ID that you select in manifest.xml or see in ConnectIQ/Devices.]

When I want to speak specifically of "CIQ devices" - as in the device IDs in manifest.xml / folders in ConnectIQ/devices, I will say "CIQ device". A CIQ device also maps 1-to-1 with a hardwarePartNumber, so we can consider these to be unique hardware platforms.]

[1/x]

Actually "connectIQVersion" / "firmwareVersion" for a given part number in a CIQ device's compiler.json is just the *minimum* CIQ / firmware combo that's guaranteed to be present on the device, if you build an app now (with the current contents of compiler.json.

When you export your project, the compiler puts `firmwareVersion` for each part number into the manifest as minFirmwareVersion (or something similar), and when a user tries to install your app (or update to the new version you built), the store will check to make sure they have at least that firmware version.

Since Garmin always updates compiler,json so that connectIQVersion and firmwareVersion are in sync, this also means that connectIQVersion will be the minimum guaranteed CIQ version on the device, for newly built apps.

This is why users with old firmware are unable to install apps that were updated recently, but they can still install old apps

[2/x]

Also, to be clear, Garmin never updates connectIQVersion / firmwareVersion until the firmware in question is 100% rolled out and has been out for a while.

So:

- connectIQVersion is not necessarily the latest version of CIQ on a given device

- connectIQVersion is the min CIQ version your app will see on a given device, if you export the app today. (because users with an older firmware / ciq version will not be allowed to install your app)

[3/x]

However, some devices like the VenuD (Mercedes, I believe), has a CIQ of 3.2.6 and yet its API is 3.3, Shouldn't be API 3.2?

I think the simple explanation in this case is that the device referred to in CIQ as venud (displayName = "Venu® Mercedes-Benz® Collection") is not in the compatible devices page at all.

What you see in the compatible devices page for "Venu" is probably the venu CIQ device. Note these are separate CIQ devices. (For later generations, the regular Venu X and Mercedes-Benz Venu X are multiple part numbers grouped under the CIQ device like venu2, which has 4 part numbers - Venu 2 WW, Venu 2 APAC, Venu 2 Mercedes-Benz WW, Venu 2 Mercedes-Benz APAC)

Furthermore, like many other devices which have WW/APAC variants, the CIQ version for venud's WW part number is not the same as the CIQ version for its APAC part number.

Unlike other devices, venud's WW part number is actual behind its APAC part number: WW has 3.2.6 while APAC has 3.3.6.

Regardless, they are different which again sort of highlights the limitations of the compatible devices page. That page does not break devices down by part number / APAC vs WW variants, either. It just has a bunch of high-level "customer-facing" model names without specifying which CIQ devices / part numbers they refer to. (Although you can guess that each variant roughly corresponds to a single CIQ device.)

------

Speaking of mapping part numbers to actual customer-facing models, I wrote a bunch of stuff about that here:

The TL;DR is you can use this API to see the description in the store website for a given part number (as seen in the compatible devices (*) tab):

You can also use it to get the store url which shows only apps for that device (*). This is handy for devices like Fenix 8 whose urls couldn't be guessed (ppl assumed there were no specific store urls for that family of devices).

I've said this before, but I don't like that CIQ revolves so much around CIQ device IDs, each of which corresponds to a single hardware part number, and each of which can have 1 to many (software) part numbers (which CIQ also revolves around), but they don't explain any of this stuff at all.

Like what the info in compiler.json means, how to map part numbers to customer-facing product names, or any of the related stuff.

Yet iirc, various sections of the docs refer to part numbers (without explaining them), and so does the compiler.

Speaking of the ambiguity with the word "device", the compiler refers to devices and part numbers interchangeably during the export process.

But ofc, elsewhere, a CIQ device (as in fr935, fenix6 or fenix6pro) is referred to as a "device" (or sometimes a "product").

Not only the nomenclature not explained, it's also not consistent.

10. Comprehensive list of supported CIQ versions per watch (past and future) - Connect IQ App Development Discussion - Connect IQ - Garmin Forums
   URL: https://forums.garmin.com/developer/connect-iq/f/discussion/211780/comprehensive-list-of-supported-ciq-versions-per-watch-past-and-future
   Comprehensive list of supported CIQ versions per watch (past and future) - Connect IQ App Development Discussion - Connect IQ - Garmin Forums

- State Verified Answer
- Replies 8 replies
- Subscribers 17 subscribers
- Views 10836 views
- Users 0 members are here

Options

Related

# Comprehensive list of supported CIQ versions per watch (past and future)

Hi all,

I'm just in the process of getting my first app ready for upload and am looking to make it compatible with as many watches as possible. What I'm running into is that I can't find a comprehensive list of watches with their supported connect IQ version, both older watches and at what version they stop working as well as newer ones that have (and possible will) be/been updated.

What I could find, both on the Garmin site, the blog and this forum are for instance some burst of limited and not maintained information, such as:

- A list in eclipse when building an appObviously this works but watches are simply grayed out or available. There's no way of knowing how far you have to go back to allow compatibility or what is limiting them in being compatible.
- A list of compatible devices per version, updated until CIQ 2 (no subversions and not up to date) https://developer.garmin.com/connect-iq/compatible-devices/
- Blog post about Connect IQ 2 being released and on which watch: https://developer.garmin.com/index.php/blog/post/connect-iq-2-the-biker-has-arrived
- Vivoactive 4 compability https://forums.garmin.com/developer/connect-iq/f/q-a/211304/vivoactive-4-compatible
- An announcement specifically for 3.0.11 with new supported devices forums.garmin.com/.../3-0-11-sdk-out-now-tag-newdevices

Any help with such a list would be greatly appreciated.

Cheers

- Sign in to reply
- Cancel

## Top Replies

- Are you setting the FW version in manifest.xml? Just set that to be 1.2.x. (the default)

## All Replies

Today, you want to use the 3.1.x SDK (current one is 3.1.6) With it, you can build for any CIQ device,

The old list you found is pretty correct for ciq1 and ciq2 devices

I'm pretty sure that new devices since then are all CIQ3, with the exception of the fr45 and swim2 which are CIQ1 devices, and out of the CIQ3 devices, many have ciq3.1. When you do a run config for a device in eclipse, the target SDK for a device will show you whats possible for the devices (3.0.x vs 3.1.x for example)

I never change the min SDK in manifest files. They are all "App Minimum SDK version" 1.2.x. The problems you will likely run into is if you try to use a CIQ2 feature with a CIQ1 device, or a CIQ3 feature on a CIQ1 or CIQ2 device. (you'll see "since" in the API doc for things.

The other thing to watch for is specific features. With the 245 (a 3.1 device) for example, it doesn't have a baro altimeter, which means it can't do floors, and if you attempt to use floors in ActMon, you'll crash.

Thanks jim_m_58 for your speedy reply!

So in general, your answers all make sense but it's still all information which you gathered from multiple sources right? More specific follow up:

- The main issue is, I built an app which both some of my friends and I already use, including the Fenix 5S and Vivoactive HR watches. I think I've backtracked that The HR needs min 2.4.x whereas the 5S needs 3.0.x. All these means that building for future watches is obviously less interesting because I won't be able to use the app myself anymore.
- The specific feature you mention in your last item is an important point but as far as I know, there isn't a list of such features and what certain watch limitations is to prevent his from happening. Surely this would be good to know ahead of time as opposed to uploading and hearing about users with other watches having crashes.

Not really multiple sources, just doing CIQ for going on 5 years! Based on when devices were intoduced, it's easy to track what version of CIQ they have.

I'm unclear about what you're saying about HR. With devices that have 2.x, OHRM and SensorHistory, you can get the HR value for watchfaces. Works the same on the vahr and f5s. The difference with the vahr and f5s is with the fenix and watchfaces, the f5x has got the HW to use onPartialUpdate() and update the HR much more often than on the vahr.

For you last point that's why you want to test the features in you app on all supported targets in the sim, as that's good at catching things.

When it comes to supporting variations, there are two ways to handle that - Jungles and "has"

Haha yes I'm not at 5 years yet ;)

What I mean with vahr is that I started with my app for the f5x in 3.0 (as 3.1 wasn't available) and then later discovered it could only be built for vahr if I selected 2.4. So I deduced that something has changed here that isn't supported (of which one is obviously the update rate of the HR) but what all is causing this is unclear to me. I was just hoping there was a more complete list. The Programmers Guide is really great and it does include a lot of notes like: available since 3.1, etc. but that refers features back to version number, not version number and watch to feature.

I will indeed then just continue to build and test in random selected relatively new models and see what issues I run into.

Are you setting the FW version in manifest.xml? Just set that to be 1.2.x. (the default)

Sure that makes sense. I had figured that some features would then not work but I guess one does select the specific version per build anyway. Thanks!

So yes I can set it to 1.2.x but that doesn't allow me to simply build for all even though I can select more. To illustrate that, I just ran into another issue which kind of illustrates why I posted. Just for future reference for others, I'll reply. While now building for Fenix3, it immediately fails on a "failed invoking symbol" error.

I start by retrieving a saved variable by doing:

```
var savedSpot = Storage.getValue("savedSpot");
```

And then check if it is null which in other builds, works fine. But here it results in a Symbol not found. There's no easy way to see which watch has which CIQ version and exactly what that entails. By having done this for a while, I know that the storage module isn't support < 2.4.x so by looking up the storage module, I guess that's the only real way to find out after building. Which I guess is an alternative way of finding the answer to my question.

Thanks again Jim!

getProperty()/setProperty can be used on older devices, and to determine with you can use:

if(Application has :Storage) {

} else {

}

Device Reference