Does that also happen on a default watchface? Connect IQ watchfaces can be nice, but there are also a lot of them that are made by inexperienced people, that just add functions, but don't optimize code, or just make very inefficient/bad code causing all kinds of weird behaviour. I'm not saying that's the case with your Watch face, I don't know PixelPathos, but stuff like that happens all the time.
It looks like you posted a MOV video recorded from an iPhone.
Just so you know, non-Apple users may be unable to play the video at all, and even Mac/iPhone users may be unable to *easily* play the video, because in your case (for whatever reason), the forum used a super old way of embedding video content.
For example, on my Mac, I can't just click on the video placeholder to play it. If I do that, the placeholder is replaced by "plugin unsupported" or a blank space. I have to right-click on the placeholder and select Open in New Tab or Open in Quicktime Player, to save it or play it.
I took the liberty of converting the video to MP4 so everyone can see it.
As far as what you're seeing with Crystal goes:
- I can't reproduce this with either Crystal or Crystal Reborn (obviously it's really happening for you tho)
- There is a known issue / quirk with Connect IQ watchfaces. When you scroll away from a CIQ watchface, the watch takes a screenshot. When you scroll back, even if it's seconds, minutes, or hours later, the saved screenshot is initially shown, before the watchface draws the screen with the current time. This makes it look like the watchface went "back in time" for an instant, then jumped forward to the correct time. Garmin does this so CIQ watchfaces seem more responsive - it's out of control of the dev. Having said that, what you're seeing doesn't really look like that.
I just checked and was able to reproduce this behaviour with face "Infinite Geometry" from Garmin.
Infinite Geometry is a Connect IQ watchface (regardless of the fact that Garmin made it) and would therefore be subject to the same quirk that I mentioned. Maybe it is that quirk after all. Or maybe it's a different bug but somehow related?
If so, I def expect that you *won't* see this with a *built-in* watchface.
