This media is not supported in your browser
VIEW IN TELEGRAM
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
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
❤10🗿8🔥4
Droidspaces
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 …
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,
Command to install:
3. Inside Termux, to use the VirGL function,
Command to install:
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
So, even if you force stop Termux, both the X11 and VirGL servers will still run in the background!
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-x113. Inside Termux, to use the VirGL function,
virglrenderer-android must be installed.Command to install:
apt update && apt install x11-repo && apt install virglrenderer-android4. 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!
❤6🤯2
Added custom VirGL and Termux:X11 flags support
Install the latest CI:
https://t.me/DroidspacesCI/490?single
Notes:
Many misunderstood the new Termux:X11 and VirGL features, expecting them to auto-boot a desktop environment. They won't unless you add a systemd service for it.
Proper usage in the exact order:
1. Install the latest Droidspaces CI, Termux, and Termux:X11 apps.
2. Update the Droidspaces backend and reboot your phone.
3. Open Termux and run:
4. In Droidspaces, open your container config and toggle Termux:X11 and VirGL.
5. Start the container.
If successful, an X cursor will appear in the Termux:X11 app.
Note:
Droidspaces auto-injects the required environment variables. If using an alternative shell like ZSH, run:
Install the latest CI:
https://t.me/DroidspacesCI/490?single
Notes:
Many misunderstood the new Termux:X11 and VirGL features, expecting them to auto-boot a desktop environment. They won't unless you add a systemd service for it.
Proper usage in the exact order:
1. Install the latest Droidspaces CI, Termux, and Termux:X11 apps.
2. Update the Droidspaces backend and reboot your phone.
3. Open Termux and run:
apt update && apt install x11-repo && apt install termux-x11 virglrenderer-android4. In Droidspaces, open your container config and toggle Termux:X11 and VirGL.
5. Start the container.
If successful, an X cursor will appear in the Termux:X11 app.
Note:
Droidspaces auto-injects the required environment variables. If using an alternative shell like ZSH, run:
source /etc/profile.d/droidspaces_env.sh❤8
Built-in audio support is on-the-way ! 😁
❤15🔥8🗿1
Do you care if the APK size increases if we pack the Termux:X11, PulseAudio, and virglrenderer-android binaries directly into the app?
The final result would be a Termux-free Termux:X11, PulseAudio, and VirGL experience at the cost of bloat.
The final result would be a Termux-free Termux:X11, PulseAudio, and VirGL experience at the cost of bloat.
Final Results
17%
Yes, I care. Don't add bloat
86%
Add them if it makes the experience better
Droidspaces
Do you care if the APK size increases if we pack the Termux:X11, PulseAudio, and virglrenderer-android binaries directly into the app?
The final result would be a Termux-free Termux:X11, PulseAudio, and VirGL experience at the cost of bloat.
The final result would be a Termux-free Termux:X11, PulseAudio, and VirGL experience at the cost of bloat.
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.
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.
❤12👍7🗿2
Initial PulseAudio test has been started..!
This CI release has PulseAudio feature.
To use this feature, installing PulseAudio inside Termux is mandatory:
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:
Then, run
This CI release has PulseAudio feature.
To use this feature, installing PulseAudio inside Termux is mandatory:
apt update && apt install pulseaudioAlso, 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 :)❤5🔥4
Droidspaces
Do you care if the APK size increases if we pack the Termux:X11, PulseAudio, and virglrenderer-android binaries directly into the app?
The final result would be a Termux-free Termux:X11, PulseAudio, and VirGL experience at the cost of bloat.
The final result would be a Termux-free Termux:X11, PulseAudio, and VirGL experience at the cost of bloat.
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
🔥9
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.
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.
❤7🤯1
Droidspaces
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.…
I guess we fixed the PulseAudio deadlock bug. It's not even related to Droidspaces
Termux issues:
https://github.com/termux/termux-packages/issues/19861
https://github.com/termux/termux-packages/issues/19623
Try this CI: https://t.me/DroidspacesCI/504?single
It is required to run our setup script even if your Termux is already configured:
I worked almost 20 hours fixing an issue that doesn't even exist on our side.
I followed the fixes in these two issues, and it looks like it fixed the deadlock issue that only happens on some devices.
Termux issues:
https://github.com/termux/termux-packages/issues/19861
https://github.com/termux/termux-packages/issues/19623
Try this CI: https://t.me/DroidspacesCI/504?single
It is required to run our setup script even if your Termux is already configured:
curl -fsSL https://github.com/ravindu644/Droidspaces-OSS/raw/refs/heads/dev/scripts/setup-termux.sh | bash
I worked almost 20 hours fixing an issue that doesn't even exist on our side.
I followed the fixes in these two issues, and it looks like it fixed the deadlock issue that only happens on some devices.
❤15🔥3🫡3
This media is not supported in your browser
VIEW IN TELEGRAM
SteamOS on Droidspaces with native performance wen ? (jk)
Video credit: https://t.me/DroidspacesDiscussion/50418
Video credit: https://t.me/DroidspacesDiscussion/50418
🗿19❤1
I'll try to release Droidspaces v6.3.0 today.
It will be our most plug-and-play "it just works", zero-duct-tape Desktop experience ever!
What it means:
> You start your container
> The desktop environment automatically appears without you even touching anything or exporting any kind of environment variables.
It will be our most plug-and-play "it just works", zero-duct-tape Desktop experience ever!
What it means:
> You start your container
> The desktop environment automatically appears without you even touching anything or exporting any kind of environment variables.
❤28🗿6
Droidspaces v6.3.0 has been released! 🥳
Plus the usual round of translation updates, UI polish, and under-the-hood refactoring.
Full Changelog and Downloads:
https://github.com/ravindu644/Droidspaces-OSS/releases/tag/v6.3.0
@Droidspaces
- One-tap Termux:X11, VirGL, and PulseAudio setup - press start and your desktop environment appears. No manual configuration required.
- Fully migrated from magiskpolicy/droidspaces.te to sepolicy.rule.
- Fixed a bug where starting a container would spawn 6 extra PTYs on the host /dev/pts
- Fixed garbled characters in TUI-heavy apps when using daemon mode shell
- Fixed shell hang when pasting large amounts of text in daemon mode
- Fixed shell failing to attach on older 4.9 kernels
- Machine ID is now always generated on container installation
- Reduced app size by 4MB by replacing the bundled BusyBox with a custom minimal build
Plus the usual round of translation updates, UI polish, and under-the-hood refactoring.
Full Changelog and Downloads:
https://github.com/ravindu644/Droidspaces-OSS/releases/tag/v6.3.0
@Droidspaces
❤14🔥2
Droidspaces
Droidspaces v6.3.0 has been released! 🥳 - One-tap Termux:X11, VirGL, and PulseAudio setup - press start and your desktop environment appears. No manual configuration required. - Fully migrated from magiskpolicy/droidspaces.te to sepolicy.rule. - Fixed a bug…
Note:
You may need to uninstall the old APK before installing the new one due to changes in the app's version code scheme.
Previously, version 6.2.5 was registered with the version code 60205. However, following a refactor to sync the Magisk module version code, version 6.3.0 is now registered as 6300. Because Android blocks installing an update with a lower version code over an existing app, a manual uninstallation of the older version is required.
You may need to uninstall the old APK before installing the new one due to changes in the app's version code scheme.
Previously, version 6.2.5 was registered with the version code 60205. However, following a refactor to sync the Magisk module version code, version 6.3.0 is now registered as 6300. Because Android blocks installing an update with a lower version code over an existing app, a manual uninstallation of the older version is required.
👏8🗿2
There is an entire new document explaining how to use the new Termux:X11, VirGL, and PulseAudio features, as well as how to set up the Desktop Environment autoboot feature for advanced users. Go check it out 👀:
https://github.com/ravindu644/Droidspaces-OSS/blob/main/Documentation/Graphics-and-Audio.md
https://github.com/ravindu644/Droidspaces-OSS/blob/main/Documentation/Graphics-and-Audio.md
🔥12👍1🗿1
Guys, I want you to try this APK:
https://t.me/DroidspacesCI/519?single
Basically, we ditched the concept of "upstream interfaces" and made it fully automated.
That means Droidspaces will automatically detect which default route is currently active and use it as the upstream interface for internet access.
That means there is no need to point out interface names. Everything is fully automated, including real-time network interface change detection (like hopping between data and Wi-Fi).
The cherry on top is that we now support port forwarding in Hotspot/USB Tethering.
That means, on your Droidspaces server phone, you can toggle the Wi-Fi hotspot, connect your PC or another phone to that hotspot, and then access your services with gateway_ip:port!
Basically, I use it as a pocket Jellyfin server hotspot right now! 🗿
It's almost stable. It has been tested on almost 6 phones, and we found no issues.
However, testing is still appreciated.
https://t.me/DroidspacesCI/519?single
Basically, we ditched the concept of "upstream interfaces" and made it fully automated.
That means Droidspaces will automatically detect which default route is currently active and use it as the upstream interface for internet access.
That means there is no need to point out interface names. Everything is fully automated, including real-time network interface change detection (like hopping between data and Wi-Fi).
The cherry on top is that we now support port forwarding in Hotspot/USB Tethering.
That means, on your Droidspaces server phone, you can toggle the Wi-Fi hotspot, connect your PC or another phone to that hotspot, and then access your services with gateway_ip:port!
Basically, I use it as a pocket Jellyfin server hotspot right now! 🗿
It's almost stable. It has been tested on almost 6 phones, and we found no issues.
However, testing is still appreciated.
🔥15🗿4