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

Added a new toggle to mirror GPU nodes, even without the hardware access mode.

There is no need to add bind mounts.

So, users don't have to worry about ruining the isolation by enabling hardware access just to use the GPU :)

A single toggle, and you're good to go 🗿

This is fire 🔥

Droidspaces is now on Weblate!

You can now help translate the Droidspaces Android app into your language - no coding skills required.
https://hosted.weblate.org/engage/droidspaces/

Just pick your language and start translating. Every contribution helps make Droidspaces accessible to more people around the world

Now, suggest a way to charge this thing 😄

My plan is to use another USB 3 adapter that has a Type-C port for power input, while plugging the UGREEN adapter into it.

The issue is that my existing adapter capable of doing that only has USB-A ports for inputs.

I'll have to buy a USB-C to USB-A adapter to plug in the UGREEN hub.

This is going to be some kind of human-centipede type of thing 🗿

Droidspaces v5.9.0 has been released..! 🥳

In this release,

we introduced a daemon, that supports two daemon modes: Native init.rc (lowest-level integration with auto-spawn/unkillable persistence) and Userspace Daemon (app-togglable, starts via post-fs-data.sh, no image modification required). Both modes bypass root-domain seccomp blocks to ensure stable container lifecycles.

Thanks to daemon mode, Magisk/APatch users can now use DroidSpaces without any issues!

Also fixed a lot of issues related to the Android app, including the built-in terminal, container configuration menu, etc.

Full changelog and release: https://github.com/ravindu644/Droidspaces-OSS/releases/tag/v5.9.0

Note: I'm actually taking a break from this. I'm planning to wipe out my entire development rig tonight. The app is stable now. Will continue cooking after some time. Peace.. :)

https://github.com/ravindu644/Droidspaces-OSS/discussions/27

@Droidspaces x @ravindu ❤️

I'm taking a temporary break from all my development work.

I'll release v5.9.0 today.

You won't hear from me on Telegram anymore. Any project-related questions should be directed to the admins in the discussion group.

I'll be back in a few months.

Documentation update:

Added native init.rc integration for Developers: https://github.com/ravindu644/Droidspaces-OSS/tree/main/init

Added 3 ways of using GPU Acceleration in Android, as well as documented about GPU Acceleration in Linux:

https://github.com/ravindu644/Droidspaces-OSS/blob/main/Documentation/GPU-Acceleration.md

Get native GPU acceleration on Adreno GPUs with Droidspaces..!

Requirements: Base/XFCE tarball from the latest GitHub release, Latest CI Build

01. Download the latest Base/XFCE tarball from the Droidspaces-rootfs-builder repository.

02. Install it using the Droidspaces app by enabling "Hardware Access" and "Termux X11", and add the environment variable DISPLAY=:0 in the environment variables section.

03. Start the container, then open the Termux app AFTER starting the container and run termux-x11 :0 to start the X server.

04. Done!

Additional: Using GPU acceleration with non-root users

05. Open a container root terminal and create a new user: newuser <username>

06. Add the newly created user to the sudo group: usermod -aG sudo <username>

07. Add the newly created user to the droidspaces-gpu group: usermod -aG droidspaces-gpu <username>

08. Log in to your new user and check GPU access with: glxinfo -B!

To start the XFCE in the XFCE tarballs: dbus-launch --exit-with-session startxfce4

@Droidspaces