Droidspaces
Let's Run Linux Containers with Droidspaces on Android recovery 🗿 7.2G FREE RAM !!! 🥹❤️
Well, let's ping Google from TWRP recovery 🗿
Everything is working out of the box; I'm using host networking mode.
So, Alpine's udhcpc can assign an IP to our newly plugged eth0 interface :)
Let me ask a question: can whacky Docker/LXC setups do this?
Everything is working out of the box; I'm using host networking mode.
So, Alpine's udhcpc can assign an IP to our newly plugged eth0 interface :)
🗿4💩1
Droidspaces
Let's run fully interactive systemd from TWRP 🗿 @Droidspaces
well, networking isn't that hard.
all you have to do is, run the container inside twrp/recovery,
plug the ethernet,
container's systemd-networkd/dhcpd will handle everything.
out of the box !
all you have to do is, run the container inside twrp/recovery,
plug the ethernet,
container's systemd-networkd/dhcpd will handle everything.
out of the box !
🔥5💩1
GOT WIFI WORKING ON TWRP !! 🗿
Connection established Just purely based on Linux tools 🥳
Connection established Just purely based on Linux tools 🥳
😱7⚡2👍2🔥2🗿1
Any logo ideas for the App/Group PFP ?
I'm using a generic container icon for now, but it's not unique
I'm using a generic container icon for now, but it's not unique
💩1
Droidspaces
Any logo ideas for the App/Group PFP ? I'm using a generic container icon for now, but it's not unique
I guess something like this doesn't fit the topic...?
😁1💩1
Droidspaces
I guess something like this doesn't fit the topic...?
how about putting him in the welcome screen?
❤4💩1
> Found an old phone.
> Cooked the kernel.
> Replaced the kernel in TWRP.
> Booted into TWRP.
> Pushed the Droidspaces binary and the Alpine rootfs to TWRP's /tmp.
> Booted into Alpine.
> Fired up parted.
> Nuked all the Android-related partitions like super, prism, optics, omr, userdata, etc.
> From the unallocated space, created a new userdata partition.
> Formatted it as ext4.
> Mounted the newly created, formatted partition.
> Moved Alpine to it.
> Booted again.
> This is it!
No Android, no bloat. Just booted Linux via Android recovery, with 13.44GB of free space, 0% used space, and 173MB used RAM out of 1.8GB 🗿
Lemme hack init to auto-boot the Droidspaces container on boot lmao
@Droidspaces
> Cooked the kernel.
> Replaced the kernel in TWRP.
> Booted into TWRP.
> Pushed the Droidspaces binary and the Alpine rootfs to TWRP's /tmp.
> Booted into Alpine.
> Fired up parted.
> Nuked all the Android-related partitions like super, prism, optics, omr, userdata, etc.
> From the unallocated space, created a new userdata partition.
> Formatted it as ext4.
> Mounted the newly created, formatted partition.
> Moved Alpine to it.
> Booted again.
> This is it!
No Android, no bloat. Just booted Linux via Android recovery, with 13.44GB of free space, 0% used space, and 173MB used RAM out of 1.8GB 🗿
Lemme hack init to auto-boot the Droidspaces container on boot lmao
@Droidspaces
🔥11🆒6💩1😎1
Droidspaces
> Found an old phone. > Cooked the kernel. > Replaced the kernel in TWRP. > Booted into TWRP. > Pushed the Droidspaces binary and the Alpine rootfs to TWRP's /tmp. > Booted into Alpine. > Fired up parted. > Nuked all the Android-related partitions like super…
just figured out we can directly mount the partition using the -i flag too !
❤1💩1
Droidspaces v5.9.5 is here ! 🥳
This release brings a significant step forward in portability and compatibility.
Droidspaces can now run on virtually anything, including Android recovery environments and ramfs-based systems, making it more flexible than ever before 🗿
GKI kernel users will also be happy to hear that Droidspaces is now integratable on GKI kernels without breaking the GKI ABI :)
Hard-coded cgroup device and devtmpfs requirements have been removed entirely. The only kernel requirements now are PID Namespaces and IPC Namespaces. Documentation will be updated to reflect this change shortly.
🗒 What's new in v5.9.5:
Full changelog and Downloads:
https://github.com/ravindu644/Droidspaces-OSS/releases/tag/v5.9.5
[Download directly from Telegram]
@Droidspaces
This release brings a significant step forward in portability and compatibility.
Droidspaces can now run on virtually anything, including Android recovery environments and ramfs-based systems, making it more flexible than ever before 🗿
GKI kernel users will also be happy to hear that Droidspaces is now integratable on GKI kernels without breaking the GKI ABI :)
Hard-coded cgroup device and devtmpfs requirements have been removed entirely. The only kernel requirements now are PID Namespaces and IPC Namespaces. Documentation will be updated to reflect this change shortly.
🗒 What's new in v5.9.5:
- Android recovery environment support
- Removed hard-coded cgroup device and devtmpfs checks, reducing kernel requirements to PID and IPC Namespaces on GKI
- Backend and app: added a new option to mirror GPU nodes, even without the hardware access module
- App: moved symlink creation to SymlinkInstaller with a settings toggle, resolving bootloops for OverlayFS meta module users
- Fix: added a 10-second stability delay after network readiness detection in boot scripts
- Mount: replaced host tool calls with pure-C loop device management
- Mount: enabled Btrfs rootfs image support and restricted support to known filesystem types
- Fixed host detection when running on aarch64 Linux environments such as Armbian
- Fixed logs not appearing in the terminal within internal_boot()
Full changelog and Downloads:
https://github.com/ravindu644/Droidspaces-OSS/releases/tag/v5.9.5
[Download directly from Telegram]
@Droidspaces
🔥10💩1