Droidspaces

[ Explanation ] @Droidspaces

LET'S PLAY DOOM ! 🗿

I had an external WiFi adapter lying around. I enabled its driver in the kernel, recompiled it, placed the WiFi firmware in recovery_ramdisk/vendor/firmware, and wired it up via /sys/module/firmware_class/parameters/path Result: Out-of-the-box wlan0, the moment it's plugged in..! This phone has 2GB RAM, 16GB storage, and a Qualcomm SoC scoring ~150 (single-core) and ~450 (multi-core) on Geekbench. Look at this htop screenshot - even this weak potato sits at 0% CPU idle! 🥔 On Android, idle CPU usage hovers around 30–50% for absolutely nothing. This is Alpine Linux, booted directly from a lightweight TWRP recovery environment, with full networking. Most people see these phones as phones. I see them as Android slapped on top of an ARM64 development board🗿 So I nuked Android and used that space for a lightweight Linux container instead. @Droidspaces

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:

- 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

just figured out we can directly mount the partition using the -i flag too !

> 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

how about putting him in the welcome screen?

I guess something like this doesn't fit the topic...?

Any logo ideas for the App/Group PFP ? I'm using a generic container icon for now, but it's not unique

Well, run docker inside Android recovery wen ?

GOT WIFI WORKING ON TWRP !! 🗿 Connection established Just purely based on Linux tools 🥳

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 !

Let's run fully interactive systemd from TWRP 🗿 @Droidspaces

Pass !

LEMME INSTALL A SSH SERVER INSIDE TWRP-

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?

Let's Run Linux Containers with Droidspaces on Android recovery 🗿 7.2G FREE RAM !!! 🥹❤️

Uptime 🗣

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 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

New option for OverlayFS users 🤡 explanation