In the latest CI build, we are moving from the magisk SELinux domain in Magisk/Apatch to our own droidspacesd domain to maintain compatibility with daemon mode in post-fs-data.sh

That means even if the binary is run under Magisk’s SELinux domain, we re-execute ourselves to run under our own SELinux domain, completely bypassing magisk domain restrictions.

We also have over ~200 lines of custom SELinux rules, specifically written for magiskpolicy, which we inject via post-fs-data.sh :)

https://github.com/ravindu644/Droidspaces-OSS/blob/main/Android/app/src/main/assets/boot-module/etc/droidspaces.te

TL;DR: we have our own permissive SELinux domain, completely independent from Magisk/APatch/KernelSU domains, giving us more freedom.

Also, all processes spawn under our droidspacesd domain. Even systemd inherits our permissive domain, meaning no denials can occur.

TL;DR: you can use Droidspaces in SELinux enforcing mode with 0 issues when using the boot-module daemon mode. No need to wire up an init.rc service.

This is the build:
https://github.com/ravindu644/Droidspaces-OSS/actions/runs/23706897589/artifacts/6165166335

According to my testing across 3 phones, everything seems normal for me.

But I suggest you guys test it and report if there are any issues. Especially, I recommend testers to drop a bug report even if there are no issues present, so I can cover all the edge cases.

Here's how:

1. Install
2. Enable daemon mode from settings
3. Reboot the device
4. Generate the bug report and drop it in the chat.