Droidspaces v5.6.0 has been released!
https://github.com/ravindu644/Droidspaces-OSS/releases/tag/v5.6.0
Note: After installing this release, if you are using an old kernel like 4.14.113 (this issue is specific to this kernel version), and systemd appears to hang,
Strangely, this issue does not occur on 4.9 kernels and only manifests on 4.14.113, which affects most devices, particularly Samsung devices released between 2019 and 2020.
Previously, to fix this, all clone() and unshare() syscalls had to be blocked to prevent systemd from creating sandboxes, which resolved the deadlock and allowed systemd to boot. However, this came at the cost of losing the ability to run Docker, Podman, or LXC inside a Droidspaces container on any kernel below 5.x.
In this release, that hard-coded block has been completely removed. Users can now enable the "Deadlock Shield" only if needed, directly from the container configuration menu.
As a result, users already running an upstream kernel such as 4.14.356 can now run Docker inside Droidspaces, while affected users can still enable the Deadlock Shield manually.
Also, this release focuses on fixing critical vulnerabilities in the project related to common exploits, further hardening security, and fixing a critical security hole where a device's block devices were exposed under /sys/block, even in non `--hw-access` mode.
https://github.com/ravindu644/Droidspaces-OSS/releases/tag/v5.6.0
Note: After installing this release, if you are using an old kernel like 4.14.113 (this issue is specific to this kernel version), and systemd appears to hang,
systemctl commands do not work, or your phone becomes unresponsive, you are affected by the grab_super() VFS deadlock bug.Strangely, this issue does not occur on 4.9 kernels and only manifests on 4.14.113, which affects most devices, particularly Samsung devices released between 2019 and 2020.
Previously, to fix this, all clone() and unshare() syscalls had to be blocked to prevent systemd from creating sandboxes, which resolved the deadlock and allowed systemd to boot. However, this came at the cost of losing the ability to run Docker, Podman, or LXC inside a Droidspaces container on any kernel below 5.x.
In this release, that hard-coded block has been completely removed. Users can now enable the "Deadlock Shield" only if needed, directly from the container configuration menu.
As a result, users already running an upstream kernel such as 4.14.356 can now run Docker inside Droidspaces, while affected users can still enable the Deadlock Shield manually.
Also, this release focuses on fixing critical vulnerabilities in the project related to common exploits, further hardening security, and fixing a critical security hole where a device's block devices were exposed under /sys/block, even in non `--hw-access` mode.
💩1
This media is not supported in your browser
VIEW IN TELEGRAM
If you are from Reddit and wondering how my S10 Jellyfin server performs,this is how:
As you can see, I'm constantly pulling heavy FLACs from the server in real-time.
Most of the FLACs are larger than 50MB.
During this testing,the CPU stays below 20%,with idle usage around 9-10%.
Temperatures stayed the same,all below 40C.Even my room temp is ~34C rn.
So,this is a huge win for me.
This setup is very efficient for streaming my music :)
Also,Android didn't kill the server.It's up and running for 8 hours according to uptime.Also,during previous testing,it held up to 2 days until my manual reboots.
As you can see, I'm constantly pulling heavy FLACs from the server in real-time.
Most of the FLACs are larger than 50MB.
During this testing,the CPU stays below 20%,with idle usage around 9-10%.
Temperatures stayed the same,all below 40C.Even my room temp is ~34C rn.
So,this is a huge win for me.
This setup is very efficient for streaming my music :)
Also,Android didn't kill the server.It's up and running for 8 hours according to uptime.Also,during previous testing,it held up to 2 days until my manual reboots.
🔥3❤🔥2💩1
Added a guide to fix the Wi-Fi power-saving issue on Android devices, which makes the networking experience sluggish when the device’s screen is turned off:
https://github.com/ravindu644/Droidspaces-OSS/blob/main/Documentation/Troubleshooting.md#wi-fi-power-save-on-causing-sluggish-networking-on-android
https://github.com/ravindu644/Droidspaces-OSS/blob/main/Documentation/Troubleshooting.md#wi-fi-power-save-on-causing-sluggish-networking-on-android
❤1💩1
Droidspaces
Built in terminal ?🌚
Droidspaces-universal-v5.6.1-2026-03-14-final.apk
14 MB
Testing... Please report any issues if they happen related to the terminal/IPv6
❤3🔥1💩1
Droidspaces
Droidspaces-universal-v5.6.1-2026-03-14-final.apk
Since no one is dropping a single screenshot, I assume the build is stable 😅
How can I tell if this has bugs in some whacky setup? You guys need to test it.
Even if it doesn’t have any bugs, you still need to report to me
Since the project is popular now, I can’t release updates every day without testing like a madman :D
Thanks for understanding the situation :)
How can I tell if this has bugs in some whacky setup? You guys need to test it.
Even if it doesn’t have any bugs, you still need to report to me
Since the project is popular now, I can’t release updates every day without testing like a madman :D
Thanks for understanding the situation :)
👍9🔥3🗿2💩1
Added support for static IPs in NAT mode.
Now, the IP won’t reset after a container reboot or fresh boot :)
This is very useful for accessing container services directly from the host.
Now, the IP won’t reset after a container reboot or fresh boot :)
This is very useful for accessing container services directly from the host.
🔥5🗿3👍1💩1
Droidspaces-universal-v5.6.1-2026-03-16.apk
14 MB
Here's a test APK:
What's added:
- Static IPv4 support in NAT mode - fully configurable via the container config menu
- Ability to resize the sparse image
- Ability to migrate from a directory-based container to a rootfs.img-based container
- Added a help card to the home page
If you find any issues, please let us know in the discussion group.
What's added:
- Static IPv4 support in NAT mode - fully configurable via the container config menu
- Ability to resize the sparse image
- Ability to migrate from a directory-based container to a rootfs.img-based container
- Added a help card to the home page
If you find any issues, please let us know in the discussion group.
❤2🗿2💩1
v5.7.0 has been released..!
https://github.com/ravindu644/Droidspaces-OSS/releases/tag/v5.7.0
What's changed?
@Droidspaces
https://github.com/ravindu644/Droidspaces-OSS/releases/tag/v5.7.0
What's changed?
- added support for built-in terminal emulator support
- add support for configuring and managing static NAT IP addresses for containers
- renamed the --enable-ipv6 toggle to --disable-ipv6
- app: Implement sparse image management for containers, enabling rootfs migration and image resizing
- app: added a help card for new users in the Home screen
- Implement a transparent DNS proxy for NAT containers
- add new /proc and /sys/vm masks to prevent Android GPU/display and Vulkan corruption
- default container user to 'root' and prioritize su -l for shell and command execution to ensure proper login context
- fix: clean up cgroup subtrees on container stop and enter/run exit - fixes cgroups leaks
- adjust /tmp mounting condition to include Android devices without Termux-X11
- implement log file rotation and rate-limit DNS proxy upstream timeout warnings
- fix: prevent memory leak of unknown config lines during container shutdown
- fix: preserve environment variables during configuration reload in internal reboots
@Droidspaces
💩1
Droidspaces
Implement a transparent DNS proxy for NAT containers
To fix DNS-related issues in existing systemd-based containers (containers already installed using the Droidspaces app), please run this command as root inside the container's shell:
cat > "/etc/systemd/resolved.conf.d/dns.conf" << 'EOF'
[Resolve]
DNSStubListener=no
EOF
❤1💩1