11-24-2023 20:24
11-24-2023 20:24
I have had my fitbit for around 2 years. Up to now it has worked perfectly well I love it. Today I charged it, and around 30 after it was completely charged it just randomly turned off and I am not able to turn it back on. I tried several things, including customer service and connecting it back to the charger, but it's still the same. Customer service said they would file it and get back to me in w3 hours. I was wondering if anyone else has had this problem and how were you able to resolve it. Thank you.
12-20-2023 11:46
12-20-2023 11:46
Do ya'll mean by "update" a firmware update or the Fitbit App? I did not update my Fitbit App (and probably won't; I have the Pre-November, Pre v. 4 version). I did have trouble restarting my watch after a shutdown, and had that issue twice now (while trouble-shooting getting Weather to work). What I did is repeatedly put in on charger then try to restart, thinking that putting on the charger "does something" maybe. I have numerous power supplies and usually use the slowest one, 0.85 A (that gives me the message that my watch is charging slowly) because it is fast enough. But I tried a higher wattage charger (the critical thing is voltage -- that must stay same, ~5 volts, to not damage your devices). And then pressed for ~ 10 sec or more and finally the watch restarted. I have no idea if the better charger helped or not, but maybe something to try. Most chargers nowadays are higher amps (for higher wattage) than 0.85 A. Just make sure you don't exceed ~ 5 volts.
I think the problem is the non-physical button. I was thinking maybe the charger makes it more "receptive" to input... maybe.
But I'm thinking the issues people are having on this thread is the syncing from the new (v4) Fitbit phone app messes up (crashes) your device and it is hard to recover from that. I did not have that issue.
Good luck everyone -- don't give up too soon.
And Dear Fitbit People, if you are reading this: make the older version of your phone app available on your web site for side-loading please. People should be permitted to roll back if your new app breaks their devices. It does not slow adaption of your newer app, because I would be willing to update to it if I knew that I can roll back if necessary. As it is, I might never update. It is unethical to make an app that breaks a bunch of devices and then take no steps to remedy the situation other than offering a discount. The Sense is not an old device! If someone bought it over a year ago so that it is out of warranty, that does not give Fitbit/G####e permission to carelessly break it. Again that is highly unethical. Please help these people out. Why should anyone buy a Fitbit/Pixel watch or device, from a maker that feels free to break it so long as there is a good chance that the majority of watches were purchased a year or more ago?