Sorry for digging this old post....but... I have the same Issue. My application should update the display "as smooth as possible" that means the short flickering for a full refresh is ok (takes less than 1 second) but not the whole startup flickering-clearing-UIFlowLogo-flickering-nothinguntilmydatagetready-flickering thing. My solution is now a wait instead of sleep which draws the battery too fast. Any idea how to do that in UIFlow?

Hi @felmue, thank you for the hint. Now the Compilie works. Thanks Cermit

Hello @ebr61168 I am out of ideas at this point in time, sorry. Have you checked with M5Stack support or the shop / store you got your M5Paper from? Thanks Felix

@m5stack it's been 3 weeks, without even a confirmation that you've read the issue. Could we please get an update? Or maybe @Zontex, you could bug someone at M5 HQ, since you seem to be more active.

@powersoft Hi, it is a very nice project! Maybe you can share your code with me?

Hi @Nili while reading the touch IC (GT911) documentation I found that there is a mechanism which allows to select which of two I2C addresses should be used. Depending on how the touch INT line is driven by the ESP32 (low or high) when the reset line goes back to high, either I2C address gets selected. But since the touch INT line is connected to GPIO36 of the ESP32 and GPIO36 is an input only GPIO the ESP32 cannot drive it. From the ESP32 documentation: GPIO34-39 can only be set as input mode and do not have software pullup or pulldown functions. I further found that the 10k pull-up resistor (R87) on the touch INT line, listed in the schematics, is not populated in my M5Paper. I guess this mean when the touch IC is not driving the INT line it is floating and the touch IC could end up with either I2C address. Now, in the GT911 library I found the following code in function begin() which I tries to figure out which I2C address the touch IC actually started up with: Wire.beginTransmission(0x14); if (Wire.endTransmission()) { Wire.beginTransmission(0x5D); if (Wire.endTransmission()) { log_e("Touch screen IIC connection error"); return ESP_FAIL; } _iic_addr = 0x5D; } I wonder if that auto detect mechanism fails sometimes leaving the touch IC with one I2C address and the ESP32 trying to talk to it with the other? Thanks Felix

This is available in the TFT_eSPI base class to canvas, but is not exposed to us. The following seems to work: int height = ((TFT_eSPI&)Canvas).fontHeight();

@powersoft Do you only have 1 canvas? Try canvas instead of canvas1. BTW, you can enclose your code in three back ticks (```) to make it easier for us to read, like this... this text has three back ticks before and after it

@powersoft Have you tried this tool yet? https://github.com/m5stack/M5EPD/tree/main/tools/image2gray It takes a jpg/png/bmp image and converts the image to a 4bit grayscale array.