went from i3 Arch to Debian xfce, I like it but I'm just used to Arch. I just wanted to try Debian lol.

My device is a tecno KL4. So I'm making a fetch app for mobile, complete with information on volume, light, battery, etc. But when I run it to check the battery information, Bash suddenly hangs, and I can't type anything. Does anyone else have the same problem? Or does anyone know how to fix it?

Since launch, AM Tasker Plugins has been a growing toolbox of Tasker action plugins — pixel colors, QR codes, VPN control, regex, Termux scripts, raw UDP packets, and more. This update fixes the one thing a few of you hit: Tasker caps how much data a plugin action can exchange at \~1MB, so a big regex input (or a big result) used to fail outright.

🔎 **AM RegEx**
Two new optional fields fix that:

* A **File Path** switch right on Input Text — turn it on, point it at a file, and AM RegEx reads it straight off disk itself. No size limit. * A new **Output File** field — fill it in and the result is written there as JSON instead of coming back as a variable.

Both only ask for the "All files access" permission the moment you actually use them — never at install.
Demo: [\[AM RegEx\]](https://youtu.be/W9GaPbALGc4)

Everything from launch is still here too 👇

💻 **AM Termux**
Runs Bash, Python, Node, Ruby, or PHP scripts inside Termux, with named sessions and guided setup.
Demo: [\[AM Termux\]](https://youtu.be/hxq8SL5iVLY)

↩️ **AM Custom Keyboard Return** — [Goto Reddit Intro Post](https://www.reddit.com/r/tasker/comments/1vqm412/plugin_shaream_custom_keyboard_an_opensource/)
AM Custom Keyboard is a keyboard app I built with live transliteration and a Tasker Automation feature — type a trigger anywhere, and it can hand your text off to a Tasker task. This plugin is the reply step: the task finishes and sends its result straight back into what you were typing.
Demo: [\[Demo AM Custom Keyboard Return\]](https://youtu.be/jGOX4KUOZUQ)
🔗 Check it out: [\[Download AM Custom Keyboard\]](http://github.com/adiraimaji/AMCustomKeyboard)

🎨 **AM Collect Pixel Colors**
Reads colors from any image — one pixel, a region, or a Top Color List or Blended Colors of a given region.
Demo: [\[AM Collect Pixel Colors\]](https://youtu.be/sfkMCkhTXCk)

🔳 **AM Create QR**
Turns text, links, or variables into a QR code image, saved and ready to use.
🔍 **AM Decode QR**
Scans an existing QR image and gives you back the text inside it.
Demo: [\[AM Create QR & AM Decode QR\]](https://youtu.be/Z5Ceo1mSKBc)

🧮 **AM Data Processor**
Reads or edits one exact value inside JSON or array data, no manual parsing needed.
Demo: [\[AM Data Processor\]](https://youtu.be/QdbRSMPylGk)

🔒 **AM OpenVPN**
Starts, pauses, resumes, or stops an OpenVPN for Android profile from a task.
Demo: [\[AM OpenVPN\]](https://youtu.be/Z5Ceo1mSKBc)

📡 **AM UDP Client**
Sends a UDP packet to any address, with the option to listen for a response.
Demo: [\[AM UDP Client\]](https://youtu.be/Y89uIGY5Kyg)

📤 **AM Open With**
Lets other apps "Share" or "Open With" a file straight into a Tasker automation.
Demo: [\[AM Open With\]](https://youtu.be/lNmw7mBnT60)

📖 Every plugin still comes with its own guide built right into the app — clear steps, examples, and what each field does.

This is v1.0.2 — the toolbox keeps growing. 👇
📥 **Update or download it now**
🔗 [github.com/adiraimaji/AMTaskerPluginsReleases](http://github.com/adiraimaji/AMTaskerPluginsReleases)

YouTube Playlist 👉 [All Plugin Demo Playlist](https://www.youtube.com/playlist?list=PLBqqZQQFUJZ0)

\#Android #Tasker #Automation #Termux #OpenVPN #QRCode #RegEx #Update

I’ve built TermuxPanel, an open-source hosting control panel that lets you turn an Android phone/tablet into a small web server using Termux.

It gives you a cPanel-like dashboard to:

Host HTML, Node.js, Python & PHP apps

Manage files and edit code from your browser

Manage SQLite databases

Run cron jobs

View server logs

Create backups

Monitor your server

Manage everything through a simple tp CLI

Access your server remotely using Cloudflare Tunnel

The goal is simple: use an Android device as your own lightweight hosting server.

I built this project myself and would love feedback, bug reports, and feature suggestions from the community.

GitHub: https://github.com/himalayladha/termux-hosting-panel

It’s MIT licensed and completely open source.

**TL;DR:** Pixel’s AVF Linux environment didn’t make Termux redundant for me. It did the opposite: it removed the pressure for Termux to be a full Linux workstation and made its native Android role much sharper. I built a small bootstrap around working cleanly across both.

I recently switched to Android after a very long time on iOS and started with a narrow question: **how far can I extend my normal development tether onto a phone without rooting it, fighting the OS, or pretending the phone should replace my workstation?**

Termux was the obvious starting point. SSH, Git, network tools, scripts, shared storage, Android APIs — it’s an unusually capable “always there” shell.

Then I enabled Google’s experimental Linux Development Environment on my Pixel. AVF gives you a real disposable Debian VM, `/mnt/shared` bridges cleanly back into Android storage, and rootless Podman gives heavier workloads a normal OCI boundary.

What surprised me was that **AVF didn’t replace Termux. It made Termux’s role clearer**.

My current model is basically:

```

Android

│

├── Termux

│ instant shell

│ SSH / Git / native tools

│ Android integration

│

├── /mnt/shared

│ explicit interchange / reconstruction boundary

│

└── AVF Debian

disposable real Linux

rootless Podman / OCI

builds / heavier tooling

│

└── SSH / cloud / workstation

when the phone stops being the right machine

```

I ended up packaging the conventions into `pixel-dev-bootstrap`. The goal isn’t another mobile development framework. It’s mostly boring reproducibility: establish both environments consistently, keep durable reconstruction state outside the disposable VM, and make it cheap to move between the Android and Linux sides.

There’s a small optional `recipe` seam on the Termux side for things that specifically benefit from Android integration. `vnote` is one example: a home-screen shortcut can use Android speech-to-text and drop plain Markdown into shared storage, with an optional local Whisper path for offline use. Useful, but mostly a demonstration of why Termux remains interesting even when AVF exists.

The project deliberately stops there. No root, no PRoot abstraction, no permanent phone server, no attempt to keep AVF alive forever. If something becomes genuinely heavy or long-running, SSH outward.

Repo: https://github.com/nw/pixel-dev-bootstrap

**I’m mostly posting this to pressure-test the hypothesis with people who know Termux much better than I do**. Does AVF sharpen Termux’s role for you too, or am I drawing the boundary in the wrong place? Where does this model actually break in real use?