Repository navigation
CoreInk: display is cleared even it's set to not clear it #370
Description
If there was anything on the display before the reset or deep sleep, it will be cleared, even if the clear display flag is set to false. As an example, consider the following code running on a CoreInk device.
void setup {
auto config = M5.config();
config.clear_display = false;
M5.begin(config);
}
Activity
EPD / OLED / LED panels: init without clear keeps the image on the panel
begin(): external displays follow cfg.clear_display
ainyan03 commentedon Oct 23, 2026
Thank you for the report. Fixed in the develop branches of M5GFX (#375) and M5Unified (#416); the fix will be in the next release.
What happened: during
M5.begin(), the display initialization re-applied the invert setting, and the CoreInk panel driver treated that as a full-frame change right after a reset, so the whole panel was refreshed with the empty frame. The same path turned the LEDs off on CoreMatrix, and M5Unified also ignoredclear_displayfor external displays (Module Display, Unit OLED / LCD and others).Two notes on what to expect with
clear_display = false:M5.begin(), after a reset and after deep sleep. We checked this on CoreInk with both panel versions (GDEW0154D67 and GDEW0154M09).EPD / OLED / LED panels: init without clear keeps the image on the panel
begin(): external displays follow cfg.clear_display
ainyan03 commentedon Oct 25, 2026
Thank you for your patience — the fix for this issue has just been released in M5GFX 0.2.35 and M5Unified 0.2.28. Please update both libraries (M5Unified 0.2.28 requires M5GFX 0.2.35 or later) and check whether the image on your CoreInk is kept with
clear_display = false.As noted above, the first drawing after such a start still replaces the whole panel with the new frame.