Using Termux:VA in Termux native

[lfdevs]

Although using MediaCodec directly is a better choice in Termux native, Termux:VA is a viable option for applications such as Chromium that cannot use MediaCodec directly. (Currently, Chromium supports MediaCodec only when built for Android.)

This article provides a brief introduction to using Termux:VA in Termux native, building on the user guide. Before reading this article, read the user guide for a basic understanding of how to install and use Termux:VA.

Installation

In Termux native, in addition to installing the latest version of Termux:VA, you also need to install the Termux native version of Mesa for Android Container.

Usage

In Termux native, simply start the Termux:VA daemon with the termux-va-start command. Since Termux is not a container, there is no need to mount directories or perform similar operations.

Basic Environment Variables

In addition to the environment variables mentioned in the user guide, Termux native requires TERMUX_VA_SOCKET=$TMPDIR/termux-va/termux-va.sock.

Chromium

In the example commands in the user guide, replace LD_PRELOAD=/usr/lib/aarch64-linux-gnu/libtva_drm_shim_wayland.so with LD_PRELOAD=$PREFIX/lib/libtva_drm_shim_wayland.so. You also need a Chromium build with VA-API support enabled: https://github.com/lfdevs/termux-packages/releases/tag/chromium_157.0.8103.38-90.

Note

Currently, hardware video decoding with Termux:VA in Chromium under Termux:X11 suffers from severe frame flashbacks. Using Anland: Termux is recommended.

FFmpeg

Tip

In Termux native, FFmpeg can use Android MediaCodec directly, so there is no need to use Termux:VA. However, you can try it by following the instructions below if you wish.

In the example commands in the user guide, replace LD_PRELOAD=/usr/lib/aarch64-linux-gnu/libtva_drm_shim_wayland.so with LD_PRELOAD=$PREFIX/lib/libtva_drm_shim_wayland.so. You also need an FFmpeg build with VA-API support enabled: https://github.com/lfdevs/termux-packages/releases/tag/ffmpeg_9.0.2-91.