FAQ

Do I need root?

No. PRoot provides a Debian userland without a privileged chroot. ternux does not unlock the bootloader, install a custom kernel or root the phone.

Some Android/OEM background-process policies may still need settings changes or an ADB action. That is device administration, not root access.

Is ternux Pro available now?

No. As of 13 August 2026, ternux Pro is in private development and is not on sale. There is no public installer endpoint. The repository and this site will name the private-beta and official release channels when they are ready.

Treat copied commands or download links claiming to be a current Pro release as untrusted.

Why is the complete installation procedure not public?

The public site now focuses on compatibility, architecture, daily operation, evidence of success, realistic workloads and troubleshooting. The complete version-bound installer procedure, rollback implementation and operator runbook are private Pro release materials.

This boundary also avoids presenting stale installation commands as safe after a Mesa, Android or package change.

Will it work on my phone?

A suitable baseline is Android 10+, aarch64, at least 12 GB free, a maintained Termux build and Termux:X11. Graphics vary by device:

GPU family	Expected route	Positioning
Qualcomm Adreno	Zink + Turnip	Preferred accelerated path on supported devices
Mali / Xclipse / PowerVR	VirGL	Compatibility path; slower and more limited

This is not a universal compatibility promise. Android build, OEM restrictions, kernel/driver versions and RAM can still affect the result. The Pro preflight and device matrix will define supported combinations at release.

How much storage and RAM do I need?

Reserve at least 12 GB for the base environment and working room. Local AI models, Blender assets, development dependencies and security datasets need more.

Four GB RAM is the practical minimum; 6–8 GB is more comfortable. Android and Debian share the same physical memory.

How long will deployment take?

It depends on storage speed, network, device, selected workload profiles and thermal state. A reliable public time promise will be based on private-beta data, not an illustrative number. Plan to keep the phone powered and available during the first deployment.

What proves that acceleration is working?

From inside the Xfce4 desktop:

glxinfo | grep -i "renderer string"
vulkaninfo --summary

Zink/Turnip is expected on a supported Adreno route; VirGL is expected on the compatibility route. llvmpipe means CPU rendering and must not be accepted as a successful accelerated deployment merely because the desktop opens.

Can Blender really run?

Yes, within phone-appropriate limits. On the author’s tested Turnip-enabled device, lightweight Blender viewport work was smooth enough for low-poly edits, simple materials and modest scenes.

That is an observed result, not a cross-device benchmark. Dense sculpting, large textures, simulations and long production renders remain poor phone workloads.

Can I run local AI?

The planned Pro AI profile uses llama.cpp with Vulkan. Compact 1–2B parameter models at Q4 quantisation are a practical starting point on many phones.

RAM, context size, model architecture and heat matter. GPU offload helps but does not remove memory or thermal limits. Local model services should bind to loopback unless authentication and intentional network access are configured.

Can I use Claude Code, Hermes or OpenCode?

A Debian terminal can host Node.js/npm and terminal-based coding assistants. Each tool has independent account, model-provider, quota and licence terms. Running inside ternux does not make a third-party service permanently free.

Protect API keys, review commands before approval and commit work before broad automated edits.

Can I install security tools?

Standard Debian security and network-analysis tools can be useful in an authorised lab. Use them only on systems you own or have explicit permission to test.

PRoot does not grant unrestricted Wi-Fi monitor mode, packet injection, direct USB access or arbitrary kernel capabilities. ternux can be a portable analysis station without replacing dedicated security hardware.

What about cryptocurrency mining?

It may be technically possible to run some arm64 compute workloads, but mining is not recommended or supported as a primary ternux use case. Sustained load causes heat, throttling, battery drain and potential battery wear, while mobile economics are usually poor.

Can Pro resume after interruption?

Recorded resume and targeted doctor repair exist in the private alpha: completed modules are stored, and failed checks map to a module that can be rerun. Transactional rollback does not exist yet; it remains a release blocker. Private beta must test interrupted runs, repair, backup/restore and declared recovery behaviour before launch.

No public installer exists today, so copied resume or doctor commands should not be treated as an official release.

Does Pro contact a server?

The planned licensed product will need a defined delivery/licence flow. Its privacy policy must state exactly what is sent, why, how long it is retained and how device seats work before launch.

The desktop itself should not require analytics. Debian packages and optional third-party tools still contact their own configured repositories or providers. Local AI can remain local when models and services are configured that way.

Why can the first launch be slow?

Mesa may be building a shader cache, Debian applications are starting through PRoot, and Android may be managing memory aggressively. Performance often stabilises after the first few launches. Save a renderer and benchmark baseline before tuning.

Can I use another desktop environment?

Other arm64 desktop environments may run under PRoot, but ternux is designed and validated around Xfce4 because it is relatively light and does not require a normal systemd boot. Alternative desktops are outside the initial supported configuration.

Can I run x86 software, Steam or Wine?

Not as a supported use case. The Debian environment is arm64. Adding x86 translation or emulation introduces another compatibility and performance layer. Native arm64 Linux applications are the intended target.

How do I move files to Android?

After Android storage permission has been granted, shared storage is the normal hand-off point:

cp report.pdf ~/storage/shared/

Keep valuable source code in Git and maintain a backup outside the container.

How should I update?

Back up first, record the renderer/toolkit version, read release notes, then use the version-matched Pro update route when available. Graphics components should not be replaced casually: a desktop can continue opening after an update while silently losing the intended GPU path.

Where do I report a problem?

Open a GitHub issue for public documentation, compatibility or reproducible non-sensitive findings. Include the device model, Android version, GPU route and exact relevant output.

Never post licence keys, API tokens, private endpoints or unredacted support bundles. Report sensitive issues through GitHub Security Advisories.