-
-
Notifications
You must be signed in to change notification settings - Fork 563
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
Enable/Disable bug #4065
Comments
I was just about to post a bug about this, I also experience this, and often. I use a Google Pixel 7, on Android 14, all stock no root |
This issue is affecting me as well. My use case is that I use quick settings tiles to connect to different VPNs depending on my needs (Adaway, PIA, OpenVPN). The reproducible steps are:
When I open the Adaway app, it shows Adaway is active with the pause icon on the bottom. The only reliable way to enable Adway again is if I disable/enable from inside the app. Sony Xperia 1 V |
When I've noticed this happening, it usually occurs when the VPN is active in the background, and then checks for/installs (or attempts to check for/install) updates to the sources. |
Is there an existing issue for this?
Current Behavior
Hello. I've noticed that since the previous update, AdAway will randomly disable itself based from the notification bar information. I'd open the app and it appears as if it's enabled so I'd have to disable and re-enable it. I have the AdAway settings: Enable At Startup & Monitor Connection enabled.
Also, I have noticed that each time I click the button to update the default lists, it will continue to show that there are new updates for them. I added 3 new lists and the same thing occurs. I'm unsure whether the lists actually get updated or not. Every 2-3 hours I'd do the same update process again and it continues that there are new list updates.
Expected Behavior
If this is an unexpected bug, I'd like for the developer to investigate it. I don't trust other Android ad blockers, only Ad Away. Thank you.
Steps To Reproduce
No response
Device Configuration
Additional context and screenshots
No response
The text was updated successfully, but these errors were encountered: