FW 2.80 came out for the vivoactive today

I bet that this is the result of a valid and correct bug fix. If I remember correctly, the startOfDay field was supposed to be in UTC time, but was actually returned as local time. If an application was written to expect local time and the firmware produces local time (old firmware) then everything worked out just fine. Now that the firmware produces UTC time, everything will be off.

Of course we won't know for sure until the Garmin guys produce and post a fix list.

Here's the code I use for the date in history. As I said, worked fine with 2.70.

var then= activityHistory.startOfDay;
var today = Calendar.info(then, Time.FORMAT_MEDIUM);
var timestamp=today.month+" "+today.day.toString();
[/code]

Update on the watchface issue. Turns out it was user error. The settings had been switched to french or something.

This is an issue we've already had reported on other products that had pulled in some of the changes from the 1.1.1 SDK. The 2.80 vivoactive firmware includes the 1.1.1 SDK changes, so that's why it's cropped up just recently on vivoactive. The change we suspect is behind the problem was a fix intended to convert the activity monitoring history moments to use the UNIX epoch, so I've created a new issue to have this investigated. I believe our intent is to use the UNIX epoch everywhere, and I'd also like to see us use UTC everywhere, but there are admittedly several issues in the Time module that cause some inconsistency. We'll get this looked at ASAP.

Thanks for the info Brandon Too bad it wasn't fixed before 2.80 came out, given that it was a known issue on other devices :(

Any chance of getting a more detailed change log for what was "fixed" in 2.80 as far as CIQ? (and don't tell us we can control the "goal hit fireworks" with CIQ... :) )

So my first night's experience with 2.8 doesn't look promising. While 2.7 had seemed to stabilize sleep time power usage for me, last night my full charge dropped by ~50% in 8 hours of sleep -- my VA hasn't done that since 2.6. Awesome.

Chad

I've pulled together a list of changes in the 2.80 release that are relevant to Connect IQ:

https://forums.garmin.com/showthread.php?250234-Vivoactive-2-80-Firmware-Release-Notes

This is an issue we've already had reported on other products that had pulled in some of the changes from the 1.1.1 SDK. The 2.80 vivoactive firmware includes the 1.1.1 SDK changes, so that's why it's cropped up just recently on vivoactive. The change we suspect is behind the problem was a fix intended to convert the activity monitoring history moments to use the UNIX epoch, so I've created a new issue to have this investigated. I believe our intent is to use the UNIX epoch everywhere, and I'd also like to see us use UTC everywhere, but there are admittedly several issues in the Time module that cause some inconsistency. We'll get this looked at ASAP.

Any news when this might be fixed? As of va FW 2.90, it's still broken. Will it be the next firmware that updates CIQ from 1.1.1 a newer version?

No news yet--it's on the road map to be fixed. I just don't know exactly when this will be addressed.

Just following up... the startOfDay bug fix was included with the 1.1.2 SDK release.