When pressing any button to leave the watchface on my Fenix 6 pro, it takes up to 3 seconds to leave the screen. I have tried a hard reset. no joy.
When pressing any button to leave the watchface on my Fenix 6 pro, it takes up to 3 seconds to leave the screen. I have tried a hard reset. no joy.
The engineers do not look in the Beta > Community forum so all bugs posted there get no attention. Which is why I am telling those that post in the Community forum to post their bugs in the Alpha/Beta…
I've had my 6X Pro Solar for 18 months (another one before that for 15 months) and, for the most part, I have not experienced the delay described here. However, in recent weeks I have noticed it a few…
Is this an automated bot?
In the past weeks I saw 10 of similar "responses" from Garmin employees, but this one makes absolutely no sense. It 1st states that 23.00 is already official release and not beta…
Exactly, it's quite strange that Garmin do not take care about the feedback post in the Beta Bug forum space even if the version has been push to Public.
forums.garmin.com/.../
What is the purpose of the "Post new bugs for the xx.xx branch here" under this space, if we can't use this direct exchange with your Garmin.
-
In parallel it's nice to see that Garmin is always looking for issue under the public community forum to track new one or strange feedback/behaviour from the community. Garmin - Chris
I've had my 6X Pro Solar for 18 months (another one before that for 15 months) and, for the most part, I have not experienced the delay described here. However, in recent weeks I have noticed it a few times.
On reading this topic I thought I'd check more carefully and, with the first button press of the day, the delay when scrolling to my first widget was very noticeable. Subsequent navigation was as quick as one would hope, but leave the watch for a few minutes and the delay on the next press returned.
I did wonder whether the problem was down to my switch from full widgets to widget glances when the new HRV Status feature was added to firmware and full widgets were not behaving. One could imagine a delay when displaying multiple data from multiple widgets rather than just one data item from one widget.
So, I returned to using full widgets and the delay disappeared. However, since that experiment I have returned to using widget glances once again and the delay is no longer present. So this is all a bit quirky and possibly tough for Garmin to track down. I would suggest, as an experiment, that you try toggling widget glances on/off/on or off/on/off to see if it improves things for you.
Actually, I did video the delay, but it's not inspiring viewing - 49 seconds of my slow droning for 3 seconds of delay - but if it helps demonstrate the problem for Garmin Support maybe it is useful.
I have the same issue with FW Ver. 20.50. It started with the previous FW and I was hoping the 20.50 would sort it out. Leaving your Bluetooth on seems to help even if it's not connected to your phone. I am battery conscious however so I only turn it on when I need to sync. There have been a few other threads with no resolution. https://forums.garmin.com/outdoor-recreation/outdoor-recreation/f/fenix-6-series/281138/anybody-else-have-a-1-second-delay-from-the-watch-face-to-a-menu-e-g-the-first-press-of-the-start-button-for-activities-or-going-from-watch-to-widgets-pls-help-its-annoying/1350097#1350097
Worked for me just now - Fenix 6 Sapphire.
Mostly it is fast for me. But the first press of the day, at least, is always very slow. It is not a big deal, just an observation.
It's as though the watch goes into a sort of deeper sleep state when not used (button not pressed) for some time and it needs a moment to gather its thoughts and wake up. Once it has woken up then the response is quick - at least until it falls asleep again.
It would be good for Garmin to comment on this. Is it by design, a bug, what?
I do experience something different, but probably the two hings are related: The gesture: when I look at the watch and it is supposed to come out from energy saving mode and display the full watchface. It doesn't work when I didn't touch the watch (any button). When I wake the watch up with a button (except the light button) then it does work for a while. I don't know for how long, probably for an hour, maybe more, but after a while the gesture doesn't work again.
I have experienced a bit of a delay, but what is more noticeable to me is the flickering/jittery rendering of the screens when transitioning from one to the other, or when scrolling (especially the control wheel icons); it's become very prominent. I've reset my Tactix Delta Solar several times, and that seems to make it ok (or negligibly minimal) for a very short while... the problem quickly returns after a few transitions or scrolls. Anyone else experiencing this? Does that seem like it's memory issue? I only have watchfaces downloaded, and although I didn't uninstall them I did revert back to stock watchfaces just to see if the third-party ones were to blame, but it still occurred with the stock watchfaces.
It's as though the watch goes into a sort of deeper sleep state when not used (button not pressed) for some time and it needs a moment to gather its thoughts and wake up. Once it has woken up then the response is quick - at least until it falls asleep again.
It would be good for Garmin to comment on this. Is it by design, a bug, what?
I guess it is an energy saving measure. It is the most prominent on a 6 Pro (SW 20.60) that is exclusively used for GPS activities. It really needs some time to process the first button press, after that it is quick.