Bug: Google Voice - Android 16

[SyCoREAPER]

Please answer the following questions for yourself before submitting an issue

• [x] Filters were updated before reproducing an issue
• [x] I checked the knowledge base and found no answer
• [x] I checked to make sure that this issue has not already been filed

AdGuard version

4.10.48

Environment

• OS version: Android 16
• Device: S25 Ultra

HTTPS filtering

• [x] yes, I do

Root access

• [ ] yes, I have it

Integration with AdGuard VPN

• [ ] yes, I do

Routing mode

Local VPN

Ad Blocking

EasyList, AdGuard Base filter, AdGuard Mobile Ads filter

Privacy

AdGuard Tracking Protection filter, AdGuard URL Tracking filter, EasyPrivacy, Legitimate URL Shortener, Peter Lowe's Blocklist, Fanboy's Anti-Facebook List, Fanboy's Anti-thirdparty Fonts

Social

Fanboy's Social Blocking List, AdGuard Social Media filter

Annoyances

AdGuard Annoyances filter, AdGuard Cookie Notices filter, AdGuard Popups filter, AdGuard Mobile App Banners filter, AdGuard Other Annoyances filter, AdGuard Widgets filter, Adblock Warning Removal List, Fanboy's Annoyances, Dandelion Sprout's Annoyances List

Security

NoCoin Filter List, Online Malicious URL Blocklist

Language-specific

No response

Other

AdGuard DNS filter

Which DNS server do you use?

Cloudflare for Families - Malware Blocking

DNS protocol

DNS-over-HTTPS

Custom DNS

No response

What Stealth Mode options do you have enabled?

No response

Issue Details

Steps to reproduce:

1. Call from another device
2. Destination device (Android 16) doesn't ring.
3. Caller sent to voicemail

Expected Behavior

Other person calls. It Dials. It rings on the other end.

Actual Behavior

Goes straight to voicemail.

Not routing Google Voice through AdGuard as a bandaid fixed it.

Same exact config of AdGuard and Google Voice (running Android 15) works perfectly fine as before without changing AdGuard.

Screenshots

No response

Additional Information

No response

[SyCoREAPER]

Come to think of it, during a Google Meet call their screenshare would not work on a Samsung nor Motorola device. Not sure what their current version of AdGuard and Android are though. Or if it was on my end. It was before I discovered Voice wasn't working.

[Swen90]

Hello @SyCoREAPER To investigate your issue I need a little bit more information. Please answer the following questions:

1. Is AdGuard installed and enabled on your main device (Samsung with Android 16), and this is the device that is receiving the call?
2. If you turn off the AdGuard, does everything work fine and you can receive a call?
3. If everything is ok in step 2, turn on the main protection switch on the Home Screen, but disable all blocks in Protection screen (Ad blocking, DNS protection, etc), extensions and turn off HTTPS Filtering in Network settings. This will allow to understand if there is a possible problem with the VPN tunnel.

[SyCoREAPER]

Hello @SyCoREAPER To investigate your issue I need a little bit more information. Please answer the following questions:

1. Is AdGuard installed and enabled on your main device (Samsung with Android 16), and this is the device that is receiving the call?
2. If you turn off the AdGuard, does everything work fine and you can receive a call?
3. If everything is ok in step 2, turn on the main protection switch on the Home Screen, but disable all blocks in Protection screen (Ad blocking, DNS protection, etc), extensions and turn off HTTPS Filtering in Network settings. This will allow to understand if there is a possible problem with the VPN tunnel.

1 ) *Not Receiving calls but yes this is my main device. 2 ) Yes, if AdGuard is toggled off or I freeze AdGuard, Google Voice works fine. Same goes for if I remove Google Voice from the app list to route through AdGuard via the main toggle in that submenu. 3 ) This was my workaround since, see above. By VPN tunnel I assume you mean the virtual one AdGuard creates to route traffic through it and not the actual AdGuard VPN product.

[Swen90]

Hello @SyCoREAPER About third point - Yes, the virtual one.

Unfortunately we can't reproduce this issue simply because of restrictions that google voice has and their policy. So in order to troubleshoot this issue, we need to get your application logs.

Here's what we need you to do:

1. Enable debug logging: Settings -> General -> Advanced -> Logging level -> Debug.
2. Reproduce the problem, then remember the exact time when it happened.
3. Collect logs: Settings -> General -> Advanced -> Export logs and system info.
4. Send this file to [email protected]:
   • include [android] keyword and #5745 as an issue number in the subject of your email
   • specify the exact time when the issue occurred

[Swen90]

@SyCoREAPER Please let me know if the issue still persists

[SyCoREAPER]

I don't know if I've been lucky or something on AdGuards end changed in the Nightlies. I've been issue free since making this. I don't get it.

[Swen90]

Very interesting, and is it now working on your other devices with new nightly version?

[SyCoREAPER]

Among them I've noticed no interuptions but will need to be conscious of it before confirming. Maybe I'm doing something to make them work and am so used to it that I don't even realize.

[Swen90]

Well, it's good that the main issue is gone 👍 And just let me know it appears again