phoneConnected on the vivoactive

I think that this is a pretty good indicator that the device doesn't currently have access to the activity recording module. I can't tell from the documentation if this is intended limitation of the device or it is just something that isn't finished in the firmware's ConnectIQ support. Unless someone digs up some documentation that indicates this is intentional, this question is probably best answered by one of the ConnectIQ team.

That is pretty disappointing. I bought this watch over the 220 mainly because i thought I would be able to write some apps for it. I have various cool ideas that I wanted to implement that require recording so they can be uploaded to strava/connect etc. I tested on the simulator and it seemed to work, so I assumed it would just work on the watch too.

I don't want to hijack the thread, but I think its probably a similar issue with things not being implemented.

I am new to this forum, so how does one get a answer from the ConnectIQ team? I thought the whole idea of the ConnectIQ was to be able to design 3rd party apps. Seems to be some serious limitations at the moment if half of the SDK is not implemented and there are no documents to show what is and what is not supported on each device.

Does this sample code for recording work on any of the watches?

I bought this watch over the 220 mainly because i thought I would be able to write some apps for it.

I don't think anyone has said that the VivoActive is not going to get support for the ActivityRecording module. Until someone indicates that it won't get the feature, I think it is fairly safe to assume that it will be there eventually.

how does one get a answer from the ConnectIQ team?

Typically you just wait until Monday. Brandon or Brian are pretty responsive, but they work during the week like everyone else.

Since your posts are interleaved with the 'discussion' that is going on in this post, they may go unnoticed. In that case it might be worth your while to create a new post. If you do that and don't get a response by Tuesday, you should bump it.

I thought the whole idea of the ConnectIQ was to be able to design 3rd party apps.

That is the idea.

Seems to be some serious limitations at the moment if half of the SDK is not implemented and there are no documents to show what is and what is not supported on each device.

Is half of the SDK not available on the VivoActive, or is it just the one module (maybe 1/10th of the SDK) that you happen to want to use? I'm betting most of it is there, but I don't have one to test with. It is my understanding that there is/was a 2.50 firmware for your device. If you aren't running the latest firmware, you can expect some features to be unavailable. Since the VivoActive appears to just recently started to arrive in peoples hands, I think you'll start seeing some updates soon.

As I understand it, there is the ConnectIQ team and then there are one or more device teams. These teams work independently. The ConnectIQ SDK can add features at any time, but those features might not be available on a physical device until the team responsible is able to release firmware to support that SDK. Until the supporting firmware is available, you have the emulator. It isn't perfect, but it's better than nothing.

Does this sample code for recording work on any of the watches?

Yes. There are apps in the store that use this right now.

I apologize if I was a bit cranky last night, but to me, calling a documented methods for a real device should never crash the device, and in my case it was a hard enough crash that it also wiped out my history on the device, as well as everything in the APPS directory (it was like a hard reset had been done)

No problem. I think it fair that I apologize for continuing to argue just for the sake of arguing. :P

Sys.getDeviceSettings().phoneConnected

doesn't work on vivoactive, causes a crash. Running 2.30. And _NO_ my vivoactive doesn't detect a later version!!!!!!

Come on Garmin lets have some bug fixes PLEASE!!!

Dude, read the thread before just posting blindly to the end.

I apologize if I was a bit cranky last night, but to me, calling a documented methods for a real device should never crash the device, and in my case it was a hard enough crash that it also wiped out my history on the device, as well as everything in the APPS directory (it was like a hard reset had been done)

What he said!

Come on Garmin, give us the tools....

I don't think anyone has said that the VivoActive is not going to get support for the ActivityRecording module. Until someone indicates that it won't get the feature, I think it is fairly safe to assume that it will be there eventually.

The ActivityRecording module not being in vivoactive 2.30 was a bug, and has been fixed with the 2.50 firmware. I'm trying to track down an answer on where the 2.50 download went, but as it's lunch time here most people are away.

Typically you just wait until Monday. Brandon or Brian are pretty responsive, but they work during the week like everyone else.

You left a name out, right? :)

I apologize if I was a bit cranky last night, but to me, calling a documented methods for a real device should never crash the device, and in my case it was a hard enough crash that it also wiped out my history on the device, as well as everything in the APPS directory (it was like a hard reset had been done)

You're right, this shouldn't happen at all. I'm sorry that this happened and we'll be investigating why this happened.

A 2.60 will be out in a day or two for the vivoactive, and it'll have the ActivityRecording module available for use.