Build Android apps where you are.

01What is ADT?

Google's Linux SDK host binaries are x86_64. ADT builds the native host tools from official AOSP source for aarch64/glibc, keeps offline-installable verified artifacts, and validates the whole pipeline on a real physical device.

02Features

Tools that only need a JVM execution path are architecture-independent at the Java level; everything else is a native aarch64 binary, built from source, or shimmed — and documented as such.

03Toolchain

Every component is classified by how it actually runs — a tool is not marked supported simply because it exists upstream.

Per-version AOSP tags, CI runs and notes are tracked in versions.json. Everyday commands for every tool live in COMMANDS.md.

04Installation

Works on any aarch64 Linux with glibc — the validated target is Termux + PRoot Debian on an ARM64 phone; Asahi, Raspberry Pi and ARM64 servers follow the same path. Idempotent: re-running updates an existing clone and skips what is already installed.

# এক লাইনে — সংগ্রহশালা এনে সম্পূর্ণ প্রাথমিক সেটআপ চালায়
curl -fsSL https://raw.githubusercontent.com/soobujmiah/adt/main/install.sh | bash
source ~/.bashrc

# কপি থেকে — ধাপে ধাপে নির্দেশসহ অথবা সম্পূর্ণ স্বয়ংক্রিয়
git clone --depth 1 https://github.com/soobujmiah/adt.git && cd adt
./setup.sh                    # নির্দেশসহ

./setup.sh bootstrap --auto   # কোনো প্রশ্ন ছাড়াই

# পরে যাচাই — সমস্যা হলে কোন অংশে তা শনাক্ত করে
./setup.sh doctor

05Workflows

The everyday developer paths. Exact commands — including wireless adb pairing, which trips most people — are in COMMANDS.md.

What I have used ADT for on this phone

These are recorded outcomes from my Redmi Turbo 4 Pro workstation, not promises for every ARM64 device.

See the device record and commands →

06Evidence — real results

The strongest test is the full path, not the presence of binaries. On 2026-09-01 this chain ran end-to-end on a real physical device:

native source → ARM64 shared library → APK packaging → signing →
ADB installation → ARM64 ABI selection → JNI loading → native execution →
log output → process remains alive

# final build      BUILD SUCCESSFUL in 1m 21s   (60 actionable tasks)
# install         adb install -r app-debug.apk → Success
# abi             Device ABI: arm64-v8a · APK primaryCpuAbi: arm64-v8a
# runtime         PID observed · crash/ANR scan clean · app alive

Shared evidence vocabulary — Verified · Measured · Observed · Experimental · Not yet tested · Not supported:

Verified Measured Observed Experimental Not yet tested Not supported

Honesty boundary: the full chain is physically validated on one device family (Redmi Turbo 4 Pro, PRoot Debian). On any other host the scripts are identical, but "should work" is not "verified" — run ./setup.sh doctor as your first evidence check.

07ADT and Ternux — two layers of one ARM64 story

Use both on the same phone

Install Ternux for the Debian desktop, then install ADT inside that same Debian userland. From Termux, enter with db; from Xfce, open a terminal in the Debian session.

# টারনাক্সের ডেবিয়ান পরিবেশের ভেতরে
curl -fsSL https://raw.githubusercontent.com/soobujmiah/adt/main/install.sh | bash
source ~/.bashrc
cd ~/adt && ./setup.sh doctor

ADT's build and physical-device workflow is verified on this shared Termux + PRoot host. Running the tools specifically from a Ternux Xfce session has been observed, but is not yet a formally tested combined workflow.

08Documentation

Simple first in the README; technical depth lives in the repository, linked here directly so what you read matches what the toolchain actually does.