Bugs in 4.16 :/

ah sorry I understood that you already got it also

Can be a bug for you and maybe others not being able to reproduce, and so, not a bug, but something specific to your "configuration" , hence why I spoke about the reset. Honestly speaking on garmin devices, when they are on their first firmwares I always prefer to reset. Or if a lot of updates have been done.
As you said, Garmin's own QA should find these...but I guess it is a bit of a fight we won't win, so better help by reporting to the good channels.
And regarding other brands, they also have their issues (coming from Suunto 9 Peak here). It is a balance to find the ones that have issues that don't bother you, or balance between stability and features.
If you manage to find your gupdate.gcd file for 4.16 firmware and share let me know.
I would love to install and test.

3799751 said:

Can be a bug for you and maybe others not being able to reproduce, and so, not a bug, but something specific to your "configuration" , hence why I spoke about the reset

Sure I get it, except this kind of a bug is not an isolated incident. Saw lots of stuff like this with the 935 (which took months to become stable after release). And I shouldn't have to reset my watch because of a Garmin bug. Now if I had done something unsupported like hack my activity profile FIT files, which caused unexpected behavior on the watch, then I would understand being asked to reset.

Let's face it, this kind of crash just shouldn't happen. Even if I did something with my configuration that nobody else does, in this case it's all within the bounds of the system that Garmin itself provides. But in reality, all I did was install a handful of CIQ watch faces and delete one built-in watchface. Now it crashes whenever I try to add a new built-in watchface.

Yeah, resetting my watch would probably clear out whatever inconsistent state caused this crash. Which brings up the questions: why does the existing code produce an inconsistent state, and why is such an inconsistent not handled gracefully? It seems that two things failed: bad code caused the inconsistent state, and additional code assumed that such a state would never happen.

Obviously bugs happen, but there's a clear pattern of this kind of stuff.

As another example of "unusual usage", maybe most people don't use the map page while not following a course, which explains why that other bug wasn't caught. It's still a feature that Garmin provides, so really can't blame users for using it.

3799751 said:

And regarding other brands, they also have their issues (coming from Suunto 9 Peak here). It is a balance to find the ones that have issues that don't bother you, or balance between stability and features.

Can't argue there. I wouldn't even consider another running watch other than Garmin. But if I only wanted a casual fitness tracker, Garmin would be last place I would look.

I'll just repeat what my co-worker said about his wife's experience with her Garmin: "If you breathe on the watch the wrong way, it crashes".

I just think Garmin has conditioned us to expect constant crashes and bugs, which is why people are so used to resetting their watches. I'd rather not do that with the 945 LTE, since there's so many things which can't be backed up now (like certain kinds of apps and music). (Unlike the 935, where almost everything could be backed up and restored, even in ways that weren't officially supported by Garmin.)

If Garmin would provide cloud sync or even local backup for things like activity profiles / data pages, settings, synced playlists, maybe I would feel better about resetting my watch. Like just reset and restore from cloud / local backup. But nope, lots of things would have to be restored manually.

3799751 said:

If you manage to find your gupdate.gcd file for 4.16 firmware and share let me know.

Sorry it's not in my device anymore. I'm not aware of anywhere that's it's cached (or stored as a temporary file) on my computer either. (But if you know of somewhere I should look, please lmk).

3799751 said:

Honestly speaking on garmin devices, when they are on their first firmwares I always prefer to reset. Or if a lot of updates have been done.

Yeah but it's not exactly a testament to our perception of Garmin products that we believe they need constant resets in order to function properly. Like I said, I don't like resetting my device unless I have a 1-click way to get back all (or most) of my settings and data.

I live in Italy and I recently bought 945 LTE. Will this new 4.16 firmware be released also here in Italy? I ask because Garmin still don't sell officialy 945 LTE in Italy.

Thanks for your help.

Doesnt matter where u live, i live in russia (moscow) bought also from 3rd ppl from europe. Garmin connect or explore will update u within 1 week or so to 4.16 but 3.07 u will get for sure right now or when u will sleep.

so, finally forced my watch to update via Garmin Express on my Mac today after i saw 100% roll out.

HR Field on a 3 field activity screen: now fixed.

so far, i still see the following problems.

NOTIFICATIONS WIDGET: beyond the first message, i still have to double-tap to read the notification. i'm almost used to this now having the watch since June but still a lame bug.

i haven't gone out yet to see if they fixed the problem where the GPS stops logging if you use a hotkey to view widgets/watch face, but i'm not optimistic that that features is fixed due to the lackluster responses i got on it (including one that said it is working the way it should -- which is unlike my 935 or other folks with other watches)

i have confirmed, the Hotkey/GPS not logging while viewing widgets bug/problem still exists.

another fix: the backlight no longer automatically goes one while viewing the HR widget.

FlowState, how did you go from 4.07 beta to 4.16 "non beta" ? Do you have two watches... or is there a trick ? Thanks a lot in advance for your answer :-) !