You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is more a question than a bug report, anyway, it happened to me twice that the display froze and was completely unresponsive.
It's difficult to debug because I don't have a serial port attached and it happens very seldom (twice in a month).
The first time it happened, I added a watchdog to restart the esp32.
I'm quite sure that the esp32 restarted at least once due to the watchdog, however yesterday the screen froze but the watchdog didn't trigger, so I think that either the main loop was still running (so the frozen display is a bug somewhere in the library) or there is an hardware problem.
The board is an esp32-2432S028R.
I'm not 100% sure, but the problem happens after this line (i.e. after an inactivity timeout the brightness is set to 0 and I show a dummy screen to avoid registering clicks on the now invisible objects, when there is new activity that line switches to the main screen). Both time I saw the problem the screen was off, I tapped on it, it showed the main screen then froze.
The text was updated successfully, but these errors were encountered:
Thank you, I have no idea how to do that and it if it's even possible without serial 😉
Maybe I should upgrade the library first (when I reported this your repo was using lvgl 8.3.9).
BTW, it didn't happen since last time.
This is more a question than a bug report, anyway, it happened to me twice that the display froze and was completely unresponsive.
It's difficult to debug because I don't have a serial port attached and it happens very seldom (twice in a month).
The first time it happened, I added a watchdog to restart the esp32.
I'm quite sure that the esp32 restarted at least once due to the watchdog, however yesterday the screen froze but the watchdog didn't trigger, so I think that either the main loop was still running (so the frozen display is a bug somewhere in the library) or there is an hardware problem.
The board is an esp32-2432S028R.
I'm not 100% sure, but the problem happens after this line (i.e. after an inactivity timeout the brightness is set to 0 and I show a dummy screen to avoid registering clicks on the now invisible objects, when there is new activity that line switches to the main screen). Both time I saw the problem the screen was off, I tapped on it, it showed the main screen then froze.
The text was updated successfully, but these errors were encountered: