stutter audio with BT headphones after 10 min

I have a problem with my BT headphones.
I have already tried the problem with three different headphones.

The problem is as follows.
The headphones connect successfully and I can play the music (Spotify) successfully.

However, after a certain time (once 10 min, once approx. 20 min) the music starts to stutter. It sounds as if you have run out of range. Of course, it has not changed the range. Watch on my wrist and headphones in my ear.

I simply assume that either the headphones or the watch wants to save some energy and is reducing the BT power. Since it occurs with three headphones from different manufacturers, I suspect it's the watch doing it.
Is there any way to set or prevent this?

  • I had a similar problem.  I noticed that the same headphones were pair to multiple devices (BT 5.0), and if i left one of the devices at home, the headphones would lose connection to that device and would start stuttering. The solution for me was to ensure no other devices were connected before I started my run. May not be related to your issue, but worth a shot.

  • I'm not sure if it's a coincidence, but yesterday I had massive dropouts again. When I ran into the forest it got better in an instant.
    Could be a random occurrence but maybe it has something to do with the GPS reception.

  • Same issue on Epix (Gen 2). Music plays fine for approx 10 minutes then starts to stutter.

  • Have the same issue on the Garmin 165 Music (19.18). After 15 mins it starts stuttering on Soundcore P20i.

  • I'm experiencing the same exact behavior with a 965 I just received. And, there doesn't seem to be a connection to what the watch is doing at the time, so it doesn't seem related to insufficient processing power as it occurs with GPS activities, with non-GPS activities, and just as often when no activity is being recorded (and the watch is mostly idle other than the music). Today, it occurred 13 minutes into my strength training activity and then later on with no activity. To me, the way there's a clear and relatively consistent delay before it begins suggests a memory leak.

    I've seen quite a few recent posts for identical (or very similar) issues on other Garmin watches, so I'm guessing the issue lies in some of the shared code (likely the library written for Bluetooth connectivity). Does anybody know if there was a recent update that could have started this? Also, I'm new to the forums, but is there any way to bring this to the attention of Garmin? Otherwise, are we just talking amongst ourselves and the people who can actually fix the issue have no idea about it? As a software developer, I totally understand that bugs happen and that they might take a bit of time to get fixed, but it sure would reassure me if someone from Garmin posted here to say that they're listening and aware of the problem and that they'll look into fixing it in a future update. If I knew a fix was being worked on, I can be patient and wait for it.

  • I have the same issue on my 955. I've seen many similar posts but yours is the first that confirmed it happens when not in an activity just like I've experienced. I've tried many different settings (wifi off, phone BT off, etc) but could not find a configuration that points to anything causing the issue.

    I have not been able to replicate the issue when using a bluetooth speaker or just a single earbud. I tested both for ~2 hours each, so keep that in mind. So for now it seems to be something with the two earbud configuration.

    It seems to happen most after 10-15 minutes, but occasionally longer. One time I went a full hour before it started.

  • I have the same problem on Epix 2 with 18.14 firmware - but only on one of my two pairs of headphones.... works ok on Shokz... so far.  Frustrating.

  • Exact same issue, exact same watch. I went through Garmin support sending in watch logs and other troubleshooting. The engineers said they wanted to take a look so I exchanged the watch. Same issue on the new watch. It seems to get progressively worse and then almost resets and works great for another 15 minutes. I thought I narrowed it down to the watch looking for HR but having issues with an external HR monitor. But I also tested without activity or other devices. While the performance improved the same issue did rear its ugly head after a while. Sometimes up to an hour or so; but always came back. I think I exchanged about 6 months ago. While there have been updates since then nothing has changed with the issue.

  • Did a bit more digging. Problem seems to be headphone specific.  The 'stuttering' occurs on my (admittedly cheap) chinese bluetooth earpods..... irrespective of the mode the watch is in.  When I'm _just_ playing music, I get about 50 minutes of ok playback before stuttering.... if doing an exercise (e.g. with Cardio mode on, but no prompts), I get 20 mins, but if using a training program with prompts (e.g. a Training Run) I get 5 mins or less before the problems start.

    Using my decent Sennheiser Momentums, I got an hour without issue....

    I'll retest with my Shokz.