I wanted to know which will give higher performance

• Chroot Ubuntu (xubuntu-desktop)with termux-x11 or
• native termux xfce4 with termux-x11

Hello,

Since upgrde to rsync 3.4.3 the package is not working. I tested between two folders on the same device, i have same bug :

Any idea ?

Does anyone know got to use these arrow keys over there? Okay up and down works but why is there a left and right key?

I literally uninstalled and then install again why is it still error

Hello, made a app to assist in estimating materials for foundations. 100% offline and completely free. Find it here.

Project is here: https://github.com/sam1am/termux_crt

Requires the Termux debug apk from github to be installed.

It is fully customizable and you can save/export/import your presets. Settings include:

• Bloom
• Burn-in
• Curvature
• Scanline RGB shift
• Ambient Phosphor
• Flicker
• Horizontal Sync Wobble
• Static
• Background and Foreground color overrides

I'd love to see what others come up with as far as presets and would love to include them in the app. Please share!

I still can’t believe I actually got this working.

I built and modded Termux:X11 entirely on my Android phone using Termux. No PC. Just Termux, Android build tools, a lot of trial and error, and help from ChatGPT when I got stuck.

The mod I added is a custom FPS limit option under the Output settings.

0 = auto / default refresh rate

1–600 = custom FPS value

The crazy part is that it actually works.

If I set it to something super low like 3 FPS, the whole X11 desktop becomes painfully choppy. If I set it to 30, it feels capped. If I set it to 60, it feels normal. If I set it to 90, XFCE/terminal reports 90Hz inside the session and it feels smoother, even though my phone display is still physically 60Hz.

Just to be clear: this is not overclocking the phone screen. My panel is still 60Hz. This is more like changing the internal framerate/pacing value that Termux:X11 reports and uses inside the X11 session.

The technical part:

Termux:X11 already had a Java path where it detects the Android display refresh rate and sends it to native code through:

sendWindowChange(width, height, framerate, name)

Originally, that framerate value came from Android’s detected display refresh rate.

I added an FPS limit preference in the Output settings, saved the value in SharedPreferences, parsed it safely, clamped it between 0 and 600, then used it to override the framerate before calling sendWindowChange.

So the logic is basically:

- 0 = use Android’s detected refresh rate

- 1–600 = force that value as the X11 framerate

- pass it into the existing native framerate path

The native side already uses that value for root_framerate / blank_interval, so it is not just a fake UI option. That’s why setting it to 3 FPS actually makes the desktop lag hard.

The build process was honestly painful. I had to deal with Java 17, Termux-native aapt2, AIDL problems, CMake/NDK issues on Android, APK signing, native lib mismatch, libXlorie.so replacement, and Android complaining about compressed native libraries.

Eventually I got it working by building the patched Java/resource side in Termux, making sure the correct official libXlorie.so was inside the APK as a stored native library, then signing the final APK.

This is definitely experimental and not upstream-ready, but I’m honestly proud of it. I don’t have a formal IT/programming background, so seeing this actually work inside XFCE on Termux:X11 feels insane.

Only having some issues installing software like vs code everything else works great. I’m using the droiddesk script by a user on GitHub.

running a Minecraft server with a proxy in termux!

I’ve published a Termux wrapper package for Codex:

u/bash0816/codex-termux

Install:

npm install -g u/bash0816/codex-termux@latest

Basic checks:

codex --version

codex login status

Notes:

- This is for Termux on Android arm64

- Do not install upstream u/openai/codex directly on Termux

- Use this package for install/update on Termux instead

Update:

npm install -g u/bash0816/codex-termux@latest

Rollback:

npm install -g u/bash0816/codex-termux@0.130.0

Repo:

https://github.com/bash0816/Codex-Termux

If you try it on another device, I’d like to know:

- Android version

- Termux version

- whether login works

- whether codex exec works

I compiled a Linux kernel using Termux with gcc on proot-distro

🚀 llama.cpp + Vulkan GPU Acceleration on Termux (Pixel 9 Pro XL / Mali-G715)

After lots of trial and error, I finally got llama.cpp running with real GPU acceleration on my Pixel 9 Pro XL. Here's the minimal working setup.

> TL;DR: Modern Termux + llama.cpp b9190 + -ngl 99 = automatic Mali GPU acceleration. No manual driver extraction needed (for now).

---

✅ Prerequisites

• Pixel 9 Pro XL (or any Android 14+/Mali-G715 device)
• Termux installed from F-Droid or GitHub
• Root access (optional, but helpful for GPU frequency tuning)
• ~4 GB free storage for model

---

🟢 Step 1: Install Dependencies

pkg update && pkg upgrade -y
pkg install git cmake clang make vulkan-loader vulkan-tools vulkan-headers glslang -y

---

🟢 Step 2: Build llama.cpp with Vulkan

git clone https://github.com/ggml-org/llama.cpp
cd llama.cpp

# Clean build with Vulkan enabled
rm -rf build
cmake -B build -DGGML_VULKAN=ON -DCMAKE_BUILD_TYPE=Release
cmake --build build -j4

✅ Verify Vulkan was compiled:

grep "GGML_VULKAN:BOOL" build/CMakeCache.txt
# Should output: GGML_VULKAN:BOOL=ON

ls -lh build/bin/libggml-vulkan.so
# Should show the .so file exists

---

🟢 Step 3: Download a Model

mkdir -p ~/models
cd ~/models

# Example: Gemma 2 2B (Q5 quantized, ~2GB)
wget https://huggingface.co/google/gemma-2-2b-it-GGUF/resolve/main/gemma-2-2b-it-Q5_K_M.gguf

> 💡 Tip: Use hf-mirror.com if Hugging Face is slow in your region.

---

🟢 Step 4: Run with GPU Acceleration

cd ~/llama.cpp

./build/bin/llama-cli \
  -m ~/models/gemma-2-2b-it-Q5_K_M.gguf \
  -p "Hello, introduce yourself in Chinese" \
  -n 100 \
  -ngl 99 \
  --jinja \
  --color auto

🔑 Key Parameters:

Flag	Meaning
-ngl 99	Offload all layers to GPU (Vulkan)
--jinja	Enable Jinja2 template engine (fixes chat format warnings)
--color auto	Color-coded output
--verbosity 0	Minimal logs (optional)

---

🔍 Verify GPU is Actually Working

Method 1: Check startup logs (verbose mode)

./build/bin/llama-cli -m ~/models/your-model.gguf -p "test" -n 10 -ngl 99 --verbosity 3 2>&1 | grep -i "vulkan\|mali\|device"

✅ Look for:using device Vulkan0 (Mali-G715) offloaded XX/XX layers to GPU

Method 2: Speed comparison (most reliable)

# GPU mode
./build/bin/llama-cli -m model.gguf -p "test" -n 50 -ngl 99 --verbosity 0

# CPU-only mode (for comparison)
./build/bin/llama-cli -m model.gguf -p "test" -n 50 -ngl 0 -t 8 --verbosity 0

📊 Expected results on Pixel 9 Pro XL:

Mode	Speed
CPU-only (-ngl 0 -t 8)	~1-2 t/s
Vulkan GPU (-ngl 99)	~7-8 t/s ✅

> If GPU mode is 5-6x faster, Vulkan is working!

---

⚡ Optional: Boost GPU Frequency (Root Required)

Mali GPUs often run at conservative frequencies by default. Unlock performance:

# Check current GPU frequency
cat /sys/devices/platform/gpu0/devfreq/gpu0/cur_freq

# Set to performance mode (max frequency)
su -c "echo performance > /sys/devices/platform/gpu0/devfreq/gpu0/governor"

# Verify change
cat /sys/devices/platform/gpu0/devfreq/gpu0/cur_freq

🚀 Expected improvement: 7-8 t/s → 12-15 t/s

> ⚠️ Warning: Higher frequency = more heat + battery drain. Reverts on reboot.

---

🛠️ Troubleshooting

❌ "Permission denied" when loading model

chmod 644 ~/models/your-model.gguf

❌ Vulkan not detected / still using CPU

1. Verify compilation: grep GGML_VULKAN build/CMakeCache.txt
2. Rebuild with -DGGML_VULKAN=ON
3. Ensure dependencies installed: pkg list-installed | grep vulkan

❌ Chat template warnings

Add --jinja flag to enable Jinja2 template engine.

❌ Slow performance (<5 t/s with -ngl 99)

• Try reducing context: -c 512 instead of -c 2048
• Enable KV cache quantization: -ctv q8_0
• Boost GPU frequency (see above)

---

📦 Recommended Models for Testing

Model	Size	Expected Speed (Vulkan)
Qwen2.5-0.5B	~0.4 GB	20-30 t/s
Qwen2.5-1.5B	~1.1 GB	12-18 t/s
Gemma-2-2B	~2.0 GB	7-10 t/s
Llama-3-8B	~4.9 GB	4-7 t/s

> Smaller = faster. Start with Qwen2.5-0.5B for testing.

---

🔄 Why This Works Now (No Manual Driver Extraction)

Older guides required manually copying vulkan.mali.so and setting LD_LIBRARY_PATH. On modern setups, this is often unnecessary because:

✅ Android 14+ has better Vulkan ICD discovery
✅ Termux's vulkan-loader package auto-detects system drivers
✅ llama.cpp b9190+ has improved Android Vulkan backend

> ⚠️ If auto-detection fails on your device, fall back to manual driver extraction guides.

---

🎯 Final Working Command (Copy-Paste)

cd ~/llama.cpp
./build/bin/llama-cli \
  -m ~/models/gemma-2-2b-it-Q5_K_M.gguf \
  -p "Hello, write a short poem about Android" \
  -n 150 \
  -ngl 99 \
  -c 1024 \
  --jinja \
  --color auto \
  --verbosity 0

---

💬 Questions?

Drop a comment if you run into issues! Happy to help troubleshoot.

Device: Pixel 9 Pro XL
Android: 15
Termux: Latest from F-Droid
llama.cpp: b9190 (main branch)
GPU: Mali-G715 (Vulkan)

---

Last tested: May 2026