30 days of uptime goal is completed!

This proves we are truly unstoppable 💪🏽

Pocket Jellyfin server 🗿

Guys,

I'm being honest,

I don't want to bring back the idea of hiding root into my own project.

It's such a pointless idea.

People are literally advising me to hide root. But why? Why would I add duct tape to our project?

It's not the point of containerization.

As I always say, if you want to use banking apps while using Droidspaces,

Either stop using Droidspaces OR your banking app.

This problem exists even in your chroot, Docker container, or LXC.

This is how Linux works.

As we are maturing, I don't want to add the poisonous Android-related idea of hiding root to our code.

If I add such things, our group fills with root detector screenshots, and it really pollutes the community.

Droidspaces is a power user's tool.

Not made for ordinary people who depend on banking apps.

I'm following LXC/Docker/FSF's roots, not the ideas of poisonous devs in the rooting community.

So, stop using Droidspaces if you need banking apps. Use PRoot or QEMU. They do not run as root. They won't give you scary warnings in your detector.

Proof of Concept: 1-click Termux:X11 support

Think of it like this:

1. You toggle Termux:X11 and add the DISPLAY=:0 environment variable.

2. You start the app.

3. You open the Termux:X11 app.

4. Your desktop is right in front of your eyes 🗿

- 0 Termux usage
- 0 Command knowledge needed.

It just works.

This is still in the testing stages. Sometimes it works and sometimes it doesn’t due to SELinux. After some testing, we will merge it into the dev branch.

Proof of Concept:

Automatic Desktop environment startup!

The dreams come true :)

Here's how it works:

1. Before the container even starts, Droidspaces does exactly what running termux-x11 :0 does.

2. Before firing up the init, Droidspaces bind-mounts /data/data/com.termux/files/usr/tmp/.X11-unix/X0 to the container's /tmp/.X11-unix/X0.

3. Droidspaces execs the init.

4. Init executes XFCE!

Resulting in a seamless experience like this 🔥

This is not a new thing , but it's a perfect execution :)

@Droidspaces

Just like a real Linux PC, internal reboot and poweroff are fully supported!

Proof of Concept

Out-of-the-box VirGL support 🔥

The flow:

> You enable Termux:X11 and VirGL from the app
> Start the container
> You open the Termux:X11 app
> The desktop environment appears with VirGL hardware acceleration

- No Termux setup required
- No manual commands
- Unkillable

@Droidspaces

Testing:

https://t.me/DroidspacesCI/486?single

What is still needed:

1. Both the Termux and Termux:X11 apps must be installed.

2. Inside Termux, to use X11, termux-x11 must be installed.

Command to install: apt update && apt install x11-repo && apt install termux-x11

3. Inside Termux, to use the VirGL function, virglrenderer-android must be installed.

Command to install: apt update && apt install x11-repo && apt install virglrenderer-android

4. After installation, to apply the SELinux rules, YOU MUST REBOOT - THIS IS MANDATORY.

Once these 4 requirements are completed, both the X11 and VirGL functions should work without even needing the Termux app to be opened.

The magic is that we are just executing termux-x11 and virglrenderer-android outside the Termux app, disguised as the Termux app, while being unkillable :)

So, even if you force stop Termux, both the X11 and VirGL servers will still run in the background!

Or, I'll just provide a unified shell script to install the required packages inside Termux 🗿

Paste the curl command -> Done.

Max lines of code additions: ~50

Me happy, you happy, no bloat.

It's so hard to maintain something that works for all 4 architectures equally 😅

Even the Droidspaces backend cannot be linked with those projects as it is a self-contained, statically linked binary.

Initial PulseAudio test has been started..!

This CI release has PulseAudio feature.

To use this feature, installing PulseAudio inside Termux is mandatory: apt update && apt install pulseaudio

Also, you have to reboot after updating the backend to apply the SELinux rules.

After installing PulseAudio inside Termux, updating the backend in Droidspaces and rebooting, open the Droidspaces app, enable PulseAudio for your container, and start it.

Note: Installing PulseAudio on the container side is still mandatory. I recommend trying it on Ubuntu 24.04:

apt update && apt install -y pulseaudio-utils pavucontrol
export PULSE_SERVER=unix:/tmp/.pulse-socket

Then, run pactl info for verification :)

Video + Audio + GPU (VirGL/Turnip) 🔥

curl -fsSL https://github.com/ravindu644/Droidspaces-OSS/raw/refs/heads/dev/scripts/setup-termux.sh | bash

Run the above command inside Termux to configure it for Droidspaces. :)

What does it do?

1. Updates your Termux.
2. Installs the x11-repo package.
3. Installs virgl, termux-x11, and PulseAudio.
4. Patches the PulseAudio default.pa file to fix a deadlock that happens on some Android devices.

Edit: Always use the latest CI apks as they contain the latest fixes: @DroidspacesCI

Do you know any reliable way to get audio working in containers?

Currently, the PulseAudio approach is very fragile. It sometimes works, and sometimes doesn't.

No denials, nothing.

The entire PulseAudio server gets deadlocked and unresponsive after ~5 minutes. Until then, audio works perfectly.

If we can't find a way to fix this issue, I'll remove the PulseAudio feature entirely, as we want reliability.

A feature that doesn't exist is better than a broken implementation.