Apple watch and Bluetooth connection is awful during my runs. Anyone else having the same issues?

Really? I knew we can use Apple Watch without iPhone for running with the Fitness App built in the Apple Watch.

Do you confirm that if I install Nike+ (I love it) on my watch, and go for a run without my iPhone. It will gets data (except GPS track of course)?

Purchased some good Bluetooth ear buds-

Jaybirid Blue Buds. I did not have a lot of problems with connectivity during runs and workouts. However, after about three weeks of good usage, the volume was too low and was unable to get it to turn up. Restarted my phone and problem was fixed.

I Have this same issue on runs with a beats wireless headset. I am a leftie so I wear the watch on my right wrist. I changed the the wrist mid-run to the left and I had no problems. Actually surprised that the Bluetooth is so sensitive to that subtle positioning. Cmon all you lefties, rise up and demand a fix!

I've got a Bluetooth headset that clearly states which arm you should carry your iPhone on, and confirmed that, if the phone's on the other arm, the BT connection is spotty. I'd assume the same to be true for the Apple Watch. I think the BT earbuds/headsets have a very short range in order to maximize battery life.

Same here. Doesn't matter if I'm walking, biking, lifting or mowing the lawn! Constant disconnect and reconnect! So frustrating, and thats using 2 different headphones, Motorola and Beats. I ended up going back to my locker and grabbing my bulky 6+ the first 2 times! Now I don't even use the watch when working out anymore AND that's the main reason I got the watch. Could've saved a few hundred and got a fit bit! LOL

Hoping Apple resolves this issue with OS2

P.S. This whole business about it being on one arm or the other is ludicrous! I can walk through my entire house or office with my phone in another room and not lose connectivity. Your telling me that 2ft makes a difference when the watch is on my wrist and headphones in my ears??!! Come on!

Motoclik..... I had the same problems. I wear the watch on my left wrist... Beats wireless headphones with small strap in front so power / pairing is in left ear. Saw a post a while ago on this & have been using this fix for 3+weeks & have not had an issue since.... 1 1/2 workouts (heavy), running, etc. You have to turn Bluetooth off on your phone...BEFORE... You go do your activity. That way the watch knows it's not there...... Otherwise it'll keep looking for it & cut out all the time. Press your music app & source to come from watch. Then it'll ask to pair the headphones.... turn on your headphones (beats you hold down button to pair) & the watch will fine them. That's it.... Your done & no interruption. Hope this helps.... Cheers

I've been having the same problem on both runs and walks--whether I bring my iPhone 6 with me or leave it at home. When walking I tried putting my iPhone in my right pocket with my Watch on my left wrist. That improved it a little but did not eliminate the problem. It seems really dumb that one would have to turn off BlueTooth on your iPhone for this feature to work properly. Apple, you need to come up with a fix!

Turning off the iPhone Bluetooth has worked for me for the past month. As mentioned by many others you have to go back to the source for music on the Apple Watch and for the headphones you are using. Because the watch does not have GPS you will have to use your iPhone in that case.

That's what I keep telling everyone!! once I began to disconnect the watch from the iphone via disabling the Bluetooth I haven't had any issues over the last month. Although you cant use the GPS its a small compromise guys until an update is issued. Happy workouts!!!!

Thanks for the suggestions! just extinguish the bluetooth connection or iphone must also disable wifi on the phone ? Turning off course you do before making the pairing with bluetooth headphones right?

you can leave Wi-Fi connected on the phone. just turn the Bluetooth off on the iPhone before you connect your headphones on the Apple Watch. Then you should be good to go! Again I've been able to successfully complete full workouts for over a month now since doing this. GOOD LUCK!!! please let me know if this was able to help you. I know that its worked for others.

first training disconnecting the bluetooth iphone . I noticed some improvement but there are still small disconnections were . I will try to reset the combination of the headphones and make a new one .

you expect it thereby disconnecting from iphone before connecting headphones ?

I tried to make a new Association of the headphones with the iphone bluetooth off.

I noticed that the clock if you are in the settings screen--and turn off bluetooth and > rekindle the earphones they connect but after a short time out a message "out of range". clicking it disappears and soon reconnect not presenting more the problem. could someone check if happens to you?

I Have the same issue after the last frickin update. This forum is useless. They will tell you reset your apple watch, reset your iphone, delete all the contents, hard restart your phone ....... etc, and they just ignore the fact that the apple watch was working like a charm before the update. They might also say: it is a new security technology, buy the new apple watch to resolve it. Come on Apple, you blow out our watch by your new update and your are reaponsibil tk fix it not us. Will never update again.

This may not be a great alternative however i haven't found a solution to the problem. Instead of listening to music from your watch you can simply play it from your phone. Now what you need to do is connect your headphones to your phone since it connects much better and easier. As long as you stay near your phone, like putting it down while working out or in your pocket ut will stay connected. It seems weird that in order to listen to music "without your phone l" you have to have your phone. Just remember you ca also control your phone music from your watch. This should work but it's not a good way to solve it. Hopefully Apple will solve this problem in a future update.