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

Forerunner 255 Music - Intermittent Earphones Connection

It seems that even after 2 years Garmin haven’t fixed the intermittent headphones connection when out running. 
I bought my Forerunner 255 Music earlier this week. I’ve been for 2 runs using 2 different sets of Bluetooth earphones and within 30 seconds the music is continually intermittent and impossible to listen to. 
I’m not sure if Garmin will read this article but it seems they’ve had enough time to come up with a fix, such as a newer Bluetooth receiver?

This only occurs whilst outside running, without my phone  

If I play music whilst at home it isn’t an issue. 

Has anyone found a recent fix at all?

  • The only working solution is to use compatible ear buds. I use huawei freebuds pro and have 0 problems with it.

  • Do you have your bluetooth phone connection enabled when you are away from the phone? It seems like the watch desperately tries to connect to the lost phone, disturbing the music connection.

  • I’ve read more on this subject since my post. I don’t take my phone running with me.  I’ll switch off WiFi and phone connectivity next time I run and I’ll post the results. 

    Keep the ideas coming. 
    Many thanks

  • I went for a run today with my brand new 255 music, turned off phone and wifi on watch, lost connection so many times, 4 sec music average each time, I guess. Using jabra elite 4 active.

    If more ppl with huawei freebuds pro claims it is without problems I guess I'll have to invest in those.

  • Same issue here. Got a Motorola 600 ANC ... Imposible to use, returned and got an earfun free pro 3 and same issue!!!

    This Is increíble really. 

  • I should post an update. Got the tips to check my earphones for update, downloaded the jabra sound + app and updated the earphones. Startet listening inside and the connection broke the second i went out the door and braced myself for another annoying run. But after that inital setback everything actually worked as it should. Such a relief! This worked for me, hope it helps you guys.

    Edit: I've been putting this of in order to be sure, but the problem is worse than ever now. The playback stops and I have to reconnect my earbuds in order to get some seconds more playback, before playback stops and I have to reconnect again. Today I couldn't even get playback going inside my own walls, both with and without wifi on. Using spotify btw. Could be update to 19.18, but I don't think so, I don't know really.

  • OK so after getting agitated today during a run I decided to see if other people have this issue. The previous run I had I started and stopped the watch music many times until it seemed to sync up enough to almost be smooth.

    It shouldn't be doing this especially if the hardware has good charge so I am exploring now what the devil is the issue because if I can do something about it I will try but if its a glitchy software problem then it needs addressing and not waste users time.

    Any official acknowledgement from Garmin on this? There must be enough data there to probe what's going on...

  • I have my FR255 music since 2 years, I use it connected to Sony WF-C500 earbuds, never was the connection interrupted

  • I was using a pair of Antimi buds and switched to another brand a few months back for the same reason (thinking the other set were just getting old). Upon reading other people's posts and tried two different sets myself I think its more likely a Garmin item rather than unicorn models being immune to the item.

    Will see if there appears to be a compatible list or some common feature to why sync/stutter.

  • I just ran a half marathon yesterday and the intermittent connection on my airpods pro 2 drove me crazy. It's happened previously during other races and I've found that tapping a pause for a nano second then unpausing clears it, but yesterday it would only clear it for a few minutes then it would start back up again. Happened throughout the entire race. At first I thought it might have had something to do with the latest software update, but I think I am now realizing it has to do with the level of perspiration. The warmer it gets the more of an issue it becomes. Wasn't really an issue during the last few winter months but as it gets warmer it's resurfaced. Super frustrating