Music control

[Udmg]

Hello, I'm having issues with blaze controls for my music. The screen tries to refresh itself and going back and forth between flickering/connecting. My blaze worked just fine on my iPhone with no delays or connection issues but on my Android phone (Google pixel) there's a problem. I have paired and unpaired while shutting off the device but no luck. Any suggestions?

[Kmransom123]

@Udmg  Your Google phone may not be a supported device, hence the difficulties you are experiencing. I am not seeing it listed - you can check here https://www.fitbit.com/devices

[Udmg]

It's not listed, however it worked for a few times but hasn't synced for two days now. Any ETA on device updates?

[Kmransom123]

Unfortunately, I don't believe there is any schedule of new compatable devices released.  Fitbit just probably adds them in as they get them tested.

Have you tried restarting the Blaze as well?

[Udmg]

I have, it seems to only work if it's a brand new install. After you turn off the classic Bluetooth it never connects again. Which reminds me why would a new Android device require Bluetooth classic support any way?

[Kmransom123]

@Udmg  I'm not familiar with Android phones, but I ~believe~ the BT Classic is required for music control only.  (Don't hold me to that, just that I think I remember seeing that on these forums). Someone who does know may chime in)

[Udmg]

@Kmransom123 I still have a iPhone device (6s) and just recently purchased pixel due to it being google first push at the high end tier. As a android fan I couldn't resist but I do see a difference from app support from apple to android. The new dashboard that just came out for android has been released a few months ago on apple, why so late? Also I understand that classic Bluetooth is too support older versions of Bluetooth hence the name but any android phone from last year onward is already 4.0 plus. Why the segregation between the two may I ask?

[Rich_Laue]

Hello @Udmg  as for music control, my problem has been, occasionally I have to reboot the phone to get it to work.

As for why so late on android, this is just my speculation, but I assume that it is simply easier to program and troubleshoot for apple phones. Why is this?  Apple writes its own OS, and designs it's hardware, Android writes the OS and let's the Hardware designers do what they want. This means that there are less variables to work with when programming for ios.  As a beta app tester I've been running the new dashboard for a few months now, helping to weed out the bugs.

[Udmg]

I'm not a coder by any means and I have basic knowledge of Python but most Android hardware is running the same Qualcomm snapdragon chipset meaning it's not a huge disparity between each brand other than custom skins with a few gimmicks. I can slightly understand if it's os version which requires some tweaking between latest and previous versions or is it the Java platform that causes complexity compared to swift? I'll try the beta versions to keep afloat and post any issues, hopefully my battery doesn't take a hit.

[Rich_Laue]

My answer was not about the music control but why the dashboard delay in Android.

[Udmg]

Your saying even the beta versions give you problems with the music control? Is your device a pixel phone as well?

[Rich_Laue]

Yes @Udmg, im going to assume you're addressing me, every couple of weeks I find the music control not working, a phone restart fixes it.

What causes it, I'm not sure, with having my cars audio(home made adapter), 3 Bluetooth speakers, and 2 Bluetooth Headphones all paired, and I switch between them frequently. All the Bluetooth devices but 2 have their own music control. So the Blaze, Surge, Two speakers, Two headphones, and One selfie stick being pairedc as  input devices, to the phone, I can't say what it is. Could the problem be in the Fitbit App or the way the phones OS handles the input interrupts?

For me it is not a big deal, since with the Android phone, the user needs to do a restart once a week to clear up memory that's tied to crashed ie closed programs. Because of this none problem I do a restart once a week anyway.

I just checked there is 11 devices shown as being remembered on the BT settings,