This is it.
From now on, if someone says "Droidspaces broke my XYZ," "Droidspaces caused kernel panics when using HW access mode," or "I lost my job because of Droidspaces because the alarm app failed while using HW access," the issue will be instantly closed.
The container is yours. You control it, not me.
Edit:
Nuked the old release and re-released it under the same release tag with the HW access gate 👍
Post #372
528
Droidspaces Starting from v6.1.0, we stopped masking systemd-udevd and systemd-udev-trigger in post-extract-fixes.sh, and allowed udevd to access 5 subsystems. ( usb, block, input, tty, net ) this is the exact feature that finally allowed real hardware access. before…
- 😁 14
- ❤ 1
- 💩 1