Glances scroll lag issue (Hydration tracking glance and glance folders)

When I bought the watch (out of the box) glaces scrolling was almost nicely smooth. Then I added the Garmin official water tracking widget and whenever the widget is displayed on the screen, scrolling through glances is very laggy (choppy, unresponsive screen).

Now with the latest update Garmin added folders, which I use because more useful data gets displayed and everything is nicely organized. These folders are making the scrolling through glances lag even more.

It's sad to see that a watch for 1000€ has a such bad user experience on a thing so simple and gets absolutely trashed when comparing to other smart watches for under 500€. Is it so hard for Garmin to have a water tracking widget that actually works and would come built in the watch? Since Garmin has time and resources to create a stocks tracking widget I see no reason why water tracking can't be implemented in a way that doesn't make a 1k€ watch look like a cheap chinese laggy piece of *** when using it.

0 3562794 over 2 years ago

Absolutely right. Having the same issue. Plus the hydration widget does not work properly. Sometimes it adds water intake by itself. Very sad indeed.

0 [Redacted] over 2 years ago

This has been an issue since the first Q3 alpha release and what you're seeing now is ten times better than before (it was a nightmare and I had to remove the Hydration glance). It's sad that they still haven't managed to completely fix the problem. I still haven't readded the glance.

0 3850910 over 2 years ago

I have the same issue by using the “folders”.

In models such as epix gen 2, they must increase the frame rate on the scrolling menu! That is basically mandatory for all models that uses touch screen, since by finger we scroll much faster than clicking buttons.

0 Josh over 2 years ago

I’ve reported this ten times. Nobody pays any attention.

0 3850910 over 2 years ago in reply to Josh

A “cheap” solution can be: despite how fast we scroll down, shift by one glance per time; similarly to what buttons do.

However, another solution is to sacrifice the scrolling speed to increase the frame rate as close as possible to 60.

0 Josh over 2 years ago in reply to 3850910

$1000 should bring a smooth UI such as a $800 Apple Watch IMO

0 gaijin over 2 years ago in reply to Josh

Josh said:
$1000 should bring a smooth UI such as a $800 Apple Watch IMO

I fixed it for you:

$1000 should bring a one day battery life such as a $800 Apple Watch IMO

See? Doesn't make much sense, does it?

0 Martin Ferenec over 2 years ago in reply to gaijin

I agree with both of you. On one side it's amazing that Garmin can pull of such a long battery life and I respect that. But on the other hand it's sad to see that use experience is so poor on a such expensive product. People buy into Apple mostly because it just works and it has a pleasant and smooth user experience.

Modern phones with high refresh rate displays allow you to select standard and "smooth" higher FPS option. Why can't Garmin introduce the same option? Settings -> Display -> Refresh rate -> 1. Low (higher battery life) 2. Optimized (balance between battery life and "smoothnes") 3. High (smooth as butter)

I suspect that the processor on the watch is simply not powerful enough to handle smooth transitions. For example in settings menu or activity selection menu it's smooth scrolling, but on glances it's laggy (because so much data needs to be rendered).

0 3850910 over 2 years ago in reply to Martin Ferenec

There are no excuses for a thousand euros watch. It is easy to blame the hardware. But from my experience, in software development, the majority of such problems can be solved in software level.

it is a fact that Garmin is used to listen to our rEmory’s and response with a solution on next (software) version updates. I hope that they will find a solution here as well, to increase the smoothness of scrolling

0 Josh over 2 years ago in reply to Martin Ferenec

Martin Ferenec said:
Why can't Garmin introduce the same option? Settings -> Display -> Refresh rate -> 1. Low (higher battery life) 2. Optimized (balance between battery life and "smoothnes") 3. High (smooth as butter)

I LOVE this idea!