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
Restore the Assistant functionality in AdGuard v4.0 #4417
Comments
|
Can you bring it back as a widget ? |
|
i dont know why this feature was removed in V4 - this was the best and most useful tool in AdGuard. |
|
Please bring it back, the current way not is so inefficient. |
|
I think it is better to have a tile instead of the notification |
|
You mean a custom widget? Let's vote, if you are for widget, upvote this comment, otherwise, downvote. |
|
Please bring back that feature to easy access the app. |
Why not all, a tile, in the notification and a widget, so the user can choose? |
|
I tried to make this a feature request to their actual support channel via email hoping to actually get some information and maybe an ETA and was instead told to revert and then ignored when I questioned if that was just going to be the response to every bug report or feedback for this nightly version. It felt like a very scripted response and then closure of the ticket immediately. I was not the only one receiving this same type of almost word for word response and then nothing further and it's rather disappointing if this is now what support has turned to instead of trying to locate the source of the errors or taking feedback and providing actual response now. Kind of like saying "don't like it don't use it then" when most of these people would be providing valuable data or logs to fix the problem if they let them and didn't shut them down immediately, myself included. |
|
The Problem is, they destroyed the entire app in v4 - not only the assistant. i dont know what are happening here but it goes in a completly wrong way... it´s a nightly yeah - but a i dont get why they removing features. |
|
I was not rude or mean is the thing. I was only asking for the missing tile to be restored as a request as here and possibly that it was a bug it was gone. I was met with almost hostility in what I'm sure was a copy paste reply on how to revert and never responded to again. This was happening on Reddit too with any mention of issues and I could almost quote the same reply I got word for word. It's why I know it's got to be a script and not even trying. I get a whole new version or engine can be like this sometimes but you have to give some encouragement to stick with things or troubleshoot instead of throwing it in the fire if it doesn't immediately work 100% which is the opinion I'm really getting from that. I couldn't tolerate the inconvenience and the complete random crashing then to be ignored by support so I'll just wait until someone I can rely on like the community tells me it's stable to attempt updating again. |
|
Same here, that's why this thread got created. |
|
It looks like in the last nightly update your brought back the button. |
|
I never liked the persistent notification (that's probably lost among other notifications). You don't spend time pausing or going to the assistant every hour/day/etc, I prefer to go into the app to manage things. |
|
If you are facing issues like this, then you like that opportunity to open Adguard that quickly over that way. |
I use the tile for issues like this |
|
Fine! But a tile you can only start over going back to home screen. |
|
I am also talking about this. I didn't know that this is also called a tile. The naming wasn't that consistent in this thread here. Cheers |
|
This is still not working in the latest Nighty update |
|
@eduardoaddad hi!
|
|
Yes since a few nightlys it's back. You can update. |

Issue Details
Currently, this functionality is missing from AdGuard for Android v4.0:
This feature request is supposed to measure the demand for this feature.
Please upvote or downvote it.
Proposed solution
No response
Alternative solution
No response
The text was updated successfully, but these errors were encountered: