Complete
over 4 years ago

WERETECH-8010

Fixed

Vivoactive 3 firmware 6.90 cause watch faces to crash

Please check the newest firmware for issues that causes watch faces to crash.

e.g. https://apps.garmin.com/de-DE/apps/fc3f9b9f-add6-46cb-8e0b-9a2172a04c31

All vivoactive 3 users with the latest firmware are reporting the same affect, the watch face crashes directly. No start is possible.

No crash error logging is written into the log file of the watch.

The simulator of the SDK works perfectly with the watch face (3.0.12/3.1.4) and the last issues caused by the watch face was reported a year ago.

Thanks for support and please keep up testing your software.

The Magician

TheMagician
  • over 5 years ago

    With the update to the newest SDK (3.1.5) the issues seem to be solved. I do not get any crash feedback for the vivoactive 3 series.

  • over 5 years ago in reply to Coleman.Apps

    Is there any update to this? I'm not seeing crashes but the latest firmware halves the battery life of my va3m, and I've gotten an inkling from users that they see the same on Fenix5. There really should be a lot of added qa, there have been way too many regressions with gcm and firmware updates lately. And is there a way to downgrade firmware without gcm automatically updating it again?

  • over 5 years ago in reply to TheMagician

    I know it makes no sense. Originally it was ment as a method for isolating the causing program-lines but it worked out the unsatisfying way I described.

    Upgrade of the firmware was in my case the visible and instant cause of the crashes. Might of course be that the cause lies in the compiler and surfaces because of the firmware-upgrade but my guess is not fwiw.

  • over 5 years ago in reply to TheMagician

    You're right, the difference is that this time is just VA3, so it's probably an entirely different issue. But why reentering code helped?

  • over 5 years ago in reply to Gertjan

    It was exactly like that. Now that you say it, I remember also loading the source file up in n++ and saw no difference in line endings. At that time I always "resolved" the issue by going back in git history and writing the code in another way (e.g. on different lines as that actually would have mattered) so it wouldn't crash.