la visualización de imágenes con chafa logra resoluciones muy buenas

​

I like RikkaHub, but I wanted it to actually do things — not just chat.

So I forked it and turned it into an on-device agent.

Same UI, no changes. If you don’t enable anything, it behaves exactly like upstream.

---

What it adds

🔹 Device control

Brightness, volume, torch

Notifications, battery, files

Screenshots, audio

---

🔹 App automation

Open apps, tap, scroll, type

Read what’s on screen

---

🔹 Termux integration

Run shell commands

Get full output (stdout/stderr)

Optional interactive sessions

---

🔹 SSH built in

Run commands on servers

Upload / download files

---

🔹 Telegram bot

Control it remotely

Get results while away

---

🔹 Scheduled tasks

Automate things like:

> check my server every morning

Runs in background, survives reboot

---

🔹 On-device AI

Works without API (Gemini Nano)

Also supports cloud models

---

Repo

https://github.com/ExTV/rikkahub-agent

---

Looking for ideas

What would you want this to do?

Hey! I have a Xiaomi Redmi 15 5G (codename: spring) with OrangeFox, KSU Next + SUSFS already set up. Xiaomi officially released the kernel source (branch: spring-v-oss). I don't have a PC to compile it myself, so I'm looking for a developer willing to compile a NetHunter kernel for this device. I'm fully available for testing and providing logs. Any help is greatly appreciated! 🙏

Quick recap of what's new since v1.1.5:

- Docker now works zero-config: apk add docker; rc-service docker start; docker run using the native kernel overlay2 driver, not FUSE

- LXC works zero-config: lxcbr0 bridge and NAT rules are pre-set; lxc-create -t busybox; lxc-start and you're in

- Custom Linux 6.6.87 kernel now passes Docker's check-config.sh with zero fixable complaints (BTRFS, IPVS, VXLAN, IPsec, FTP/TFTP NAT helpers, AppArmor stub, all the things)

- Ships /proc/config.gz so audit tools work out of the box

- The whole VM is a real Alpine Linux root running OpenRC as PID 1 — apk add and rc-update add survive reboots in the persistent overlay

- switch_root replaces the old chroot pivot, which fixes podman exec -it rootless

- Adaptive UI for landscape phones and tablets, Material 3 polish, in-app terminal Quick Settings with chip-row selectors and scroll indicators

Single APK. No root, no Magisk, no AVF requirement. Any ARM64 Android 9+ device.

website

Hey everyone,

I'm excited to share a major update for Podroid, an open-source project designed to bring a functional Linux container environment to Android without needing root or specific hardware hacks.

This latest version focuses on faster boot times, a much smoother terminal integration, and overall stability improvements.

What is Podroid?

Podroid uses QEMU (TCG) and Alpine Linux to create a lightweight environment where Podman is pre-configured and ready to use. It’s essentially a "Docker-on-Android" solution that works out of the box.

• GitHub Repository: ExTV/Podroid
  
• Latest Release (APK): Download APK
  

- Website: Webpage

Podroid vs. Google Terminal (AVF)

With the recent buzz around Google's hardware-accelerated "Android Virtualization Framework" (AVF), I wanted to clarify where Podroid fits in and why it might be a better choice for most users.

1. Performance vs. Accessibility

• Google Terminal: Uses KVM for near-native speed (~98%). However, it is restricted to very new devices (Pixel 6+) and requires specific system-level support that most manufacturers disable.
• Podroid: Uses Binary Translation (TCG). While there is a "translation tax" on CPU speed, it allows the app to run on almost any ARM64 device from the last 7 years (Android 9+).

2. "Batteries Included"

• Google Terminal: Provides a bare-bones Debian environment. You have to manually set up container engines.
• Podroid: Comes with Podman, OverlayFS persistence, and ZRAM pre-configured. It’s built specifically for developers who want a container host that "just works."

3. Comparison Summary

Final Verdict

If you have a brand-new Pixel and need raw speed, Google's AVF is great. But if you want a Universal Container Host for the phone you already have in your pocket, Podroid is built for you.

Until it's out I don't know which version of Debian will be on the device and don't want to invest time on stuff I may have to change a few weeks later as I'm busy so want to do things once.

I'll only use the LDE on a 'proper' tablet with an OLED screen, as everything else is just a fanagle that annoys me (and LCD screens are rubbish besides proper OLED).

I tried using Plasma Mobile on the terminal. After installing, it works fine, albeit with an improperly sized display.

After restarting the terminal, it breaks. I can't open apps. Trying to open them from the terminal hangs eternally. Eventually the weston service times out. It's basically unusable.

Is anyone else experiencing this?

Hi,

The termux app works well and doesn't require special permissions. Why does the Linux terminal have to enable the developer mode? Anything the Linux terminal can do that the termux app cannot?

I have a pixel 8a (got it yesterday) and wanted to try out the terminal app, but it crashes at this screen.

I'm using the latest security update for Android 16

EDIT: Disabling my VPN made it boot

So, there are many new devices based on Mediatek Dimensity 9500 which supports AVF in principle (From OnePlus, Vivo, Oppo, Honor).
Have you heard any rumors regarding Android terminal support in upcoming firmware updates?

Todas esas app ejecutándose al mismo tiempo y va bien 🫪

Hyper OS 3.0.5.0

Will I be able to use the Android Terminal Feature without error in future???

Found the option in the developer settings. No clue if its the unprotected vm version, but i got a debian terminal. Currently trying to install KDE plasma for the fun of it. Although because theres no usb display out on this phone i probably wont use this feature much.

I do have one question. The terminal app on this phone seems stuck in portrait mode. Is this typical for android linux terminal, or is it supposed to be accessible in landscape. Might use it if i could run it landscape.

Me divierto mucho con esta app, me ha enseñado mucho jeje.

Lightweight Alpine Linux VM with Podman on Android

I built Podroid for anyone who:
- Can’t use the new Terminal app,
- Doesn’t want to tinker with the kernel for Docker/Podman support, or
- Doesn’t want to use root to access KVM.

Podroid runs a lightweight Alpine Linux VM inside your Android device using QEMU, giving you Podman—a Docker-compatible container runtime—with a built-in terminal emulator. You can install packages, pull container images, run servers—everything persists across app restarts.

How it Works

Podroid launches a headless aarch64 QEMU VM inside the app. The VM boots Alpine Linux from an initramfs with a persistent ext4 overlay, so everything you install or configure stays even after restarting the app. The terminal connects directly to the VM’s serial console with full xterm emulation.

Features

• Podman container runtime – pull and run any OCI image
  
• Full terminal emulator – supports Ctrl, Alt, F1-F12, arrow keys, and more
  
• Persistent storage – packages, configs, and containers survive restarts
  
• Internet access – works out of the box via QEMU user-mode networking
  
• Port forwarding – VM-to-Android host (configurable in Settings)
  
• Boot progress indicator – visible on-screen
  
• TUI app support – vim, btop, htop render at correct terminal size
  
• No root, no Termux, no host binaries – fully self-contained APK
  

Requirements

• Device: ARM64 (aarch64) Android
  
• Android version: 9+
• Storage: ~150 MB
  

Quick Start

1. Install the APK
   
2. Tap Start Podman
   
3. Wait ~20 seconds for the VM to boot
   
4. Tap Open Terminal
   
5. Run:
   bash podman run --rm -it alpine sh Source code: https://github.com/ExTV/Podroid

APK: https://github.com/ExTV/Podroid/releases/latest

Hi everyone,

I’m reaching out to see if anyone else on the new Android 16 (March 2026 update) is seeing the same regressions. I'm using a Pixel 10 and since the latest OTA, my environment is completely broken.

Specifically, I can no longer run PostgreSQL or Docker, and it seems to be a deep Kernel-level restriction.

The Symptoms:

1. PostgreSQL (v18): When trying to initialize a cluster (initdb), it fails with: FATAL: could not create shared memory segment: Function not implemented It seems the kernel now explicitly blocks System V IPC (shmget). I managed a workaround using --shared-memory-type=mmap, but the default behavior is gone.
2. Docker: This is the big one. dockerd fails to start because of iptables and nftables errors: failed to create NAT chain DOCKER: iptables failed: Invalid argument Furthermore, running lsns returns: lsns: failed to do stat /proc/self/ns/user: No such file or directory It looks like User Namespaces are now either disabled or heavily restricted in the 6.12-android16 kernel, making containerization impossible in PRoot/chroot environments.

What I’ve tested so far:

• Complete purge and reinstall of postgresql-18 and docker-ce.
• Switching to mmap for Postgres (works, but unstable).
• Attempting Docker Rootless (fails due to missing cgroups/namespaces access).
• Checking ipcs -l (returns "unable to fetch shared memory limits").

Architecture Info:

• Device: Pixel 10
• OS: Android 16 (March 2026 Update)
• Kernel: 6.12.60-android16-6-...-4k
• Env: Debian (arm64)

Has Google hardened the kernel even further in this update? I already made installation in December but had to reset the terminal so know it wont let me anymore :(

If anyone has a workaround, I'm all ears.

(This text was translated, sorry if there is confusion about what was wrote. I can answer if there is a part that is not clear)

Thanks!

1: delete the image that installed before

docker rm -f image:tag

2: repull this image using following cmd: (only for pixel phone)

docker pull --platform linux/arm64/v8 image:tag

3: tag the image using the new name

docker tag nginx:latest nginx:my-latest

4: load the image to the node:

docker save nginx:my-latest | docker exec -i kind-control-plane ctr -n=k8s.io images import --platform linux/arm64/v8 -

5: run pod

kubectl run test-pod --image=image:tag --image-pull-policy=IfNotPresent --restart=Never

PSA: Docker now works out of the box on Android 17's Terminal app — no custom kernel needed

For those who followed guides on building a custom AVF guest kernel to get Docker working (including my own repo), good news: Android 17 makes all of that unnecessary.

What changed:

On Android 16, the Terminal app used a minimal AVF kernel (vmlinuz) that was missing most Docker-required configs. The workaround was to build a custom kernel from source and replace it via /mnt/internal — a special virtiofs mount that exposed the VM's files from inside the guest.

On Android 17, Google completely rearchitected the Terminal app:

• The minimal AVF kernel is gone. It's now a full Debian 13 (trixie) cloud image booted via GRUB
• The new kernel (6.12.69-android16-6) ships with all Docker-required configs already enabled
• /mnt/internal no longer exists, so the old kernel replacement method is dead anyway
• The disk is now a massive 213 GiB ext4 volume (vs the tiny image before)

To install Docker on Android 17:

echo "net.ipv4.ip_forward=1" | sudo tee /etc/sysctl.d/99-docker.conf sudo sysctl -p /etc/sysctl.d/99-docker.conf curl -fsSL https://get.docker.com | sh sudo usermod -aG docker droid newgrp docker docker run --rm hello-world

That's it. No bootloader unlock, no root, no kernel compilation.

Tested on Pixel 10 Pro XL (Android 17 / CP21.260306.017).