04-30-2016 19:47
04-30-2016 19:47
Any update on when the Turbo 2 is going to be live? We have the turbo 2, and literally, the ONLY reason that my wife bought the Blazes (one for her and for me), instead of the charge HR that she had (and the Vivofit that I had), is for the ability to control her music. To say that she is pissed because this $200 (x2) device doesn't work with a flag-ship, popular phone that's been out for 7 months is... a bit of an understatement. Before she returns these, I'd like to know if you're close and/or have and ETA for the Droid Turbo 2 having full functinoality with the Blaze? (Everything but the "classic" pairing, and therefore music control, currently works)
Thanks,
Mike
05-10-2016 02:36
05-10-2016 02:36
05-10-2016 08:17
05-10-2016 08:17
The Turbo 2 is different than the Droid 2 (which is an older slider keyboard phone).
Been there, done that (like 10x, on 2 different Turbo 2's, with 2 different Blazes).
05-10-2016 08:40
05-10-2016 08:40
Honestly, I have not had any noticable (or unexplainable) issues on my Verizon Motorola Droid Turbo 2 (just to be clear what I am using)
05-10-2016 08:43 - edited 05-10-2016 08:44
05-10-2016 08:43 - edited 05-10-2016 08:44
Are you using the "classic" bluetooth to control music skip and volume on your phone, or are you doing what I'm not having any problems with, which is just the stuff that the ap does (syncing, workout GPS tracks, text/call/calendar alerts, etc.)?
Mike
05-10-2016 08:53
05-10-2016 08:53
05-10-2016 09:00
05-10-2016 09:00
Sorry, I dont use the music functions on my Blaze, the notifications and syncing are all working as expected. I will try and see if I can use them later today and report back... never had a need for the controls to this point
05-10-2016 09:02
05-10-2016 09:02
Yeah, that's what I was saying. All the "normal" stuff works fine, but the music controls on the "classic" bluetooth is what I'm asking about an ETA for. I've since talked to their tech dept. and the answer is that they're working on it right now.
Mike
05-10-2016 09:18
05-10-2016 09:18
05-10-2016 09:20
05-10-2016 09:20
05-10-2016 09:22
05-10-2016 09:22
05-10-2016 09:25
05-10-2016 09:25
05-10-2016 09:37
05-10-2016 09:37
05-10-2016 11:10
05-10-2016 11:10
2 hours later, and the "Classic" will not setup to my Droid Turbo2, so I am guessing we are screwed and it wont show on the "supported list" any time soon
I always get the 'pin doesnt match' error... rebooted both devices, uninstalled/reinatslled fitbit app, and many different combinations of those
sigh
05-10-2016 11:45
05-10-2016 11:45
05-10-2016 11:48
05-10-2016 11:48
Rich,
Yeah, as I said, it all works flawlessly on my old Droid Maxx (which is on the "supported devices" list).
05-10-2016 11:49
05-10-2016 11:49
Exactly, GMM. Same here.
Mike
05-10-2016 12:12
05-10-2016 12:12
@Charmbutterfly wrote:
Yup that's exactly what happens with mine! Are you getting any
notifications on your blaze at all?
I did have one time where the 6 digit number appeared for a moment, it did match, but I could not confirm it on the Blaze... which would then allow the device to lock in as available on the Turbo2 :'(
05-10-2016 15:24
05-10-2016 15:24
05-11-2016 07:06
05-11-2016 07:06
FWIW, I tried to link again, no such luck today
05-11-2016 07:55
05-11-2016 07:55