10-31-2016
21:33
- last edited on
05-11-2017
09:09
by
ErickFitbit
10-31-2016
21:33
- last edited on
05-11-2017
09:09
by
ErickFitbit
I just got the Pixel XL last week and my charge HR hasn't synced once. I removed it from my device and tried to add it back on, but it won't add. After 30 seconds, it would say, "We found your charge hr!" And 30 seconds later, "TryAgain." I did the troubleshoot by restarting my Fitbit multiple times. I uninstalled and reinstalled the app. I called support who said to try it on another phone or computer. I don't have another phone, and the computer dongle is lost. Is anyone else having this issue with the Pixel XL?
Moderator edit: edited title for clarity
Answered! Go to the Best Answer.
12-12-2016 17:52
12-12-2016 17:52
@doug5222 amazing workaround! Thanks for sharing.
@lucre thanks for joining us! Fitbit frequently adds support for new devices, so if yours isn't listed check back soon. I've found an idea in the Feature Suggestion board proposing compatibility with Google Pixel device. Check it out here, make sure you add your votes and comments!
Did you receive the answer you were looking for? Mark the post as an accepted solution! 🙂
12-20-2016 06:19
12-20-2016 06:19
New Google Pixel phones not yet a supported device for call notifications etc. Fitbit: please make it a supported device ASAP.
12-20-2016 06:30
12-20-2016 06:30
It's nice to see new faces around, welcome @JoelFIT! I'd like to start saying the Google Pixel phone still is not on our list of compatible devices and we cannot guarantee it will work as it should. Nonetheless this does not mean the phone won't support the app or the tracker. It might sync temporarily but the stability of the app might fail from time to time, or it won't sync and will be harder to maintain a connection with the tracker. Our teams are still testing different phone models and brands to make wider the selection of mobile devices to make more compatible the trackers and all the features.
I've voted for the suggestion "Google Pixel smartphone support" on our Feature Suggestion Board. We're constantly striving to improve Fitbit products and services, and we very much appreciate all of the input we receive from our customers.
Thanks for jumping up here!
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...
12-25-2016 09:01 - edited 12-25-2016 09:02
12-25-2016 09:01 - edited 12-25-2016 09:02
I'm with Joe here. The pixel is a great phone and I hate that the charge 2 isn't supported. I guess I'll be returning mine ASAP and go back to my old charge. I hope the development team steps up and remedies this so one day I may have an even better tracking device.
Dan
12-26-2016 10:30
12-26-2016 10:30
I received the charge 2 for Christmas. I have a pixel phone. I really wanted the Charge but if I cannot sync it I may have to return it. Please add Pixel to your supported devices.
12-28-2016 15:11
12-28-2016 15:11
I can confirm doug5222 post that we need to turn Bluetooth off, in phone settings, prior to opening the fitbit app in our Pixels then wait for the fitbit app to give the "Bluetooth is off" message. Then just turn bluetooth on and let the fitbit app connect via low energy bluetooth in the background. Don't try and pair via the phone bluetooth device settings just turn on the bluetooth switch, in phone settings, after being asked to by the fitbit app. This method has synced with my Surge since the 25th.
This method may help until our Pixels are fully suported.
12-29-2016 12:25
12-29-2016 12:25
Thanks for sharing what has been working for you @showkit! This is what the Community is all about, sharing solutions and knowledge! It's great having you around in the forums.
Keep it up!
Did you receive the answer you were looking for? Mark the post as an accepted solution! 🙂
01-03-2017 09:38
01-03-2017 09:38
Hello,
Any sign of progress with this? If the moderators cannot answer then could they suggest who to ask?
Many thanks,
Ian
01-03-2017 12:47
01-03-2017 12:47
@SunsetRunner thanks for your question. Welcome to the forums. These things take time. I really wouldn't like giving you any misleading info or any false expectations. Our devs have to test devices to make sure they will seamlessly sync with your trackers. Please add your votes and further comments in the feature suggestion I posted above. Catch you later!
Did you receive the answer you were looking for? Mark the post as an accepted solution! 🙂
01-03-2017 12:50
01-03-2017 12:50
Thanks for the reply!
This question was first asked over 2 months ago. Is there really nothing to report in that time?
01-03-2017 12:59
01-03-2017 12:59
@SunsetRunner thanks for getting back to me. Not yet, I have checked the Feature Suggestion and there isn't any update about it. As I was mentioning before, our devs need to make sure that the sync function will properly work. They have to run many tests to make sure that all functions and features work on the Google Pixel mobile device. Please take a look at the suggestion I linked above in this thread as any update regarding this will definitely be posted there.
Did you receive the answer you were looking for? Mark the post as an accepted solution! 🙂
01-10-2017 13:47
01-10-2017 13:47
So what you are saying is that I have wasted my money buying a Fitbit charge 2 as it isn't compatible with my Pixel phone. I take it I can get a refund
01-11-2017 11:51
01-11-2017 11:51
I have turned on my location and read everything I can find. My google pixel will not sync with my Fitbit alta. Very frustrating.
01-11-2017 14:31
01-11-2017 14:31
01-11-2017 15:44
01-11-2017 15:44
@Tetley I recommend getting in touch with our Support Team and letting them know the details of your experience for further options.
@PegyD The Google Plxel is currently not listed as a supported device. This could be the reason why you're unable to sync the device. Our Android team is always working on testing and adding more devices to the supported devices list. I recommend keeping an eye on this list for updates.
In the meantime, you can try syncing with a different supported device or using a computer. Hope that helps to get you up and syncing.
01-14-2017 14:57
01-14-2017 14:57
Fitbit has really dropped the ball here. Not only is this a flashship device, but it's a device that is running pure, vanilla android. On top of that, it's been released for 4 months now, and to rub salt into the wound even further, android N has had developer preview releases dating back to Google I/O in May of 2016.
Can you please pass this thread along to the developement team so that we can get some actual information as to why fitbit is failing its customers? Note: No offense meant to you at all. As a moderator, we know that you can't give us any information because you don't get any infomration. This thread needs to be passed along and we need to hear from a Fitbit employee, manager, or developer because this is terrible customer service.
01-17-2017 18:57
01-17-2017 18:57
After 40 minutes of waiting to be connected the Fitbit "Customer Support" told me that Fitbit isn't compatable with the Google Pixel. Sad that this company is ignoring one of the hottest new devices on the market. I am taking my Charge 2 back in hopes of getting a refund.
01-17-2017 18:57
01-17-2017 18:57
After 40 minutes of waiting to be connected the Fitbit "Customer Support" told me that Fitbit isn't compatable with the Google Pixel. Sad that this company is ignoring one of the hottest new devices on the market. I am taking my Charge 2 back in hopes of getting a refund.
01-26-2017 05:53
01-26-2017 05:53
I was able to sync when I created a new profile. My previous phone was an iphone, once I deleted my old profile from my first Fitbit I was able to create a new profile and it works great.
02-06-2017 09:30
02-06-2017 09:30
Do you think this process would work with the Charge HR 2? I am getting the Pixel and would like to also get the Charge HR 2, but want to make sure it is compatible. I know the website does not list the Charge HR as compatable with Google, but I am hoping that will change soon. Thanks!