Termux for Beginners: Install, Manage Packages and Check Your First Script

Mixing Termux installation channels or placing scripts on shared storage causes failed add-on installs and permission errors. Install the core app and any add-ons from one matching source—typically F-Droid or the official GitHub releases on Android 7 or newer—and keep executable scripts inside your internal $HOME directory.

For readers looking for a practical termux beginner guide android workflow, Termux provides a non-root Android terminal environment with ported command-line utilities for Python, Git, and OpenSSH client tasks 2 4. It is not a full desktop Linux distribution or a virtual machine: all packages are cross-compiled with the Android NDK against Bionic libc and installed under /data/data/com.termux/files/usr ($PREFIX), which means standard Debian or Ubuntu .deb packages will fail 4 5 7. Current project documentation checked October 17, 2026 lists v0.118.3 as the latest release for Android 7+ and distinguishes the main F-Droid and GitHub builds from a separate experimental Google Play codebase for Android 11+ 1 3.

This guide is compiled from official Termux documentation checked October 17, 2026. The package commands and starter Python script below are proposed verification checks for your own phone, not results from device benchmarking by us. See our review policy for how we separate documentation research from hardware testing.

A matte-black smartphone connected to an aluminum USB-C hub on a workbench mat.

Which Termux installation channel should you choose?

Start with F-Droid or the official termux/termux-app GitHub releases on Android 7 or newer, and never mix APKs across channels 1. Older tutorials often state simply that Google Play builds are abandoned, while current official documentation explains a more specific split: Google Play now carries a separate experimental branch for Android 11+ devices built from https://github.com/termux-play-store/, whereas F-Droid and GitHub distribute the main codebase (latest release v0.118.3 in the reviewed README) 1 3.

Keeping add-on signatures matched

The core Termux app supports six optional plugin apps: Termux:API, Termux:Boot, Termux:Float, Termux:Styling, Termux:Tasker, and Termux:Widget 1. In the main F-Droid and GitHub builds, the base app and all six plugins declare the same Android sharedUserId (com.termux) 1. Android’s package manager requires every app sharing that user ID to carry an identical cryptographic signature 1.

If you install Termux from F-Droid and later try to install Termux:API or Termux:Widget from GitHub, Android blocks the installation with errors such as App not installed, INSTALL_FAILED_UPDATE_INCOMPATIBLE, INSTALL_FAILED_SHARED_USER_INCOMPATIBLE, or signatures do not match previously installed version 1.

To prevent channel conflicts:

1. Pick one channel before installing plugins. If you use F-Droid, install both Termux and any Termux:* add-ons from F-Droid (you can download the APK directly on the F-Droid package page or use the F-Droid client) 1. For a broader look at how F-Droid package IDs and signing keys work, see our F-Droid app selection and signing guide.
2. Disable Google Play auto-update if you use F-Droid or GitHub. Because the experimental Google Play build removed sharedUserId, Google Play can attempt to overwrite an existing F-Droid installation and fail 1. Open the Termux listing in the Google Play Store app, tap the three-dots menu in the top right corner, and uncheck Enable auto update 1.
3. Never install GitHub builds re-uploaded to Telegram or social media. The official README warns that GitHub APKs use a publicly shared testkey_untrusted.jks certificate, meaning third parties can forge malicious updates that install cleanly over a GitHub build 1.
4. Uninstall every Termux APK before switching channels. If you decide to move from Google Play or GitHub to F-Droid, back up your files first, open Android Settings → Applications, search for termux, and uninstall the main app plus every installed Termux:* plugin before installing from the new source 1.

Takeaway: Verify where your base Termux APK came from before adding Termux:API or Termux:Widget; switching channels later wipes internal app directories during uninstallation 1 6.

How does Termux package management differ from desktop Linux?

Use the pkg wrapper for daily package operations, upgrade existing packages before installing new ones, and never add Debian or Ubuntu repositories 4 5. Although Termux uses Debian-style apt and dpkg under the hood, it is a rolling-release Android environment rather than a standard GNU/Linux distribution 4 5.

Why pkg is preferred over raw apt

The official Package Management wiki recommends pkg instead of calling apt directly for three reasons 5:

• It runs apt update automatically before installing a package when the index is stale 5.
• It performs client-side load balancing by rotating between official repository mirrors, helping prevent hosting quota failures 5.
• It provides concise subcommands such as pkg in for pkg install 5.

Boundaries that break a Termux environment

Keep four documented package restrictions in mind before copying commands from general Linux forums:

• Do not install Debian or Ubuntu .deb files: Standard Linux distributions follow the Filesystem Hierarchy Standard (/bin, /etc, /usr) and link against GNU libc (glibc) 7. Termux places its environment under /data/data/com.termux/files/usr ($PREFIX) and compiles packages with the Android NDK against Android’s Bionic libc 4 7. Adding Ubuntu lines to sources.list or forcing foreign .deb files with dpkg will not work 5 7.
• Do not disable repository signature verification: Official packages are verified using public keys in the termux-keyring package 5. If pkg upgrade reports a repository error, switch mirrors with termux-change-repo or update from a supported Termux build rather than bypassing GPG integrity checks 1 5.
• Do not run apt or pkg as root: Even on rooted phones, Termux restricts running apt under root because root execution alters file ownership and SELinux labels on Android’s /data partition 5 6.
• Do not expect package downgrades: Termux repositories do not retain historical versions of .deb packages to save server disk space 4 5. If your workflow depends on a specific compiler or interpreter release, back up your environment before running a major upgrade 4 8.

Where should your scripts live? Internal $HOME vs shared storage

Write and execute your scripts, Git repositories, and SSH keys inside Termux’s internal $HOME directory (/data/data/com.termux/files/home), and use shared storage (~/storage/shared) only to exchange non-executable data files with other Android apps 4 6.

Physical card trays and USB drives use Android storage layers that restrict Linux permissions and direct script execution.

The Termux storage documentation divides device storage into three categories with strict filesystem boundaries 6:

Why scripts fail on /sdcard or microSD cards

Android exposes shared storage and adoptable microSD cards through filesystem overlays that emulate FAT32/exFAT behavior and block Unix permissions (chmod/chown), symbolic links, sockets, and direct binary execution 4 6. Because $PREFIX is hardcoded into Termux binaries and requires Unix permissions and symlinks, you cannot move $HOME or $PREFIX onto an SD card 4 6 7.

When you want to move a finished text output, CSV, or archive into your phone’s Download folder, run:

termux-setup-storage

Accepting the Android prompt grants storage access and creates $HOME/storage containing symlinks such as ~/storage/shared (root of shared internal storage) and ~/storage/downloads 6.

Protecting files before uninstalling or clearing app data

Because $HOME, $PREFIX, and the external private folder ~/storage/external-1 (Android/data/com.termux) belong to the Termux app sandbox, uninstalling Termux or tapping Clear Data in Android Settings permanently erases all of them 6 7 8.

• Manual full archive ($HOME + $PREFIX): The official backup wiki documents archiving both ./home and ./usr to shared storage outside private Termux folders:

  termux-setup-storage
  tar -zcf /sdcard/termux-backup.tar.gz -C /data/data/com.termux/files ./home ./usr

  Store /sdcard/termux-backup.tar.gz outside /sdcard/Android/data/com.termux so an uninstall does not delete the archive 8.
• Supplied termux-backup / termux-restore limitation: The helper scripts included in termux-tools (termux-backup /sdcard/backup.tar.xz) back up and restore $PREFIX (./usr) only and do not touch $HOME 8. Back up your $HOME projects separately, or sync a dedicated folder outside the private sandbox using our Syncthing Android-to-PC folder sync guide alongside the Android phone backup checklist.

Suggested first check: verify paths, packages, and a starter Python script

Before building larger workflows, run a bounded check inside $HOME that confirms your directory paths, package index, and a single standard-library Python script. The sequence below is a proposed editorial check grounded in Termux’s documented paths and package commands, not a record of device testing 2 4 5 7.

Termux supports external keyboards for longer shell sessions while keeping scripts inside the app’s private home directory.

Step 1 — Confirm $HOME, $PREFIX, and your single-user identity

Open Termux and run these read-only inspection commands:

pwd
echo "$PREFIX"
whoami

• What to expect: pwd should report /data/data/com.termux/files/home, $PREFIX should report /data/data/com.termux/files/usr, and whoami will show an Android sandbox user ID such as u0_a231 rather than root or a desktop login name 4 7.
• Stop condition: If pwd points inside ~/storage/shared or /sdcard, return to $HOME with cd ~ before creating scripts or keys 6.

Step 2 — Upgrade packages and install Python, Git, and OpenSSH

Refresh the rolling-release environment first, then install the core tools documented on the main Termux site 2 4 5:

pkg upgrade
pkg install python git openssh
python3 --version
git --version
ssh -V

• What to expect: Each --version or -V check prints the installed binary version from $PREFIX/bin without dynamic linker errors 5 7.
• If downloads fail: Run termux-change-repo to select an active mirror rather than editing sources.list with non-Termux URLs 1 5.

Step 3 — Run a disposable Python environment check in $HOME

Create a small workspace inside $HOME and run a one-file Python check that inspects your current path and platform:

mkdir -p ~/check-env && cd ~/check-env
cat << 'EOF' > env_check.py
import os, sys, pathlib

home = pathlib.Path.home()
prefix = os.environ.get("PREFIX", "unset")
print("Python executable:", sys.executable)
print("Home directory:", home)
print("PREFIX:", prefix)
print("Inside Termux home:", str(pathlib.Path.cwd()).startswith(str(home)))
EOF
python3 env_check.py

• Pass condition: sys.executable resolves under /data/data/com.termux/files/usr, and Inside Termux home prints True.
• Shebang note: If you later run standalone scripts starting with #!/bin/sh or #!/usr/bin/env python3 directly via ./script.py, Termux includes termux-exec to translate standard shebang paths, or you can rewrite hardcoded headers with termux-fix-shebang <file> 7.
• Cleanup: When finished, remove the disposable folder with rm -rf ~/check-env.

Android background limits and when Termux is not the right tool

Treat Termux as an on-demand local shell or SSH client rather than an always-on server or a full GNU/Linux desktop 1 7.

1. Android 12+ phantom process killing (signal 9): The official termux-app README warns that Android 12 and newer terminate phantom background processes when the system-wide count across all apps exceeds 32, or when background processes use excessive CPU, printing [Process completed (signal 9) - press Enter] 1. Android 12L and Android 13+ include a developer option to disable phantom process trimming; consult the README’s linked Android docs if background sessions terminate unexpectedly 1.
2. Single-user non-root boundaries: Without root, Termux cannot modify device firmware, kernel parameters, or hardware interfaces directly, and server packages (ftpd, httpd, sshd) default to high ports (8021, 8080, 8022) because unprivileged Android apps cannot bind privileged ports below 1024 4 7.
3. When to use PRoot or a remote server instead: If a tool requires a standard Linux /usr and /etc layout or unpatched glibc binaries, the Differences from Linux wiki notes termux-chroot (from the proot package) or a PRoot distribution—or use Termux’s ssh client to connect to a remote Linux machine 2 4 7.

For the rest of your mobile setup—including local Markdown notes, file managers, and automation—return to our Android productivity and essential apps guide.

Frequently Asked Questions

Why does installing a Termux add-on fail with an incompatible signature error?

Termux and its six official plugins share the Android user ID com.termux and must be signed with the exact same cryptographic key 1. Mixing an F-Droid core app with a GitHub or Google Play add-on fails; back up your files, uninstall every Termux APK, and reinstall all components from one channel 1.

Can I install standard Ubuntu or Debian .deb packages inside Termux?

No. Termux is not Filesystem Hierarchy Standard compliant and links binaries against Android’s Bionic libc rather than GNU libc 5 7. Adding Debian or Ubuntu repositories to sources.list or installing foreign .deb files breaks package management; install packages only from Termux repositories via pkg 5.

Why does Termux show Process completed (signal 9) on Android 12 or newer?

Android 12 and later enforce a system-wide limit of 32 phantom processes across all apps and terminate background tasks that exceed CPU or process thresholds 1. The official README links Android 12L and 13+ developer settings that disable phantom process trimming when background sessions terminate unexpectedly 1.

Method and sources

This guide was prepared with AI assistance and editorial review by TasteOfAndroid using the official termux/termux-app README, the termux-play-store organization, termux.dev, and the Termux Wiki pages on Getting Started, Package Management, Internal and External Storage, Differences from Linux, and Backing up Termux, all checked October 17, 2026. The command sequences and starter Python script are proposed verification steps derived from those specifications; we did not execute device benchmarks or audit APK binaries. Hardware photographs show physical workbench connections and input setups rather than terminal screenshots.

Last updated October 17, 2026.