Instinct 2 support

Hi,

I've been asked by one of my users to support Instinct 2 for my Connect, but I can't get it working. I've downloaded SDK version 4.0.10, set it to the active version and restarted Eclipse and I can see Instinct 2 in the list of watches in the manifest. I can select it, however, if I try to create a run configuration it only gives me the option of Target API version 3.2.x in the dropdown. I believe it should be using 4.0.x. I already support the Venu2 and that has 4.0.x in the corresponding dropdown.

When I try to start the app it instantly fails with out of memory, nothing appears and the simulator memory plugin is totally blank as if it's not working.

Is there some trick to getting it to recognise that it should use 4.0.x, or is there a file or different SDK version I should try. I've tried 4.1.0-beta in case that was any better, but that didn't make any difference. I restarted Eclipse every after each change.

Thanks

David

0 jim_m_58 over 4 years ago

The Instinct2/2s are not a 4.x devices. They are 3.3.x, but 3.3 isn't available in eclipse. Kyle made a change so it can be used in Eclipse by making them 3.2 in devices there.

See https://forums.garmin.com/developer/connect-iq/f/discussion/285506/the-instinct2-s-require-vs-code-to-run-the-sim/1375728#1375728

Depending on the type of app, the Instinct2/2s has less memory than other devices. For example, a watch face maxes out at 60k, a device app at 92k, and a widget at 60k

0 Dresbo over 4 years ago in reply to jim_m_58

Thanks. I'll take a look, but 92k is likely too small.

0 mqbfxw over 4 years ago

I am honestly a tad disappointed that these "new" Instinct 2/s/etc, Descent 1G/s watches were released with less 'app memory' (92k) than my 2016 era Forerunner 735xt (120k). And there have also been 10 other Forerunner models released since 2016. I look forward to seeing a newer, better Instinct next time, and hope to not lose more users to other smart(er) watches