jpmschweitzerandClaude Fable 5
6b3b9ce0ed
Root cause (investigation): the BSP default tear-avoid mode is TRIPLE_PARTIAL. On ESP-IDF 5.5 the MIPI-DSI driver has no on_frame_buf_complete callback (added in IDF 6.0 -> the boot warning "buffer-switch...may not function on MIPI DSI"), so the adapter falls back to on_refresh_done, which fires every refresh (~60Hz) as a fake vsync. In PARTIAL mode that release path is NOT submit-gated, so when one LVGL frame takes >1 refresh to render it over-releases the buffer that is still being scanned out -> LVGL draws into the live front buffer -> tearing/flicker. Why it only started with the wake word, and only under load: at idle (sparse rain) a frame renders in <16.6ms so exactly one submit per refresh -> harmless. The always-on WakeNet added constant CPU/PSRAM load that pushed the heavy-rain frames (listening=16, thinking=40 streams) past one refresh -> triggered the over-release. User correctly identified it as a resource starve exposing the latent bug. Fix: switch to TRIPLE_FULL, which IS submit-gated even without the callback (one release per actual submit). Same 3 framebuffers, zero memory cost, app-side one-liner via bsp_display_start_with_config so the managed component is untouched. Trade-off: full-screen redraw per frame; if the rain gets choppy under load, cheaper rain rendering (canvas / half-rate tick) is the follow-up. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>