Android N Support

[NabobCoffee]

Before I install Android N on my Nexus device does Fitbit apps support the new Android N? thank you

[mightyfo]

It is working. I was finally able to get mine to connect and sync.
--

Foster
(347) 469-1479 (GV)

[jefmes]

I updated my Nexus 6P yesterday with the beta release, and it's funny how quickly losing this functionality made me start using my Fitbit less! I'll try synching mine up when I get home and share the result.

[robschertzer]

Developer release notes though shows the following for Android N Preview 3
Connectivity
* When a Bluetooth Low Energy (BLE) peripheral role device advertises a service and a BLE central role device connects, the peripheral role device disconnects very quickly.

Since the Fitbit connect using BLE, there still could be connectivity issues. Right?

--R

[thomasrpowers]

I have installed the developer preview 3, and I'm having pretty good luck
with it. The Fitbit app syncs fine, though there are still some apps that
won't even load. HBO GO is one of them.

[ptrowski]

With Preview 3 on my 6P I am getting the crash notice for the Fitbit app paired with my Blaze.  The app says notifications needs to be turned on even though it already is. 

[jefmes]

Update as promised - Charge HR is now syncing successfully with Nexus 6P on Android N Beta (NPD35K). It seemed a little slow, but it worked and has been syncing correctly today.

[Gakio]

---

@NabobCoffee wrote:

with Preview 3 released is fitbit app still not functioning properly?

---

My fitbit is syncing on my Nexus 6P with the latest Android N preview (preview 3, released May 18th)! At first I thought it wasn't working still as my tablet with preview 3 could not sync to my blaze. I installed preview 3 on my 6P and it is still syncing. However, my tablet never had connected to my fitbit, while my phone has prior to preview 3 (which was marshmallow).

[Skyeclad]

I concur that notifications are not working properly. The application seems to forget that notification priveleges have been granted and then can no longer send notifications. The fix is to go through the settings and let the app know that notifications are approved but this only lasts a few minutes for me before reverting back. I've tried uninstalling the app and reinstalling but this didn't help.

[Rich_Laue]

If it really the app forgets? You don't give Fitbit permission, but your giving the operating system permission to allow Fitbit to communicate. IE Fitbit true to do something, the OS says hey user, Fitbit wants to do XYZ, shall I let Fitbit do XYZ?

The Fitbit has tried to do something, and when the operating system seems to forget it  asks again. All I'm saying is it sounds more like an OS problem.

[ptrowski]

The toggle stays on in the OS, that is why I attribute the issue to the app.

[Skyeclad]

For me, I'll notice that I'm not receiving notifications on the device anymore. The persistent fitbit notification will be gone. If it go to the notification settings in the OS, it looks fine. If I go to the notification settings in the app, it tells me that I need to grant permissions. I'll click enable permission and it takes me to the OS permission page where it is already enabled. If I go back I get the request page again. The only way to move forward is to take permission away and enable it again. Once that's done, you return to the app and see your previously selected text, call and calendar app choices. If you back out, notifications work again for a little while.

Not saying that isn't an N problem but the issue looks like it's on the app side because the app appears to be forgetting that it was given permission. It could be that it has lost permission and it only appears to have it on the OS side.

[robwilkes]

So are too guys going to be working on this issue. Do you have a release date?