Droidspaces v5.7.1 has been released..!
https://github.com/ravindu644/Droidspaces-OSS/releases/tag/v5.7.1
What's changed?
@Droidspaces
https://github.com/ravindu644/Droidspaces-OSS/releases/tag/v5.7.1
What's changed?
- Fixed issues where runit caused crashes on Android because it modified kernel sysctl parameters, leading to system crashes. Resolved by selectively masking the entire /proc/sys.
- Fixed issues where Gentoo + OpenRC could not obtain an IP from the DHCP server.
- Fixed issues where Devuan received an incorrect IP from the DHCP server.
- Fixed shutdown issues in Void Linux.
- Repaired sysfs symlinks for OpenRC/Gentoo network detection.
- Rewrote firmware path management for Android.
@Droidspaces
🗿3💩1
Set up UFW and Fail2Ban properly, and it actually works!
But had to enable some kernel configs to pull this off :(
Everything behaves like a real Linux server...
But had to enable some kernel configs to pull this off :(
Everything behaves like a real Linux server...
🔥2💩1
Fixed 2 issues with the hardware access feature:
1. On Android, block devices like USB storage and SD cards appear under /dev/block, not /dev, unlike standard Linux. This meant attached storage never showed up in the container's devtmpfs, even in hw access mode. Fixed by bind mounting the host's /dev/block to the container's /dev/block.
2. On some devices, GPU nodes were missing in freshly mounted devtmpfs inside containers. Previously, users had to manually bind mount GPU nodes. Now, if a GPU node exists on the host but is missing in the container, we create it in the container using mknod(), no bind mount needed :)
This also fixes binder, hwbinder, and vndbinder missing issues, and resolves the GitHub issue:
https://github.com/ravindu644/Droidspaces-OSS/issues/19
1. On Android, block devices like USB storage and SD cards appear under /dev/block, not /dev, unlike standard Linux. This meant attached storage never showed up in the container's devtmpfs, even in hw access mode. Fixed by bind mounting the host's /dev/block to the container's /dev/block.
2. On some devices, GPU nodes were missing in freshly mounted devtmpfs inside containers. Previously, users had to manually bind mount GPU nodes. Now, if a GPU node exists on the host but is missing in the container, we create it in the container using mknod(), no bind mount needed :)
This also fixes binder, hwbinder, and vndbinder missing issues, and resolves the GitHub issue:
https://github.com/ravindu644/Droidspaces-OSS/issues/19
❤7🥰1💩1
This is also one of my side projects, came way before Droidspaces.
To use
It even supports dynamic namespace isolation, hardware access, rootfs.img support, post-exec scripts as a replacement for init, running at boot even the device is locked and encrypted, etc.
Even though this is more primitive than the Droidspaces project, it still provides basic Linux on Android.
v4.4 was released with fixes related to BusyBox. From now on, we specifically use our custom BusyBox to perform certain shell operations.
https://github.com/ravindu644/Ubuntu-Chroot/releases/tag/v4.4
To use
ubuntu-chroot, you only need root access. No kernel configuration needed. It just works.It even supports dynamic namespace isolation, hardware access, rootfs.img support, post-exec scripts as a replacement for init, running at boot even the device is locked and encrypted, etc.
Even though this is more primitive than the Droidspaces project, it still provides basic Linux on Android.
v4.4 was released with fixes related to BusyBox. From now on, we specifically use our custom BusyBox to perform certain shell operations.
https://github.com/ravindu644/Ubuntu-Chroot/releases/tag/v4.4
🥰1💩1
Added an official guide on how to compile a kernel with Droidspaces support for any GKI device:
https://github.com/ravindu644/Droidspaces-OSS/blob/main/Documentation/Kernel-Configuration.md
You can now compile the kernel just like a legacy non-GKI kernel and flash only the boot.img or compiled kernel Image, without worrying about ABI or LKM compatibility 🥳
@Droidspaces
https://github.com/ravindu644/Droidspaces-OSS/blob/main/Documentation/Kernel-Configuration.md
You can now compile the kernel just like a legacy non-GKI kernel and flash only the boot.img or compiled kernel Image, without worrying about ABI or LKM compatibility 🥳
@Droidspaces
🔥5❤4😁1💩1🗿1
Droidspaces
:)
Initial guide:
https://github.com/ravindu644/Droidspaces-OSS/blob/main/Documentation/Cool-things-you-can-do.md
Will add hardware hacking as well in near-future :)
https://github.com/ravindu644/Droidspaces-OSS/blob/main/Documentation/Cool-things-you-can-do.md
Will add hardware hacking as well in near-future :)
🗿3💩1
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