10-30-2017 08:59 - edited 11-09-2017 07:50
10-30-2017 08:59 - edited 11-09-2017 07:50
Hi,
Case open with fit bit: ref:_00D40N2lj._5000b1BbOc6:ref
Issues:
1. Took 24 hour effort to atleast setup watch. Finally it worked only after log in my account on wife's iPhone.
2. In start Motorola phone Moto X pure will never get connected and you will waste hours doing that. Later after getting frustrated you will try on other phone which is IOS based and that to you will be able to connect after one hour of effort.
3. Wallet does not work. Image attached.
4. Pandora never sync and hard to connect Bluetooth device in first go.
5. Sync will fail all the time.
6. No notification on phone as this is not supported on Moto X pure. Customer support says phone will be added soon, but how soon as this was released already in 2015.
Issue resolved after downloading update from following website.
https://www.thecustomdroid.com/manually-install-moto-x-pure-nougat-ota/
Answered! Go to the Best Answer.
10-30-2017 16:31 - edited 10-30-2017 17:13
10-30-2017 16:31 - edited 10-30-2017 17:13
I have a Moto X Pure too (but with Android 7.0). When I still had Android 6, there were Bluetooth sync issues with this phone; had to turn my location on for it to work. I got my Ionic after the update to Android 7. Though it's not an officially supported phone, it took about 1.5 hour to set everything up and works fine for me now. I sync twice everyday manually without the auto-sync. It sometimes takes 1-2 retries to sync properly. But I'm able to use Wallet. As you said, Pandora was a nightmare to sync, but it worked, ultimately, God knows how. Clockface changes need much more retries. Notifications don't work too. Only the "Send Test notification" option in the Fitbit app works :D.
If you haven't returned it yet, I would suggest two things:
1) Try updating your phone to Android 7
2) If your WiFi at home is not good, do not add that connection. This happened in my case: it felt like the Ionic is continuously trying to find a good reception but never succeeds. I removed it and the Bluetooth connection just worked.
10-30-2017 09:00
10-30-2017 09:00
Try turning off two settings on your Android device then rebooting your phone and watch:
10-30-2017 09:04
10-30-2017 09:04
Another link you might find useful:
https://www.fitbit.com/uk/devices#
10-30-2017 09:11
10-30-2017 09:11
Hi,
I have Fitbit IONIC, Moto X Pure (XT1575), Android 6.0. Issue is not just with sync the issue is with other app. Music does not work with this phone settings, not able to setup wallet as mobile is not able to connect to watch and also not able to sync regularly after tunring of all day sync.
It fails in 5 to 10 attempts and then sync after 10 minute. So I can wait for 15 seconds but not 10 minute to do that.
10-30-2017 09:15 - edited 10-30-2017 09:20
10-30-2017 09:15 - edited 10-30-2017 09:20
@rohu.2788 wrote:Hi,
I have Fitbit IONIC, Moto X Pure (XT1575), Android 6.0. Issue is not just with sync the issue is with other app. Music does not work with this phone settings, not able to setup wallet as mobile is not able to connect to watch and also not able to sync regularly after tunring of all day sync.
It fails in 5 to 10 attempts and then sync after 10 minute. So I can wait for 15 seconds but not 10 minute to do that.
Please try it before you rule out and assume it isn't going to fix your problem/s and then let us know. If you read the thread you'd probably would have done so before responding. For my Pixel it fixed pretty much most of what you are describing. It sync's fine now and notifications come through immediately. I'm not trying to fix 100% of your issues immediately.
10-30-2017 09:16
10-30-2017 09:16
You don’t give your location. Wallet only works in a few locations at the moment.
10-30-2017 09:25
10-30-2017 09:25
My location is United States
10-30-2017 09:31
10-30-2017 09:31
I Tried all the options which you have suggested and still this does not work. Even called customer support, they have worked with me multiple time and not able to resolve the issue. Finally they tried the same thing on device which they have with them and it is not working for them to. They suggested me to wait for the device to be added into supported list. This is not the best approach.
In USA, I have:Ionic. Moto X Pure(XT1575). Android 6 OS.
10-30-2017 09:38 - edited 10-30-2017 09:38
10-30-2017 09:38 - edited 10-30-2017 09:38
@rohu.2788 wrote:I Tried all the options which you have suggested and still this does not work. Even called customer support, they have worked with me multiple time and not able to resolve the issue. Finally they tried the same thing on device which they have with them and it is not working for them to. They suggested me to wait for the device to be added into supported list. This is not the best approach.
In USA, I have:Ionic. Moto X Pure(XT1575). Android 6 OS.
IMHO if it's not here:
https://www.fitbit.com/uk/devices#
Return it. Your device is not supported plain and simple. Or get another phone.
10-30-2017 09:41
10-30-2017 09:41
Hi,
Thanks for help. Yes this is what I am thinking, device is not supported. I can not put money again on new phone.
The only issue is that now merchant is not taking device back as it is not their policy. They have policy to directly deal with fitbit. but customer support was not helping on this case so, opened a ticket on email to work with them on this.
10-30-2017 09:42 - edited 10-30-2017 09:45
10-30-2017 09:42 - edited 10-30-2017 09:45
@rohu.2788 wrote:They suggested me to wait for the device to be added into supported list. This is not the best approach.
In USA, I have:Ionic. Moto X Pure(XT1575). Android 6 OS.
Ah well, if the device isn’t listed as supported... frustrating but you can’t really complain if it doesn’t work.
edit - n.b. Must remember not to bother trying to reply to threads while @SunsetRunner is online, as he types quicker
10-30-2017 09:44 - edited 10-30-2017 09:45
10-30-2017 09:44 - edited 10-30-2017 09:45
10-30-2017 09:56
10-30-2017 09:56
I don't buy that it's the phone that is the problem. my Blaze worked perfectly with my phone.
10-30-2017 10:01
10-30-2017 10:01
@SunsetRunner wrote:
@rohu.2788 wrote:I Tried all the options which you have suggested and still this does not work. Even called customer support, they have worked with me multiple time and not able to resolve the issue. Finally they tried the same thing on device which they have with them and it is not working for them to. They suggested me to wait for the device to be added into supported list. This is not the best approach.
In USA, I have:Ionic. Moto X Pure(XT1575). Android 6 OS.
IMHO if it's not here:
https://www.fitbit.com/uk/devices#
Return it. Your device is not supported plain and simple. Or get another phone.
This is a very bad and misleading answer; many-MANY folks, myself included, use Moto X and Moto Z phones with no issues; that and there are many-MANY other phones on the market which are not on the supported device list which interface with the Fitbit lineup with no issues.
10-30-2017 10:18 - edited 10-30-2017 10:24
10-30-2017 10:18 - edited 10-30-2017 10:24
@shipo wrote:
@SunsetRunner wrote:
@rohu.2788 wrote:I Tried all the options which you have suggested and still this does not work. Even called customer support, they have worked with me multiple time and not able to resolve the issue. Finally they tried the same thing on device which they have with them and it is not working for them to. They suggested me to wait for the device to be added into supported list. This is not the best approach.
In USA, I have:Ionic. Moto X Pure(XT1575). Android 6 OS.
IMHO if it's not here:
https://www.fitbit.com/uk/devices#
Return it. Your device is not supported plain and simple. Or get another phone.
This is a very bad and misleading answer; many-MANY folks, myself included, use Moto X and Moto Z phones with no issues; that and there are many-MANY other phones on the market which are not on the supported device list which interface with the Fitbit lineup with no issues.
Sounds like POTUS tweeting LOL.
I've offered all the advice I can, do you have any ideas you can offer the OP on how to fix this?
Look it's this simple, if it's not working and it isn't a supported device, and it still continues not to work then the OP isn't going to have a leg to stand on and that will be the end of it. The OP will be stuck in limbo. ** I strongly recommend people buy officially supported hardware for their device **
That said I hope the OP finds a solution so he can use it. Your turn.
10-30-2017 11:14
10-30-2017 11:14
Hi, I do not say it is a problem for Blaze. This problem is with Ionic watch
10-30-2017 11:35
10-30-2017 11:35
@rohu.2788 wrote:Hi, I do not say it is a problem for Blaze. This problem is with Ionic watch
Hmmm, no, not buying, I have a Moto Z Play and an Ionic and they work perfectly together.
10-30-2017 11:46
10-30-2017 11:46
@shipo wrote:
@rohu.2788 wrote:Hi, I do not say it is a problem for Blaze. This problem is with Ionic watch
Hmmm, no, not buying, I have a Moto Z Play and an Ionic and they work perfectly together.
Well I don't know the answer and nor does Fitbit according to the OP.
Over to you then.. hopefully you can offer the OP some very very good advice, the best advice. Perhaps many MANY people will benefit from your wisdom and the Ionic will be made great again.
10-30-2017 11:55
10-30-2017 11:55
@SunsetRunner wrote:
@shipo wrote:
@rohu.2788 wrote:Hi, I do not say it is a problem for Blaze. This problem is with Ionic watch
Hmmm, no, not buying, I have a Moto Z Play and an Ionic and they work perfectly together.
Well I don't know the answer and nor does Fitbit according to the OP.
Over to you then.. hopefully you can offer the OP some very very good advice, the best advice. Perhaps many MANY people will benefit from your wisdom and the Ionic will be made great again.
Sorry, all I can tell you is it works perfectly well; unless y'all are willing to release the code base to me for both Android and the Ionic, I would have no way if diagnosing why it works for me (and many others), but not for some. The fact it, if it works for the majority of folks who try it (or even one single individual for that matter) it should work for all; I mean, it isn't like I'm trying to move a trigger from one hand-made flintlock rifle to another.
10-30-2017 11:57
10-30-2017 11:57
So OP is stuck and has to return it if nobody has any better ideas.. which is basically what I was saying.