Adguard causing phone reboot on Android 10

BobbyPhoenix

New Member
I recall the uptime doesn't reset if the phone rebooted by itself.

The uptime will reset if force reboot by user.
Didn't know that. Thanks. I haven't noticed any reboots, so I think it's accurate. When the reboot happens I have to unlock the phone for AdGuard to start, and then I'll see the VPN key icon in the notification bar. If I don't unlock it AdGuard won't start until I do (at least that's the way it used to be), so either I'm lucky with it rebooting when I'm not using the phone, and AdGuard is now starting on its own before I unlock the screen, or it's not rebooting at all. I'm happy either way since it's been that long without issues while using it.
 

BobbyPhoenix

New Member
Just a quick update. Had a reboot a couple minutes ago. First one is over a week. DPSK is correct as the uptime didn't reset, and my theory of it not rebooting in that time also seems to be correct. AdGuard didn't start until I unlocked the lockscreen. I waited almost ten minutes, and as soon as I unlocked it, AdGuard started, and the VPN key showed, so I went 220 hours between reboots. I can deal with that until Google pushes the fix.
 

DPSK

New Member
So the mitigation done by AG helps to reduce the frequency of reboot.

Is there a compromise of performance by this mitigation?

If no compromise, why can't the mitigation eliminate the reboot completely?
 

avatar

Administrator
Staff member
Administrator
Is there a compromise of performance by this mitigation?
Nope.

If no compromise, why can't the mitigation eliminate the reboot completely?
The root cause (abandoned descriptors) accumulate with time every time AdGuard detects what app makes a connection.
The mitigation is that for some connections (for instance when we see that this is a DNS port) AdGuard does not call the detection method, but for others, it still does so abandoned descriptors still accumulate.
 

avatar

Administrator
Staff member
Administrator
It seems that Google had deployed the fix in the January update.

However, I heard that some people are still experiencing random reboots.
I couldn't confirm that this is the same bug, though (Android 10 is pretty buggy by itself).

If this happens to you after the January patch, please capture the Android bug report and send it to us so that we could look inside and see what exactly has happened.

1. Capture the bug report: https://developer.android.com/studio/debug/bug-report
2. Send it to devteam@adguard.com
3. Mention this forum thread in the email
 

DPSK

New Member
The root cause (abandoned descriptors) accumulate with time every time AdGuard detects what app makes a connection.
The mitigation is that for some connections (for instance when we see that this is a DNS port) AdGuard does not call the detection method, but for others, it still does so abandoned descriptors still accumulate.
I see thanks for the clarification.

Now it is much clearer.

Good news is, I have not gotten a reboot since my encounter on the 12/Jan by enabling the mitigation feature.
 

StrykerJC

New Member
I registered just to express my sincere gratitude for all the informative comments on this thread. I've got a Pixel 2 phone running Android 10 and the random reboots have been driving me crazy. Every other site I was visiting was suggesting a factory reset to fix, but I prefer not to do the nuclear option without at least trying to determine the cause first.

My reboots were happening at least once a day, if not more often. They were even happening overnight, which rendered my use of the phone as an alarm clock as unreliable at best.

So, I found this thread and upon disabling Adguard, the reboots seem to have stopped. Furthermore, the latest build that I got via the app update includes the mitigation option. So far (fingers crossed), I've not had a single spontaneous reboot since installing that build. Hopefully the impending Android fix will be here soon, but for the time being I'm enjoying full Adguard functionality on a much more stable and reliable device.

Thank you, all, for contributing to this discussion. It's been most helpful, and I do appreciate it.
 

DPSK

New Member
I've got a Pixel 2 phone running Android 10 and the random reboots have been driving me crazy. Every other site I was visiting was suggesting a factory reset to fix, but I prefer not to do the nuclear option without at least trying to determine the cause first.
lol I like your nuclear adjective word.

I agree factory resetting is really the stupidest thing to resolve any potential problems.

I have used 5X -> Pixel 1 -> Pixel 2 -> Pixel 4.

I think I have to resort to factory reset once or twice only. Once during after the firmware update of Pixel 2 to Android 10.

Anyway, I am happy that the mitigation option has fixed my random reboot.
 

StrykerJC

New Member
I registered just to express my sincere gratitude for all the informative comments on this thread. I've got a Pixel 2 phone running Android 10 and the random reboots have been driving me crazy. Every other site I was visiting was suggesting a factory reset to fix, but I prefer not to do the nuclear option without at least trying to determine the cause first.

My reboots were happening at least once a day, if not more often. They were even happening overnight, which rendered my use of the phone as an alarm clock as unreliable at best.

So, I found this thread and upon disabling Adguard, the reboots seem to have stopped. Furthermore, the latest build that I got via the app update includes the mitigation option. So far (fingers crossed), I've not had a single spontaneous reboot since installing that build. Hopefully the impending Android fix will be here soon, but for the time being I'm enjoying full Adguard functionality on a much more stable and reliable device.

Thank you, all, for contributing to this discussion. It's been most helpful, and I do appreciate it.
Update: I've still not experienced a spontaneous reboot since updating AdGuard. I'll be glad when the underlying fix in Android 10 is pushed out, but am certainly thankful for the interim fix from the AdGuard devs.
 

StrykerJC

New Member
I know it is early but the February update (for Android 10) was just released. Does it contain any fix for this?
I got the February update installed yesterday afternoon, but don't know quite how to look to verify if this specific fix is included in any update.

There are reports in this thread that the fix was in the January update, but I was still getting spontaneous reboots after receiving that update. It wasn't until the last week in January before I got the updated version of AdGuard that included the mitigation option before my rebooting issues stopped.
 

tox1c90

Beta Tester
Had a reboot again on my Pixel 3a, latest February update and latest Adguard with mitigation enabled.
Woke up in the morning and had the "You need to enter a PIN after reboot" screen and Adguard was disabled, but started automatically a minute later.

I immediately collected the Android log and will send it to you (later today when I have more time).

Before mitigation I had reboots every 2 days, now it's like every 3 weeks. Are you really sure they released the fix in January?
 

Chinaski

Support Marine
Staff member
Administrator
Moderator
In my opinion, back in February, the mentioned fix was released and complaints about such an issue are stopped.
 
Top