-
Notifications
You must be signed in to change notification settings - Fork 98
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AdGuard does not create a local VPN. Protection does not start #4269
Comments
@Daviteusz it's because the "Kill switch" is enabled. You need to disable it for AdGuard VPN and enable it for AdGuard |
@maxikuzmin Restore the old title, because now it is wrong I did not have Adguard VPN enabled, I just had it installed. After killing the Adguard, it started working again until next device reboot. Android 12+ has some problems with the permissions controller (removes granted permissions after tens of minutes or hours, or reboot) Several users have already reported this problem when I spoke to them about it. Problem not occurs on A11. |
@Daviteusz let's take a look at your logs, go deeper into the situation. I don't have this on repeat. Did you confirm the setup of a local VPN during the installation?
|
I had the same problem on my Pixel 6 Pro. Reboots didn't help. Swiping AdGuard didn't help. |
@latsson can you also send the logs using the instructions I wrote above? |
@maxikuzmin Sorry, I switched back to android 11, and I can't reproduce this issue for now. Maybe @latsson will send needed logs. |
@latsson any news? |
@Daviteusz has the problem not happened again? |
@Daviteusz @latsson for the moment, I’m closing this issue. You can reopen the issue in the future if the problem persists |
The problem repeated, I sent logs to email. I can't reopen issue. |
@Daviteusz okay, we will check it |
@Daviteusz check that you don't have a VPN profile in the system settings, in the VPN section. If there is one from Adguard, uninstall it and try to run it again |
@maxikuzmin When protection can't start, the VPN profile is not present there. Killing the app helps, but after several device reboot the problem comes back again. I also tried reinstalling adguard, configuring cleanly, but it didn't help and problem returned after several device reboots. |
@Daviteusz we need some time, please wait a little longer |
@Daviteusz probably a problem with the OnePlus firmware. Doesn't sound like our problem. We don't control the state of the system window, we just request it from the OS. If it doesn't appear, the issue is with the firmware manufacturer. Try updating the firmware to the latest version if the manufacturer has released the appropriate firmware |
OxygenOS11-13 (Android 11-13):
A11 Custom Roms (OOS11 FW):
Custom Roms A12-13 (OOS11 or 12 FW)
Custom Roms A13 QPR1 (OOS12 or 13 FW)
The problem also occurs on other devices I tested:
It seems to be a problem of AOSP android 12 and 13 (before QPR1). |
@Daviteusz hello! If this looks like an AOSP issue, you'd better report the issue to the Google team: https://issuetracker.google.com/issues/new Highly-likely they'll ask you to get a bugreport. You can follow this instruction: https://kb.adguard.com/en/android/solving-problems/logcat#capture-a-bug-report-from-a-device or use the BTW can you check this issue with other VPN apps? |
@Daviteusz we solved your problem in the 3.6.11 Beta 1 update. Please update to this version and check it out. Let us know the result |
@Daviteusz any news? |
@Daviteusz you are right, this problem is because of your firmware. You need to send a bug report to them. |
Sorry I never replied. I haven't used Github in a while 😄 |
Prerequisites
Please answer the following questions for yourself before submitting an issue. YOU MAY DELETE THE PREREQUISITES SECTION.
Issue Details
Expected Behavior
Enabling protection and VPN serviceActual Behavior
Protection does not start, and neither does the VPN service.
Screenshots
Screenshot:
screen-20221105-163939.mp4
Additional Information
The notification shows:
Preparing to start protection. Please wait...
The text was updated successfully, but these errors were encountered: