02-14-2016
14:37
- last edited on
03-30-2017
12:43
by
ErickFitbit
02-14-2016
14:37
- last edited on
03-30-2017
12:43
by
ErickFitbit
I have a surge paired to a Huawei p8. I have tried all the different fixes listed in various forums. I have notification on in the all on my phone set to Huawei contacts. I have notifications on on my surge. I get absolutely nothing. Anyone with a P8 solved this problem. I have later Android and fitbit versions.
Moderator edit: edited title for compatibility
Answered! Go to the Best Answer.
03-26-2018 21:07
03-26-2018 21:07
Any updates??? I hope your team knows that Huawei is one of the largest phone brands sold worldwide. I'm still upset about this. I literally have to bring out my old LG3 to sync my fitbit. I have nothing else to sync it to. This better be fixed soon.
03-26-2018 22:04
03-26-2018 22:04
03-27-2018 09:35
03-27-2018 09:35
Hi @FitmanFit, I've seen that like a month ago Fitbit declared the Hauwei lite models not to be compatible. After more than a year since the issues began. That's ridicolous.
Now, very recently I've started googling a lot and it does seem that it's Huawei's fault, also other trackers from other brands are having the same troubles. But here you see where Fitbit is at fault. On Garmin forums as soon as the issue appeared the engineers answered in days, in a week or so they identified the root of the problem and then escalated the problem to Huawei and found some solutions. While constantly keeping the customers updated about what was going on.
Here we haven't been given any update of any kind for more than a year. The only answer that they keep on giving us is a ridicolous "please, choose a phone from the list of supported devices", despite the fact that the list has seen just 2 additions since 2016 and, at the moment, it lists JUST ONE phone that is currently on the market.
03-27-2018 09:48
03-27-2018 09:48
Hi @luca85,
thanks for the info.
Do you have a link to the declaration regarding the Huawei lite models being incompatible?
I wonder what is going on because there seem to be some users who got the P9 lite working with their Fitbit devices. There really shouldn't be a major issue. I realise that some Huawai phones are very aggressive regarding increasing battery life, but there should be a way by using phone settings and Fitbit app behaviour in a manner that makes the Fitbit device work with the Huawei phones.
I recently managed to get my Pebble (the classic, the very first model they made) going on the P9. I had severe disconnection issues initially but managed to configure the P9 in a manner that it does not turn off the Pebble app in order to increase battery life. I have some hope that the same technique could work for the Ionic.
How is it possible that a smartwatch from a lowly garage company from 2012 is working with my Huawei P9, but Fitbit devices from 2016 or later find it impossible to work with such phones? That does not make one bit of sense to me.
03-27-2018 09:54
03-27-2018 09:54
Here it is:
https://help.fitbit.com/articles/en_US/Help_article/2315
It's been published recently, most likely at the beginning of february with no publicity whastoever. Mods weren't citing it even weeks after it appeared, keeping on copy-pasting "not compatible yet". That's all I know.
03-27-2018 10:12
03-27-2018 10:12
Thanks for the link.
I'm very puzzled.
First, there is at least one user who reported that the Ionic syncs with the P9 Lite.
Is the Ionic not a Fitbit device?
Second, why don't they just program the watch/app combination in the same manner as the Pebble classic combination works? I repeat, my Pebble from 2013 perfectly syncs with my Huawei P9. Fitbit is supposed to have engineers from the Pebble team, so they should know how to do it.
I find it extremely hard to believe that the Huawei Lite models have limitations that make it impossible for Fitbit to make their devices compatible with them. As a result, the phrasing "Due to Bluetooth issues that prevent Huawei Lite models, including P8 and P9 Lite, from syncing with some devices, like Fitbit devices, our products are not compatible with these mobile phones." strikes me as laying the blame on others while it would seem technically possible to make the combination work.
There is a chance that the P9 Lite user I referenced above used on older version of the Android OS running on the phone and that there are indeed severe technical hurdles with newer versions, but that seems unlikely to me.
03-27-2018 10:35
03-27-2018 10:35
03-28-2018 03:49
03-28-2018 03:49
Now I'm going to throw a spanner in the works. Ever since it became apparent to me that Fitbit was not going to support the Huawei P9 lite with my Charge2 I bought a Sony Xperia. Recently I've had some minor trouble with the Charge2 recording inaccurate distance when linked to the phone (after a year of being 100% accurate) and Fitbit help was at a loss to correct it. Different problem I know, but I decided to fire up my old Fitbit Surge to obtain the GPS functionality. After reading the latest postings I decided to get the Huawei P9 lite another go, again refuses to sync with the Charge2 BUT SYNCS PERFECTLY WITH THE SURGE.
Someone within Fitbit is not being honest with its customers, Huawei may have changed the android operating system in such a way as to make it difficult for Fitbit Charge2 to sync but as the Surge syncs I cannot see that this is an insurmountable issue. Rather I see it as a direct decision not to support certain phones.
03-29-2018 04:09
03-29-2018 04:09
Regarding your Garmin VivoActive HR have you tried temporarily deactivating Google Play Services? Maybe it won't work for you; maybe there is a hitch, but any time I look into something it appears that someone finds a solution.
So, I wouldn't be too quick to state that the Huawei P9 Lite makes a connection impossible.
03-29-2018 04:12
03-29-2018 04:12
@SunsetRunner
I agree, it sure looks like it is a "decision not to support certain phones" rather than any insurmountable technical hurdles.
I guess future Huawei P20 Pro users -- this phone has just been measured to have the most capable smartphone camera on the market -- won't be able to use Fitbit devices either (unless they manage to come up with their own workarounds).
03-29-2018 04:17
03-29-2018 04:17
Regarding your Garmin VivoActive HR have you tried to temporarily deactivate Google Play Services?
It seems any time I look into such issues there is someone who is able to find a workaround. So I wouldn't be too quick to believe that the the Huawei P9 Lite makes connections impossible. As other watches/apps demonstrate, as long as one properly programs to account for these phones (probably regarding energy saving features that exist on some other phones as well) then they do work with external devices.
03-29-2018 07:52
03-29-2018 07:52
I'm ready, this time, to give fitbit credit. If other brands had the same issue most likely there's something wrong in the Huawei device. I don't have any clue regarding what it could be. It just doesn't make any sense that noone is investigating the issue and reporting what's happening. Like you, it seems impossible to me that someone is making the hardware incompatible (Bluetooth is so standard) but... What do I know?
Why can't anyone tell where the issue is? I mean... if it turned out that it was 100% huawei's fault, wouldn't it be better for fitbit?
03-29-2018 09:21
03-29-2018 09:21
03-29-2018 19:35 - edited 03-29-2018 19:38
03-29-2018 19:35 - edited 03-29-2018 19:38
Unlike you, I'm not ready to give Fitbit credit.
I agree that if there were an actual issue with Huawei phones, it would be ideal for Fitbit to explicitly point that out. Fitbit doesn't, however; they only use suggestive language to imply that this is the case but the phrasing is such that they don't unequivocally assign blame.
One can wonder why Fitbit isn't more forthcoming about blaming Huawei devices. Either it is because they are unable to as the fault is with their technology, or they just don't care.
03-29-2018 19:37
03-29-2018 19:37
Do you have a link for us?
03-29-2018 19:51
03-29-2018 19:51
Unlike you, I'm not ready to give Fitbit credit.
I agree that if there were an actual issue with Huawei phones, it would be ideal for Fitbit to explicitly point that out. Fitbit doesn't, however; they only use suggestive language to imply that this is the case but the phrasing is such that they don't unequivocally assign blame.
One can wonder why Fitbit isn't more forthcoming about blaming Huawei devices. Either it is because they are unable to as the fault is with their technology, or they just don't care.
03-30-2018 01:54
03-30-2018 01:54
03-30-2018 01:57
03-30-2018 01:57
@Ternerh
You said something very similar before.
I looked for a respective statement but didn't find anything, that's why I asked for a link.
Can you point us to a source, please?
P.S.: Why would they not "allow" it?
They "allow" it for the P8, etc.
03-30-2018 04:22
03-30-2018 04:22
@FitmanFitwrote:
One can wonder why Fitbit isn't more forthcoming about blaming Huawei devices. Either it is because they are unable to as the fault is with their technology, or they just don't care.
That's the other thing I don't understand. Apparently fitbit mostly works with all android phones. Yet the list of approved devices doesn't include any device made after 2015, excluding the S7, S8 and the first pixel. It does look like they're trying to hide something.
03-30-2018 04:37
03-30-2018 04:37