09-15-2017
11:53
- last edited on
09-16-2017
07:04
by
MarcoGFitbit
09-15-2017
11:53
- last edited on
09-16-2017
07:04
by
MarcoGFitbit
When starting the gps, I continue to get the message "Poor gps alert, continuing with this activity could result in inaccurate results. It's not
calculating correctly all of a sudden. I've been doing the same route for 6 months so don't know why all of a sudden. I've trouble shot every idea out there. I've done it all and customer service seems to be at a loss for me as well. Help.
Moderator Edit: Clarified Subject.
07-25-2018 15:36
07-25-2018 15:36
07-26-2018 03:30
07-26-2018 03:30
A week after getting my Flex 2, I attempted then dumped Coach app. Maybe it’s coincidence but...Seems since then this Poor GPS Alert shows up and is very frustrating for me .
Its on constant since, everything is charged and my iPhone 6 exercise tracker deactivated. Please help before I dump this device.
07-28-2018 06:23
07-28-2018 06:23
I have done everything you have stated. My charge 2 will not track my run. period.
I have reloaded down free running apps and most likely will not buy a fitbit again.
very disappointed I purchased a product that is defective.
07-28-2018 13:27 - edited 07-28-2018 13:28
07-28-2018 13:27 - edited 07-28-2018 13:28
Hi @Obermeier21 -- I've moved your post from the Flex 2 forum to the iOS forum as it sounds like you are getting a Poor GPS alert when starting a running, walking, or hiking activity from the iOS Fitbit app.
@FitMarcoFit has noted that this is a known issue for some users and that the developers are working on the problem. I have NOT experienced the problem using my iPhone 7, but I've noticed at least one other user who has this problem has an iPhone 6S. I am kind of wondering if this issue only affects certain models of iPhones.
Apparently some users with this problem have been able to fix it by making sure that "Restrictions" in the iPhone settings is disabled or off. Restrictions is an iPhone feature designed for parents to restrict access to certain apps on their children's iPhones or to restrict usage of certain features, including locations services. By default it is disabled or off, but some folks appear to have turned it on at some point or another and forgotten about it. If it turns out that you have Restrictions ON, try turning it off. (If it is turned on, you will need to enter a pin to turn it off. The pin will probably be different than the pin you use to access the phone at the main screen).
I hope that helps and you get it working properly soon.
Scott | Baltimore MD
Charge 6; Inspire 3; Luxe; iPhone 13 Pro
07-28-2018 20:31
07-28-2018 20:31
@Baltoscott This has been a known issue for over a year. I’ve had on going dialogue with this FitBit support for over a year regarding this and a couple of other issues. The answer is always the same. We are aware of this and working on it.
07-29-2018 05:02 - edited 07-29-2018 11:00
07-29-2018 05:02 - edited 07-29-2018 11:00
@J-flex -- Thanks Until yesterday, I probably had not used mobilerun (starting a GPS activity from the app instead of from a fitbit device like my CH2 or Versa) for more than a year, so I thought I might have just not experienced it. But when I tried it myself, with an iPhone 7, I did not have any problem starting the activity and did not get a poor GPS alert. Since it doesn't happen to everyone, it is probably hard to troubleshoot and fix.
Are you using an iPhone 6 or 6S? I am wondering if this crops up more often in certain iPhone models.
Scott | Baltimore MD
Charge 6; Inspire 3; Luxe; iPhone 13 Pro
07-29-2018 10:20
07-29-2018 10:20
@Baltoscott It’s not a phone issue. The issue is strictly with Fitbit and lack of support to address the issue. I just received confirmation from them that due to the Blaze (which is what I have) being discontinued they aren’t fixing any issues associated with the Blaze. But, they were more then happy to advise me to buy their newest product..
07-29-2018 13:45
07-29-2018 13:45
07-30-2018 11:19
07-30-2018 11:19
Hello everyone, I hope you're doing well.
I really appreciate the time you all have taken to try all the troubleshooting steps I've provided earlier. I understand your concern about this issue, which is why I would like to gather some information from you so I can forward it to our team. I'd like to thank some of you who have already provided some information but I will need to complete all of the following as it will be very useful for our team:
Thanks again for all your patience and understanding, I'll be waiting to hear from you.
07-30-2018 15:42
07-30-2018 15:42
@MarcoGFitbit I’m not inclined to go through all this again, when in fact FitBit’s own tech team has been unable/unwillingly to fix this issue. I have a Blaze which is now no longer available and as such no support will be provided for the issues that I’ve had for over a year. Essentially I am left with a watch, that provides accurate time, day & date. So far, the steps and distance appear to be accurate. Will I be buying another Fitbit product. No, I won’t and it’s all due to the inability and/or unwillingness of the tech team to fix anything.
Good luck for finding solutions to a product that Fitbit no longer sells or provides support for.
07-31-2018 11:19
07-31-2018 11:19
I don't think it's specifically device related, based on the many posts.
I have a Charge 2,which used to work fine and now has issues.
I have an iPhone 6s, which has no trouble with GPS tracking on other apps.
My feeling is that its a bug in Fitbit's app.
Although I can occasionally get it to track, I shouldn't have to twist myself into a pretzel each time to do it! I used to track with one click and no issues. Same phone. Same device. Same location.
All my apps and operating systems are up to date.
07-31-2018 11:25
07-31-2018 11:25
It is a problem with the App, but here you go:
07-31-2018 17:24
07-31-2018 17:24
The issue is that Fitbit has been aware of this problem for a long time and have neglected to,fix it.
08-02-2018 07:21
08-02-2018 07:21
Hello everyone, I hope you're doing well.
I appreciate some of you have replied to me with the information requested. I've compiled it and escalated it to our engineering team along with all the troubleshooting steps you've already tried in hopes to resolve this issue. When I get an update about the state of this issue, I'll make sure to let you all know here in the official Forums.
Thanks again for your patience and understanding, I hope you all have a great day.
08-02-2018 13:42
08-02-2018 13:42
Hello everyone,
I have been experiencing this GPS alert for a while now. I followed the suggested solution to disable restrictions. When I went to this setting on my iPhone 6S I noticed the restrictions were already disabled. I continued to enable them and then returned them to a disabled status. After this was completed I returned to the Fitbit app and the GPS function was working without alert or error. This has been working consistently for hours.
I hope the rest of you will experience this positive result.
08-02-2018 13:49
08-02-2018 13:49
I found that if I set location services to “always” before starting a run on the app that it seems to be better. I typically have it set to “while using” to use less battery.
08-02-2018
14:01
- last edited on
08-06-2018
09:57
by
MarcoGFitbit
08-02-2018
14:01
- last edited on
08-06-2018
09:57
by
MarcoGFitbit
Yes TXJayhawk,
I tried that too but nothing worked until I cycled the restrictions settings. I've now had the opportunity to test the app in multiple locations and everything is still working as intended.
UPDATE:
Well I spoke to soon. This fix only lasted one day. It's back to not working.
08-06-2018 09:58
08-06-2018 09:58
Hello @Jim_Macomb, thanks for joining the conversation, it's great to have you on board the Fitbit Community! Thanks for taking the time to reply @TXJayhawk, I hope you're doing well.
I appreciate your participation in the forums and for letting me know the troubleshooting steps you've tried recently. @TXJayhawk, have you had consistent GPS readings after setting Location Services to "Always"? If so, please let me know.
@Jim_Macomb, I would like to thank you for trying to cycle Restriction in your phone, I appreciate you have taken the time to share your results.
Thanks again for your patience and understanding, I'll be keeping an eye on this thread for your replies, I'm on top of this issue and will let you know once I have more information to share with you.
Happy stepping!
08-20-2018 05:31
08-20-2018 05:31
I am having the same trouble on my Alta HR - i went on my usual 3.66 mile walk on Saturday and it logged it as 8.18 miles with a 5.05 pace..... looks good ..... but totally inaccurate - I just did the restart as you suggested ..... still get the poor signal alert......
08-21-2018 07:31
08-21-2018 07:31
Hello @JNett1966, thanks for joining the Fitbit Community, I appreciate you have taken the time to share your experience with us.
Tell me, are you tracking your walks using the Alta HR and MobileRun at the same time? Please note that this is not recommended as when the activities finish, as they happen at the same time, some of the information might get lost when the information from both devices consolidates, as the Alta HR does not have connected GPS.
Have you removed restrictions from your phone Settings too? Which other troubleshooting steps have you tried yet? This will be very helpful for me to add it in my previous report to our team.
Thanks for your patience and understanding, I'll be waiting to hear from you.