Martin F.

**Warning:** If you assemble the touch overlay take great Care when connecting the small flat cable. The connector in the Lilygo PCB is not meant to open and close many...

Second one looks nice. But attention that the buttons seem all in one piece, I guess that is supposed to break and move, but I'm not sure if it will...

Looks ok are you sure is not drawing the pixel over another black element and you don’t see it? Try to draw 3 or 4 and do it on gray...

@nellydocs unless Lilygo has the will of updating this one day ( Check #33 ) I highly recommend to use this repository: https://github.com/vroland/epdiy That has an upgraded version of the...

Please give a try to my JPG example in the component EPDiy https://github.com/vroland/epdiy That is the father's repository of this project.

I also think that this is kind of a blocker. But of course esp32 has not so many GPIOs and counting the 8 data bus plus I2C and buttons does...

Yes I2C is a good idea but you loose the touch connector. One great component if you want to have up to 16 more IOs is to use PCA9555 but...

Of course I2C data can be shared among many devices and you won't loose touch, but if touch int pin signals there is an event to read and you are...

No, I just meant that touch is not another pull data device, and it might be not working 100% correctly if being used along another I2C things that are also...

With Atanisoft update and adding this defines: #define I2S1O_WS_OUT_IDX -1 #define I2S1O_BCK_OUT_IDX -1 #define I2S1O_DATA_OUT23_IDX -1 Plus a small update suggested by the compiler works: esp32S2/NeoPixelBus/src/internal/Esp32_i2s.c:168:20: error: 'volatile union '...