The latest firmware ruined my Ionic, version 30.5.8. Over the course of the last 10 days it started doing some very odd things, deteriorating to tonight where the watch completely crashed.
Over last weekend I noticed the watch locking up during long runs. First on mile 7 on a 10 mile run I looked down to check my pace and noticed the watch still holding on the "Mile 7" screen. Annoyed I tapped the screen, no change. Then I pressed the buttons to pause the workout and I felt the watch vibrate, but still the "Mile 7" screen persisted on the screen. Supremely annoyed and sweaty at this point, I hard reset the watch by pressing the two reset buttons. Upon reboot I restarted a new run activity and after just one mile it locked up again with "1 Mile" on the screen. When I got home I synced the watch to my iPhone and luckily my stats synced.
Over the week my calories burned has been severely under-reported and step count is wonky. It even confuses my three other connected FitBit trackers on their daily accumulated stats.
Tonite my Ionic decided to call it quits... I get home from a short 2 mile walk, then attempt to sync my entire days stats plus that walk but it only syncs my steps and floors, but not calories and the exercise itself. Attempting to troubleshoot the problem, I cycled my BlueTooth on my iPhone without luck. Then I tried re-pairing my Ionic with my iPhone but it refused to pair even when putting in the correct codes. So finally I removed the Ionic completely from the FitBit app, then tried to add it back without success falling it to the before mentioned loop. So I invoked the nuclear option; I did a factory reset on the Ionic and attempted to add it back to my FitBit app on my iPhone. It connects but forces a firmware download and is going VERY slow, like its been doing it for-the-last-two-hours slow.
Exasperated about this whole "developer" program and lack there of, I want out. My long time passion and loyalty for FitBit is being tested with the mess that is the Ionic. I submitted my email to opt-out and I'm going to wear my Surge until I can hopefully reload the production firmware. I only wanted to make watch faces for my Ionic, thats all... but instead this rough beta garbage has ruined my $300 watch.
I tell ya... for all the build up and anticipation for this new watch yall at FitBit have majorly fumbled. As a guy that works in IT and has the patience of a saint with this kind of stuff, I'm exasperated and annoyed. As a marathoner, all I wanted was a "Surge 2" with just minor tweaks like changeable bands, but I digress. The stats inaccuracy and corruption is unforgivable at this point causing me to not trust the Ionic.
I sincerely hope that once I'm off the list and back on production firmware I can tip-toe back into it.
Bottom line is this: Please don't run off your most loyal FitBit fans with a half-baked product launch trying to chase a feature set that your competitors already have covered. Focus on what makes FitBit special, instead of trying to capture what others already have mastered.
Community Moderator Alumni are previous members of the Moderation Team, which ensures conversations are friendly, factual, and on-topic. Moderators are here to answer questions, escalate bugs, and make sure your voice is heard by the larger Fitbit team. Learn more
Best Answer
Fitbit Developers oversee the SDK and API forums. We're here to answer questions about Fitbit developer tools, assist with projects, and make sure your voice is heard by the development team.
