Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

AirPods Pro (2nd gen): audio cuts out

WillNorthYork
over 2 years ago

This seems to happen fairly quickly once a GPS activity is started. The UI acts as if music is still playing and it still responds to playback controls from the earbuds (play/pause, skip forward/back), but no sound is heard.

For me, the only way to recover is to go to the Headphones menu, disconnect, then reconnect. (It doesn't always work.) It's bad enough that I don't bother trying to use these earbuds on a run.

This doesn't seem to happen if GPS is not active. (e.g. Listening to music without starting an activity.)

Beats Fit Pro (similar to AirPods Pro first gen) and Jabra Active 65t work fine for me, except that I have dropouts/static while GPS is activated but before I start running. (I'm guessing it has something the combo of GPS interference and lack of arm motion when I'm not running.) IIRC, I would also have problems with dropouts with the Jabra earbuds during running, but it's less of a problem with the Beats Fit Pro.

Related:

https://forums.garmin.com/sports-fitness/running-multisport/f/forerunner-955-series/311679/airpods-pro-2nd-gen-with-955/1509742#1509742

https://forums.garmin.com/outdoor-recreation/outdoor-recreation/f/epix-2/309726/airpods-pro-2-bluetooth-connectivity-and-audio-issues

  • 0 over 2 years ago

    Can confirm that this seems to be fixed with the latest Airpods firmware. Just went for an hour long run with my 2nd gen Pros and had zero dropouts. Finally.

  • 0 over 2 years ago

    I'll be honest and say I assumed this was a Garmin issue, given that I'm kinda new to the Beats/AirPods ecosystem (so maybe I've missed out on a lot of old bugs), and I've been with Garmin for a while and seen all the bugs.

    So I def appreciate the effort on Garmin's part to help us resolve this, even though it was obviously Apple's fault this time. Thanks , and everyone else at Garmin who's looking at this at this issue!

    As a software dev myself, I def know what it's like to be blamed for something that isn't my fault (or my team's fault) haha.

  • 0 over 2 years ago

    Thank you everyone for the updates.  We'll keep an eye on this thread for other users' feedback as well.

  • +1 over 1 year ago

    All, 

    This disruption should have been resolved with the 13.23 software update. If you are still experiencing this on or after 13.23, please start a new thread.