Google pixel 2 buds 2020 edition not working properly with IONIC

[Shashi21]

I recently bought pixel buds 2 and synced up with my fitbit ionic. Once I start playing the audio is all choppy. It chops like every 2 seconds and consistently. This has been a bummer for me lately

[elijahp]

Exact same issue. I see older posts dating back to 2018 with people reporting this problem with several different pairs of headphones.

[baucoma]

It's true. I have Fitbit Flyer earphones and wear Ionic on my left wrist. When jogging and my left arm goes behind me, the music cuts out. Fitbit doesn't acknowledge the issue. Told me to wear my Ionic on my right wrist. I think there is a Bluetooth connectivity issue. I'm glad to know that it isn't just a problem with the Flyers. I need to buy new earphones now and was looking at Google's earbuds. Flyers are no longer available on the Fitbit website. I read Google is getting rid of them in favor of their Pixel Buds. Not sure what to do now.

[BrianKing]

Same exact issue.  Fitbit Ionic + Google Pixel 2 Earbuds.  Music 'pauses/skips' every two seconds consistently.  Makes listening impossible.  I have an open ticket with Fitbit, case #36089232.  I call every few weeks for an update.  It's been escalated, but has not be resolved.

[MarkFarina]

Was this ever solved?

[BrianKing]

No, not solved yet.  Has it been for you?

[baucoma]

Not solved. I'm now using Bose Sport wireless earphones. Reception is better than with Fitbit Flyer but I frequently change Iconic to my right wrist while running which gives the best reception. I still maintain there is a Bluetooth issue with Iconic.

[elijahp]

Still does not work with my Pixel Buds 2. Both my watch and my headphones have received at least a couple of firmware updates since I last posted to this thread, but the issue persists. Constant skipping every two seconds. I have to wonder if this is a really a firmware or bluetooth signal issue, or if it could be related to the way the Ionic transfers music files over WiFi or writes to memory.

[BrianKing]

That's an interesting idea.  I will try wiping my Pandora stations and downloaded music from the Fitbit, and then re-add music.  Perhaps it has been fixed, but the music on the Fitbit now is corrupted.

[BrianKing]

I tried re-downloading music, and still same issue.  Skips/pauses every two seconds. I should have known it wouldn't work.  I don't have the issue with any other Bluetooth headphones.  Only Google Pixel 2 Earbuds are the problem.  I've tried working with Google, who blame Fitbit.  I've tried working with Fitbit, who blame Google.

[LLicea]

Same problem here with fitbit sense and pixel buds 2, I think it is a problem with the pixel buds because I do not have any problem with my fitbit flyers.

[Jmoney2020]

Pixel buds 2 and Fitbit Sense 3.  Customer service with google is blaming Fitbit. 

We all know it is a software issue somewhere.  

Please, fix this fitbit. 

[Daniel_i]

Thanks for the update and quick reply. I'll be sure to keep an eye on this thread Walgreenslistens.

[JettleMania]

Exactly the same behavior on the Sense. 😞

[JettleMania]

Doubt it; the Sense exhibits exactly the same behavior. Pixel Buds 2 firmware at 252 (August 2020 release).

[JettleMania]

Funny b/c Google & Fitbit will  be the same company... eventually. I had hoped the Sense wasn't affected, but alas, apparently no one has bothered to touch the Bluetooth code.

[LatinFury]

Just tried pairing a new pair of Pixel Buds with a new Sense.  Same issue. Is there no resolution in sight for this?  Or are we just SOL and have to switch to another tracker and/or earbuds. Has anyone had any luck with any other brand?

[LatinFury]

Honestly, my feeling is this is an issue on Google's end. I get occasional dropouts using the Pixel buds with a Pixel Phone (e.g. even devices in their own ecosystem). 

[elijahp]

The buds definitely had problems at launch. I may be in the minority, but I
haven't had connection issues with them on any device except my Ionic. They
work fine with my phone, laptop, and desktop computer. Still could be a
Google problem.

[BrianKing]

Agreed.  Only Ionic has the issue.  Fitbit blames Google.  Google blames Fitbit.