Instinct - 13.20 Public Release Candidate

darnich said:

Thanks for the update. Minor bug: Watch reports SW Ver 13.20 but Garmin Express on my Windows PC says: 12.20

Not a bug.  On the main page in Garmin Express only the latest installed Public Release Version is displayed.  Click on the "Tools & Content" panel in Garmin Express to see the correct installed latest Beta version.

HTH

Just before the update the main page showed 13.00, I was updating from 12.85

The frozen bug is still there.
The instinct woke up with press ABC.
But don't forget to restart because of losing data e.g HR or no sync with connect app.

I just woke up to frozen time screen on my instinct solar I've only had for a few days... restarted with ctrl, had a notification saying update applied or whatever. Checked the version and it was on the 13.20. 

I'd say more than anything else, its gonna be problematic if this watch cant perform is primary function.

5595492 said:

frozen time screen on my instinct solar

Please report it rather on the Instinct Solar forum, since I do not think that there are any problems with freezing of the standard Instinct, and so it may confuse both the developers, and other users as well.

trux said:

since I do not think that there are any problems with freezing of the standard Instinct

Why do you think that?
It's horrible if you think the time ok and it's not ok, because of frozen instinct.
Be happy without freezing of your standard instinct.

Yes, there are. The freezing behavior that started with V11 is still around, at least for some of us. My watch froze two nights ago, and other recent reports exist here. :(

PMO said:

My watch froze two nights ago, and other recent reports exist here. :(

I had a froze with v11 when I unplugged it from the USB cable, but nothing since that time. The problem is that most of the reports of the freezing that I have seen here, came from Solar users, so it was unclear whether there are any issues, or how often, among the the standard users as well. And that's why it is better to report Solar issues on the Solar forum, and non-solar issues here - to avoid the uncertainty. I stand corrected if it happens on non-Solar devices too. Not experiencing any, and not seing any reports explicitely telling to be from a non-solar device, I did not believe it was the case.

Would be interesting to find some common denominators for the devices with this issue. Is some data missing after the freeze? For example:

• Is there a gap in the sleep or HR data, or does the watch continue to record the data?
• Was there sufficient free space on the storage? The watch could perhaps freeze because of an overfilled storage.
• Are you using the default face, or an alternative one?
• Did you check the Device Sync Audit, trying to browse to a sync audit from the time when the watch froze, trying to find some errrors or warning?
• Did you look into the folder //GARMIN/Debug, after the freeze, checking for a file with a matching time stamp? 
• Did you try resetting the watch, and running certain time with the default settings to see whether it happens too?
• Is it more likely to happen in a low-battery state?

You have a point there. I should be more proactive in trying to find any clues to the reason for these freezes. The thing is that I usually detect those freezes precisely when I want to know the time because some pressing Issue is at hand. But I will enable the extended sync audit and try to do some investigation next time (if there is a next time, because the thing is random and not that common; maybe an average of once a month).

Having said that, those guys from Garmin know what they changed to build V11. They could trace back the changes to see what might be causing the thing. The task becomes easier given that no freezes occurred before V11. I will certainly not hold my breath waiting for them, though.

At this point, all I can say is that it is not battery related, and it is not caused by a lack of storage. Also, hard resets do not stop them from appearing.