Adguard causing phone reboot on Android 10
- Thread starter OMGJJ
- Start date
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.
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.
@avatar
I just read the latest status update of the GSI request you filed at Googles issue tracker.
What does that mean now? First he said it will be available as part of QPR2 which would mean in March, but then he said it was merged right now.
So will it come with the next security update or do we have to wait until March?
Im not sure if I read it correctly, but here it looks like he abandoned it first but then changed his mind and decided to ship it?
I just read the latest status update of the GSI request you filed at Googles issue tracker.
What does that mean now? First he said it will be available as part of QPR2 which would mean in March, but then he said it was merged right now.
So will it come with the next security update or do we have to wait until March?
Im not sure if I read it correctly, but here it looks like he abandoned it first but then changed his mind and decided to ship it?
So how is the nightly beta? Did anyone try it?
jack24254029
New Member
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.
Last edited:
jack24254029
New Member
My pixel 4 occurred reboot on 12/27/2019.
jack24254029
New Member
I have updated my Pixel 4 today.
I will keep observe software reboot.
Corey W Dimick
New Member
Any updates yet? I miss Adguard!
I wonder what mitigation was done. Is there anything that is compromised? ie performance?
It's true I did not encounter any reboot after the latest AdGuard update.
The latest AG update does help.
I have not gotten a reboot so far.
As for Google fix, I doubt so. Otherwise, AD staff would have made an announcement here.
That's why I emphasize that a mitigation is necessary instead of relying on Google fix.
BobbyPhoenix
Member
I'm over 60 hours uptime so far, and no issues.
The mitigation can only do so much, it'll minimize the issue but not fix it. Google already did a fix and *hopefully* it's in this security patch for January, but if not likely February.
Well, Google already fixed it, so let's hope it's in the January patch. The AdGuard team/devs are all on vacation, hence why there's been radio silence on if this is fixed in the January patch or not.
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.
Well, Google already fixed it, so let's hope it's in the January patch. The AdGuard team/devs are all on vacation, hence why there's been radio silence on if this is fixed in the January patch or not.
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.
Oh OK I will try to disable that and feedback.