001 displayed on Charge 3

[KateFitbit]

Fitbit Update 1/18/2019: If you see the Fitbit logo and error 001 on your tracker, please see this link and restart your tracker. This should resolve the issue. If you are still stuck, please let us know. 

[fionac]

@DavideFitbit

Thanks.  It hasn't done it again yet.  I'll see how it goes.  Thanks for the advice about restarting, but if you can't swipe the screen (which you can't in 001 mode) that's not very helpful!

[Ping10000]

Appeal to Fitbit CS. They are well equipped to help.

God loves you

[MarreFitbit]

Hi there @fionac and @Memelting! Thanks so much for trying the tips and recommendations provided along this thread. I have reached out to our support team and created a case regarding your inquiry. Someone will be reaching out to you within the next 24-72 hours with next steps. Let me know if you both have any questions present. 

Thanks for helping out my friend @Ping10000! Hope you have a great day! 

[ghostRansom]

Update on the "001" error:

I was unable to restart the Fitbit once it was plugged in to the charging port. It would vibrate twice, but the error message would continue to appear and the device would not restart. Therefore, I left the device unplugged overnight, which allowed it to run out of battery. The next morning, I plugged the device in, and it turned back on. I then let it charge to 100%. I have not received the "001" error since.

[Mae07]

 I'm at work and just got noticed this error.  Can't do anything about it for 3 more hours.  Just trying to open up the line of communication now incase I can't resolve it when I get home. 

[ghostRansom]

From my experience, the way to have this fixed temporarily is to let the device run out of battery and then plug it in once it has died. I was not able to restart my device while in "001 mode" even when the device was plugged in.

I say temporarily fix because there's no telling if this will happen again or what caused it to occur.

[MarreFitbit]

Hi there @ghostRansom! Thanks a lot for sharing what has worked for you. I'm glad to hear you're back on track. 

Welcome to the Community Forums @Mae07! Were you able to get this solved? I was checking and I couldn't find a support case from you. Did you contact our Support Team?

Looking forward to your reply!

[joelseph25]

Hey @MarreFitbit and @KateFitbit,

Just an FYI for than anything, since tinkering around with my Fitbit settings via the mobile app it has been behaving beautifully, I'd had no 001 errors for about a month until today. I went for a run at lunch, got back to the office, jumped in the shower, went back up to my desk and them boom the error 001 came up on my Fitbit.

Weirdly, this is how I'd usually get the error! Go for a run, have a shower, walk back to my desk and then it would appear, there's definitely something odd about that but I can't figure it out, maybe I should stop showering for a bit!

I'm 100% sure the error will clear when I do the 15 second reset later and the device will sync my steps etc, unfortunately I don't have my charger at work so will lose my steps for the afternoon but I thought you guys should know that my issue isn't resolved like we thought and I'd also like to know if your guys can advise what error 001 actually means and if you're looking into a resolution?

Thanks 

Joel 

[Mae07]

I was able to restart it after the battery died.

So far so good.

Thank you!

[MarreFitbit]

Awesome @Mae07! Glad to hear so far so good. 

Hi my friend @joelseph25, it's great to see you again! Thanks a lot for the detailed information about your Charge 3's behavior during the last few days. Since the issue came back, I have reached out to our support team and created a case regarding your inquiry. Someone will be reaching out to you within the next 24-72 hours with next steps. 

Point me out if there's anything else I can do for you in the meantime. 

[EagleFH]

My Fitbit charge 3 did the same thing. It showed the Fitbit logo and the 001 below the logo. I had to let the battery go dead.  When I plugged to the charger the screen came back up and the error was gone. The error came up when I try to syc to Samsung galaxy A tablet. The tracker is really bad about not syc to any device. i have trouble all the time. This is the only device that I have that gives so much trouble syn to another device.

[Ping10000]

It seems that by now Fitbit should be responsive to customers. Responsive is acknowledging a serious problem with the Charge 3. Reporting what can be done in the interim. And advising if solution is near in time. Hoping Fitbit thinks about actions. Companies are not just what they make but how they manage their product.

God loves you

[DavideFitbit]

Welcome to the forums @EagleFH, and thank you for the update about the 001 error disappearing from your screen.

Unfortunately I've confirmed that the Samsung Galaxy A Tab that you mentioned is currently not listed as a compatible device to sync with the Fitbi app, you can check the complete list here. Although many users have reported being able to sync with some of the phones that aren't listed, unfortunately it's not possible for Fitbit to guarantee that it'll always work properly if the device is not fully compatible. 

Thanks again for all your feedback regarding this error @Ping10000. 

Do let us know if you have any other questions. 

[jch85]

Just wanted to add my complaint to this thread. For background, I just turned on my Charge 3 two days ago. I'm running Android 9.0 on a Pixel 1. I almost immediately had some syncing issues and began getting the "001" error every few hours during my first full day of use. I just want to say that I'm pretty disappointed with the Charge 3 so far. I was hoping the issues I'd had with the Charge HR (mainly syncing and needing to do a hard reset almost every day) would be better, but they're actually worse with the new model.

I just did the long reset, just to be safe I also: 1) Reset the screen to the default one, 2) Uninstalled the app and 3) Restarted my phone.

(I reset my screen because I heard it might be an issue with the new screens.)

So far in the first hour, no "001" error... but I did have to plug the tracker in and do a manual reboot because the screen wasn't responding (it wouldn't turn on immediately when pressing the button, and wouldn't respond to swiping when it did). I've also still had syncing issues, needing to reset my bluetooth or "forget" the tracker to sync at times. 

I know that many people have had issues with this, but it's disheartening to see that lots of people have been having issues for months, even with multiple replacements. Hope Fitbit figures this out soon...

[fionac]

Mine has not done the 001 thing since last weekend. I ran on Thursday and today, using the Fitbit to time my runs and it worked fine both times (though I was obsessively checking it).

When the Charge 3 works, it is a fantastic device, but I shouldn't be worrying about it crashing, not syncing and whether I need to buy a power bank so I can reboot it on the move if I need to.

[jch85]

Well, at least it lasted through the night! Around 9AM today, about 12 hours after doing the long reset, reinstalling and re-pairing my almost brand new Charge 3, I got the "001" error again...

Fitbit, please figure this out. It's kind of crazy that you're still selling a product that is riddled with well-known software/sync issues without any warning at all.

Does this mainly happen to android users? My girlfriend who uses her charge 3 with an iPhone 6s doesn't seem to have any issues (knock on wood). Getting pretty close to returning this. I really liked my Charge HR... until it broke in half (that also required a pretty frequent hard reset all well though). And I think I'd really like the charge 3, if it worked!

[joelseph25]

@jch85

I was under the impression that it was mainly effecting Android users, myself being one of them.

After playing around for some time I was able to fix my sync issue and almost fix my error 001 issue, when I say almost fix, I mean I don't see the error as frequently anymore and I'm generally happy. Give this a go and see if it helps you:

1. Remove your bluetooth pairing from the bluetooth settings on your phone.

2. Uninstall the Fitbit app.

3. Reboot your phone.

4. Do the 15 second reset on your Fitbit.

5. Reinstall the Fitbit app and run through the set up.

6. Go to your Fitbit from with the Fitbit app and turn off the 'Always Connected' option.

7. Reboot your phone.

This made a massive difference for me, hope it does the same for you.

Cheers
Joel


Sent from my Samsung Galaxy smartphone.

[jch85]

Thanks Joel I'll give it a try (although I did most of that last night, e.g. disconnect, reinstall app, long reset etc).

Update: Bought me about 4.5 hours before I saw the "001" error again. Pretty close to returning the tracker. Pretty annoying to have to keep the charger and a power source handy at all times just in case I need to hard reset the device...

Fitbit, if you're going to make devices that require constant rebooting, maybe consider an option that allows for a hard reboot without a charger...

[MarreFitbit]

Thanks a lot for your help @fionac and @joelseph25! Also, thanks for sharing how your tracker is doing and what you both have done so far. 

Hi there @jch85! I'd like to give thanks for the feedback you've provided towards our product. Please know that we provide feedback to our team based on community posts and we are always working on improving our devices and overall environment based on that feedback. 

I've seen that you reached out our Customer Support Team already. If you have any questions or doubts, please make sure to let our team know. They'll be more than glad to assist. 

Have a nice day guys! 

[Ping10000]

When will Fitbit report to its Charge 3 customers as to what they can expect of the product and support in the short run as well as progress to address the repeated common issue regarding the Charge 3.  Folks have invested in Fitbit.  Fitbit should be open with them.  Fitbit has been good to me.  Fitbit replaced my Christmas watch,replaced the replacement, and I am happy to say the current unit replacement has lasted nearly 3 weeks without code.