04-14-2016 14:09
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

04-14-2016 14:09
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
Since the last Android N (Beta) update, I can't sync my Blaze anymore.
Quote from Google:
Bluetooth Low Energy (LE) GATT characteristics are using the wrong write type and will not be sent to a remote device. Thus, for example, some fitness devices will not work.
Can you Please fix that with a update for the Blaze. I mean better start coding yet than later, because seems to be the new standard. Or it's only a Bug?
Answered! Go to the Best Answer.

Accepted Solutions
04-14-2016 15:23 - edited 04-14-2016 15:28
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post


04-14-2016 15:23 - edited 04-14-2016 15:28
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
Please remember that Android N is on beta form, and not for general use, but releases for those that develop.
The Google quote above says that Google is aware of a problem that prevents messages through the GAAT service. The problem is on Androids end, not Fitbit. It to put it another way Anfroid N has stopped talking, there is nothing Fitbit can listen to.
As for it being a bug, that's exactly what you posted Google as saying

04-14-2016 14:22
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

SunsetRunner
04-14-2016 14:22
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
- Who Voted for this post?
are're you saying ::
Google defined a bug as a new standard ?
04-14-2016 15:23 - edited 04-14-2016 15:28
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post


04-14-2016 15:23 - edited 04-14-2016 15:28
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
Please remember that Android N is on beta form, and not for general use, but releases for those that develop.
The Google quote above says that Google is aware of a problem that prevents messages through the GAAT service. The problem is on Androids end, not Fitbit. It to put it another way Anfroid N has stopped talking, there is nothing Fitbit can listen to.
As for it being a bug, that's exactly what you posted Google as saying

05-19-2016 01:43 - edited 05-19-2016 01:44
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

05-19-2016 01:43 - edited 05-19-2016 01:44
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
Why is this classed as 'Solved' when, after the 'Solved' answer, it is still an outstanding issue? Sorry I am new. Perhaps it's because its not a fitbit problem?
Anyway - the real solution to the issue for me, my Nexus 6P and Charge HR was the Android N update that I recieved OTA thismorning. Unfortunatly I had tried deleting the device and re-adding it before the update so I need to set it up again but they are synced!!
Just thought I would update this as I landed here the other day and couldn't find a solution anywhere.

05-19-2016 02:45 - edited 05-19-2016 03:04
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post


05-19-2016 02:45 - edited 05-19-2016 03:04
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
@Pryors having a thread marked solved does not necessarily mean that the original point of not working is now working. It could mean that the original poster @CROFIGHTER has had thier question answered to their satisfaction.
N is in beta form, meaning that it is still not reliable, and not officially released, anybody that is smart enough to know how to load it, should know this release is still considered to be unstable by the developers, IE Android.
No @Pryors what beta means is that Android says the release of unstable andat any feature might accidentally be broken with an update. This is something that the word beta is understood to mean.
As stated on the main thread, depending on which version, it might both be working because Android broke the Operating System to the point that they say that it will not work with BT 4.0 devices such as Fitbits.
Would you call up the TV salesman and complain that the TV doesn't work, when the tree on your front lawn feel and broke the lines casting the power into the house?
Fitbit therefore will not be able to fix anything until Android fixes what they broke.
Yes Fitbit will make sure that with the official release of the newest Android OS, whatever it will be called, it won't be called "N", their software will work.

