What about the config-*.cvs files? Do they contain default values ​​for factory images?

with moving over to LVGL shortly, can this be adapted?

with moving over to LVGL shortly, can this be adapted?

I'll look into it. We don't have a backlight with OLED, right?

[esp_lcd_panel_disp_on_off()] can turn on or off the LCD screen by cutting down the output path from the frame buffer to the LCD screen. Please note, this is not controlling the LCD backlight. Backlight control is not covered by the esp_lcd driver.

Here is a branch with LVGL (untested)
https://github.com/terratec/ESP-Miner/tree/lvgl_display_timeout

Take a look at https://docs.lvgl.io/9.2/overview/display.html#inactivity, there's already an inactivity timer built in, which resets automatically on any input, e.g. button press. I think it only needs to be checked in screen_update_cb in screen.c.

There's no backlight indeed.

Ah thank you!

Is it correct that we need our own timer to call lv_tick_inc? And we would be limited to uint32 with ~49 days of inactivity?

Is it correct that we need our own timer to call lv_tick_inc? And we would be limited to uint32 with ~49 days of inactivity?

No, ticks are handled by the framework. Each lv_tick, screen_update_cb is called and the inactivity time in ms can then be retrieved by calling lv_display_get_inactive_time. Comparing to whatever configured timeout and the call to turn the display on or off should be done there.