In the original launch of Connect IQ it was written that Apps would be able to access the internal accelerometer. I have searched through all of the API documentation without finding out how to access this data. Is this not yet possible via the API? How is it/will it be possible to use this data. I.e. can I make an algorithm which does simple calculations/filtering on e.g. 100 Hz or 10 Hz accelerometer data and writes it to a FIT-file? Or alternatively write the 10Hz accelerometer data to the FIT-file for later processing?
I don't know what the folks at Garmin are planning, but you don't have access to the accelerometer via ConnectIQ at this time. There is currently no way to write any application specific data to the FIT file either, so for the time being, your application will be difficult/impossible to implement as you're currently envisioning it.
It's been abandoned for now. It's a highly requested item, but often times the requests are followed by "and can I get 2000 samples/sec so I can <insert use case here>?" and I have to go into a long rambling answer about how my bytecode interpreter won't be able to keep up with the data on the wearable. I'm hoping future versions of CIQ will have improved performance (*cough* native methods *cough*) so we can give full accelerometer access, but I don't want to provide an API that will only be a disappointment.
Relavent Alpha Monkey quote:
I'm hoping future versions of CIQ will have improved performance (*cough* native methods *cough*) so we can give full accelerometer access, but I don't want to provide an API that will only be a disappointment.
A pity, that announcement about the accelerometer support last year is the reason I planned to go from Polar and back to Garmin. I would be happy even with a minimum access to the accelerometer, then the developers can decide themselves if it is something to work with or not. I guess I'll stay with Polar as sports watch for now, then. And do the programming on Android wear GPS watch.
