Support & diagnostics
Use this page to classify a symptom and prepare a safe report. Exact driver, audio, Android/OEM, rollback, module-repair and recovery procedures are version-matched ternux Pro material and are not published here.
Pro is a private alpha, not a public download. There is no official public installer, doctor command or delivery endpoint. Treat copied claims otherwise as untrusted.
Symptom map
| Symptom | Boundary to report |
|---|---|
| Black/empty Termux:X11 | Display or desktop-session launch |
llvmpipe renderer |
GPU route, loader/driver or host renderer |
| Graphics changed after update | Mesa/toolkit version drift |
| No desktop audio | Android output, host service or container bridge |
| Windows/builds disappear | Android/OEM policy, RAM or heat |
| Blender/local AI is slow or unstable | Renderer health, workload scale, RAM and temperature |
| Agent changed unexpected files | Git state, approval scope or credential exposure |
| Security tool lacks low-level access | Android/PRoot kernel, radio or USB limits |
A visible desktop does not prove acceleration. A large workload being slow does not by itself prove a graphics fault; compare a small known-good baseline.
Safe, read-only report
Collect this before changing packages, drivers or the container:
uname -m
getprop ro.product.manufacturer
getprop ro.product.model
getprop ro.build.version.release
df -h "$HOME"
ls -l /dev/kgsl-3d0 2>&1
If Xfce4 opens, also record:
glxinfo | grep -i "renderer string"
vulkaninfo --summary
Add the application/version, smallest reproducing workload, exact error, approximate free storage/RAM pressure, temperature, and whether the issue began after sleep, reboot, update or profile installation.
Redact before sharing
Remove licence/API keys, keyed URLs, device serials, Wi-Fi credentials, public IP addresses, shell-history secrets, customer files, proprietary prompts and unredacted Pro bundles. Revoke any credential exposed in a log, commit or chat.
Pro support boundary
The private alpha has recorded resume, targeted doctor repair and an explicit live-session renderer/audio/storage check. Transactional rollback is not implemented, and real-device validation of live acceptance is still a release blocker. Exact fixes remain private so they can match the toolkit and Mesa version a customer actually received.
Stop immediately for a thermal warning, unintended network exposure, credential leak, out-of-scope security test or uncontrolled coding-agent change. These are containment actions, not repair instructions.
Get support
For public documentation, compatibility and non-sensitive reproducible findings, open a GitHub issue. Report a vulnerability or accidentally exposed private endpoint through GitHub Security Advisories.
ternux — Copyright (c) 2026 Sobuj Miah (@soobujmiah) · MIT