Rotating Cubes and Built-In Uncompletion

There’s a virtual cube as a screensaver on my LG 3D TV. It rotates clockwise, then blinks out for a moment to reappear somewhere else on the screen, still rotating. Or is it? Does the algorithm continue the rotation pattern during the blanking phase, or does it simply repeat itself for a short span from place to place on the screen? Looking closely I see that each time it reappears, it is, in fact, already in motion, but the edge of the cube is always in the same starting point as it turns. Then, looking at where it fades out, an edge it coming around. But, if I project that motion over the time of the blanking out, like continuing a song in your mind when you walk out of a room where it is playing and then back in again, I find that the edge on the right does not have time to reach the starting point of the edge on the left for the spin algorithm to have continued during the blanking period. They might have just continued the on-screen spin but a little longer and the gap would have been right, so even if it was just a repeat of the same small segment and not a true algorithmic spin, you could never tell – it would be identical because the timing would line up perfectly. Yet they chose not to do that and just to let it not quite match up and, therefore, clearly be nothing more than a simple repeat. All that programming work and still to leave such an easily remedied flaw – a lack of completion – a jarring reset at each repetition. Why would they do that?