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…
Stock watchface or third party one?
I have tried with both stock and third party, same issue
Which software version on your watch ?
In the past we saw many feedback about slow reply of the watch from watchface to menu/activity/etc.
forums.garmin.com/.../slow-first-response-after-pushing-button
23 im on the beta testing thingy too
The version 23.00 software is official software and not Beta. Once on official release, all reports go in the Fenix 6 forum. If you side load Alpha software or are on Beta software, you will post your report in the Beta forum that matches the version of Beta software you are using. Thank you.
- https://forums.garmin.com/beta-program/fenix-6-series/bug-reports/
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, then it tells him what to do when he is on beta software. Actually if anyone would post anything in the beta forum (included in your comment) then the 1st and only response they would get is the same nonsense reply with the only the 1st sentence being relevant.
The top of the Community forum in our Beta forums advises everyone to not post their bugs there but they are posted in there frequently on accident. I am the one moving them where they belong. I am definitely not a bot.
Ok, but given that the official word from Garmin is that they might or might not look at the community forum wouldn't it make more sense to open a bug report in the internal bug system?
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 forum put in place by engineering for the version being used.
But 23.00 is official, not beta, as you also wrote in your comment. Once someone tries to report now anything about 23.00 in the beta forum we get a similar reply telling that 23.00 is not beta any more...
I know you want to help, and you're one of the few Garmin employees who are active in the forum, but this is a bit confusing.