Cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Surge (Classic) pairing issues with Powerbeats2 Wireless headphones

Replies are disabled for this topic. Start a new one or visit our Help Center.

Hi Fitbit community,

I've noticed a bit of a dissapointing issue with my fitbit surge and the functionality of using bluetooth headphones in conjunction. From what I've seen searching around the forums, people are having similar issues, but some are able to use their bluetooth headphones with the bluetooth surge (classic) without any interference or compatibility issues.

 

Here's a quick rundown of what's causing me issues:

Samsung Galaxy S5 paired with Surge (Classic) works fine. Powerbeats2 Wireless Headphones works fine with my phone. However the issue comes when I try to use the Surge (Classic) with the Powerbeats2

 

More complicated Rundown:

Upon using the headphones connected to my phone, all I have to do to pair is press a button on top of the headphones to connect (which is super convenient) given that my phone's bluetooth is turned on. Now, if I have Surge (Classic) connected before I connect the headphones, it may allow me to access the song track via my Fitbit Surge for one song before it kicks me out of my tracklist on the watch and says "No Music" on the screen if I'm lucky, or it may kick me out and not connect at all. On the reverse side of this, if I connect my headphones first, then double tap my surge to pull up the music track it will say "Connecting..." and fail to connect. Also, another interesting thing to note is that in the bluetooth settings on my phone, under paired devices it says:

Powerbeats Wireless

Connected to phone and media audio.

Surge (Classic)

Connected to input device.

---- It seems as if everything is in order here and working properly, however the functionality just doesn't work.

 

If anyone smarter than me would like to enlighten me on the issue I would appreciate it very much.

Thanks

 

 

Best Answer
0 Votes
14 REPLIES 14

bump

Best Answer
0 Votes

getting tired of bumping.

Best Answer
0 Votes

Anyone?

Best Answer
0 Votes

So let me understand, and correct me if I'm off track:

 

Your trying to connect your BT earbuds and control the music with the Surge?

 

Edit:

 

FWIW - Mine works with my BT headphones without an issue. I had to manually connect the Surge after the headphones were connected - it didn't just connect on it's own - then just double-press the home button, and the screen showed the song that was playing and was able to go to the next song. Worked with both the stock music app, and google music.

 

Granted, I am not using the same earbuds, so that could be the issue...

Best Answer
0 Votes

Yes this is exactly the problem. I believe there must be a compatibility issue? But not sure..

Best Answer
0 Votes

Still no answer here, someone please help me fix this it's bugging me. #FirstWorldProblems 

Best Answer
0 Votes

The problem comes from the priority of the interrupts that the pgones os assigns to your music xontrol devices. Which ever music control, assigned the higher interrupt level wins the race.

Best Answer
0 Votes

o..kay? but this doesn't explain why other bluetooth headphone devices work seemlessly. IF anything, I must have stumbled upon a bug that fitbit should fix.

Best Answer
0 Votes

How can I report this issue to fitbit people so that it can potentially get fixed in a firmware update?

Best Answer
0 Votes

I have the exact same problem! Its with a Blueant Pump bluetooth headphones and LG G4 phone. Individually they connect fine, but once it comes together the Fitbit cant seem to do music control anymore. But it still syncs with the app fine.

 

It gets really frustrating especially during the run 😞

Best Answer
0 Votes
Unsync your surge while the headset is still syncd and then resync the surge. Double tap home.
Best Answer
0 Votes
I tried that before, but it doesnt work. It works initially, but once the
surge shows the time, and I try to go to music player mode on the surge, it
cant connect again.
Best Answer
0 Votes

Fitbit simply needs a firmware update to fix this! I believe that is all it takes.

Best Answer

Hello there guys! Thank you for providing your ideas and suggestions. I want to encourage you to voice your opinion in our Feature Request board. Feel free to share your idea with us, in that way you'll get a lot of votes!

 

Good luck!  

Fitbit Community ModeratorVivian | Community Moderator, Fitbit

Did this help you? Help others by marking it as a solution! 🙂

Best Answer
0 Votes