When I first got my Ionic back in late-November, I had no problems at all with the GPS sync. I would go outside, activate the run app, and GPS would consistently sync within 15 seconds or so. However, it has gotten progressively worse and now on average I'm looking at 5-6 minutes to get a sync, if not longer.
I had the Blaze before and the built-in GPS was the #1 draw to upgrade to the Ionic, but this has been getting really bad and it's a massive letdown. I've made sure to keep firmware up to date (I get excited when I see one is available because I think it might fix the issue), I've done two or three factory restores, I've tried disabling GPS from the FitBit dashboard, syncing, then re-enabling it. Nothing seems to help.
I understand that various environmental factors can have an affect, but my runs have been in the exact same two places as the ones I did in the late-Fall when there were no problems, and one day where I couldn't get a connection during an entire 20 minute run was on a clear blue sky. Furthermore, I have recently opted to run RunKeeper simultaneously on my phone on days where I don't have time to wait for Ionic's GPS (I run during my lunch break). How is it that RunKeeper on my phone can grab a perfect GPS connection in 5-10 seconds whereas the Ionic, at the same time on the same day with the same environmental factors, takes 5-6 minutes?
I had a Surge, Blaze, and now Ionic and as an IT Professional I always assumed the nay-sayers were suffering from PEBCAK errors. My experience with the Ionic has me second guessing, and it's disappointing considering I can credit FitBit for getting me active in the first place.
Do I have a defective device or is this typical?
