Droidspaces
New option for OverlayFS users 🤡 explanation
For more context: when installing the backend, we don't create the symlink by default. The user has the complete ability to control the symlink via a toggle.
This is my best solution for a problem that the overlayfs developers don't want to fix 👍🏼
IF you are a power user AND use magic mount, use this toggle to use Droidspaces with the
IF you are an overlayfs user, don't even enable this toggle.
Both users still have full backend access via
Testing: https://t.me/DroidspacesCI/83
This is my best solution for a problem that the overlayfs developers don't want to fix 👍🏼
IF you are a power user AND use magic mount, use this toggle to use Droidspaces with the
droidspaces command from adb shell/root shells.IF you are an overlayfs user, don't even enable this toggle.
Both users still have full backend access via
/data/local/Droidspaces/bin/droidspaces though.Testing: https://t.me/DroidspacesCI/83
💩1🗿1
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