The new Heart Beat Intervals feature in CIQ 3 does not work on Vivoactive 3 even though this device is listed as supported in CIQ 3. This seems to be due to lack of a 3.0 VM for the device. Is such a VM expected? The Heart Beat Intervals feature works fine in the simulator. Test app: https://github.com/vtrifonov-esfiddle/TestHeartBeatIntervals
I coded the use of the built-in rr interval, in the simulator and works well. In target hardware, I'm seeing data dropouts of greater than 3 seconds. I confirmed this in a fr935 and f5x+. this maybe an artifact of the optical hr since the data dropouts were less using the chest hrm (but still happening). also in the example your only looking at the first element in the array, the faster the heart rate the array will have more rr-Intervals.
if using the ANT+ channel, hr interval data has redundancy checks built-it and near zero dropouts.
Good that the stable version of CIQ3 is out. I had tried the beta's before and I was very enthusiastic about it. Today I installed a fresh Eclipse Oxygen, the new SDK and plugin. However when I try to run the SimpleDataField sample I can't choose 3.0.x as the Target SDK version for the Edge 1030, only 2.3.x or 2.4.x. This is strange because it was possible in the beta's. When I choose the Edge 130 or Forerunner 645 it is possible to to choose 3.0.x.
I guess I'm not the only one with this problem, what happened to the Edge 1030? My device just received its firmware update to version 6.0.0, now my physical device supports 3.0 but the simulator doesn't.
ejdevries. There was a similar thing with mapping on the 1030, where one of the betas supported it, but 3.0.1 didn't. It could be because the FW you mentioned hadn't been released when the SDK was.
You really only need to set it for 3.0.x if you're using any 3.0.x functionality, and you can built for 2.3.x or 2.4.x and it will still run fine on the devices with a 3.x VM. I'm sure the sample you're running will run fine if built for 2.x.x.
Only a couple of my apps in the store were built with 3.0.1 but they all run find on devices with a 3.0.x VM
CedricD - Do you call enableLocationEvents()? (that "fires up" GPS)
You can only do that in a Widget or Device App. You can't in a watch face or widget.
What data do you want? Activity.Info.getCurrentLocation will give you the last know GPS location until it goes stale, and when simulating data in the sim will change as you run the simulation.
In the simulator, Position.Info.when always return the same (constant) value, be it when simulating data or replaying a real-life FIT file
@jim_m_58: an App of mine (correctly) uses Position.Info data. Position.Info.when always return the same (constant) value in the (SDK 3.0.1) simulator, even though other Position.Info data evolve as expected. It does work on the actual watch (CIQ 3.0.1), as well as in SDK 2.4.9 simulator.
