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