-
Notifications
You must be signed in to change notification settings - Fork 89
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
ESP32_2432S028R display tearing, landscape/portrait incorrect, vertical direction flipped #35
Comments
Hey, I have the same board type and managed to figure out a solution based on lcdwiki/LCDWIKI_kbv#3
After updating this declaration, I was able to run the demo project successfully with the screen outputting a correctly displayed image. I am unsure exactly what this change does (perhaps the creator of this repository may have a more clear idea of the impact of these definitions) but it seems to work. I haven't tested the touch screen calibration, but tapping the button in the center of the screen worked for me, not sure if the touch calibration will need to be reoriented too. Hope this helps! |
Amazing, thank you very much. I'll try it out as soon as I can! Did you test for all 4 orientations (TFT_ORIENTATION_PORTRAIT, LANDSCAPE, etc)? If not, I'll test it myself. |
Strange, Just compiled and retested the library and it is all working normally, nothing switched. However, as Curtis02 mentioned, some of the displays are mirrored? Maybe they're mounted the wrong way up or something? |
@rzeldent Clearly our hardware has to be different than yours in some way. But I don't think this can be explained by just mounting the display the wrong way up because that would only affect the orientation/"flippedness" of the image, I think, not the fact that in our case (at least my case) the library code is drawing out of bounds... This could perhaps be explained with the draw order being different, like for example the library assumes the pixels are sent to the display row by row, and for whatever reason our hardware instead expects column by column...? That's what I suppose the |
Update I have done some further tinkering and testing. The previous changes were somewhat correct, however the touch coordinates were now completely out of wack. After some further testing, I realised that the Landscape / Portrait definitions for
After doing this, I reverted all changes I made to It would be great if @truppelito is able to verify is this is also working for them, and then possibly add a variable to switch as suggested by @rzeldent. |
@Curtiss02 That's exactly right, I reached the same conclusion yesterday, but only tested the TFT_ORIENTATION_LANDSCAPE_INV. Now I tested the other cases and I can confirm the images are displayed correctly in all of them. Touch also seems to be working correctly. In conclusion, the only changes needed for a fix are indeed the four |
Just made a new branch. Can you verify this works for you? This has a new option TFT_FLIPPEDMIRRORED |
I bought two displays recently and just found your wonderful library. I've successfully identified my displays as being of the ESP32_2432S028R type and I've been trying to get them to work correctly.
I'm using the following demo code:
First, I just set the following compiler flags as per the instructions:

-D ESP32_2432S028R -D TFT_PANEL_ORDER_BGR -D TFT_ORIENTATION_LANDSCAPE -D LV_CONF_PATH=...lv_conf.h
and I got this result:
Having worked with displays before, this seemed to me like the width/height pixel sizes were wrong, so I switched them in
esp32_smartdisplay.h
:That gave me this result:

There's two things wrong with this:
Any idea what could be causing this, and what I can do to solve it? Maybe there's some #define I can change? I looked through
lv_conf.h
andesp32_smartdisplay.h
and didn't find anything that seemed useful.Thank you!
The text was updated successfully, but these errors were encountered: