09-20-2016
07:19
- last edited on
10-17-2016
08:39
by
RodrigoFitbit
09-20-2016
07:19
- last edited on
10-17-2016
08:39
by
RodrigoFitbit
I'm rather upset... when I first thought about getting the Surge, I checked the Fitbit website and saw that the Moto X (2015) or Moto X Pure was listed as a compatible device. Over the last few weeks/month or so, I've been noticing that my call notifications "disables itself." This seems to happen when I go for a run, and my device is out of reach... but haven't verified that. I have to go into the app, disable and then re-enable the call notification option for it to begin working again. This happens every few days (or whenever I'm seemingly out of reach of the phone, I think).
I chat with Fitbit support who tells me that my device isn't supported, which is probably why it's happening. The Moto X (2015) is now not listed. I bought the Surge in part because it was compatible with my phone.
Moderator edit: Format
09-20-2016 07:29
09-20-2016 07:29
I think that happend to me a couple of times with the Nexus 5 after an Android update. It eventually sorted itself out after (I think) an app update.
It's very unusual for Fitbit to drop compatibility with a new phone after previously certifying it. I see that it is no longer listed, but that may be until they sort out this bug with the phone.
09-20-2016 07:50
09-20-2016 07:50
@Bwangster12 wrote:I'm rather upset... when I first thought about getting the Surge, I checked the Fitbit website and saw that the Moto X (2015) or Moto X Pure was listed as a compatible device. Over the last few weeks/month or so, I've been noticing that my call notifications "disables itself." This seems to happen when I go for a run, and my device is out of reach... but haven't verified that. I have to go into the app, disable and then re-enable the call notification option for it to begin working again. This happens every few days (or whenever I'm seemingly out of reach of the phone, I think).
I chat with Fitbit support who tells me that my device isn't supported, which is probably why it's happening. The Moto X (2015) is NOW NOT LISTED. I bought the Surge in part because it was compatible with my phone.
I believe you are mistaken; I use a Moto X (2013) with my Fitbit Surge and have been tracking the https://www.fitbit.com/devices page for about a year now and have never seen the Moto X Pure (2015) listed, and unless I'm missing it, it still isn't listed.
09-20-2016 10:26
09-20-2016 10:26
I'm 100% sure that for a minute or a week that the Moto X (2015) was listed. I was researching running watches and checked out the Surge specifically to see. I remember clicking on Moto X (2015) and viewing all the compatible features.
09-20-2016 10:56
09-20-2016 10:56
@Bwangster12 wrote:I'm 100% sure that for a minute or a week that the Moto X (2015) was listed. I was researching running watches and checked out the Surge specifically to see. I remember clicking on Moto X (2015) and viewing all the compatible features.
Timeframe? I ask because I've been holding off on upgrading my phone to a Moto X Pure until the new phone is supported. I've been checking the Devices page pretty consistently since last fall and have never once seen anything other than the 2013 and 2014 versions of the Moto X listed.
09-20-2016 13:22
09-20-2016 13:22
Hello guys @shipo @Bwangster12, hope you're doing great today! Thanks for your help @SunsetRunner!
I was double checking the supported devices we have for Motorola and I still get the following:
Sometimes this have happened to me when I go for a short run. There is a radius of distance the GPS will pinpoint your location and sometimes wont reflect the actual course you have took it. To give you an example, it will show you were running across the street, but in reality you were running in straight line. However this shouldn't impact your final result specifically talking about distance, amount of steps and other stats. Although the actual accuracy depends on both your environment and the weather.
GPS location is not recorded unless you initiate an activity on your Surge, Blaze, or App using MobileRun. You can learn more specifics about Fitbit's GPS functionalities here.
Nice day!
Was my post helpful? Give it a thumbs up to show your appreciation! Of course, if this was the answer you were looking for, don't forget to make it the Best Answer! Als...
09-20-2016 13:39
09-20-2016 13:39
@MarreFitbit, any word on when the Moto X (2015) Pure will be supported?
09-22-2016 05:00
09-22-2016 05:00
Fitbit is the first fitness device to offer Bluetooth Smart syncing with your Android device. Wireless sync has been a frequently requested feature from our Android users, so we've been eager to get support out as quickly as possible. While many Android devices have a Bluetooth 4.0 chip, not all devices are able to be accessed by apps like the Fitbit App.
To see the latest list of supported devices, please go to the list of supported devices. If your device isn't listed, you can check the link at a later date to see if device support has been added.
I appreciate your understanding while we work to improve this experience, and encourage you to let us know if you have any additional feedback on this and other features, you have a great day @shipo!
Was my post helpful? Give it a thumbs up to show your appreciation! Of course, if this was the answer you were looking for, don't forget to make it the Best Answer! Als...
09-23-2016 03:16
09-23-2016 03:16
Very unusual ??
My phone is an Honor6 (huawei), it is right into the certified list, but it NEVER worked for notifications.
After a very long fight with developers, they have hacked the beta fitbit app for make it to work under the latest firmware update (Android 5.0.1), then huawei have upgraded honor6 to marshmallow 6.0 firmware, and all the notifications stack suddenly stop to work again.
Certification list is completely speculative for me, it means "it is supposed to work, verify yourself please"
09-23-2016 04:11
09-23-2016 04:11
Thanks for joining us here @MaRaNtZ! Since you are running OS 6.0 (Marshmallow), please note that Google has changed the permissions required for Bluetooth syncing. You must turn on location services to sync your tracker (Settings > Location). For more information about the latest Google permission requirements, see Google's Android 6.0 Changes document.
If your notifications are still not working after checking that, I'd recommend troubleshooting your tracker and phone by following the instructions I've posted here.
Let me know the good news!
Was my post helpful? Give it a thumbs up to show your appreciation! Of course, if this was the answer you were looking for, don't forget to make it the Best Answer! Als...
09-23-2016 06:10
09-23-2016 06:10
09-23-2016 06:24
09-23-2016 06:24
If you have tried what has been suggested and your tracker is still not syncing properly I'd recommend getting in touch with Customer Support directly so they can do a deeper investigation into your account and see where the issue is coming from.
Don't forget to mention the steps you've done so far to avoid getting the same ones, you'll be in good hands @MaRaNtZ!
Was my post helpful? Give it a thumbs up to show your appreciation! Of course, if this was the answer you were looking for, don't forget to make it the Best Answer! Als...
10-09-2016 16:20
10-09-2016 16:20
Does location need to be turned on to receive notifications or only for syncing?
@MarreFitbit wrote:Thanks for joining us here @MaRaNtZ!
Since you are running OS 6.0 (Marshmallow), please note that Google has changed the permissions required for Bluetooth syncing. You must turn on location services to sync your tracker (Settings > Location). For more information about the latest Google permission requirements, see Google's Android 6.0 Changes document.
If your notifications are still not working after checking that, I'd recommend troubleshooting your tracker and phone by following the instructions I've posted here.
Let me know the good news!
10-10-2016 03:40 - edited 10-10-2016 03:42
10-10-2016 03:40 - edited 10-10-2016 03:42
The "location" settings need to be turned on for syncing.
In my case, it *IS* turned on, and sync works.
BUT, notifications have nothing to do with syncing.
They has been always an hit or miss affair, because the app so poorly programmed.
In my case, i have 4 mobiles around, and it works in only one of them (the older 5.0xx).
No way to get it working properly on most modern 6.0.x phones. *BEWARE USERS*
Of course, fitbit do not care about this, always indicating to follow useles throubleshooting guides, so taking time instead of fixing things obviously broken.
10-28-2016 17:08
10-28-2016 17:08
I really like my X Pure, so this is dissappointing. This is making me consider other brands if I can't use these together.
10-28-2016 17:17
10-28-2016 17:17
@chemicalx wrote:I really like my X Pure, so this is dissappointing. This is making me consider other brands if I can't use these together.
I checked around about a month ago and none of the major brands of trackers supported the Moto X Pure at that point; that said, there are plenty of anecdotal reports which suggest Android 6.x on the Pure will interact with a Fitbit successfully.
10-28-2016 17:21
10-28-2016 17:21
It hasn't been working well with the Moto X pure, there was a whole post about it. As things currently exist, this is tolerable. Things seem to be able to comunicate well enough for how I use my fitbit, but I am definitely not able to get full use of my fitbit blaze at the moment.