Yesterday my Instinct locked up for about 30 minutes.

Yesterday my Instinct locked up for about 30 minutes. The cclock facre was stuck at 11:30 AM. It would not rerspond to any button presses. Eventually after pressing CTRL for an extended time it turned off. When I turned it back on it was working again but was disconnected from the Connect app and the app could not find it. I eventually got it into pairing mode. Is the lock up a known issue and what may have caused it?

0 thomass001 over 4 years ago

Same here.
Today it happened two times.
I don't know why, but it was gone for about two weeks.
May be it has to do with the connect app.

0 bobchappuis over 4 years ago in reply to thomass001

Maybe but I don't think so. I have always used connect when running or lifting waits and it has always worked fine. When the lockup occurred I was not using Connect.

0 KENWASHIO over 4 years ago

It has happened to me quite a few times. Sometimes if I press GPS and back, it resumes and sometimes the watch just freezes until I press CTRL for an extended time to turn it off. Most times, I wasn't even in an activity. On one time, it freezes right at the end of a 10K run and it won't let me select "Done" and the entire watch freezes -- fortunately, the run data was still saved after a reboot. Is anyone from Garmin reading this ?

0 PMO over 4 years ago

These freezes have been randomly occurring since V11.00, if I'm not mistaken. And they are still happening (V12.20). I had one of the deep ones yesterday (where you have to force a reboot), and a few of the light ones (where pressing a button - typically GPS - will unfreeze time) during the last month. I already emailed the beta team, but no answer, as expected. It is really frustrating to look at your watch and be fooled by a wrong time indication. And it may lead to many unpleasant scheduled-related situations. :(

0 bobchappuis over 4 years ago in reply to PMO

Well, I am happy to report no further lockups since my report 15 days ago. However the heart rate measurment seems to have gone bad. Shows high at rest and in 60s on exertion

0 darnich over 4 years ago in reply to bobchappuis

Restart the watch and see if that helps

0 bobchappuis over 4 years ago in reply to darnich

Well, after I made that last post about the heart rate I went for a run and it was working ok. A bit high I think but pretty close.

0 thomass001 over 4 years ago

I'm on 13.20 now and the bug is still there.
Yesterday the instinct was frozen.
It woke up with press ABC.
But don't forget to restart because of losing data e.g HR.

0 PMO over 4 years ago in reply to thomass001

Same here. Frozen at 02:04 AM. Woke up with ABC. :( Why do we not see Garmin reacting to this fundamental freezing behavior (presumably idle watch), so often reported here and directly to them? It really bugs me. May this be a sign that they are simply at a loss to deterministically replicate the behavior and thus address it?