Skip to main content

AirPods Connection Bug / Phone Call

Whenever AirPods are connected to a phone call (On an iPhone) the AirPods keeps connecting and disconnecting.

Ways to produce the bug:

Have Seam Opened

  • Join a phone call on your iPhone & have AirPods connected

  • The AirPods will keep connecting/disconnect every time unless Seam is quitted.

Status: Completed6 comments

Log in to comment and vote

Comments6

  • Ramzi

    Team•

    Aug 2

    Hey, thanks for the detailed report.

    I tried to reproduce this on my end (Seam running, AirPods on an iPhone call) But it works fine for me.

    A few questions to help me pin this down:

    1. Which macOS version, Seam version, and AirPods model are you on?

    2. On the Mac, in System Settings > Bluetooth > your AirPods > Options: is "Connect to This Mac" set to "Automatically"? If yes, does setting it to "When Last Connected to This Mac" stop the loop?

    3. In Seam's settings, go to Audio Devices and turn off "Connection alerts", then try a call again. That disables Seam's Bluetooth monitoring entirely, so it tells us whether Seam is involved at all.

    4. If it still loops with Connection alerts off, could you run this in Terminal during a call and send me the output?

      log stream --predicate 'process == "bluetoothd"' --style compact > ~/bt.log

    Then hang up, stop it with Ctrl+C, and attach ~/bt.log.

    The symptom you describe also exists as a macOS bug with AirPods automatic switching, so I want to be sure of the cause before shipping anything.

    Thanks!

  • mchung

    •

    Aug 2

    Here’s the video

    • Ramzi

      Team•

      Aug 8

      I really don't think this behavior comes from seam, but rather from how Apple handles Airpods device switching. We just alert you when your airpods have switched devices. But we don't trigger that.

      Can you try not using seam for a day and let me know if you really don't have that happening anymore?

      • mchung

        •

        Aug 14

        Sorry for not updating on you regard to this as I thought it was fixed (Which doesn’t seem to happen anymore after the updates you had released? Or possibly I have restarted my mac. Not so sure)