06-09-2018
11:35
- last edited on
08-20-2020
18:17
by
MatthewFitbit
06-09-2018
11:35
- last edited on
08-20-2020
18:17
by
MatthewFitbit
Fitbit ~ you all know that you need to fix whatever is now broken with your last update. Alto just shuts off without warning, even though notifications are on. It seems to happen after a lot of activity. One. Day just after the 10K celebration. Then today after some text activity. I had at least half of the battery, synced halfway through my hour long walk. Then when I got home, it was dead. No warning. This happens at least 1 to 2x per week since an update in May.
06-10-2018 02:22
06-10-2018 02:22
@SunsetRunner Have you tried restarting your Alta several times? If not, give it a try and I think it will fix it. Let us know.
Helen | Western Australia
Want to discuss ways to increase your activity? Visit Get Moving in the Lifestyle Discussion Forum.
06-10-2018 04:42 - edited 06-10-2018 08:42
06-10-2018 04:42 - edited 06-10-2018 08:42
I have done that several times, and I am still having the issue. It will try it again, but I am not hopeful.
it was dead again this morning after a restart and full charge less than 12 hours before.
i have restarted and charged again. We will see how long it lasts today.
Sent from my iPad
06-13-2018 17:33
06-13-2018 17:33
Just happened again after an hour walk. It vibrated and died. No warning.
Last charge was on Sunday, and now only 3 days later. A full charge should last more than that.
04-18-2020 11:09
04-18-2020 11:09
This started happening to me, too. While on a long walk, I felt the alta vibrate and assumed I had just hit 10,000 steps. Once I got home, I discovered the device had actually shut down, both times. So my activity never finished recording. When I plugged the device in to charge, there was no response until I pushed the reset button three times, as advised on your site. The device restarted, and showed more than half a battery charge. Both times. I see this has happened to other people who own an alta, but I do not see a solution. I have tried restarting the device three times in a row, but that doesn't fix the problem. Do you have a solution? Other than on extended activity (longer than an hour), it seems to work fine.