Prevent updates during workout

[N1dhu9]

When opening the Fitbit app it seems to check for updates to any equipment registered in it.

If there is an update available, the app brutally forces the update to be installed on the device, even if the device is in active use, e.g. during a workout.

This results in the workout being stopped and being either partially recorded or not recorded at all.

I consider performing a workout with a Fitbit (Charge 6) a core functionality of the product and this behaviour completely destroys the experience and is very frustrating.

I try to remember not to use the app while working out, but honestly this seems stupid.

Do the developers of the app have the target audience in mind when implementing such "features"? At least let the user decide when to install updates - it works fine in almost any other app!

[MakMak]

Hi, @N1dhu9! I've never had the app do a force update of a tracker on either Android or iOS. Can you share what phone/OS/app version you have? Also, these updates don't happen very often and it sounds like you have something happening fairly often.

[N1dhu9]

Edited!

Hi MakMak,

I am using a Google Pixel 7a with Android 14 (currently at AP2A.240705.004) and the newest version of the Fitbit app.

I have experienced the problem over a longer period of time - several months and thus several versions of Android 14 and the Fitbit app.

My experience is that the updates happen several times a week and it is very clear that it happens shortly after opening the Fitbit app.

What actually happens is that the watch vibrates and shows a message that it has been updated along with a progress bar - I suppose that it is restarting to apply the update.

What actually happens changes between two scenarios. The first is that the watch vibrates and show the message "Update complete" inside a circle - I suppose that it is restarting to apply the update. The second is that the watch vibrates and shows no pulse.

The latter case also happens when the watch actually is unable to read my pulse, but in the case above, there is a significant coincidence with opening the Fitbit app.

The app shows nothing about the update whatsoever, so I have no idea what versions it updates between or what changes the updates contain.

It does not happen every time I open the app, far from it, but I use the app quite a lot, so I guess that makes sense.

[Heather-S]

I agree with @MakMak. Never once have I had any Fitbit device apply an update automatically. They don't even put out updates for devices that often -- maybe an update once very couple of months if we're lucky. Very strange behavior from your device.

[N1dhu9]

Edited!

Hi Heather,

I must admit that I was quite impressed by the development cycle, at first - I got the impression that they cared a lot for their product, which is common for a period for new products.

However, I am getting the impression that things are not that great ..

Whether it is the app or the device that is acting strange is hard to tell, but I experience a tight connection between the behaviour and using the app. Maybe an update has been cached in the app and it sometimes try to apply it? I will try the following to find out if that could be the case:

1. Clear the cache of the app and see if it happens again within a week - It does happen even though the app cache has been cleared
2. If it still happens, uninstall and re-install the app and give it another week - It still happens

I will post my findings here in a couple of weeks!

[MakMak]

Yes, you're correct. It's nowhere near that. There was a firmware update in July, and the previous one before that was Nov/Dec of last year. Your plan sounds good. You should also be able to check within the app what the current firmware is, the latest is 210.26.

Best of luck!

[Rich_Laue]

I haven't noticed a forced fitbit update. Even after starting the download, I can still postpone the install to a later time. 

Now on my phone, there is a limit to how many times I am able to postpone an update. 

Clearing cache will require re-downloading the update. 

[N1dhu9]

Hi Rich,

Your experience is otherworldly to me. I have never seen anything about updates in the app; no download options, possibility to postpone or to install right away.

Are we talking about the same products? I have a Fitbit Charge 6 and use the Fitbit app on Android ..

------

Hi all,

I have updated my post of August 1. 16:38/4:38 to be more specific about what happens.

I have also been able to rule out my first step both steps of trouble shooting.

I am at a bit of a loss as to what to do next. I cannot do anything more on the app side and I have very limited options on the device - I can restart it, which I have done several times.

Is there a service menu on the device that might have further information or options, such as clearing temporary storage?

------

Hi again,

It's been a while now and in the meantime I got an actual real update for my tracker. This update was announced in the app with the option to install immediately or postpone, just as @Rich_Laue writes.

Hopeful that this update would solve the problem, I installed it immediately (so I am now on 66.20001.210.26), but to my disappointment I still experience the behaviour described in OP.

I managed to take a few pictures of the tracker when it does this - see below:

[sarbruis]

Just want to note that I am having the same problem and you're not having some singular experience.  I'll post anything if I can figure out how to stop it.  I haven't had a single run log fully over the last few weeks because of this issue.

[N1dhu9]

Hi sarbruis,

I am sorry that you are having similar problems - it is very annoying. It seems that you are having a worse time than I am logging exercises.

The only "solution" I have found is to be careful not to open the Fitbit app while logging exercises.

[Caroluna]

I have same problem… cant I turn auto updates off somewhere? Happens everyday at this point 

[RiekoC]

Hello @Caroluna 

This page (<-- click) has the instructions to turn off Automatic Updates for iOS users. 

If you're an Android user, please use these instructions (<-- click)

[N1dhu9]

I have recently been in contact with Fitbit customer support and they
suggested the most unlikely fix: change watch face.

Reluctantly I changed the watch face from the default (Fast lane) to
Slashed. When changing the watch face, the watch did exactly what it
usually does when using the app during workout and it has not done it once
ever since (10-ish days).

So it seems that changing the watch face solved the problem for me. I have
tried to trigger the error by using the app during workout and it seems
stable now.

I hope this can help those of you out there experiencing similar problems
with your Charge 6!

Best regards,
Anders

[Caroluna]

I’ll try this, is it still stable for you? 

[N1dhu9]

Hi Caroluna,

Yes, it's still stable 👍 I haven't tested whether it is the different
choise of watch face or the process of changing watch face that has fixed
the issue, but I have been able to get accustomed to the new watch face, so
it is not a big deal for me.

Regards,
Anders

[Caroluna]

Hi everyone

Im happy to report that changing the clock face worked for me as well 😄

I changed it to “readiness” but I don’t know if it matters which one you pick

[RiekoC]

Hello @N1dhu9 , @Caroluna 

I believe you can restore the clock face you had before, now that your issue has been fixed. Please let us know if that's not the case. 

[N1dhu9]

Hi again,

So this &#¤/& came back with increased force a few weeks ago.

When opening the (updated) FitBit app on my (updated) Pixel 9a, the watch restarts and claims that it has been updated - exactly same scenario as before.

I have kept the watch face that I previously changed to, so I tried to change it to something else, but this time it does not work.

The exact scenario, which I can reproduce every single day, is as follows:

I take off the watch in the morning, before taking a shower, and connect it to the charger. The watch starts charging.
I then restart the device through the Settings menu.
After my shower I put the watch back on.
The first time I start the FitBit app after this routine, the above scenario happens. So far subsequent use of the app has no impact on the watch's stability.

The watch has not been updated since I "fixed" it the first time.
The error has not been present after I changed phone to the Pixel 9a.
The FitBit app has, however been updated several times since and it seems like the error has been introduced as part of this.

I am very seriously looking into available alternatives (other brands), but unfortunately there is little competition on the form factor of the Charge 6 ..

Best regards,
Anders