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

Issue with Jaybird Run Volume Up On headphones Not working

Former Member over 5 years ago

I have the jaybird runs buttons set to control volume. Volume Down works, but volume up does not. I can only turn volume up only using watch. Volume Up on headphones works with other devices. Anything I can do? Is this a problem also with Run XTs (thinking of upgrading)? Thanks

0 runningfan97 over 5 years ago

Looks like the same issue the guys with Aftershokz Aeropex have reported in this forum.

Please send Garmin support a mail.

0 stjopachio over 5 years ago

I had something similar with Tarah Pro (my watch is on beta 2.64 though). It was more drastic as the headphones became totally unusable after connecting to the watch (they did not work at all, I could not switch them off or pair with other devices; or if they worked 2-3x, I could not turn volume up or down) and the only way I could reboot them and make them usable again was by putting headphones on the charger. But this started to happen after I installed beta.

What seems helped me was to delete headphones from the watch and to pair them again. I've had 3 runs afterwards and everything seems to be OK thus far.

0 2251627 over 5 years ago in reply to stjopachio

Had the same issue

The headset lost control…

Few times remove and pair helps

Last time had to soft reset the headset (simply connect to a USB port)

I must say that the headset works perfectly with my phone

0 stjopachio over 5 years ago in reply to 2251627

The with me - headphones work flawlessly with my phone.

0 Former Member over 5 years ago

Still not working with 2.70.

0 Former Member over 4 years ago

I am having real problem connecting my Jaybirds of late. For 4 or 5 runs it disconnects 10 mins in. Today, for the first time, I couldn't connect to my Vistas at all- it just failed to connect . I am sure the buds are OK as they work with my phone and other devices. I read somewhere that the problem might be linked to the recent upgrade of OS3.6 to OS 4.1. Is that right I wonder? If so, does anyone know how to do that?