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

Connection with Google Pixel Buds 2 constantly dropping

I got the vívoactive 4 and Google Pixel Buds 2 (with the latest updates).

Pixel Buds 2 and my phone work great, no problem.

Pixel Buds and my watch are not working great :/

When I run and move my arms the connection drops every few seconds for a half/one second. I tried wearing my watch left and right, the same problem.

Anyone any idea?

My gf has the same watch (only smaller) and has in-ear from Jabra and she has no issues.

Top Replies

seilogramp over 3 years ago +1

Do the Google Pixel Buds have the option to connect as a footpod? Some headphones can be paired with the watch as a footpod as well, which causes the disconnects when starting an activity. If so, from…

All Replies

0 seilogramp over 3 years ago

Do the Google Pixel Buds have the option to connect as a footpod? Some headphones can be paired with the watch as a footpod as well, which causes the disconnects when starting an activity. If so, from the Sensors menu, pair the Google Pixel footpod, then when it's paired set its status to off.

0 RaRoos over 3 years ago in reply to seilogramp

I disconnected the Pixel Buds (PB) and connected them again. Went for a run today. It sems like the problem is less but still every x meter there is a drop in the connection.

If that is because ever x meter my wrist makes the same movement as a foot running (Assuming the watch thinks it is a food pod) I don't know.

How can I check if the PB are connected as a headset (They do play music) or also as foot pod?

Thanks anyway!

0 seilogramp over 3 years ago in reply to RaRoos

The Jabra Elite 65t headphones have the known issue regarding footpod sensor. The Pixel Buds 2 maybe are too new for us to know the actual fix. Check this out to see if applies to your issue: Jabra Elite Active 65t earbud

0 RaRoos over 3 years ago in reply to seilogramp

Seems to be the same issue indeed, I tried the proposed solution but still the same issue... Thanks for your help. I will try to experiment a bit more.

0 mike_snodgrass over 2 years ago

Have the same issue - just tried it today!