I don't know if this is applicable... but...
I remember years ago writing a Public Access Automation system. It had a smooth-scroll of announcements; upcoming shows, community events, etc. etc.
I had a terrible screen-tearing (jelly) problem with my smooth scroll machine. I realized that it was the way that it re-drew the window; it exhibited exactly the same behavior that you're seeing on the minis.
The way that I fixed that was to have a separate memory space where I did my "scroll" to move my image up a pixel, then I used a machine language call called BITBLT (Bit Block Transfer) to "instantly" update the visible window. The scroll tearing was gone.
It looks like just some lazy programming to me; their redraw routine is inefficient, much like it was in my project, prompting my workaround.
I remember years ago writing a Public Access Automation system. It had a smooth-scroll of announcements; upcoming shows, community events, etc. etc.
I had a terrible screen-tearing (jelly) problem with my smooth scroll machine. I realized that it was the way that it re-drew the window; it exhibited exactly the same behavior that you're seeing on the minis.
The way that I fixed that was to have a separate memory space where I did my "scroll" to move my image up a pixel, then I used a machine language call called BITBLT (Bit Block Transfer) to "instantly" update the visible window. The scroll tearing was gone.
It looks like just some lazy programming to me; their redraw routine is inefficient, much like it was in my project, prompting my workaround.