Originally Posted by Akomack
You got Adaway to request root after this? I never had hide magisk checked. I'm still not having any luck getting Adaway to request root.
I have one of my Android 6.0.1 devices I have Adaway 4.26 installed. My other, same model devices have v3.3 installed with no problems.
Just out of curiosity about your problem, I went into Magisk Manager superuser page and clicked on the trash can icon to remove it from superuser permissions. Then when I launch v4.2.6, just like you, it does not ask for superuser permissions, even if I click on check for updates. However, if I click on disable ad blocking, I almost immediately get a new superuser request popup, which I approve, then I re-enable ad blocking and it works normally again. I'm not sure if this will help on your Android 10 device, but it is worth a try. To me this appears to be a bug, as I don't see this kind of behaviour on v3.3 on my other Nextbook Ares 8A's, x86, Android 6.0.1 tablets when su is revoked. When revoked in v3.3, I get an immediate su request when the app is relaunched. Please let us know if this works for you, or not.
The only major thing that is different on that v4.26 device is that I run SElinux switch app at boot to make the kernel permissive so that a modifed version of adbd insecure will run properly, to allow adb root access.
UPDATE: I thought I had updated this to the latest v4.2.9, but it was one of my other devices I did it on. I will download and do the same test on v4.2.9.
V4.2.9 has the same behavior on that device where it does not ask for su permission unless I click on the disable ad blocking button.
what kind of logs would be useful to troubleshoot this for you?