08-05-2024 02:11
08-05-2024 02:11
Hi all,
I have just had my Fitbit 6 replaced, for the second time, as it was impossible to charge from a flat battery. (V good customer service during the replacement process)
However, Google is telling me that I shouldn't ever let the battery drain completely, but how can you always guarantee that you can charge and sync? (Eg we are going into the back of beyond for ten days next month on a hiking trip.)
Does the Fitbit 6 really have a built- in fault- that is accepted by Google- that makes it impossible to leave the device idle for days? This seems bizarre, and how can it be legal?
08-05-2024 03:21 - edited 08-05-2024 03:23
08-05-2024 03:21 - edited 08-05-2024 03:23
Welcome to the Fitbit community, @ThreeCsRock!
Sad to hear that you're having issues charging your Charge 6.
In general, to preserve battery life in the long run, it's a good idea to avoid draining any Li-ion battery completely if possible. And you also shouldn't always charge any Li-ion battery up to 100 percent to extend it's lifespan. Best practice is to keep it around 10 and 90 percent all the time with an occasional full charge from time to time.
Your Charge 6 should give you a low battery warning you if the remaining power is at 20 percent. If you're out for a trip for several days, there's the option of taking a small power bank with you which will allow you to charge your mobile devices right on time without issues.
If your Charge 6's battery is deep discharged, it may take quite a while to show a sign of life after having been put on the charger. For detailed information about charging issues, please have a look here:
Why isn't my Fitbit device's battery charging?
08-05-2024 05:05
08-05-2024 05:05
Thank you for your reply- and education about Li- ion batteries as I had no idea!
However, for our forthcoming trip, it's really not an option to take a charging pack as every gram counts in a very small luggage allowance...
But, if I understand you, you can't, say, decide to take a "month off" from tracking with Fitbit? This is just bizarre for me since I never had any issue with my previous (Garmin) tracker...