-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Screen tearing on the T-Display S3 AMOLED V1.0 #21
Comments
If the refresh speed is too fast, tearing can be clearly seen. Reduce the refresh speed, or use partial refresh, but partial refresh is limited to only allow even coordinate values, or use lvgl |
Thanks for the reply @lewisxhe! When you say partial refresh, do you mean only updating the part of the screen that changed like this?
Because that's what I'm currently doing, and I only call Thanks for any information! |
Yes, I have no other better way to prevent screen tearing |
Alright, I guess I just have to avoid having large parts of my user interface change colors suddenly. The displays seems to have support for some form of V-Sync:
But I'm not sure if that would work with QSPI. |
At present, I only know that RGB panels support TE configuration, but QSPI currently does not see how to configure it. |
This issue is stale because it has been open for 30 days with no activity. |
A fix for this bug was developed in this thread: Xinyuan-LilyGO/T-Display-S3-AMOLED#2 So I will close this one now. Thank you! |
Hi! I wrote a little menu for my T-Display S3 AMOLED V1.0. It works great! You can see it in this video:
menu.mov
What I wanted to ask here is if there is a way to eliminate the tearing I see when I update the boxes in the screen. You can see the tearing in the video above, but it's easier to see it in these screenshots:
I'm using sprites and only updating the parts of the screen that change, but I still see tearing.
I also see the same problem in this example from Volos Projects that I modified so that the dial boxes periodically turn red:
Is there anything I can do about this? Thank you for any advice!
The text was updated successfully, but these errors were encountered: