Have you got laggy 3rd party watch faces when wrist is raised? It takes probably 3 secs to display turn on....
Have you got laggy 3rd party watch faces when wrist is raised? It takes probably 3 secs to display turn on....
unfortunately, it appears to be a "feature" of the Venu and not a "bug"
Glad I stumbled upon this thread. Was thinking about upgrading my VA3 to Venu (perfect size and the bezel looks nicer than VA4's). However, while it's an acceptable trade-off to get a high-res display…
To avoid that the amoled screen burns in there are techniques used as changing the intensity of pixels, in my watch faces I additionally move the time every minute for extra safety.
Where are…
a workaround is to set your display to always on, this way the watch face can keep operating in low power mode and there's no delay in getting the full watch face to show. I use my Data Lover watch face in that way on the Venu and it works really great and fast. (I have the setting Display -> Always On and Sensitivity to High)
(getting it to work in non-always mode is unfortunately not up to the developer as the delay is before the watch face is starting. This delay is something which needs to be fixed in the garmin firmware on the Venu. Fixing it could be as simple as switching the order in which things happen when the watch boots, but granted the amount of time that have gone over fixing this issue, it's probably not as easy as that....)
hi peter, but always on display is possible only during activity, am i right?
Glad I stumbled upon this thread. Was thinking about upgrading my VA3 to Venu (perfect size and the bezel looks nicer than VA4's). However, while it's an acceptable trade-off to get a high-res display without true always-on watch face, it is not acceptable that there is a delay when accessing that watch face (tech in 2020 needs to be snappy). I guess I should wait for 'Venu 2' as Garmin usually gets their FWs in order after six months and you'd think by now they would have resolved this (although obvious covid-19 might affect progress).
I understand your point, but it doesn't make sense to me: why native watch faces doesn't present this lag?
I was using always on with the Crystal watchface and the battery use was a little too much for my liking, unfortunately
With Data Lover I get about 4 days (includes about 1 hour of running per day)
I understand your point, but it doesn't make sense to me: why native watch faces doesn't present this lag?
Native watch faces reside on the chip and are not written in monkey c.... so it's a completely different type.