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

Bluetooth music connection issues

Hi all,

I've been a Forerunner 245M user for almost 2 years and never had any problems with my bluetooth connection while running. Nowadays my bluetooth connection is horrible, it stutters a lot and listening to music is unbearable while running outdoors (indoors everything is fine). First I thought my Redmi airdots where broken but I have tried a lot of different buds and they all stutter. Is my device broken or? I saw someone suggesting to wear my watch on my right wrist and this seems to work but I don't feel like wearing it to my right wrist, especially since it worked flawless before..

Is there a solution for this problem?

Software version 6.20 (7ae543d)

Tested buds:

- Redmi Airdots 2 (Not working)
- Samsung Bud+ (Not working)
- Jabra 65T (Not working
- JBL Free 2 (Not working) 
- Apple Airpods (Not working)
- JBL Reflect Mini (Not working) 

Strange thing is that the Apple & JBL Reflect mini will play flawless if you only connect 1 (left) bud and as soon as you connect the right bud the stutter begins.. 

I'm really annoyed and hopefully Garmin has a solution. 

  • I have spoken to Garmin several times and they don't seem to be able rectify it for me (it's as if they aren't aware and obviously aren't publicly acknowledging it).  Below was the response I received after emailing pictures of the front and back of the watch:  

    Thank you for contacting Garmin Australasia.

    The product you have purchased is not sold in Australasia. The part number is for a Southeast Asia Garmin Forerunner 245 Music. We will require a copy of the invoice before we can proceed

  • Me too. I had this problem last spring, it went away for the summer, and just came back. It's only an issue when gps is on, and when the Bluetooth connection has to go through my body: my Jabra active elite 65's receive through the right earbud, and it's fine if the watch is on my right wrist or if I hold my left wrist out in front of me. Very frustrating. 

  • I am also experiencing difficulties with disconnections with software version 8.20 using Skullcandy Dimes. Used to work almost flawlessly with software versions 7. Now it's barely usable.

    It works flawlessly when seated, but during runs (with a lot of arm swinging), the buds will (momentarily) disconnect, but the podcast (via the payrun app) will continue to play silently without playback happening on the buds. Strangely, the buds will reconnect automatically and running audio alerts will be played on the buds, but no automatic reconnection of podcast playback to the buds happens. Instead, you are required to open the menu on the watch, pause playback, rewind and unpause for playback to happen on the buds again, and repeat this process a minute later due to another disconnection.

    So basically 3 issues.

    1. Buds disconnecting during running. Buds do not disconnect if connected to smartphone so definitely a watch issue.

    2. Track playback on watch via music app does not pause when buds disconnect. Playback timer keeps running.

    3. Track playback via music app does not automatically reconnect to buds after disconnection. But reconnection of audio alerts playback is automatic.

    # Restarting and repairing of watch and buds does not fix the issue.

  • The latest sensor hub update has greatly reduced the drop outs.

    Still receive the occasional drop which annoyingly does not pause the playback timer on the app.

    At least the buds now reconnect automatically to the music app after +-15 seconds without requiring any user input.

  • I have had the same issue for years depending on the update. I can confirm this worked for you, however, does not work for everyone. 

  • Hi, it did not fix all my issues. The issue where it does not pause when it loses connection is particularly annoying. 

    Also, after further usage, it seems like my connection issues might be fixed due to a change of location. Connections seems to improve when I am not near power lines. That said, connection to my cell seems to be fine when near power lines, so I have the carry my cell on grounds that have overhead power lines.

  • Similar issue, have had my 245Music for 2+years with no issues with music with the watch on my left hand. Recently updated to 8.2 and as soon as the GPS is enabled (by initiating a run) the music cuts out. No other changes have been made to the watch in over a year. If I now switch my watch to my right hand the music plays fine, but nothing has changed other than the recent software update.  I have 3 different pair of "approved" bluetooth headphones that were all working prior to the update but now none are working if the watch is on my left hand.  Yeah I can move the watch to my right hand each morning I go for a run, but its really annoying.

  • Also worth noting, I tried restarting and even resetting the watch after the update as some have suggested, but it has made no difference.  Music still breaks up on each running stride when the watch is on my left hand.

  • Yes, it's really strange. Sounds like your buds are receiving the signal in the right bud.

    I usually run with one bud only. When I use my left bud, I get less dropouts. I wear my watch on my left hand. Bluetooth range is 9m, and the distance from my left to right hand is definitely less than that, so I am not sure why the signal quality will change much from hand to hand. Perhaps the 8.20 update is pushing less power to the bluetooth receiver on the 245m?

  • Bluetooth range is 9m

    BT range is UP TO 10 meters.

    There is no guarantee that it will always cover that range. But I agree absolutely that from left arm to right ear should be covered in every circumstance, even with BT Low Energy and aggressive settings.

    In the end there seem to be difficulties in the standards. I was unable to permanently connect a BT LE HRM from third party to my Concept2 rower, even though it was working with the FR 245, an iPhone and the original running watch it came with.

    I imagine that there are slightly different interpretations of the standards and settings, that cause problems