1. Run the daemon via Magisk/Apatch/KernelSU modules' native
post-fs-data.sh. By enabling the toggle in the app, you activate the logic in the post-fs-data.sh of the Droidspaces Magisk module to run the daemon on boot. For 99% of users, this solves all issues with Magisk and Apatch. No modifications to your vendor.img are needed.
2. Run the daemon via Android's native init.rc:
- This mode is the most privileged and completely independent of Magisk/Apatch/KernelSU. It even works without any root solutions.
- The daemon is unkillable. If something kills it, init will automatically respawn it.
- Run-at-boot containers are unkillable as well. If droidspacesd gets killed, once init restarts it, run-at-boot will also restart all killed containers.
I don't think Android will ever kill the daemon, but even if it does, all edge cases are covered—thanks to my overthinking 🗿
Notes: If the native init daemon is enabled, the app's toggle will be automatically enabled. The
post-fs-data.sh script will auto-detect if the native init.rc daemon is running, so no collisions will happen if it is.Everything is backward compatible. You don't even need to worry about daemons if everything is already working for you 🗿
Nothing bad will happen; the binary still supports running everything natively, with or without a daemon 🗣
There are three different logics baked into the same binary:
- Daemon
- Client for the daemon
- Native execution if no daemon is running