I recently updated my SDK to 2.1.x, then i discovered that i cannot create a project for the FR235
So my question is to know if SDK will be available for Forerunner 235 in the future?
I recently updated my SDK to 2.1.x, then i discovered that i cannot create a project for the FR235
So my question is to know if SDK will be available for Forerunner 235 in the future?
Thanks
For the 235, you need to set the Minimum SDK Version to 1.3 on the properties page.
Roger - I keep it at the default and don't have a problem, as in the app store, the "minimum FW" is used... Somewhere I saw a post of how this all fits, and by setting to 1.3.x, it really only comes into play with the "J" (APAC) devices where many still have 1.2.x VM production FW, and that's the "minimum FW" for those devices.
So if you set the CIQ version to 1.3.x, it won't build for devices with a minimum FW version that has a 1.2.x VM and none of the "J" devices are shown as supported in the app store.
Maybe I'm missing something or am confused myself..
Are youe using FitContributor as there's no way that would work on a 1,2,x VM?. But stuff that was written for 1.2.x shouldn't need this (and maybe even with some 1.3/2.1 functionality with the use of "has"..)
Jim - I have been setting the minimum SDK version to 1.3 on my data fields that use Fit contributor. I did not code in the "has" functionality so I wanted to prevent anyone with old firmware from downloading the app. I think this prevents that scenario too.
Jim - I have been setting the minimum SDK version to 1.3 on my data fields that use Fit contributor. I did not code in the "has" functionality so I wanted to prevent anyone with old firmware from downloading the app. I think this prevents that scenario too.
But my point is that you set to a 1.3.x minimum because you're using fitContrib.
Things that worked on 1.2.x shouldn't need the 1.3.x minimum.. I think the person that started this tread may have a different problem. (like the onStart() and onStop() parameter)
But my point is that you set to a 1.3.x minimum because you're using fitContrib.
Things that worked on 1.2.x shouldn't need the 1.3.x minimum.. I think the person that started this tread may have a different problem. (like the onStart() and onStop() parameter)
Ah yes, I think I am off in the weeds. I was thinking the default was 2.1 but it's actually 1.2.
For now you can set the minimum to be 1.2.x (you can still do 1.3.x/2.1.x calls and test in the sim). With the vibration stuff you may need to switch to 1.3.x as a minimum (so it's not loaded on devices with a 1.2.x VM... I'm not sure if it works with a 1.2.x VM or not) The key is with a 235, you must use a min of 1.2.x (the default) or 1.3.x, and don't want to use 2.1.x.
As far as the whole vibration in a DF thing, you may want to look at this thread. I posted a really simple DF that just vibrates about every minute and runs fine on my 230 (which has a 1.3.x VM)
Thanks jim_m_58 , i tried your example and i get it working.
But the problem is that the onUpdate() is called once a second and my goal is to make a beep 180 times per second.
So i need to use Timer but i get a "permission Required" error
