Lichii Vulkan Drivers Explained: Stock, RADV and Turnip in Plain Words

The driver is the floor

The lichii emulator speaks Vulkan 1.3 directly to your phone graphics driver, which makes the driver the floor everything stands on. Two phones with the same GPU silicon can behave differently on different driver versions, because the driver decides how shaders compile, how textures convert and how memory is really allocated. Everything here assumes the tested build from lichii Github.

This is why the Android port test notes always name the driver alongside the phone. A result quoted without its driver is a story missing its main character.

RADV and the Xclipse story

Testing of the Android port leans on a custom Mesa RADV driver for Samsung Xclipse graphics, the AMD architecture GPUs in Exynos phones. RADV is the open source Vulkan driver from the Mesa project, and the port grew up around it: mesh shader workarounds, ASTC texture strategies and tensor operation paths were all measured against it.

On desktop the same pattern repeats with different names: specific AMD card families had shader build crashes in Ocarina of Time that a later build fixed, and an NVIDIA driver version is the suggested workaround for a Star Fox device loss. Drivers are not background noise in emulation; they are half the release notes.

What to change first

Before blaming a game or the emulator, know your driver facts: phone model, GPU, and the driver in use, which is exactly the trio a good bug report carries. If a known custom driver exists for your GPU family and the port tests against it, that is the configuration with evidence behind it.

Change drivers the way you change settings: one at a time, with a known scene as your measuring stick, and a way back. The black screen checklist assumes driver sanity before it goes hunting deeper, because so many rendering faults end there.

Related reading: the black screen checklist.

Related reading: the requirements page.