Android 6.0 Sony Z5 Surge (Classic)

[Tao75]

Just got android 6.0 on my Sony Z5. Experiencing problems with Surge (Classic), my phone keep trying to start the Throw function when music control is enabled. And I have not turned on the Throw function in my phone. This keeps restarting music control again and again on my Surge. Making problem with skip function on my Surge. Anyone experience the same problem? Or have a solution how to prevent the Throw function to interfere?
Have tried reseting my Surge, reinstalling app, disconnect device, and setting it up again, but the problem is still there... HELP

[VivisFitbit]

Hey, @Tao75 nice to see you again! This is the first time I hear something like this. I'd like to know if you're using your native Android player or another app. Are there any other Bluetooth devices nearby? Something like headsets maybe? And last but not least, please try to turn your Bluetooth off and then turn it back on. 

Le me know if this helps! 

[Jubed]

Happens to me too on a z3 compact.

[VivisFitbit]

Hello there @Jubed! Allow me to help you with this. I'd like to know if you already tried to disable and enable your notifications and music control, to do so: 

1. On your mobile device, go to Settings > Bluetooth.
2. In the list of devices, find your tracker.
3. Tap the icon next to the tracker name and then tap Forget this Device.
4. Restart your mobile device.
5. Try setting up music control and notifications again.

I also want to share a list of app that work with Surge. 

-Samsung music app

-LG Music app

-Rdio

-Amazon Music

-Spotify

-Play Music

Currently Pandora doesn' work with Surge. 

Let me know if you need more help. 

[Tao75]

Went from Surge to Blaze. The z5 still try to enabel throw every time i use music control. This makes a disturbens with conection between the device and phone. Using Spotify.

[VivisFitbit]

Thanks for the update @Tao75! Currently  the Sony Z5 is not included in our list of supported devices. I recommend keeping an eye on this list and check for the updates. 

Good luck! 

[Tao75]

@VivisFitbit Well everything else runs smoothly between Sony z5 and fitbit blaze end surge. No prooblems with notifications. Its only the Throw function thats make some disturbens with Bluetooth classic.

[imagine002]

I've got a z3 compact with the same issue, and it is on the list of compatible devices, specifying music. Sony's "Throw" app turns on and the fitbit suddenly says "connecting". I've followed the forget device instructions as well. 

[AlejandraFitbit]

Great to see you around @Tao75 and @imagine002 welcome to the Community! I would like to know if you keep having problems connecting your tracker with your phone? If you do, I recommend checking if your phone is on our list of compatible mobile devices, if it is not there that's the reason why you are having problems connecting your tracker with your phone.

If your phone is there, check the Surge (classic) won't sync for music control post, where our friend @DerrickS is providing some good troubleshoot to fix this inconvenience.

I hope this helps, let me know the outcome. 

[SalvorHardin]

Wow, that was a super unhelpful reply and link from a so called Moderator. Thanks...

So this issue exists for users of Android 6.0.1, and occurs when you activate the music controls of the device. Sony's Throw application starts trying to repeatedly connect to the Surge.

I can post a video of this happening if it would help. I have a Sony Xperia Z3, for the record, though to be honest this information is fairly irrelevant.

[SalvorHardin]

(I should have added - please can this be mentioned to a developer, not just looked at by a web forum moderator who then directs me to the supported devices list?)

[imagine002]

Yes, Moderator seemed to miss the point. We mentioned out phone models, and as I mentioned specifically, it is in the supported device list. And as we'd mentioned, we'd already paired.  After they are paired (following the instructions linked), that is when the issue arises. It appears the "Throw" software on Sony phones (those on the "supported list" and those not) interferes with how the Fitbit and the phone communicate with each other in some way. 

The minimum effort would be to update the Supported Devices list to accurately reflect the Sony phones not supported. The real solution is a software update.

[AlejandraFitbit]

Welcome to the Community @SalvorHardin and it's great to see you around. Thanks both for your feedback, I recommend doing the following:

• On your mobile device, go to Settings > Bluetooth and make sure Surge (Classic) is connected. If you no longer see Surge (Classic) on the list, you need to set it up music control again.
• Confirm that your mobile device is within about 20 feet of your Surge.
• In the settings on your Surge, confirm that Bluetooth Classic is set to "Pair."
• Try switching Bluetooth Classic from "Pair" to something else and then back to "Pair."
• Restart your mobile device.

If you keep having problems, get in touch with our support team for further assistance. For a faster response you can contact them via phone or chat.

Catch you later. 

[imagine002]

Sorry, but you're missing the point. The devices connect via Bluetooth. They even sort of work. When initially connected, it works for a second. then, On the phone, the "throw" app -- a Sony app that handles Bluetooth connections -- pops up every half second, saying "connecting". When it does that it interferes with the existing connection. A half second later, it disappears, the Fitbit connection works, you see the album and options on the Fitbit, then throw kicks in again and tries to resolve the connection again. It's rhythmic and independent of the proximity. As we've said many times before, this is a software issue. Of anyone at Fitbit would try this on an actual z3c or z5c this would be obvious.

[imagine002]

Or a z3 or z5 apparently

[SalvorHardin]

I fixed this! 100% fully fixed!

I sold my Fitbit.

Job's a good 'un. If they can't even understand being told "this is a fault, this is how to reproduce it, please advise", then sod it. Not worth the hassle.