Skip to content

Releases

RedTerm v2.6.0

Choose a tag to compare

@github-actions github-actions released this 19 Nov 17:16

Added

  • Android Shell — a session running the phone's own /system/bin/sh
    (toybox + the Android tools: pm, am, dumpsys, getprop), with an
    optional bundled bash/busybox toolkit on top for the usual text tools.
    No install; reached from the Welcome screen, the dashboard, the home
    new-session button, and Settings, and listed there as a preinstalled entry
    with the Android icon and a launch affordance. It starts in the app's own
    writable storage, so files can be created and scripts run. Starter
    commands once inside:
    • getprop ro.build.version.release — the Android version
    • pm list packages — the installed packages
    • ps — the running processes
    • echo "android" | grep a — pipes and the text tools work
    • sh script.sh — run a script through the interpreter (a bare
      ./script.sh cannot exec a script out of noexec app storage)

RedTerm v2.5.0

Choose a tag to compare

@github-actions github-actions released this 16 Nov 09:19
8254fd1

Added

  • Amazon and NixOS added to the catalogue: images built by the rootfs-images pipeline,
    installable from the Welcome screen, each with its own icon.

  • NixOS ships nix itself, so a session installs packages over the network: the image
    keeps the nix tool family and the nixpkgs registry source, and nix profile install nixpkgs#nodejs, nix shell nixpkgs#git and nix run nixpkgs#hello substitute from
    cache.nixos.org into the session's writable store. The base tools move with a newer
    image; in-session installs do not.

  • The nixpkgs channel is registered on the live alias: the image's channel table
    points at nixpkgs-unstable, because the nixpkgs-26.05 alias no longer resolves.
    The classic channel update (the nix-channel/nix-env unpack) cannot finish under
    proot — it is nix's own privileged unpack step, and a proot session cannot satisfy
    it — so the registry commands above are the supported install path, and the table's
    job is environment completeness, not update-ability.

  • Named the CA bundle, so HTTPS verifies: the store's openssl was built against a
    prefix the image prune removes, so its compiled-in certificate paths were dead and
    standalone curl and git over HTTPS failed verification (curl rc=60), measured.
    The session now exports CURL_CA_BUNDLE and SSL_CERT_FILE to the kept nss-cacert
    bundle; HTTPS works without anything else.

  • Custom distro installer: install a distro from a tarball, a URL, or a Docker/OCI image,
    instead of only the catalogue. Reached from the Welcome screen, the Distro dashboard, and
    Settings → More tools. Registry images are pulled through the registry-v2 flow (anonymous
    token, per-arch manifest selection) and the layers unpacked in order; the compression of a
    file or URL is read from its own magic bytes, never the extension.

  • Mosh reachability probe: when a mosh session produces no output, probe whether the host's
    UDP port is actually reachable, so a blocked-UDP path is told apart from "the server has no
    mosh" and a working tunnel is suggested.

  • Recording GIF export and playback speed: export a session recording to GIF, and step the
    player through 0.5×/1×/2×/4×.

  • Workspace pin and split-open: pin a workspace to the home screen, and open a two-session
    workspace straight into a split pane.

  • Scheduled job history and backoff: each job shows its recent runs (with an output tail in
    the notification), and consecutive failures back off the next retry before it gives up.

  • Workspaces: bundled shells, servers, theme and snippets that open in one tap (Settings → More tools → Workspaces).

  • Startup-hook GUI: edit the guest startup hook written into a distro (Settings → More tools → Startup hook).

  • Snippet library: save commands and paste them into any session (Settings → More tools → Snippets).

  • Distro dashboard: per-distro version, size, updates and disk (Settings → More tools → Distro dashboard).

  • SSH tunnel manager: open and close standalone ssh -N tunnels that keep a server's saved
    forwards open with no terminal in front of them. Reached from the SSH screen.

  • SFTP transfer queue: parallel, resumable SFTP transfers. Reached from the SFTP browser's menu.

  • Scheduled guest jobs: run guest commands on a schedule (Settings → More tools → Scheduled jobs).

  • Local port forward: open device ports that reach a target, any number at once and across
    any servers. A target is either the device itself (a guest service bound to 127.0.0.1 in a
    proot distro) or a saved SSH server, in which case the forward rides ssh -N -L and the
    remote host:port is reached through the connection. Reached from the SSH screen.

  • Recording index: recordings are listed newest-first and searchable on the Recordings screen.

  • Settings: eight feature rows consolidated into a single "More tools" hub.

Fixed

  • RedTerm:API bridge stop: the redterm-api listener stops cleanly when a session ends instead of lingering.

RedTerm v2.4.0

Choose a tag to compare

@github-actions github-actions released this 05 Nov 07:24
e1d26ed

Added

  • A Termux:API bridge of RedTerm's own. A command run inside a proot session can now
    reach an Android feature in the app, over the same wire protocol Termux:API speaks — an
    abstract Unix socket, the text of a fake am command line, and a uint16 length-prefixed
    answer on the same connection. The guest half is a small C helper built for all four
    architectures and extracted per-ABI in app storage, the same way the bundled ssh binary
    already is; the app half is a listener that starts with the process and one feature object
    per API. The command names and the grammar are Termux:API's on purpose, so a script
    written for termux-api runs in a RedTerm distro unchanged — but the shell, the helper and
    the features are all in this app, and nothing is handed to another package.

  • A persistent user startup hook, separate from the generated
    /root/.startup.
    RedTerm rewrites /root/.startup on every new
    proot session, so a hand edit there does not survive. An optional,
    user-managed /root/.startup.local now runs once, when a new
    interactive session opens, before the interactive shell starts: the
    launcher marks the interactive tail (REDTERM_INTERACTIVE_SESSION),
    the generated startup runs the hook as a separate process when that
    marker is set and the file exists, and skips it otherwise. A missing
    file is a silent no-op; a non-zero exit is reported (RedTerm: /root/.startup.local reported an error (exit N) — continuing the session) without ending the session; one-shot commands never run it;
    and the file is user-owned — RedTerm regenerates /root/.startup but
    never the hook, so it survives session restarts and app updates. This
    is the requested persistent initialization point for distro startup
    tasks such as Debian's dynamic MOTD (run-parts /etc/update-motd.d).
    The mechanism is distro-agnostic — the hook block is in the shared tail
    of the generated startup for all twenty distros, not Debian only. A new
    guest command redterm-startup-local (pure guest-side, no bridge)
    prints a safe starter body for the hook: its Debian-family MOTD line is
    double-guarded so it is a no-op on the other nineteen, so one printed
    body is correct everywhere. Pipe it to create the hook:
    redterm-startup-local > /root/.startup.local. Fixes #32.

Commands

Every command below is installed in the distro's /usr/local/bin under both a
redterm- and a termux- name (same body), so existing Termux:API scripts keep
running. Commands with structured output write JSON to stdout. Parser errors and
refused commands write plain text. A refusal may report a declared-but-missing
grant, or a permission this build does not declare at all. After the response
is received, the helper exits with status 0 — the exit status reports transport,
never the command's outcome, so the text is the answer. A missing grant on a
declared permission is fixed in Settings; an undeclared one cannot be enabled
there, and the refusal says so.

Bridge control

  • redterm-api <args…> — generic pass-through to the app's action handler (-a <action> --es/--ei/--ef/--esa …)
  • redterm-api-start / redterm-api-stop — bring the app-side listener up / down
  • redterm-download <url> [-d desc] [-t title] [-p path]
  • redterm-callback <url> [-d data] [-m METHOD] [-t secs]

Guest tools (installed under redterm- only — no termux- alias, no bridge round-trip)

  • redterm-startup-local — print a safe starter body for the user-managed
    /root/.startup.local session hook (#32). Create the hook with
    redterm-startup-local > /root/.startup.local.

Device state

  • redterm-battery-status — level, status, health, plugged, temp, voltage, current
  • redterm-audio-info — playback/recording device info
  • redterm-telephony-deviceinfo — device_id (IMEI/MEID) and sim_serial_number from the subscription (read reflectively; privileged identifiers answer only where the OS allows)
  • redterm-telephony-cellinfo — current + neighbouring cells
  • redterm-wifi-connectioninfo — active connection (IP, speed, BSSID, frequency; the SSID is masked without a location grant)
  • redterm-wifi-enable true|false
  • redterm-network-cidrs / redterm-network-interface
  • redterm-storage-get <path> — stat a path on the device
  • redterm-sensor (list) / redterm-sensor -s <name> [-n count] [-d ms] (read)
  • redterm-usb -l / -p <dev|vid pid> / -o <dev> [vid pid] / -f <dev> <file>
  • redterm-camera-info
  • redterm-keystore list|create|sign|verify|destroy [alias] [-a alg] [-s size] [-c curve] [-d data] [-g sig] [--detailed]

Controls

  • redterm-volume [-p|-d|-i|-m|-u] [-s stream] [-f value]
  • redterm-vibrate [-d ms] [-P pattern]
  • redterm-brightness [0..255]
  • redterm-notification [-t title] [-m msg] [-i id] [-r|--remove | -c|--clear]
  • redterm-notification-list / redterm-notification-remove [-i id]
  • redterm-notification-channel <id> [name] / -d <id> (create / delete)
  • redterm-toast "text"
  • redterm-clipboard-set "text" | -f file / redterm-clipboard-get
  • redterm-media-scan [-r] [-v] <path…>
  • redterm-dialog <confirm|checkbox|counter|date|radio|sheet|spinner|text|time> [-i hint] [-t title] [-v values] [-r range] [-d datefmt] [-m] [-p] [-n] — blocking, answers on stdout
  • redterm-job-scheduler [--script sh] [--period-ms N] [--network any|metered|unmetered] [--battery-not-low] [--storage-not-low] [--charging] [--persisted] [--cancel] [--cancel-all] [--job-id N]
  • redterm-contact-list [name]
  • redterm-share <text…> [-d mime] [-s subject] [-f files]
  • redterm-tts-speak [-e engine] [-l lang] [-n region] [-v variant] [-p pitch] [-r rate] [-s stream] [text | stdin] / redterm-tts-engines [-e engine]
  • redterm-media-player play [file] | info | pause | stop
  • redterm-microphone-record [-f file [-l secs] [-e encoder] [-b kbps] [-r rate] [-c channels]] [-i] [-q]
  • redterm-speech-to-text [-l lang] < audio

Storage access framework

  • redterm-saf-grant — opens the system tree picker and persists the read+write
    grant for it; prints the tree URI. Every other saf-* command is only as
    usable as the trees this has granted.
  • redterm-saf-create <tree-uri> <filename> / redterm-saf-dirs / redterm-saf-ls <tree-uri>
  • redterm-saf-read <document-uri> / redterm-saf-rm <document-uri> / redterm-saf-write <document-uri> < data

RedTerm v2.3.1

Choose a tag to compare

@github-actions github-actions released this 25 Oct 20:00
8cefccb

Fixed:

  • Fix proot TLS alignment for arm64 (p_align 8->64) and build proot v5.1.107.101
  • Update proot to v5.1.107.101 (commit 968ae1be) with link2symlink fix
  • Patch PT_TLS p_align 8->64 for arm64-v8a to satisfy bionic's TLS alignment requirement
  • Build with NDK r27c for arm64-v8a
  • This fixes the 'TLS segment underaligned' abort on Android 14+ devices

Updated:

  • Build proot v5.1.107.101 with link2symlink fix and TLS alignment fix for arm64
  • Update proot to v5.1.107.101 (commit 968ae1be) with link2symlink fix
  • Fix TLS alignment for arm64-v8a: patch PT_TLS p_align 8->64
  • armv7 binary built with linker script for TLS alignment (known issue: TLS alignment not fully fixed)
  • All 4 architectures built with proot v5.1.107.101
  • Proot binaries updated in jniLibs for all 4 architectures
  • Fix proot TLS alignment for the 32-bit ABIs and rebuild all four binaries

bionic's ARM32 static-TLS check (StaticTlsLayout in bionic_elf_tls.cpp)
gates on p_align AND the vaddr skew together: a plain NDK link emits
p_align 8 with a 16-aligned vaddr, which aborts on-device with
"executable's TLS segment is underaligned ... needs to be at least 32
for ARM Bionic". Patching the program header alone cannot fix the vaddr
half, because p_vaddr also feeds init_ptr, the address bionic copies the
TLS template from. Re-link armv7 and i686 with a linker script that
START-aligns .tdata at 32 (PT_TLS p_align 32, skew 0); the previous
scripts only end-aligned .tdata and their ld.bfd re-link was a no-op
(the NDK ships no ld.bfd). 64-bit keeps the p_align 64 program-header
patch, which now actually writes the file back. build-proot.sh: the
-T script is baked into the main link, the 32-bit branch verifies
instead of the dead re-link, the ABI case is fixed (i686's ABI is
"x86"), and the loader page-size injection is idempotent. All four
ABIs rebuilt from d4d2a19: arm64 p_align 64 / armv7 32 / i686 32 /
x86_64 64, every LOAD 16 KB aligned, entry at bionic's static _start.

  • Build proot from 3c6aa6f so the link2symlink/fake_id0 fixes reach the binaries

Fixed:

The rm -rf .git/objects/pack EPERM in a distro session is a link2symlink
issue, fixed in the commit series between d4d2a19 and 3c6aa6f (968ae1b
'link symbolic links as symbolic links', the fake_id0 statx/chmod record
series, 32-bit getdents parsing). The previous binaries were built from
d4d2a19, which predates all of it, so the TLS fix alone could not heal
it. Bump PROOT_VERSION to 3c6aa6f and rebuild all four ABIs:
arm64 p_align 64 (vaddr 64-aligned), armv7 p_align 32 (skew 0),
i686 p_align 32 (skew 0), x86_64 p_align 64 (no bionic gate there, so
the vaddr-64 hard guard now applies to arm64 only). 16 KB aligned
throughout.

RedTerm v2.3.0

Choose a tag to compare

@github-actions github-actions released this 22 Oct 06:52
4b70375

Added

  • mosh, as a per-server option. A saved server can be set to open over mosh instead of
    SSH. mosh keeps no connection at all once the shell is up — it runs over UDP — so a
    session survives switching between WiFi and mobile data, a lift, or a cell handover, all
    of which drop a long-lived TCP connection. The protocol is mosh's own, built from mosh
    1.4.0's libraries and shipped as a per-ABI native client for all four architectures, the
    same way the bundled ssh binary already ships.
  • The transport is visible. The session title and the notification show the transport
    that actually connected, not the one that was requested, so a server whose card says
    mosh next to a session saying · ssh has made the fallback visible without any extra
    state. See Fixed.
  • Switching transport from a running session. ⋮ → Connection → Reconnect using mosh
    or Reconnect using SSH, on SSH sessions. It opens a new session over the other protocol
    and closes the old one — the two are separate processes, so one cannot be converted into
    the other — and the server's saved preference moves with it.
  • A connecting indicator while an SSH or mosh session is brought up, covering the
    plain-SSH connect and the SFTP browser's first connection as well, each with a way
    out if the connection stalls.

Fixed

  • Recording a session actually records that session. Recordings used to mean
    "arm it now, and the next session you open gets captured" — which often
    happened to be a throwaway, produced a file whose name was guessed at start-up,
    and said nothing when no recording ever recovered the terminal output. Now the
    Record button captures the session it sits on: the emulator's visible screen is
    snapshotted on every drawn frame and re-encoded as plain ANSI (positioned rows
    and SGR state deltas, the same playback the Recordings player already speaks),
    so exactly what the session drew is what replays. Files are written under the
    app's recordings directory in one place, named at start from the session's own
    identity (distro or server), flushed per frame, and cleaned up when a recording
    ends empty — ending with its session, by hand, or when the activity dies. Both
    ends log through AppLog: started, stopped (with frame and byte counts), and why
    a storage failure or a frame write stopped it.
  • Playing a recording no longer crashes the app. The replay view attached its
    session and never gave it a font, so the first layout ran straight into
    TerminalView's null renderer — the same crash the mosh bootstrap hit, from the
    same missing order. The player now sets the size and typeface before the
    attach, and applies the theme's palette after it, so a recording replays in
    the same colours it was made with. Font and palette helpers moved to a shared
    TerminalTheming so every surface showing a terminal uses the same ones. The
    view's client pointer is the next unguarded slot in the same row of machinery
    (updateSize calls its onEmulatorSet with no guard), so the player answers
    that too — and pinch zooms the replay the way the session terminal does.
  • And replay no longer runs a shell at all. Feeding the file through a pty
    made playback depend on whichever stty vocabulary the device ships: on this
    one the child exits stty: -icanon: unknown option, code 1, before a single
    frame is fed in — the replay was a blank page that finished before it started.
    The pty existed only because TerminalView needs a session; the emulator does
    not. Playback now feeds chunks of the file into a private TerminalEmulator
    on a background thread and draws it with the library's own renderer — no
    process, no stty, nothing device-dependent in the middle.
  • "Press Enter to close this session and open one over SSH" now works. The
    failed mosh session's report is printed by a process that then exits, so nobody
    was listening for the Enter it asked for: dismissing the failure dialog left a
    dead terminal eating keys. The dialog's dismissal now arms the promise — and an
    Enter aimed at that dead session is intercepted at the terminal client, where
    the library offers both key events and input-method-committed text before it
    types anything — closed, and the same server opens over SSH, without changing
    the mosh preference the user chose to keep.
  • The build is back at zero warnings. Six compiler warnings from Android 16/17's
    deprecation wave are fixed at the source rather than suppressed: the deprecated
    TRIM_MEMORY_RUNNING_LOW threshold (any trim signal now drops a cache that is a
    map clear to rebuild), the deprecated announceForAccessibility (the connecting
    overlay's message is now an accessibility live region whose text changes on screen,
    the sanctioned replacement), the deprecated SHOW_IMPLICIT flag (deprecated and
    without effect since Android 16; the flag is simply omitted), the Int versionCode
    field (PackageInfoCompat.getLongVersionCode), and two conditions that compared
    things they could never satisfy — a File tested for null and a non-null list's
    element tested for null.
  • exit at the remote shell now ends a mosh session. mosh-server says goodbye
    on its own protocol — encrypted packets that arrive wherever the session's
    packets do, ICMP-filtering NAT and all — and the client never acted on it: by
    the time the shell exits every state is acknowledged, so nothing more is sent,
    the network falls silent in both directions, an error-based detector never
    hears an error, and the session sat at logout for ever. Measured before the
    fix, against a real mosh-server: killed after 50 s, still running. After it:
    a clean goodbye, exit 0, no failure text, in a few seconds.
  • A mosh session that never reached the server is covered until it says so. The
    connecting overlay used to end the moment the bootstrap handed back a listening
    server, on the theory that the client draws its own connecting status — which it
    no longer does. A blocked UDP path then read as a blank terminal for the full
    twenty-second wait. The overlay now ends on the session's first drawn output, the
    failure report or the 30-second cap, exactly as a plain ssh connect is handled.
  • Closing a mosh session that never connected can no longer leave the screen
    behind it stale.
    The no-reply dialog's early return skipped the session
    bookkeeping the ordinary close runs — the split teardown, the re-attach to the
    surviving session, the title, the drawer and the home-screen widget — so drawer
    rows could point at sessions that no longer existed. Only the activity's own
    close is skipped while the dialog is up; everything else runs.
  • The no-reply dialog no longer claims a session was opened. Cancel opens
    nothing, and the buttons open one on choice; the message now says the server can
    be opened over SSH instead.
  • The credential loop stops on a failure no credential can fix. An attempt
    that is not a refusal — the host unreachable, or it accepted a key and then had
    no mosh-server to run — used to send the remaining keys and the password stage
    at the same question, each a fresh connection and possibly a prompt on a server
    that had already shown its hand. The first such attempt now ends the loop and
    carries its own reason out, instead of the last credential refusal masking it.
  • The native mosh client's error text can no longer be read while it is being
    rewritten.
    mosh_session_last_error returned a pointer into a string the
    worker keeps reassigning, which a caller formatting the previous failure while
    the next recv() threw could read mid-mutation — the remote-exit path does
    exactly that. The text is now copied out under the lock. The client's
    connected flag is atomic (the caller's thread reads it while the worker
    writes) and its consecutive-error counter is initialised rather than left
    indeterminate.
  • A font collection is no longer accepted and then hidden. .ttc/.otc
    passed the import filter but neither the settings list nor the terminal's font
    loader honours them, so an imported collection appeared in no list and could not
    be removed. They are refused at the picker, where the refusal is readable.
  • Cancelling one connect attempt can no longer spoil another. The attempts
    shared one abandoned-flag, so a stalled attempt the user cancelled went on to
    attach when a newer attempt had already begun — and could discard the session
    they had just asked for. Results are now tracked per attempt: Cancel invalidates
    only the attempt it was shown for, and a worker attaches only when its token is
    still the newest.
  • The browser's SFTP connection check can no longer freeze the UI. Asking
    whether a connection is up took the same lock a running transfer holds for its
    whole duration, so a tap that started a load waited behind it. The check now
    takes no lock.
  • A passphrase key further down the list gets its prompt. An open key's
    refusal — where no dialog can help — was spending the connection's one
    opportunity to ask, so a server that accepted the second key, an encrypted
    one, rejected the connection without ever asking for its phrase. Only a
    question actually asked now counts as asked.
  • Cancelling during the attach-wait is not a session failure. It ended the
    session the overlay was attached to, which arrived as a kill and was then
    reported to the user as "session ended" with status -9 — a dialog for the
    cancel they had just chosen.
  • The connection test's result can actually be copied now. Long-press selection
    was broken by a movement-method conflict and is fixed; a Copy button has been
    added to the card as well, which puts the whole result on the clipboard in one
    tap without depending on selection working at all.
  • A successful connection test no longer prints a wall of debug trace. The
    -v output that diagnoses a failure is n...
Read more

RedTerm v2.2.0

Choose a tag to compare

@github-actions github-actions released this 16 Oct 16:12

Highlights

  • A freshly installed distro now keeps the permissions the distribution chose. Installing
    used to flatten every directory to 0755, so /tmp stopped being world-writable with its
    sticky bit, /root was loosened, and every pacman transaction on Arch and ARMtix reported
    the difference:
    warning: directory permissions differ on /tmp/ filesystem: 755 package: 1777.
  • openSUSE is no longer reconfigured on every launch. The repository aliases, the libzypp
    service and RepoManager.db are all left exactly as the image ships them, because they were
    never the fault.
  • Four distributions were silently running with none of the setup applied. Oracle, Fedora,
    AlmaLinux and Rocky ship a /root this app could not write into, so the prompt and the whole
    first-time setup had never landed on them. See Fixed.
  • Twelve more distributions, bringing the catalogue to twenty, all built from upstream by
    this project and checksum-verified before installation.
  • SFTP is documented as what it is — a home-screen tool that browses a saved server
    without a distribution installed.

Fixed

  • Installing a distro discarded the file modes in the image. The install path chmod'd
    every directory to 0755 as it created it and reduced every file to "executable or not" —
    it read the mode out of the archive and then threw it away. Restore has always preserved
    modes correctly; install had its own extractor and it was the one that was wrong. The
    published images were correct throughout, so no change to how they are built could ever have
    fixed it.
  • A setgid directory lost its bit. The mask now keeps setuid, setgid and sticky instead of
    discarding them, and directory modes are applied after their contents rather than on
    arrival — a directory the archive records as 0555 cannot have children created inside it
    if its mode is set first.
  • The post-install permission repair is gone. It existed only to undo the bug above, and
    could only ever agree with the flattening because it had no other mode to work from.
  • Arch and ARMtix images applied DisableSandbox twice, which pacman reports as a
    duplicate directive on every command.
  • openSUSE's startup script was rewriting working configuration. Alias rewriting, file
    renaming, service removal and RepoManager.db deletion were each applied across several
    releases, fixed nothing, and cost the user repositories they could install from. Verified by
    running zypper refresh natively against both this project's published image and
    proot-distro's, whose repository files are byte-identical: both succeed with the stock
    configuration and build the very cache path that had been reported as impossible.
  • Four distributions never received any of it. Oracle, Fedora, AlmaLinux and Rocky ship
    /root as 0550 — no owner-write bit at all — and on Android the extracted tree belongs to
    the app's own uid, so those owner bits are the ones that apply. Every write into /root
    failed with EACCES: the prompt, .bash_profile and .startup, and with .startup goes
    the entire first-time setup. The session-writing path swallowed this into a log line that
    Diagnostics does not show, so those four came up silently unconfigured; applying a shell
    template crashed instead. The write bit is now borrowed for the one file being written and
    the mode restored afterwards, so /root is left as the distribution intended.
  • Reinstalling a distribution failed with EACCES. cadir is recorded read-only, so the
    first install left a tree the second could not clear: unlinking a child needs write access
    to its parent. The result of deleting the old rootfs was ignored, so extraction continued
    into the old tree and wrote into files it could not open —
    .../cadir/ACCVRAIZ1.pem: open failed: EACCES. Which is why the first install worked,
    reinstalling did not, and the obvious response to the error was the thing causing it.
  • Hard links in an image were extracted as empty files. The installer had no branch for
    type 1 entries at all, so anything a distribution hard-links came back zero-length. They
    are now materialised as independent copies, which is also what proot wants, since it
    emulates link() and a real hard link would alias inodes the guest treats as separate.
    Restoring now keeps the linked file's mode and resolves both ways a link target is written
    — a bare sibling name, and a path from the archive root.
  • Arch asked for database signatures that no mirror serves. The images shipped
    SigLevel = Required DatabaseOptional, so pacman requested <repo>.db.sig; the databases
    download fine and the signature beside them does not exist. With curl -f as the transfer
    command that is a hard error, and every pacman command on every repository printed
    curl: (22) The requested URL returned error: 404. Package signatures remain required.
  • A step warned about a gcc-libs conflict that did not exist. It ran on every first
    launch of Arch and Manjaro and could only ever fail there. Arch has already split the
    runtime into libgcc/libstdc++, and Manjaro never split it at all, so there is nothing
    to repair on either. Five tests asserted the step's presence, one of them as a requirement
    that it exist; it is gone, and an assertion of absence replaces them.

Changed

  • First launch no longer upgrades anything. No image runs a package upgrade on your
    behalf; updates are started by you, from Package Updates or from the terminal.
  • openSUSE's cache is made writable, and nothing else. A session runs as the app's own uid
    while the image builds that cache as root, so a cache it cannot write is one it cannot
    build. That is now baked into the image as well, so a new image works on its own rather than
    waiting for a particular build of the app to repair it.
  • Images come from this project's own builds, published by
    GlobalTechInfo/rootfs-images, rather than
    from Termux's proot-distro. Every image carries a recorded upstream version and the recipe
    that produced it.
  • A wrong comment about find -perm -400 in the image builder, which described the
    predicate as testing read permission when it tests the owner's execute bit.

Added

  • Twelve distributions: Adelie, ARMtix, Chimera, Gentoo, Oracle, Pardus, Parrot, Rocky,
    Slackware, Trisquel, and additional architectures for the existing ones.
  • docs/proot-distro-reference.md, recording what proot-distro's own install and recipes
    actually do, with the measurements behind each claim and how to reproduce them.

Notes for existing installs

  • The permission fix applies at extraction. A distro installed with an earlier build already
    has /tmp at 0755 on disk and will keep it — delete and reinstall the distro to pick
    this up. Reinstalling the app alone changes nothing.

RedTerm v2.1.0

Choose a tag to compare

@github-actions github-actions released this 08 Oct 18:58
7fd26d6

Highlights

  • SFTP file browser. Browse, download and upload files on a saved SSH server without
    typing a single command. Runs over the bundled OpenSSH client, so it needs nothing
    installed.
  • Backup and restore now work on every distro. Previously any distribution containing
    hard links — Arch and Manjaro in particular — could not be restored at all, and a backup
    could quietly leave out files it was not permitted to read, such as /etc/shadow.
  • Themes now apply to the terminal, not just the app around it. Switching theme
    re-themes a running session immediately, and the Light theme is legible.
  • Distro logos on the install, home, settings and backup screens.

Added

  • SFTP browser (SSH → Browse files): the same file manager used inside a distro,
    pointed at a remote server. Navigate, upload, download, rename, delete, create folders
    and search, plus the remote-only extras — change permissions, create symlinks, and see
    free space. Progress is reported in bytes as transfers run.
  • SSH keys are now a proper keyring: several named keys, generated as ed25519, ECDSA or
    RSA-4096, optionally passphrase-protected, importable from an existing private key, and
    bindable to a server so it is offered automatically. A passphrase is asked once per key
    and remembered for the session, so you are not prompted again for every listing.
  • Server options per saved host: keepalive interval and count, compression, agent
    forwarding, a jump host, and local or remote port forwards.
  • Trusted hosts screen, listing the fingerprints the app has accepted and able to
    forget one.
  • Import an OpenSSH config, including its Host blocks, and import an existing
    private key
    rather than only generating new ones.
  • Password authentication for servers without a key, stored in the Android keystore.
  • Sessions survive the app being closed and are restored on the next launch.
  • Long-running sessions option, keeping the terminal and the device awake while a
    session is open.
  • Record the next session from the terminal quick panel, so a recording no longer needs
    a command typed out by hand.
  • Progress bars for backup and restore, which take minutes on a real distribution and
    were previously indistinguishable from a hang.
  • Copyable failure output. A backup or restore failure can be selected and copied out
    of the dialog, and every restore outcome is recorded in Diagnostics.
  • Backup and restore now report anything they could not include instead of quietly
    leaving it out.

Fixed

  • Backup failed on any distro containing hard links. Arch and Manjaro could be backed
    up but never restored; Void appeared to work only because it happened to have none in the
    affected place.
  • Backup could omit files it could not read. A distribution image ships files only root
    may read, and RedTerm does not run as root, so a backup could be missing /etc/shadow
    while reporting success — and restoring it gave a distro where login cannot work.
  • A truncated or damaged archive is now refused instead of being restored into a
    half-populated installation.
  • bash: fg: no job control on login, on distros that do not ship their own bash
    configuration.
  • The shell prompt was invisible on every theme except the default, and after changing
    theme while a session was running.
  • The Light theme's terminal was unreadable, appearing blank because the text stayed
    dark-on-dark.
  • Buttons wrapped one word per line on narrow screens, turning short labels into tall
    ovals.
  • Recording no longer needs a command typed by hand, and the list gained a Diagnostics
    action.
  • The notification permission is now requested once during first-run setup, where the
    reason can be explained.
  • Distro names are now shown correctly everywhere: almalinux was rendered "Almalinux" and
    opensuse "Opensuse".

RedTerm v2.0.0

Choose a tag to compare

@github-actions github-actions released this 28 Sep 22:56

Highlights

  • Bundled OpenSSH for all four architectures. Connect to any host without
    installing a package first.
  • Backup and restore now round-trip a distribution cleanly, storing only the
    distribution's own files.
  • Soft keyboard behaves as expected: tap inside the terminal to open it, press
    back to close it.
  • Package management works on Arch and openSUSE from a fresh install.
  • Landscape layout on the welcome screen is usable again.
  • Rotating the phone no longer cancels an install or disturbs the terminal.

Fixed

  • Install progress is no longer cancelled by a configuration change.
  • The back button closes the keyboard instead of leaving the terminal unusable.

Added

  • SSH → Test runs a non-interactive connection check (BatchMode, 10 second connect timeout,
    remote command true) and shows the verbose trace, so a failed connection names its cause
    instead of dying silently.

  • Kali Linux: added as a supported distro, installed from NetHunter's own rootfs on kali.download (it is not published by Termux proot-distro). Available on all four architectures.

  • Free-space check before install: the installer now measures available storage against the space a distro needs and refuses up front with a clear message instead of failing part-way through extraction.

  • Distro diagnostics: a Diagnose action on every installed distro reports on 12 health checks (rootfs layout, root uid, DNS, bash, busybox, /bin/sh, /usr permissions, /tmp, device nodes, sudo, /root, size) and can be copied to the clipboard.

  • File manager actions: every row has a visible ⋮ button for Rename, Copy, Cut, Delete, plus Edit for text files, Open in terminal and Folder info for folders. New folder, paste and refresh actions, a hidden-files toggle, Go to /root and a folder size summary.

  • Recursive file search: search now walks the entire subtree below the current folder and updates as you type, instead of only matching names in the folder you were looking at. Results are capped and it says so when truncated.

  • File manager navigation: the back arrow and the system back gesture both go up one directory instead of leaving the app, and the arrow keeps the same appearance used everywhere else in the app.

  • Image and video preview: images open with automatic downscaling and EXIF rotation so photos are not sideways; videos play in place.

  • Text editor: text files can be edited in the app and saved back into the rootfs. Saving stages a temporary file and renames it over the original, so an interrupted write cannot truncate a config, and the original permission bits are re-applied first so scripts keep their executable bit.

  • Per-distro and multiple sessions: launching a distro that has no session open now creates one instead of re-showing whatever session happened to be open, and New Session offers every installed distro — picking the current one starts a second, independent session.

  • Package updates: run a distro's own package manager update from the app, with the real output streamed live, and a notification when it finishes.

  • Base image update: check whether Termux publishes a newer proot-distro image for an installed distro and swap it in, keeping /root and /home. If anything fails, the previous install is put back.

  • Storage usage: free and total space on shared storage, plus per-distro the largest directories with proportional bars.

  • SSH: save servers and connect straight from the app. A full OpenSSH client is bundled with the app, cross-compiled for all four ABIs, so a connection needs no distribution installed and does not depend on a distro shipping openssh-client. It is unpacked into a small rootfs of its own and run through proot, because Android 12+ mounts app storage noexec — the same constraint the distro binaries already work around — so the client is subject to exactly the same rule. Host key checking is on, and an ed25519 key pair can be generated from the SSH screen.

  • ANSI recordings: record the output of a command with colours and cursor control intact, then replay it in the app. Recordings can be shared or deleted.

  • Backup manager: a dedicated screen lists backup archives with size and date, and offers restore, share or delete for each, plus cleanup of files left behind by interrupted backups.

  • App log: Settings → App log keeps a persistent, bounded log of the app. It can be copied to the clipboard, shared, or downloaded to Downloads/, and Capture system log adds everything the process wrote to logcat, including output from the support libraries, so a failure that ends a process immediately can actually be diagnosed.

  • Completion notifications: background work (package updates, base image updates, backups, recordings) posts a notification when it finishes.

  • Termux proot-distro rootfs: all distros now install from the official prebuilt rootfs images published by termux/proot-distro, extracted and verified in-app.

  • Per-architecture SHA-256 verification: every distro/arch pair ships a hardcoded checksum; downloads are verified before extraction and a mismatch discards the partial file and asks for a clean retry.

  • Resumable distro downloads: interrupted downloads resume over HTTP Range instead of restarting from zero; a corrupt or server-rejected range falls back to a full re-download automatically.

  • Crash reports: uncaught exceptions are recorded centrally under Settings → Crash Reports, following Termux's rollover scheme (crash-report.txt, then crash-report2.txt, … at 4096 characters each). Reports can be viewed and copied in-app, downloaded to Downloads/RedTerm-crash-report-<timestamp>.txt, or deleted.

  • File viewer: tapping a file in the built-in file manager now opens it in a new viewer with monospace text, horizontal scrolling, binary detection, a 2 MB preview cap and a Copy action. Previously files could be listed but never opened.

  • Home button on the welcome screen: a Home icon now sits opposite Settings, so Home is reachable before any distro is installed.

  • openSUSE: added as a supported distro.

  • Settings section icons: seven new vector drawables (ic_section_distro, ic_section_appearance, ic_section_font, ic_section_terminal, ic_section_power, ic_section_extra_keys, ic_section_app_lock) shown next to each settings section header.

  • Hardcoded strings extracted: all hardcoded text in XML layouts moved to strings.xml (~90 string resources), enabling full localization.

  • RTL symmetry: settings layout uses symmetric horizontal padding for proper right-to-left support.

  • Plurals support: match_count_for_query converted from <string> to <plurals> with proper getQuantityString() in code.

  • KILL_BACKGROUND_PROCESSES permission: added to manifest.

  • ToolbarTitle theme: new TextAppearance style for toolbar titles (single-line, ellipsize end).

Changed

  • Rootfs source: distro downloads point at termux/proot-distro release assets instead of self-hosted tarballs.
  • Distro lineup: openSUSE added. Artix is no longer offered; Kali returns as a NetHunter rootfs (see Added).
  • First-time distro setup: the setup script now installs bash and sudo with each distro's own package manager, unsets ENV and falls back to the distro's own /bin/sh when bash is unavailable. Alpine previously had no bash, leaving users in Android's mksh where bash was "inaccessible or not found". The script is version-stamped and regenerated on existing installs, and failures no longer abort the whole setup.
  • Per-distro setup correctness: Arch runs a full pacman -Syyu upgrade (a partial pacman -Sy against a prebuilt rootfs left packages requiring a newer GLIBC than the image shipped); openSUSE clears and recreates /var/cache/zypp and disables the x86-only repo-openh264 repository that broke solv cache builds; Fedora/Rocky/AlmaLinux pass skip_if_unavailable, lower retries and shorter timeouts so a stale mirror 404 cannot fail the whole run.
  • Shell configs preserved: .bashrc and .bash_profile are only written when missing, so user customizations are never overwritten.
  • SHA256 checksums: populated for every supported distro/architecture rather than omitted.
  • Notification permission flow: the foreground service is no longer gated on POST_NOTIFICATIONS being granted at the moment the activity is created, which meant it was never started and no ongoing notification ever appeared. The service now starts from onResume regardless, and the Android 14+ PROPERTY_SPECIAL_USE_FGS_SUBTYPE is declared.
  • Rootfs permissions: extracted directories are 0755 and files 0644/0755 (applied with Os.chmod), with umask 022 in the proot launcher. Previously every directory was forced to 0700, which produced directory permissions differ on /usr warnings and blocked some package managers.
  • Distro size display: computed on a background thread and cached with a 10-minute TTL instead of walking the entire rootfs on the main thread.
  • Terminal toolbar title: shows only the distro/session name instead of appending the full working-directory path.
  • Version bump: versionName 1.0.4 → 2.0.0, targetSdk 35 → 37.
  • Resource shrinking: isShrinkResources = true enabled in release build.
  • Toolchain: Gradle 9.7.1 → 9.8.0.
  • Dependencies: core-ktx 1.18.0 → 1.19.1, appcompat 1.7.0 → 1.8.0.
  • proot rebuilt from source: cross-compiled at the current termux/proot commit for all four ABIs (arm64-v8a, armeabi-v7a, x86_64, x86) and linked with 16 KB page alignment, so RedTerm's own native libraries are loadable on 16 KB-page devices. native/build-proot.sh was fixed to install the libproot*.so names the app actually loads, build talloc per-ABI, and ...
Read more

RedTerm v2.0.0-beta

RedTerm v2.0.0-beta Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 25 Sep 11:02

Release notes for v2.0.0-beta.

See the CHANGELOG for details.

RedTerm v2.0.0-alpha

RedTerm v2.0.0-alpha Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 22 Sep 13:52

Release notes for v2.0.0-alpha.

See the CHANGELOG for details.