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

Is anyone using the watch for music w/ bluetooth headphones successfully?

I got tired of waiting on Spotify so I copied some old MP3s down to the watch and to be perfectly honest it was almost completely unusable because it kept cutting out so much.

I do wear the watch on my left wrist, will moving it to the right make enough of a difference so that it's usable?

I feel like I have to hold the watch up in front of my face to eliminate cutouts. Holding my phone in my left hand when paired with the same headphones (have tried two different ones so far) will also lead to some cutouts but nothing like what happens with the watch.

I love the watch and all of the metrics and tracking I can get from the app and site and just purchased a flipbelt so I can carry my phone without holding it in my hand so I guess I just won't be using the watch to play music directly.

One thing to note, I had an original Moto 360 smartwatch and didn't have this level of cutouts when paired with headphones and on my left wrist.
  • I wear sometimes. I also copied some MP3 I have, and my BT headphone is a JBL very simple.
    It works perfecly.
    This behavior you describe I have already noted when pairing to my mobile (oneplus 6), and headphone batteries is low.
  • Former Member
    0 Former Member over 6 years ago
    I use the watch with runcasts frequently and have come across what you say on a few occasions. I've found that if i have the watch covered with tight skins the problem arises and also if the wire from the earphones is covered with a hat the same applies. 99% of the time it does work. I use Fitbit Flyer earphones.
  • It got a lot better for me (hardly any dropouts) with the new 3.50 firmware (I have an APAC model, so the US model equiv is 3.30) where they released also a new bluetooth update.
    However that new bluetooth update totally drains the watch battery if it can't find your phone and the phone connection is on.
    But yes, I used to have this problem. It seems to depend on your headphones mostly. I am surprised at how bad the range is for my headphones, because with my UE Boom that I sometimes take in the shower and pair with my watch, I can be 3 rooms away and BOOM is still happily playing music.
  • Former Member
    0 Former Member over 6 years ago
    I use Garmin 645M on right hand with Bluetooth ear buds and really works fine for me. In the city though remember glass and buildings affect Bluetooth so cutting out can occur. There is one short tunnel I run through and consistently the music stops and I have to start over, but 99.9% it works fine, in subway too.
  • Thanks for the responses, looks like Spotify has been added so I'm syncing now and am going to try this again in a few minutes!
  • Mine works flawlessly with my Bluetooth headphones, no drops ever - even when running.
  • I'm happy about the music experience too, I have several bt devices and compared them on my site: http://starttorun.info/the-best-bluetooth-headphones-and-bluetooth-speakers-for-garmin-watches/
  • Wow, really nice site!

    I'm happy about the music experience too, I have several bt devices and compared them on my site: http://starttorun.info/the-best-bluetooth-headphones-and-bluetooth-speakers-for-garmin-watches/


  • Former Member
    0 Former Member over 6 years ago
    I'm using it with a pair of Anker SoundBuds Tag. Bluetooth module is just off the right ear on them, and I wear my watch on my left wrist. No issues with bluetooth drop outs so far (although I don't listen to music all the time when running). I'm actually really impressed, because I used to get horrendous BT audio drop out issues with the same earphones back when I used to use my phone when running.
  • Former Member
    0 Former Member over 5 years ago

    Yep, for me the same. I've got the Samsung Galaxy Buds. Not usable when I wear the watch on my left wrist. No problems on the right wrist. When I first read this, I couldn't believe it. In the mean time you can find this solution/workaround in already so many other threads.