Windows Phone Support Blaze

[supermoe]

So you've developed a completely new device but still don't support CallerID,Text Messaging or Calendar updates on Windows Phone?

Moderator edit: format

[ScottDurow]

You have to distinguish between the device and the OS. Although Microsoft are winding their device business down (until the Surface phone perhaps) - they are still actively developing Windows 10 for mobile.

[AntnyGoomba]

 Just to be clear,  the issue with Blaze and some Windows devices has nothing to do with the OS nor Fitbit. It is actually a chipset issue with Qualcomm. And it is not effecting every device with it. It's a bug. Microsoft is working on a work around for it.

[ScottDurow]

I have a Lumia 950 which has the Qualcomm Snapdragon 808.

Does the issue also happen on the other devices that share this processor? https://www.qualcomm.com/products/snapdragon/devices/all?filters=JTdCJTIyZmllbGRfZGV2aWNlX3Byb2Nlc3N...

[AntnyGoomba]

It’s a bug that does not effect all the chipsets with the same model. I’m thinking it's only effecting certain runs of it.

Sent from my Windows 10 phone

[Cybdiver]

I won't hold my breath.  I've got my Fitbit over a year now and this was a problem back then. 

As said in the post above this the Surface phone is supposedly in the works.  Maybe and big maybe they will sort it out by then.

---

@AntnyGoomba wrote:

 Just to be clear,  the issue with Blaze and some Windows devices has nothing to do with the OS nor Fitbit. It is actually a chipset issue with Qualcomm. And it is not effecting every device with it. It's a bug. Microsoft is working on a work around for it.

---

[MaxLV]

Here we go again....

First thing: It's NOT a 'bug in a chipset' at all! The reason the windows phone cant send notifications to the Fitbit Blaze is because the Blaze does not have GATT support. 

Fitbit promised us (like they've been promising for the last 2 years) in November 2016 that it will be available from March 2017. End of March 2017, NO Windows Phone 10 support.

They even ran a closed beta tester programme for selected Blaze owners from November 2016 to April 2017. It may still be running but Fitbit have been noticeably silent since their delay announcement in May. 

In May they said it would now be late Fall 2017 when the next Windows 10 update is released, before the Windows phone support would be available for the Blaze. They claimed Microsoft was having 'problems' with Windows Phone 10 GATT implementation in Windows 10.  That is not true as far as Microsoft is concerned.  The 'ball' and problem is entirely in Fitbit's court as far as I'm concerned.

No doubt Fitbit will run another 'six month' closed beta tester programme from late Fall, delaying Blaze support for Windows 10 phones until sometime in mid 2018. Then they'll be able to claim they cant offer it as MIcrosoft will be releasing Windows 11 later in 2018 or that the Blaze is now a 'legacy product' and is no longer be supported from 2018. 

[MaxLV]

 There's well over 100 messages in this thread discussing why Fitbit wont/cant/doesn't want to support the Windows 10 phone on the Blaze. Seriously, do some reading before posting questions (and incorrect answers)  that have already been asked numerous times already!

[Rich_Laue]

@MaxLVthe beta testing is still going on. Fitbit never said they won't/doesn't /they did say they can't, but that was because the problem was on Microsofts side. You need to get

The problem was that the Windows phone only had a GATT client, not the required GATT server that Fitbit, Garmon and several other activity trackers required. 

I know last year Fitbit, maybe earlier, has been working closely and still is working with Microsoft to get the notifications and GPS working. 

You really need to read the updates from the Moderators and ignore the users who have no idea. 

So where the problem is right now, I'm not in the beta, but I know Fitbit and Microsoft are working together on this to get it working. 

[AntnyGoomba]

I have been in the closed beta since day one. I also work with people in Microsoft. What I said about the bug in the chipset is true. If you read through the other forum you will see it there as well mentioned by Tristan.

Sent from my Windows 10 phone

[Cypherke]

So what you're saying is... tough luck, try another 950xl and you might get lucky?

---

@AntnyGoomba wrote:
I have been in the closed beta since day one. I also work with people in Microsoft. What I said about the bug in the chipset is true. If you read through the other forum you will see it there as well mentioned by Tristan.

Sent from my Windows 10 phone

---

[AntnyGoomba]

No, what I’m saying is between Microsoft and Fitbit they found the bug, now Microsoft is working on a work around for it. It should be coming out within the next few fast ring releases.

Tristan also posted because it’s such an odd bug in the chipset and not in the software or OS is why it took so long to find.

Sent from my Windows 10 phone

[Rich_Laue]

A bug can not be found until some piece of software accesses the routine in the buggy price if code. 

If you are old enough to remember, believe it was the 80's, the tellephone system had been working smoothly for years, then one day a piece of code was accessed. This loop had no exit point and took down the central office. This was no big deal, since the neighboring office stepped in and took over. Unfortunately this office also got trapped in the same loop, and a second then third, forth, fifth, etc office stepped in. The result was that within an hour the whole northeast area of the USA had no working telephones. The result of a very few lines of not well written code, that had never been tested or executed before. 

[ScottDurow]

All of these replies are very confusing and contradictory! I used to have a Microsoft Band 2 that showed notifications perfectly from my Lumia 950. Garmin also supports push notifications from Windows Phone 10 since GATT server support was added.

I have noticed that fitbit have made the lack of notifications in Windows Phone 10 clear at - https://www.fitbit.com/uk/devices 

*Fitbit staff* - can we have a clear statement of when/if you will add support. Please no more blaming or finger pointing!

[MaxLV]

What updates from what moderators?! The ONLY time anything comes up about it is when another disappointed customer with a Blaze finds out they cant get notifications on their blaze from their windows phone, and we get all these different 'reasons' why it doesn't/cant work!

Now we're being told by ONE user in the closed beta testing programme that it's a chipset fault! (that's a new excuse...) with no links to any of the posts he's referring to, or factual information about this 'chipset bug'.  A chipset bug in what device? The Blaze? Windows Phones?

And if it is a chipset bug how is that going to be fixed?  

As for the so called testing going on in the 'closed beta test group' where/why aren't are the updates and results being posted for the rest of us to let us know whats happening and what progress is being made?

No, just silence from Fitbit as usual, and what I've been reading about the Windows phone having GATT server/client support, Microsoft have provided this (the API and code) months ago. And still Fitbit cant get it to work!   

[MaxLV]

---

@AntnyGoomba wrote:

 Just to be clear,  the issue with Blaze and some Windows devices has nothing to do with the OS nor Fitbit. It is actually a chipset issue with Qualcomm. And it is not effecting every device with it. It's a bug. Microsoft is working on a work around for it.

---

Where is the links, posts, evidence? I've been trying to find out about the 'chipset bug' and so far all I've seen is your posts here....

[Rich_Laue]

If you go to the windows forum, yes this has nothing to do with the Blaze, Alta HR, Alta, Surge Charge 2, Charge or Charge HR. The problem is in the app and it's interface. 

The main thread is in the win10 forum. Last I read, they hit a snag that micros in

[AntnyGoomba]

 Some good news for those having notification issues…

 After yesterdays Fast Ring update, the notifications seem to be consistently working. I did notice, at least for myself, if the phone is turned off I have to open the app and let it sync before I received notifications again. I don't know if I would have waited longer if it would have done it on its own or not.

 Another thing, if you sleep with your Blaze on it'll keep waking you up at night with notifications. Quiet hours seem to be ignored.

[Cybdiver]

Does this mean the app has to be open all the time to get notifications?  can I open then close it?

So far I've been trying and no notifications.  

[AntnyGoomba]

No, the app does not need to be open. But, keep in mind the update from Microsoft was only rolled out to Insiders on the fast ring.

Sent from my Windows 10 phone

[Cybdiver]

Help me out,  is that an update to the Windows phone or the Fitbit?   I have the Windows Insider program?