uk
Feedback
Droidspaces

Droidspaces

Відкрити в Telegram
1 399
Підписники
+424 години
+507 днів
+14330 днів
Архів дописів
Should I try running doom now ?
Anonymous voting

Display on and off support, natively 🙈 This is Linux phone now

Even under xfce, 1.31GB Available memory out of 2GB
Even under xfce, 1.31GB Available memory out of 2GB

This is how the Linux shuts down

This is how it boots - 0 user interactions. systemd boots -> fires up the GUI 🔥 You know what the fun part is ? my method is universal and requires 0 source code compilation for Linux.

Fixed the freaking keyboard, mouse, and touch! Full Linux, booted on a phone, no Android, no apps, real display output, I didn't even compile any ROMs, did with all the resources already available in every phone, even doable on stock recovery. We just need brains.

Still, the keyboard mouse is dead, but it's still a huge achievement. I just installed xubuntu core. Then, the kernel panicked due to over heating. When the phone boots up, it showed systemd boot logs, then straight up booted into GUI 💀💀💀

Hard work pays off 🔥 Accidentally booted desktop environment using my crappy project on android recovery 💀
+1
Hard work pays off 🔥 Accidentally booted desktop environment using my crappy project on android recovery 💀

PC 🗿
+1
PC 🗿

+1
Systemd + Droidspaces + Native display out #PoC

:)
:)

Demonstration 🔥

Droidspaces OS wen ? 😳
+1
Droidspaces OS wen ? 😳

Proof of concept. Booting Linux from Android recovery with direct display output. Works in stock recoveries, too.
Proof of concept. Booting Linux from Android recovery with direct display output. Works in stock recoveries, too.

Direct display output 💀 Basically, another way to run Android on Linux 😌
Direct display output 💀 Basically, another way to run Android on Linux 😌

Guyss.. I have a good news 👀 regarding X11 :)

Okay. new option..! Testing: https://t.me/DroidspacesCI/
+1
Okay. new option..! Testing: https://t.me/DroidspacesCI/

🧱
🧱

Do you want a "Privileged/F*ck Security" mode? Runs the container with zero restrictions: no seccomp, no cap drops, no masking, just execute init with maximum permissions. Perfect for recovery mode!
Anonymous voting

Final update for the ~200MB RAM Galaxy A01 Droidspaces setup 🗿 The key difficulty with this setup was that you had to hold the recovery key combination every time you wanted to enter TWRP, manually type Droidspaces CLI commands to start the container, and if the phone was plugged into a charger while powered off - it would bootloop forever since there's no Android left to show a charging animation. Here's how I solved all of that: - Flashed recovery.img directly to the boot partition, making the device boot straight into TWRP by default; no key combos needed - Since flashing to the boot partition means Android's init now executes TWRP's init binary on charger detection, I patched TWRP's main init.rc to trigger a clean reboot whenever a charger is connected while the device is powered off, which boots straight into TWRP - Wrote a simple init.rc service called "alpine" that automatically starts the Alpine Linux container right after the Droidspaces daemon is ready - meaning Alpine boots automatically as part of the TWRP boot sequence - Wrote an OpenRC service that watches for the wlan0 interface, brings it up, connects to the WiFi network, and assigns an IP - running as a daemon forever, handling hotplug and reconnection automatically Final result: a fully functional Raspberry Pi-like device that powers on the moment a charger is detected, auto-boots Linux, and fires up SSH, Tailscale, and WiFi - all with only ~200MB of RAM usage. This is what I call a proper server 🗿 [ Demonstration, init Script ] @Droidspaces