Gyroscope values in Sensor::Info

How did we all miss that........ so it's been available ever since 3.3?

Thanks Jim 

Now I will be stuck trying to figure out the maths for the next few months

Nick said:

How did we all miss that........ so it's been available ever since 3.3?

Correct me if I'm wrong, but I think API Level 3.3 is new for Connect IQ System 5. I interpret this to mean that any "older devices" which end up receiving 3.3 will get this feature, as well as any 4.x device (and any > 4 device in the future). (Then again you'd think the docs would also show a minimum 4.x version, assuming that 4.x devices will need a firmware update for this feature.)

Now it makes sense to me why Garmin split out CIQ versions into API level and system number. This way each yearly update has a single "system" number, and they can also increment the minor version number for older products which get some new features but not all new features.

As a matter of fact, if I try to edit an app's minimum SDK API level in either Eclipse or VS Code, I'm not allowed to select 3.3 yet. (My SDK is CIQ 4.1.0 Beta 1)

The 3.3 devices are system 5, and there aren't any actual devices yet with 3.3.  There is a f6pro System 5 Preview device with 3.3 amd the venu 2 System 5 preview has 4.1..

I just noticed that in Eclipse. I cannot select API level 3.3, only 3.2 or version 4.0

Yes, to use the f6pro System Preview device (the only thing with 3.3) you need to use VS Code. There must be a check in the eclipse plugin.

fenix 5 is listed under supported devices now though?

Actually most of the devices I support under 3.0 are all listed as supported in the Toybox Gyro module?

But not without System 5/a 3.3.x VM.  Right now, you can only use it in the sim, and only for the two "System 5 preview" devices.

Same for things like stress and body battery.

As well as onFlick() and onDrag() in a delegate.

Ok - so for the time being it's possible to test some basic code on the f6pro for example, until the VM updates and system 5 update occurs, and then it should be available on all the devices listed?

FlowState said:

As a matter of fact, if I try to edit an app's minimum SDK API level in either Eclipse or VS Code, I'm not allowed to select 3.3 yet. (My SDK is CIQ 4.1.0 Beta 1)

Nick said:

I just noticed that in Eclipse. I cannot select API level 3.3, only 3.2 or version 4.0

jim_m_58 said:

Yes, to use the f6pro System Preview device (the only thing with 3.3) you need to use VS Code. There must be a check in the eclipse plugin.

I can see the F6 Pro System 5 Preview and Venu 2 Sq System 5 Preview devices in both VS Code and Eclipse, although I haven't tried to build with them.

But neither VS Code nor Eclipse allow you to select a *minimum API version* of 3.3.

This could be intentional, as there are no real devices with 3.3 yet. I guess it won't matter until real devices actually get the 3.3 update.

I am sort of curious how Garmin is going to handle the situation where a feature like this will seemingly have multiple minimum API levels. e.g. In this case it seems that the minimum API level for Sensor.GyroscopeData would be:

- 3.3 (for 3.x devices)

*and*

- 4.1 (for 4.x devices)

But just saying that the minimum API level is 3.3 seems to incorrectly imply that the feature would also be present in 4.0.

(I'm referring to both the docs and the minimum API level in manifest.xml.)

TL;DR if certain System 5 features are only for >= 3.3 (for 3.x devices) and >= 4.1 (for 4.x devices), how will that be handled in the documentation and/or the manifest minimum API level?