06-23-2022 21:42
06-23-2022 21:42
Hello, I bought my Charge 5 in January this year. I wore it about 2-3 times a week (usually would forget it charging dangling on the USB connected to computer.
About a month ago, I went out for a jog and it started to rain (average; not a sprinkle but not a storm either). Rain started at ~3km; at around 4km, it started vibrating furiously. No screen response to tapping it or anything, just constant vibration while screen is off in non-responsive. At around 6km (10-12 mins), it stopped. Again, non-responsive.
Back home, I just decided I would like it dry first. After a couple hours, still unresponsive, I connected it to the charge port. Next day, it still was unresponsive.
I am assuming the battery is dead. Was this not water resistance up to 50 meters? I was never submerged in water, but it seems safe to assume an average amount of rain (there were still areas on my shirt that were still dry) somehow may have damaged something.
06-24-2022
06:23
- last edited on
01-23-2024
09:24
by
MarreFitbit
06-24-2022
06:23
- last edited on
01-23-2024
09:24
by
MarreFitbit
Hi, @bamboloozedby5 you are correct in thinking that your Charge 5 ought to be able to withstand a rainstorm. I would suggest putting it in a bag of uncooked rice for a couple of days - the rice will absorb any water and help it dry out completely.
Once it has had a couple of days in rice, try charging it again, and keep it charging (ideally on a wall charger, not your computer; your cell p) even if it still seems unresponsive. Once it has had a couple of hours charging on wall charger (or significantly longer on the computer - and don’t forget that in many cases a computer will not deliver power unless it is awake), give your Charge 5 a restart. Instructions here .
If that doesn’t help, or the issue persists, I would recommend contacting Fitbit Customer Support .
Good luck and let us know how it goes. Welcome to the forums!
Sense, Charge 5, Inspire 2; iOS and Android
06-25-2022 09:51
06-25-2022 09:51
Had same issue this week and the restart got it working just fine. Thanks