Ionic's GPS keeps searching

[kindaichi]

i had two runs recently and the GPS did not registered any of the routes and it was forever searching...

Moderator edit: Updated subject for clarity 

[SilviaFitbit]

@kindaichi It's nice to see you on the Community. 

Thanks for sharing what you're experiencing with your Ionic's GPS. 

I would like you to check the following: 

• Confirm that the exercise type uses built-in GPS. In the Exercise app, choose from walk, run, hike, bike, interval workout, and golf. On Charge 4, outdoor workout also uses GPS.
• Check that GPS is turned on for the exercise. For more information, see How do I turn on GPS for an exercise on my Fitbit device?
• Make sure that your device is charged to at least 80%.
• Confirm that your device is syncing with the Fitbit app. The more you sync your device, the faster your device can connect to GPS.
• Make sure that you have a clear view of the sky when you start the exercise. Environmental factors, including tall buildings, dense forest, steep hills, and even thick cloud cover, can interfere with your device’s ability to connect to GPS satellites. If the signal is blocked—either because you're indoors, underground, or due to another reason—GPS won't work. 
• Avoid trying to start an exercise with GPS several times in a row, which can prevent your device from connecting to GPS.

Keep me posted! I'll be around if you have any additional questions. 

[kindaichi]

nope still not working

=(

[Maria_C_a]

Have the same problem with my Ionic. Was perfect until my last update on 2nd May 2020. Use it for the bike and running every day. Worked fine for 2 years!

[johnnyKay]

I too have the same exact problem with my Ionic. GPS worked perfectly until the recent update on 2nd May 2020. I use it routinely with walking and biking for two years.

I'm no fitbit expert, however, it seems obvious the recent update "broke" the gps connectivity. Rebooting the device does not help...

[Maria_C_a]

Hi JohnnyKay,
Yes really fustrating. I turned on the run function this afternoon and left it on for over an hour as I sat outside for lunch and walked a bit around the garden. It did pick up some movement when I synced but still no joy for my cycle today.
I hope they do a new update soon.
Maria

[johnnyKay]

Hi Maria,

>I hope they do a new update soon.

I just updated my Ionic today to Version 70.8.0. The update did nothing to fix the GPS connection issue.

The recent acquisition of Fitbit by Google already had me thinking about dumping my fitbit. This GPS screw up has pretty much sealed the deal for me. So sad...

john k

[Maria_C_a]

Hi John,

Sorry to hear you are having bother too. My GPS is back sporadically but now my times are rounded to the nearest 10 minutes for runs (not on the bike).  I know I'll never make the Olympics but every few seconds knocked off a previous time is hard won so being told e.g., 50 minutes regardless if time is 46 minutes or 53 minutes is a bit soul destroying. Hoping for a solution soon! 

Maria

[Logrunner]

The issue is the recent update of the App. Why will Fitbit not reply on this specific diagnosis rather than assume the device is not set up correctly?

[barbaraacollins]

Darn, I just bought the Ionic, and the whole reason I bought it was for the GPS.   Just went for a walk down to the mailbox and back to test it.  Got back, and was like "Where's the map?".

Went back out and started "Hiking".  GPS Signal just blinks "searching".

[Logrunner]

Seems strange to have such a basic problem seemingly after a software update. I now suspect if I stand still for about two minutes it manages to locate itself and is then OK -ish. But not sure..

[Maria_C_a]

Sorry to hear that. My Ionic is much improved since the last update. The GPS doesn't work all the time, 2 days ago after much 'searching' it connected but .3k into my run it disconnected. It worked fine yday. I tried leaving the GPS on continuously for a few days ...don't know if that helped but I told myself it did!

[barbaraacollins]

How do you turn the GPS on all the time?  I can only seem to get it to come on during exercise.

[Maria_C_a]

Hello Barbara, I select the 'run' option and just leave it on all the time. It does run the battery down but I tried that for 2 days - in the house and outside. It may not have made any difference but I was so frustrated and tried that. The GPS seems to connect more quickly now and tends to hold the connectivity in most instances. 

[barbaraacollins]

Since I just got mine yesterday,  I am considering doing a factory reset then not letting it update.  But then I don't think it will sync.

[barbaraacollins]

Hey Maria,

I tried that this morning.  Went outside to do some yard work.  Set it to run.  That seems to have worked but I didn't notice how long before it started.  I know it was at least 10 minutes.   That is unacceptable.

I am so mad at myself right now.  I torn between getting an Ionic or moving over to Garmin.  I have had problems with almost every fitbit I have owned.  But I thought the Ionic was going to be the top of the line and got suckered in again.

Barb

[barbaraacollins]

I tried to chat with support this morning about this.  It was a waste of time.  Told me the standard answer that it was probably clouds or trees blocking the GPS.  Neither were true.

[johnnyKay]

Barbara I think you can quit wasting your time. The folks at Fitbit continue to fail to acknowledge that they created the problem with GPS and the Ionic. I wouldn't expect much help.

My Ionic worked with GPS for me for two years. In May 2020 they pushed out an update and GPS has never connected again. Always, "Searching..."

To me the evidence is clear. They broke it and they won't publicly take responsibility. Maybe it's because of their new owners (Google) who likely have different priorities related to harvesting your data.

[barbaraacollins]

Well, I think we should all complain to them.  Clearly they are not responding here.

[RobOda]

Mine's gone off since two weeks ago.

Searches forever, finally clicks in at some point during the run, but it doesn't even draw the line anymore. It was working perfectly prior to this.