Adguard causing phone reboot on Android 10
- Thread starter OMGJJ
- Start date
hohokus
New Member
i've also switched to blockada on 2 android 10 devices with zero reboots over the past 7 days. certainly doesn't appear that all VPNs are having this issue.
"it's an android problem" and closing the ticket (https://github.com/AdguardTeam/AdguardForAndroid/issues/3096) is a pretty weak support response for a paid product.
Last edited:
hohokus
New Member
thanks, that helps. can you confirm that android 10 is an officially supported platform for adguard? if it is, "it's a google issue" is an unsatisfactory response, regardless of where the fault lies. if it isn't, then adguard isn't certified to work on the latest android OS, which is probably worse.
i suppose at this point, i'm just trying to gauge how long paying customers are supposed to accept the situation with no workaround and no ETA.
Kevin mc
New Member
I'm in the same boat and quite aggravated that another VPN works fine, different API or not. Im guessing because users on Android 10 are a tiny fraction of the entire user base...we just aren't a priority. I will continue to monitor the situation but I've grown quite comfortable over the last few months using another effective adblocker, lifetime subscription to Adguatd or not.
If Google doesn't fix, AdGuard has to find a workaround. There must be an alternative for Android 10 users.
Sooner, more and more phones will be migrating to this version.
I am still keeping to my premium AdGuard. I thought of subscribing to a few more licenses but this issue is stopping me for now.
D
Deleted member 29773
Guest
unfortunately i can confirm that the reboots are also available with the december patch on my pixel 3a...
Master Li
New Member
I am really disappointed. Two and a half month, nothing happened. I did pay for this software. I expect it to run and not make my phone impossible to use. It took me some days to even find out, why there are spontaneous reboots.
Then I hear "sorry, not our fault" sounding more like "sorry, not our problem". You offer your software for android, I expect you to make it work as expected. As customer, I am not interested in "but the other one did something wrong". It is your software, discuss any problems with google and offer your customers a solution.
Then I hear "sorry, not our fault" sounding more like "sorry, not our problem". You offer your software for android, I expect you to make it work as expected. As customer, I am not interested in "but the other one did something wrong". It is your software, discuss any problems with google and offer your customers a solution.
It's an Android bug in Android 10 that only Google can fix. Google has already fixed it, but haven't pushed the fix out yet in a patch. AdGuard developers can't fix it on their side, or else they would've already. AdGuard for Android relies on the getConnectionOwnerUid VPN method, and that's where the bug is in Android 10. It affects ALL apps that use the getConnectionOwnerUid VPN method. Yes, there are other VPN methods but AdGuard for Android has to use getConnectionOwnerUid to know what apps are trying to establish connections, which is VERY important for AdGuard for Android so it can function.
I hate to say it but you just gotta wait until Google finally pushes the fix out in a monthly patch, that's really all that can be done at this point. You guys probably should contact Google and request they push the fix out in a patch, but I suspect it may fall on deaf ears (or just get canned responses) until they decide to push it out.
I hate to say it but you just gotta wait until Google finally pushes the fix out in a monthly patch, that's really all that can be done at this point. You guys probably should contact Google and request they push the fix out in a patch, but I suspect it may fall on deaf ears (or just get canned responses) until they decide to push it out.
Master Li
New Member
I already understood before. But I never heard that adguard is in contact with google and is trying to make this happen*. If you do, I'm fine, but all I read was, we have to wait for it an it sounds a lot like "and we are waiting, too"
* surely not easy for adguard to argue with a big player like google, but that is, what i would expect from you as your customer
* surely not easy for adguard to argue with a big player like google, but that is, what i would expect from you as your customer
There's nothing to contact about, if you read the issue here you'll see that the Android team confirmed the bug and have pushed a fix. It's been fixed for two months now but they've yet to push the fix out. They know about it, they fixed it and they decide when to release the fix.
I doubt the AdGuard team trying to contact Google about issuing the fix in a patch would get anywhere. Considering how AdGuard for Android can't be in the Play Store (aka persona non grata) I doubt they'd even respond or just get a canned response back. AdGuard (the company) just isn't big enough to get Google's attention that way. Maybe if other major VPN services like PIA or NordVPN had the same issue they could make noise about it, but even then I doubt that'd force Google to release a patch any quicker. The ball's in Google's court now, and they're just holding onto it until they choose to release it. It's really annoying actually, that Google can't release a timely fix like that, but I guess they don't really consider it as that important to release it sooner?
I doubt the AdGuard team trying to contact Google about issuing the fix in a patch would get anywhere. Considering how AdGuard for Android can't be in the Play Store (aka persona non grata) I doubt they'd even respond or just get a canned response back. AdGuard (the company) just isn't big enough to get Google's attention that way. Maybe if other major VPN services like PIA or NordVPN had the same issue they could make noise about it, but even then I doubt that'd force Google to release a patch any quicker. The ball's in Google's court now, and they're just holding onto it until they choose to release it. It's really annoying actually, that Google can't release a timely fix like that, but I guess they don't really consider it as that important to release it sooner?
Disclaimer: I'm not a member of the AdGuard team, I'm just another user like you guys are, except I help deal with SPAM bots on the forums here and I volunteer my time to try to help people, that's it. I've been doing beta testing for several commercial apps (including AG for Windows, Mac, Android and the browser extensions) for years now. I also encounter an issue kinda like this one in Android 9 where I can't switch from a Wi-Fi connection to mobile data (or vice versa) when using AdGuard for Android or else the phone immediately reboots. Andrey looked into it for me months ago and found it was an issue in my phone's firmware. Since I actually doubt I'll ever get a firmware update for the phone, I have to live with that issue and make sure I pause AG for Android before switching from Wi-Fi to mobile (or vice versa). So I get how annoying phone reboots like that are.
And I know how frustrating it can be to wait when dealing with a dealbreaker issue like this. I've seen companies (I'm looking at you Microsoft) drag their heels at pushing fixes in a timely manner. Look at how many times Google's Project Zero disclosed details on vulnerabilities when companies haven't yet pushed a fix yet within the 90 day window. What's even worse? Companies (again, looking at you Microsoft) pushing half-baked updates and fixes that only either not work correctly or just simply break more stuff. There's still bugs in Windows 10 that hasn't been fixed for the longest time. If it was an issue in an AdGuard app that could be fixed or worked around, they would've done so already. The AdGuard developers/team are at the top of my list of software companies that take bug reports like that seriously (I mean, look at the amount of the hotfix releases they've done after major version releases for sometimes major issues that need fixed ASAP). I've reported countless bugs, some pretty bad (or annoying) ones and they've issued fixes for them pretty quickly in a timely manner. So if they say they can't workaround the issue and that only Google themselves can fix it, then I believe them.
I don't really know why Google hasn't pushed the fixed out yet. If I had to guess, based on experience testing and talking with software developers, the severity of the bug wasn't high enough to warrant an expedited patch in an update that was released as soon as possible. My guess it's at a lower severity so a patch is 'delayed' with higher severity bug fixes being pushed first.
And I know how frustrating it can be to wait when dealing with a dealbreaker issue like this. I've seen companies (I'm looking at you Microsoft) drag their heels at pushing fixes in a timely manner. Look at how many times Google's Project Zero disclosed details on vulnerabilities when companies haven't yet pushed a fix yet within the 90 day window. What's even worse? Companies (again, looking at you Microsoft) pushing half-baked updates and fixes that only either not work correctly or just simply break more stuff. There's still bugs in Windows 10 that hasn't been fixed for the longest time. If it was an issue in an AdGuard app that could be fixed or worked around, they would've done so already. The AdGuard developers/team are at the top of my list of software companies that take bug reports like that seriously (I mean, look at the amount of the hotfix releases they've done after major version releases for sometimes major issues that need fixed ASAP). I've reported countless bugs, some pretty bad (or annoying) ones and they've issued fixes for them pretty quickly in a timely manner. So if they say they can't workaround the issue and that only Google themselves can fix it, then I believe them.
I don't really know why Google hasn't pushed the fixed out yet. If I had to guess, based on experience testing and talking with software developers, the severity of the bug wasn't high enough to warrant an expedited patch in an update that was released as soon as possible. My guess it's at a lower severity so a patch is 'delayed' with higher severity bug fixes being pushed first.
hohokus
New Member
so -- at present, adguard does not work on android 10. period. until google <does something> or adguard <does something>, it does not work on android 10.
there were over 10 million pixel 3 devices sold. pixel 4 was just launched. the android 10 user base will continue to grow.
paid software comes with some expectation of support by the vendor, not hand waving and finger pointing. asking paying end users to plead with google is nonsense -- that's adguard's job.
there were over 10 million pixel 3 devices sold. pixel 4 was just launched. the android 10 user base will continue to grow.
paid software comes with some expectation of support by the vendor, not hand waving and finger pointing. asking paying end users to plead with google is nonsense -- that's adguard's job.
I'm afraid pleading with Google would be like pleading on deaf ears. All they'd likely say is they fixed the issue already and wait for the fix to be pushed in a monthly patch. AdGuard (the company) can't dictate to Google to release their fix faster, it doesn't work that way. To them a small company like AdGuard is insignificant or worse they would simply consider them a hindrance to their livelihood, since they do block Google's ads after all which denies Google that revenue, so why would Google do anything for them if they asked or inquired about it?
Ultimately it doesn't change anything... still have to wait until Google pushes the fix for it.
Ultimately it doesn't change anything... still have to wait until Google pushes the fix for it.
You paid Google for your Pixel device, which runs Google's Android OS which because you paid Google for said device, gets updates monthly. How's that any different?
Nonetheless, that's neither here nor there nor does it actually matter, like I said, it doesn't change anything.
I suspect if you root the device and use the local HTTP proxy option, this won't be an issue. But yes, I know, rooting isn't for everyone. Until then, gotta wait.
Nonetheless, that's neither here nor there nor does it actually matter, like I said, it doesn't change anything.
I suspect if you root the device and use the local HTTP proxy option, this won't be an issue. But yes, I know, rooting isn't for everyone. Until then, gotta wait.
Google has already fixed it, we are waiting for them to ship the fix to Android users.
There is plenty of apps that use this method. Orbot (Tor), for instance. The thing is that it might be not that important to a regular VPN app as it is to AdGuard. Anyways, I've just filed another report to Google asking them to ship the fix with a security patch and not wait for 10.1. Hopefully, they will listen (I'll post here once I receive any response).
Also, it seems we have no choice and we'll have to implement some mitigation mechanisms in the v3.3 release (which is planned for the middle of December). We won't fully solve this issue (not using that part of the API would make AdGuard a simplistic blocker like Blokada, and we don't want that), but we'll make this "soft reboot" issue happen considerably less often.
I have asked this before and I want to ask again.
This method is being used randomly throughout the day.
Why is the soft reboot happening almost periodically?