Quest 3 v83: Outgoing headset call forces pause state for in-app WebView media (incoming call OK)

Hi all — I’m posting this because it took me a while to isolate, and the behavior is really confusing if you’re trying to play media in an app while also using Quest headset calls.

Devices / Version

• Meta Quest 3
• OS: 83.1034 (both headsets tested)

What I’m seeing

I have a custom Unreal/Android app that plays music via an in-app browser (Chromium/WebView). If I’m in a Quest headset chat/call and I join a listen server in my game (as a client), my in-app media gets paused/muted by the OS.

The weird part: this does not happen consistently across headsets, even on the same OS version.

Repro steps

1. On Quest 3, launch my app (or any app that plays media inside a WebView/Chromium browser).
2. Start media playback (ex: YouTube music playing in the embedded browser).
3. Start a headset call.
4. Observe: on one headset, media playback gets paused/muted and immediately re-pauses if you try to resume.

Key discovery

The behavior depends on who originates the call:

• ✅ If the other person calls me (incoming call), the call works and my in-app media keeps playing normally.
• ❌ If I call them (outgoing call from the problematic headset), my media gets auto-paused/muted and can’t be resumed (it re-pauses immediately).

So the workaround is:

Have the other person call you instead of you placing the call.

Logs / evidence

On the problematic headset, right around the pause I see Chromium and audio teardown messages like:

• Chromium audio warning:[WARNING:services/audio/sync_reader.cc:148] ASR: No room in socket buffer.: Broken pipe (32)
• And the audio stream being stopped:AAudioStream_requestStop(...) called AudioTrack.stop(...)

I also see Telecom-related logs only on the problematic headset when I originate the call, including com.oculus.presence ... ConnectionServiceBridge and repeated state=DIALING updates.

Bluetooth note

I removed/forgot all paired Bluetooth headsets and still saw the issue. I also noticed a line like:

BluetoothAdapter: getActiveDevices(profile= HEARING_AID)

…but nothing was actually paired/connected.

What I’m asking

Has anyone else seen Quest headset calls behave differently depending on whether the call is outgoing vs incoming — especially causing WebView/Chromium media audio to pause/stop?

If this is a known Quest OS bug or a call-path/policy difference, it would be great to know if there’s a recommended fix, setting, or planned update.

Workaround (repeat)

Don’t originate the call from the problematic headset.
Instead, have the other person call you.

Thanks!
(p.s. I had some AI help putting this post together, thus all the fancy formatting)