AdguardForAndroid
AdguardForAndroid copied to clipboard
AdguardTeam
Shazam can't search when traffic control is enabled in Adguard
@jbionic2016 commented on Wed May 25 2022
Prerequisites
- [X] This site DOES NOT contains sexually explicit material, otherwise use NSFW-specific form;
- [X] Filters were updated before reproducing an issue;
- [X] AdGuard product version is up-to-date;
- [X] Browser version is up-to-date;
- [X] If the site or app is broken, disabling AdGuard protection resolves an issue.
What product do you use?
AdGuard for Android
AdGuard version
3.6.8
What type of problem have you encountered?
Website or app doesn't work properly
Which browser(s) do you use?
the problem is with app, not a site
Which device do you use?
Mobile
Where is the problem encountered?
Shazam app
What filters do you have enabled?
AdGuard Base filter, AdGuard Mobile Ads filter, AdGuard Russian filter, AdGuard Spanish/Portuguese filter, AdGuard Turkish filter, AdGuard Tracking Protection filter, AdGuard Social Media filter, AdGuard Annoyances filter, AdGuard DNS filter, EasyPrivacy, Online Malicious URL Blocklist
What Stealth Mode options do you have enabled?
No response
Add your comment and screenshots
Hi,
I have found this unusual behaviour which is observed on my old Android 8 phone. See attached picture below.
When traffic control is enabled in Adguard, Shazam assumes it is offline and can't search for tracks. But as soon as I disable traffic control, Shazam immediately can access it database to identify a track.
I've been using both apps on this phone for a number of years with no issues. Why is this happening now?
Thanks.
https://i120.fastpic.org/big/2022/0525/22/92b5b72299b4f2ccfe35e492a3e85f22.jpg
Privacy
- [X] I agree to follow this condition
@jbionic2016 commented on Thu May 26 2022
Anybody home?
@BlazDT commented on Thu May 26 2022
Not reproduced on my Android 12 on latest AdGuard nightly. Please check filtering log for latest blocked requests when you are entering the song and you search for it.
I can only reproduce if I enable HTTPS filtering for the app.
@zloyden can you reproduce on an older Android?
Btw is it working if you disable your VPN and let AdGuard create local VPN?
@jbionic2016 commented on Thu May 26 2022
Yeah, that's the whole point. My Android 11 tablet doesn't have the problem either, but my old Android 8 smartphone is somehow exposed to the problem
@BlazDT commented on Thu May 26 2022
Then it looks like not a filters issue (likely some I compatibility with older Android). Sadly I cannot test again as I only have that one device. Have to wait for colleague if he can reproduce issue.
@jbionic2016 commented on Thu May 26 2022
I don't mind if you duplicate the issue to the Android fork and close it here
@github-actions[bot] commented on Mon May 30 2022
This issue has been automatically marked as stale because it has been open for 4 days with no activity. Unfortunately, our resources are limited and we can not always take the time to respond to requests about websites that are not popular enough. The issue will be closed if no further activity occurs. Please note, that AdGuard Filters is an open-source project that is used by different content blockers and we welcome contributions. If you have some technical knowledge about how websites work, you are welcome to create a pull request following these instructions.
@jbionic2016 commented on Mon May 30 2022
What actions from my side are required at this point?
@BlazDT commented on Tue May 31 2022
You can exclude the app temporarily.
@zloyden @AdamWr please check on older Android. Probably some requests are made different than in latest Android.
@zloyden commented on Tue May 31 2022
I do not have an old Android, but on my Android 11 it works fine. It looks like this does not related to the filters, will move the task to our Android repo.
The issue is still present. The funny thing is that as soon as I switch from Home WiFi network to mobile network, Shazam immediately connects to its database and produces the title for a track (with Adguard enabled), whereas in Home WiFi network Shazam doesn't work till I turn off Adguard protection.
@jbionic2016 Please share the debug logs of the application. Here's what we need you to do:
- Collect the debug log as it's explained here;
- Remember the exact time when the issue was reproduced. We will need it to find the corresponding records in the log file;
- Send it to
[email protected]. Mention the Github issue number and the exact time when the issue was reproduced.
Any news?
The problem persists no matter whether I use mobile or home WiFi network till I turn off Adguard.
@jbionic2016 Any news? You can also try
||beacon.shazam.com^rule.
The last rule didn't work either. I've learnt to disable Adguard every time I need to find a song via Shazam. I sorta was hoping that Adguard would make it easier for its users to handle such situations.
Disabling Shazam control in Adguard DOES work, but I find this setting insecure because Shazam app has access to the mic (I am a bit paranoid)
@jbionic2016 So disabling protection for Shazam in Apps Management did help? It should work the same way as disabling AdGuard's main switch.
So disabling protection for Shazam in
Apps Managementdid help? It should work the same way as disabling AdGuard's main switch.
The only difference is that I fully control the later, so that Shazam won't be able to connect without my permission.
Why don't you change your rules for Shazam so that Shazam remains under control by Adguard and still is able to connect to its database without Adguard being disabled
At this moment the set of rules that I have enabled for Shazam allows it to use Mobile and Wifi networks, but only when the screen is on. But it still doesn't work the way it should.
@jbionic2016 sorry for the wait
- We need to know which requests are blocked in Filtering Log, please retry the steps and take screen shots
To troubleshoot this issue, we need also to get additional logs.
Here's what we need you to do:
- Collect the debug log as it's explained here;
- Remember the exact time when the issue was reproduced. We will need it to find the corresponding records in the log file;
- Additionally, capture the system bug report after reproducing the issue. Here's the instruction;
- Send both files to [email protected]. Mention the Github issue number and the exact time when the issue was reproduced.
We need to know which requests are blocked in Filtering Log, please retry the steps and take screen shots
I sent my log files twice to your email address devteam at .., and got no response. First time the log files were sent on 2nd of June (not July) from my email starting jbionic, second time I sent my log files on 13th of July.
@jbionic2016 please double-check the e-mail address. We don't have any mail from you on those dates e-mail: [email protected]
@jbionic2016 please double-check the e-mail address. We don't have any mail from you on those dates e-mail: [email protected]
Please download from the below link. Shazam was enabled between 18:46-18:47 MSK. Let me know when you've finished https://drive.google.com/file/d/1oxeXW2tmemvJtwA_rIWGGOXakJwFZkVx/view
@jbionic2016 I asked you to send the debug logs. Please follow the instructions and upload the debug logs.
We need to know which requests are blocked in Filtering Log, please retry the steps and take screen shots.
To troubleshoot this issue, we need also to get additional logs.
Here's what we need you to do:
- Collect the debug log as it's explained here;
- Remember the exact time when the issue was reproduced. We will need it to find the corresponding records in the log file;
- Additionally, capture the system bug report after reproducing the issue. Here's the instruction;
- Send both files to [email protected]. Mention the Github issue number and the exact time when the issue was reproduced.
@jbionic2016 did you send the logs?
ping.. yes, I did. the Google Disk link was shared above (https://github.com/AdguardTeam/AdguardForAndroid/issues/4179#issuecomment-1198064144), but the logs files didn't satisfy you, so I removed the files. The logs files were collected precisely the way described in your manual: https://kb.adguard.com/en/android/solving-problems/log#debug I don't know what else I can do for you. At this moment out of my 2 Android devices, one can connect to Shazam with Adguard turned on, the other one (Xiaomi) requires Adguard to be turned off
@jbionic2016 please repeat the error with Shazam and take screenshots from the filtering log. We need to see what is blocking at this point. Also, please upload extended logs as described in the instructions above with the time. Send everything to [email protected] Without this information, we can't help you
Please check you devteam-email at 11:53-11:54 Moscow time (today is Friday, 12 August 2022). I've sent my new log files from my Google address. Should you not have received the files by email, I'll share the same files via Google Disk, so you can download them at your own convenience. This is a Xiaomi device we talk about. Thanks.
@jbionic2016 try to disable DNS filtering. If it helps, change the server. Have you tried adding ||beacon.shazam.com^ to the list of DNS rules?
@jbionic2016 try to disable DNS filtering. If it helps, change the server. Have you tried adding ||beacon.shazam.com^ to the list of DNS rules?
Yes, it didn't help
@jbionic2016 thanks for the wait. For a more detailed analysis, we need a logcat log from you. Here's how you can do it https://kb.adguard.com/en/android/solving-problems/logcat
Not yet. Seems kinda complicated. Your guidelines say that I need to install an additional ADB app. I'm a little suspicious
@jbionic2016 if you have an older version of Android, then unfortunately there is no way without ADB app. Do you have an older version of Android?