Ionic Firmware Release - 32.10.15

[MattFitbit]

Fitbit Update: Fitbit OS2.1 has been released to 100% of users!

---

Hi all! 

I am excited to announce the release of Fitbit OS 2.1! (Firmware Version: 27.32.10.15)

We've started to roll out this update to 10% of Ionic users. This is a progressive rollout, and all Ionic users can expect to have it within a few weeks. We roll out releases in phases as a cautionary measure so that we can monitor performance closely and make adjustments if needed. 

WHAT’S NEW

Introducing quick replies. Send customized responses to text messages and messages from select messaging apps with your Fitbit watch. Note that this feature is currently only available on watches paired to an Android phone. For more information, see How do I respond to messages with my Fitbit watch?

This release includes other bug fixes and improvements.

Step by step instructions for updating your Ionic can be found here.

I recommend updating your Ionic over a home Wi-Fi network as this can greatly reduce the time it can take to get set up. For more information on connecting your Ionic to Wi-Fi, check out this article. 

If you run into any trouble updating your Ionic, I can also recommend reviewing these troubleshooting tips. 

Looking forward to hearing everyone's feedback on the latest release. If you have any questions, feel free to let me know! 

[Yodacoda99]

I update my Ionic this morning, since than I do not receive my notifications. I can get phone calls but not notifications.  Help!

[d_k]

Hi @Yodacoda99

which messenger are you using?

[avanarden]

@d_k @MattFitbit
Looks like there is a perfectly usable NotificationCompat package to use available instead of the direct OS call. Using this should be simply adding the compat import, instead of the direct OS import, leaving the rest of the code the same.  The package will automatically handle it appropriately on a new OS

Google makes it really easy for developers maintain features on older OS. I have done this many times in my work.

So yes Fitbit can do something really easy to make this work back a few OS versions. (Android 4 to be exact)

Hope this gets to a developer

More supported os, means a bigger market for fit-bit, good business decision. 

From the documentation, it's clear that direct replies are available in the compat version that google supplies.

https://developer.android.com/guide/topics/ui/notifiers/notifications

Notification compatibility

Since Android 1.0, the notification system UI and the notification-related APIs have continually evolved. To use the latest notification API features while still supporting older devices, use the support library notification API:NotificationCompat and its subclasses, as well as NotificationManagerCompat. This will allow you to avoid writing conditional code to check API levels because these APIs handle that for you.

NotificationCompat is updated as the platform evolves to include the latest methods. It is important to note that the availability of a method in NotificationCompat does not guarantee that the corresponding feature will be provided on older devices. In some cases calling a newly-introduced API results in a no-op on older devices. For example,NotificationCompat.addAction() displays the action button on a device running Android 4.1 (API level 16) and higher only.

The following is a summary of the most notable behavior changes for Android notifications.

---

Next Android app update Please!!! 

[Chriswhite75]

@MattFitbit

Looks like I've just managed to calibrate my Ionic. Hopefully this may solve the other little issues I have. I'll keep you posted

Any news when the Samsung S9 will be added to the supported phones list????

[Yodacoda99]

Messenger +


Sent from my Verizon, Samsung Galaxy smartphone

[d_k]

@avanarden

yes and no.

i'd highly appreciate it if that would be the solution, but you just found the "notifying-app"'s compatibility layer. that one helps developers to put in everything possible, and depending on the executing OS version, the supported features are enabled and utilized.

so you can put in a quick reply, and don't care about your user base. if they have android >= 7, it's shown, below it isn't.

the benefit is that you as developer don't have to make if's and checks for every single feature.

the 2nd hurdle is that fitbit's app isn't native but some kind of one codebase fits all platforms stuff. i guess PhoneGap, Cordova, ... (also according to their job-descriptions), which add another layer of abstraction (and sometimes prevent access to the native layers).

[avanarden]

@d_k
I totally buy the none native app issue. That may very well make it impossible to support android 6.
Compats are not always available in that environment and it can be lots of work to add it manually. Although sometimes doable  

However,  Compat packages are full featured and do divert to the OS call if it is available, otherwise they run the code available in the compat with the same functionality. It's rare there are features missing in the compats.  

For example I have quick reply from the notification bar for various apps, like what's app and signal,  a 7.0 feature running on 6.0.2. ( Which I think is the same calls needed to reply from the ionic)

So much of android API is running in the java vm, so if there is functionality missing in the  os, it can just be loaded dynamically in with an external package, like a compat.

I've got many years dev experience 7 in mobile dev, native android and ios 😉

Anyways I'm not on the project, in the trenches and there are probably also other hurdles I'm not aware of, complexities, project priorities...... and maybe NotificationsCompat isn't even the right one here. But I'm sure in the right dev environment it's doable.

Thanks for engaging with this old developer.
I want a new phone anyway.

[carlosgrebe]

My heart monitor and step tracker stopped working when I updated...

[JeffBMI]

Good day,  Update completed on my Iconic.  Quick reply (using Textra), and messenger working most of the time.  On occasion when I select to quick reply using an emoji or text the message I am trying to reply too disappears and the iconic indicates no messages exists.

Additionally, I am wondering if it is normal operation for the messages to disappear after I reply.  I would like them to stay on the watch until I clear them out. 

Phone is Samsung S9+

Thanks

Jeff

[Sirlance709]

Did they fix the inconsistency issues with the music controls and music player?

That would be great to know

[Eckslax]

Any word from the development team if they are going to to fix GPS distance calculation? I’m updated to the latest firmware and my running distances when using GPS tracked runs consistently come up short when compared to Garmin and Suunto devices (those tend to agree within a few strides over the course of a run). My last run was off by a tenth of a mile on a 3 mile run. Might not sound like a huge deal, but it makes a big difference when you are analyzing pace and training for a race. The GPS track looks good so it’s an issue with the software using a weird formula for steps for distance instead of true GPS data like every other watch does (well documented in another thread). 

Can we at least get an affirmative that the development team is aware of this issue and intends to address it at some point? Otherwise the Ionic gets ruled out as a serious training tool. I love the device otherwise, but this is a deal breaker so far. Thanks.

[johnandmya]

can I ask which phone you are using ?

I would love to know, thanks 

[Eckslax]

I’m using an iPhone. I always make sure I have a solid GPS lock before I start my run as well. It’s pretty well documented that the Ionic distance algorithm is using some weird hybrid that involves steps and that is most likely why people are seeing variable distance accuracy. 

[Balsam]

Dear Fitbit

The Ionic has still a very inaccurate GPS. The heart rate function remain unhealthy wrong if you use it to measure your pulse while exercising hard. The Ionic is not measuring your heart rate at all, its "guessing" your bpm depending on which exercise you choose. In other words, very incorrect Logarithm.

When will you do something about the safety issues regards his? 

Fitbit, you should do better in support and updates and follow up your customers. Many cutsomers have spent lots of time and money on the Ionic and your updates havent solved anything (so far).

The last update 32.10.15 took 11hours and we followed Fitbits step by step guidance as recommended... The Ionic remains unacceptable faulty after this update, still giving customers delusive meassure of the heart rate and GPS tracking while exercise. 

Thats not OK at all

[Mark2018]

Hi,

What a pity!

Maybe you should escalate that to Fitbit.

Hopefully they change to better support and provide bugfixes!

Regards

Mark

[Osmar]

Just did the firmware update here.

4 hours waiting and multiple disconnections.

and, as I can see, the music transfer problem was not solved.

i repeat: another update and I still can't put music in my ionic.

one more time: the music transfer issue was not fixed!

[CMichelle]

@MattFitbit Thanks for the response but unfortunately, none of the suggested fixes for text messaging worked, including pairing and un-pairing the device.  I can get all app notifications, the test call even worked just fine.  The ONLY thing I cannot get on my Ionic is text notifications.  I'm using a Samsung Galaxy 7 Edge with Verizon Message+.  I've had my Ionic since Christmas and never had any issues getting any notifications until now.  I've checked all settings in the Fitbit app and on my phone and everything is set the way it was before - on and ready to go but no text notifications will come through.

[Yodacoda99]

I have the same problem! I have tried several things and nothing works! I have a Galaxy 7. I hope it gets fixed! I miss my text messages on my watch!


Sent from my Verizon, Samsung Galaxy smartphone

[SunsetRunner]

Nope, I never was able to calibrate successfully.  It failed the few times I tried, then it never nagged me on subsequent evenings.  Not sure what is/was going on. 

[MissUrka]

---

@SunsetRunner wrote:

Nope, I never was able to calibrate successfully.  It failed the few times I tried, then it never nagged me on subsequent evenings.  Not sure what is/was going on. 

---

My calibration prompt to appears at 8pm (that’s the one guaranteed time but sometimes at other times, too). Prior to having all current updates available to me, I would do the same as everyone else: try to calibrate following the directions in the prompt and get a red X that it had failed. Then I tried the “later” suggestion by Fitbit (who said to ignore the message by selecting “later” and that not calibrating didn’t interfere with functionality or accuracy of Ionic (this I will never understand). Since I updated to current versions available to me, I still get at least one calibrate prompt at 8pm but it disappears before I can choose “later” or “start” and then a green check. Voilá. I guess that means it’s calibrated. You’d think. But then I get prompt again the next day. I have no idea if this is helpful to you or not but it just happens to be what I am experiencing in the past few days since updates.

Ionic

Firmware 27.32.10.15

iPhone X (running 11.3.1 software)

iOS Fitbit App version 2.5