Азалия Смарагдова

I've tested it on my system, and it seems working fine. However, there are several use-cases I'm not sure about: * Systems that don't use AppArmor. I have added a...

Closing this in favor of #503, #504, #505 and #506.

Solved by allowing the **waydroid0** interface in the firewall.

AppArmor profiles from the original commit were breaking the Magisk root by preventing edits to /sbin. In order to fix that, I've added a read-write access rule for /sbin to...

Force-pushed in order to resolve a conflict.

These profiles were written for Android 10, and they seem to cause issues on Android 11 if they are in **enforce** mode. I'll try to figure out the issues and...

OK, I have modified the profiles to fit Android 11. The new policies work fine for me in **enforce** mode.

Force-pushed in order to resolve conflict.

I checked today -- the waydroid session doesn't start if write access to ```waydroid.log``` is denied, but write access to other files and directories can be made for root only.

So, the Makefile should just copy the profiles? (I think that if a user installs a packaged Waydroid, the profiles are loaded by ```postinst```, but if a user installs it...