Here are two updates.
1. As @Boo Berry just mentioned, we added a mitigation mechanism to the AdGuard v3.3 nightly (and beta). It does not fully solve the issue, but it will make them occur less often.
2. And here are some good news: the fix will most likely be included in the next security patch. It appears that once the bug is fixed, you need to file a new one and explicitly request Google to add it to a security patch. Currently, the pull request with this fix is in review and once it's merged it will be in the security patch finally.
Yes, I tried it.So how is the nightly beta? Did anyone try it?
My pixel 4 occurred reboot on 12/27/2019.Yes, I tried it.
My Pixel 4 didn't occur reboot when I installed AdGuard 3.3 nightly on 12/18/2019 .
So I think the problem maybe had be solved on software side.
I will keep observation it.
I have updated my Pixel 4 today.January Android update is available, hopefully it includes the fix this time.
Any updates yet? I miss Adguard!I have updated my Pixel 4 today.
I will keep observe software reboot.
I wonder what mitigation was done. Is there anything that is compromised? ie performance?Even if the January update doesn't include the fix, the latest version of AG for Android has a mitigation for this issue, making it more infrequent (and thus making it more usable now).
The latest AG update does help.24 hours stable connection.
Anyone checked if we got it fixed on Google latest updates (Jan)?
As for Google fix, I doubt so. Otherwise, AD staff would have made an announcement here.
Oh OK I will try to disable that and feedback.There is a setting in the low level settings to disable the mitigation for the reboot issue. A good way to test to see if this is indeed fixed in the January patch is to disable the mitigation in the low level settings then wait and see if it happens. If it doesn't, then it's probably fixed.