Hosted my own Git server and VS Code server, only accessible to me via Tailscale :)
Everything works with just one click.
No trial and error.
So, my S10 officially runs:
- Tailscale
- Samba
- Jellyfin
- Fail2ban
- UFW
- Docker
- MySQL server
- Getea
- VS Code server
- OpenSSH server
All under 3GB of RAM usage (including Android) and under 5% idle CPU usage.
Nothing is impossible :)
Everything works with just one click.
No trial and error.
So, my S10 officially runs:
- Tailscale
- Samba
- Jellyfin
- Fail2ban
- UFW
- Docker
- MySQL server
- Getea
- VS Code server
- OpenSSH server
All under 3GB of RAM usage (including Android) and under 5% idle CPU usage.
Nothing is impossible :)
π₯10π3π©1
Droidspaces
Photo
Well, why not? π
The uptime got messed up when I was setting up HTTPS :)
Even this is more powerful than the latest RPI 5 in benchmarks.
The only caveat is this phone isn't using the latest Linux kernel, as that's the nature of old Android :(
The uptime got messed up when I was setting up HTTPS :)
Even this is more powerful than the latest RPI 5 in benchmarks.
The only caveat is this phone isn't using the latest Linux kernel, as that's the nature of old Android :(
π₯4π©1πΏ1
Droidspaces v5.8.0 has been released..!
https://github.com/ravindu644/Droidspaces-OSS/releases/tag/v5.8.0
What's new?
TLDR:
@Droidspaces
https://github.com/ravindu644/Droidspaces-OSS/releases/tag/v5.8.0
What's new?
- mount: slave-bind host /dev/block in --hw-access mode (fixes external storage not visible inside the container)
- hardware: mirror missing GPU nodes into devtmpfs on hw_access boot
- ds_dhcp: fix misaligned iphdr access in send_reply
- net: use kernel ip rule as primary upstream detection on Android (100x better upstream detection on wildcards π₯³)
- app: removed global uptime from the 'System Statistics' card and using per-container uptime in the container info menu
- Modify service.sh to update module description
- fix: Introduce Termux environment detection and prevent --termux-x11 killing termux, when running the droidspaces ... command within Termux
- app+backend: Decouple Hardware Access and Termux-X11 features
- app: implement Material You Accent color picker
- fix(backend): sort bind mounts alphabetically to prevent shadowing
- feat: implement port range forwarding
- fix: serialize DHCP "started" log via cond var to eliminate race with port-forward and boot logs
- fix: persist port-forward state file to guarantee full rule cleanup on stop
TLDR:
- 100x better upstream detection. Now you can hop between SIM1/SIM2 mobile data + WiFi without dropping any requests.
- Added Docker-like port range forwarding support.
- Mirrors GPU nodes from host to container if the containerβs devtmpfs doesnβt have the detected nodes
@Droidspaces
π₯5πΏ2π©1
Droidspaces
Droidspaces v5.8.0 has been released..! https://github.com/ravindu644/Droidspaces-OSS/releases/tag/v5.8.0 What's new? - mount: slave-bind host /dev/block in --hw-access mode (fixes external storage not visible inside the container) - hardware: mirror missingβ¦
found 2 hidden bugs that were unnoticed for months. fixing them right nowπ
1. https://t.me/DroidspacesDiscussion/4279
2. https://t.me/DroidspacesDiscussion/4257
1. https://t.me/DroidspacesDiscussion/4279
2. https://t.me/DroidspacesDiscussion/4257
π₯°1π©1
Droidspaces
Droidspaces v5.8.0 has been released..! https://github.com/ravindu644/Droidspaces-OSS/releases/tag/v5.8.0 What's new? - mount: slave-bind host /dev/block in --hw-access mode (fixes external storage not visible inside the container) - hardware: mirror missingβ¦
Droidspaces v5.8.1
https://github.com/ravindu644/Droidspaces-OSS/releases/tag/v5.8.1
Fixes:
@Droidspaces
https://github.com/ravindu644/Droidspaces-OSS/releases/tag/v5.8.1
Fixes:
- fix(runtime): prevent metadata overwrite during container scan
- fix: restrict Termux X11 conflict check to 'start' or 'restart' commands
- fix: skip Termux force-stop if unified /tmp bridge is already mounted
@Droidspaces
πΏ5β€1π©1
Droidspaces
Photo
Well,
Developers can now integrate the droidspaces daemon at the init.rc level.
Theoretically, you can run droidspaces without root if it is integrated into the Android init system.
However, since it is dangerous, I have artificially limited the ability for non-root users on Android to connect with the droidspaces socket.
On Linux, though, users can run droidspaces commands without
Developers can now integrate the droidspaces daemon at the init.rc level.
Theoretically, you can run droidspaces without root if it is integrated into the Android init system.
However, since it is dangerous, I have artificially limited the ability for non-root users on Android to connect with the droidspaces socket.
On Linux, though, users can run droidspaces commands without
sudo!β€2π₯°1π©1
For Magisk/APatch issues, enabling the toggle is enough.
For GrapheneOS users, however, they might need to integrate droidspaces as an init service to fix certain syscalls that get blocked even when running as root.
For GrapheneOS users, however, they might need to integrate droidspaces as an init service to fix certain syscalls that get blocked even when running as root.
π©1
Droidspaces-universal-v5.9.0-daemon-test2.apk
14.1 MB
testing :)
1. Install
2. Enable daemon mode
3. Reboot the device
4. Tell me the results :)
1. Install
2. Enable daemon mode
3. Reboot the device
4. Tell me the results :)
π©1
After the recent changes to the Droidspaces daemon and using custom SELinux policies to fix denials related to Droidspaces during boot,
I can finally confirm that Droidspaces is fully stable on Magisk and Apatch π₯³
Now, only GrapheneOS needs testing..
I can finally confirm that Droidspaces is fully stable on Magisk and Apatch π₯³
Now, only GrapheneOS needs testing..
π₯2π1π©1
Droidspaces
After the recent changes to the Droidspaces daemon and using custom SELinux policies to fix denials related to Droidspaces during boot, I can finally confirm that Droidspaces is fully stable on Magisk and Apatch π₯³ Now, only GrapheneOS needs testing..
Droidspaces-v5.9.0-daemon-final.apk
14.8 MB
here's the test APK:
1. Install
2. Enable daemon mode
3. Reboot the device
This APK should fix:
1. All the issues related to Magisk/APatch
2.
1. Install
2. Enable daemon mode
3. Reboot the device
This APK should fix:
1. All the issues related to Magisk/APatch
2.
rootfs.img mounting issues in all devicesπ©1
We just integrated
Here's what that means for you:
Unkillable daemon - even if you
No root manager needed - the daemon runs as UID 0 (root) natively, without relying on Magisk, APatch, or KSU to function.
Clean SELinux - runs under its own permissive domain with no noisy denials.
Symlink mode - developers can place a symlink at
The app just updates the real binary inside
https://github.com/ravindu644/Droidspaces-OSS/commit/9fdca856bd2d296980ab6c0becb490981283a025
@droidspaces
droidspacesd directly into Android's native init system - no KernelSU, Magisk, or APatch needed. No post-fs-data.sh or service.sh scripts either.Here's what that means for you:
Unkillable daemon - even if you
kill -9 it, init brings it right back up automatically.No root manager needed - the daemon runs as UID 0 (root) natively, without relying on Magisk, APatch, or KSU to function.
Clean SELinux - runs under its own permissive domain with no noisy denials.
Symlink mode - developers can place a symlink at
/vendor/bin/droidspaces pointing to /data/local/bin/droidspaces. This means once the vendor image is repacked and shipped, you never need to unpack it again for updates.The app just updates the real binary inside
/data, and init picks it up automatically on the next bootπΏhttps://github.com/ravindu644/Droidspaces-OSS/commit/9fdca856bd2d296980ab6c0becb490981283a025
@droidspaces
π€―6π₯3β€1π©1