> For the complete documentation index, see [llms.txt](https://docs.udroid.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.udroid.org/udroid-landing/quick-installation-and-usage.md).

# Installation & Usage

### Before installing:-

* Get termux from [termux.com](https://termux.com) or [F-Droid.](https://f-droid.org/en/packages/com.termux/)
* [Vnc Viewer](https://play.google.com/store/apps/details?id=com.iiordanov.freebVNC), [Xserver XSDL](https://play.google.com/store/apps/details?id=x.org.server), or [Termux: X11](https://github.com/termux/termux-x11) for Display

### Quick Install

{% hint style="info" %}
Install all dependencies and developer-selected Distro
{% endhint %}

```bash
. <(curl -Ls https://bit.ly/udroid-installer)
```

#### From sources (manual install)

```bash
apt update && apt install git -y
git clone https://github.com/RandomCoderOrg/fs-manager-udroid
cd fs-manager-udroid
bash install.sh
```

then use `udroid --list` to get a table of available distros and the names of their suites ( something like **jammy:xfce4** ) then use `udroid install jammy:xfce4` (or the suite you like) to install.

Here are some examples that show both install and login commands of popular distros

{% tabs %}
{% tab title="XFCE4" %}

```bash
udroid install jammy:xfce4
udroid login jammy:xfce4
```

{% endtab %}

{% tab title="GNOME" %}

```bash
udroid install jammy:gnome
udroid login jammy:gnome
```

{% endtab %}
{% endtabs %}

### Removing a Distro

udroid cli tool has an argument `remove` that takes care of wiping the suite installation from the device, and `--clear-cache` option to remove any download (if present) for max release of device storage

{% code title="Example:" fullWidth="false" %}

```bash
udroid remove jammy:xfce4
udroid --clear-cache
```

{% endcode %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.udroid.org/udroid-landing/quick-installation-and-usage.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.