Skip to content

About

No description, website, or topics provided.

Resources

Stars

0 stars

Watchers

0 watching

Forks

Repository files navigation

impeller_tv_repro

Minimal reproduction of stale / ghosted frames under Impeller's Vulkan backend on TCL Android TV with an Imagination PowerVR B-Series BXE-4-32 GPU.

Vulkan-specific. The default backend here is Vulkan (android_context_vk_impeller.cc) and it ghosts. Forcing the OpenGLES backend (android_context_gl_impeller.cc) on the same device renders correctly — so the bug is the Vulkan path on this GPU, not Impeller in general. Confirmed on Flutter 3.44.2 / engine 77e2e94772, debug and release. The backend line is only visible when attached via flutter run --verbose-system-logs.

Symptom

Navigating a TV-style grid (vertical list of horizontal carousels) with the D-pad, previous frames are not cleared — old cards/rows stay ghosted above the new UI, the upper rows appear to reappear, and the UI shakes. Disabling Impeller (Skia) renders correctly.

Affected device

Model TCL Smart TV G10 (G10_4K_GB_NF_32BIT)
SoC Realtek RTD6748
GPU Imagination PowerVR B-Series BXE-4-32, OpenGL ES 3.2, driver 23.2@6491706
OS Android 12 (API 31)
ABI armeabi-v7a (32-bit)
Backend Impeller Vulkan (confirmed via android_context_vk_impeller.cc; not denylisted for BXE-4-32)

Reproduce (bug present)

flutter run --release -d <tv-device>

Then use the D-pad: move down through the collections and across the carousels. Watch previous rows fail to clear / ghost.

Confirm the fix

Two verified workarounds:

A. Force the OpenGLES backend (keeps Impeller). Add to AndroidManifest.xml <application> (a commented-out block is already there):

<meta-data android:name="io.flutter.embedding.android.ImpellerBackend"
           android:value="opengles" />

B. Disable Impeller (Skia):

flutter run --release -d <tv-device> --no-enable-impeller

Both render cleanly. repro-capture/backend_*.txt holds the captured backend lines for the buggy (Vulkan) and working (OpenGLES) cases.

Automated capture

run_repro.sh builds + installs the APK, launches the app, auto-drives the D-pad over adb, records the Impeller backend line (via a short attached flutter run --verbose-system-logs → backend.txt), and collects device/GPU/logcat/flutter doctor artifacts into a timestamped impeller-report-*/ folder. Fully non-interactive.

./run_repro.sh                 # bug present (Impeller ON, release)
IMPELLER=off ./run_repro.sh    # control run (Skia)
BUILD=debug ./run_repro.sh     # debug build (verbose engine logs)
DEV=host:port ./run_repro.sh   # override device

A completed capture lives in impeller-report-20260720-171452/ (see its SUMMARY.md).

On the G10, on-device motion capture is impossible: screenrecord fails with err=-38 (no hw encoder) and screencap returns a cached buffer. Visual proof is the phone-camera shot repro-capture/ghosting_proof.png. The defect is purely visual, so the release logcat is quiet (no crash/error).

Notes

  • No assets, no network, no third-party packages — pure flutter/material.
  • flutter --version: Flutter 3.44.2 stable, engine 77e2e94772.

About

No description, website, or topics provided.

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages