Skip to content

Please add Google Play Services to Low-level QUIC bypass for users with Wear OS watches #6198

Description

@Dondrejohnson5

Please answer the following questions for yourself before submitting an issue

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

AdGuard version

4.13.2

Environment

  • OS version: 17
  • Device: Google Pixel 11

HTTPS filtering

  • yes, I do

Root access

  • yes, I have it

Integration with AdGuard VPN

  • yes, I do

Routing mode

Local VPN

Ad Blocking

AdGuard Base filter, AdGuard Mobile Ads filter

Privacy

EasyPrivacy, Peter Lowe's Blocklist

Social

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

Security

Online Malicious URL Blocklist

Language-specific

No response

Other

No response

Which DNS server do you use?

DNS protection disabled

DNS protocol

None

Custom DNS

No response

What Stealth Mode options do you have enabled?

Protect against DPI

Issue Details

Steps to reproduce:

  1. Connect a Wear OS device, such as a Google Pixel Watch, to your device. Ensure Google Cloud Sync is enabled in the Watch companion app Privacy settings
  2. Lock your phone and leave the screen off for a while
  3. Step far away from the phone as necessary to sever the Bluetooth connection between your phone and watch. The watch should resort to LTE or any known Wi-Fi network saved on the watch

Expected Behavior

As the watch is connected to Wi-Fi/LTE, the watch should still be able to communicate with the phone, such as being able to send texts, check phone's battery through 3rd party apps, etc

Actual Behavior

The watch is unable to reconnect to the phone regardless of network as long as the AdGuard VPN is still active while the phone is locked and screen off. This does not occur under the same circumstances if the screen is on. Adding Google Play Services to QUIC bypass manually seems to mitigate the issue

Screenshots

Screenshot 1

Additional Information

No response

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions