Sublimis
commented
4 years ago This shouldn't be happening, of course. It's an indication of firmware problems, i.e. something that the app cannot control. The only suggestion would be to make sure you always install all the latest system updates, and hope it gets fixed. Also, make sure all battery optimizations are turned off, just in case. Can you please verify that the GPS continues to work properly after the call ends? If it works while driving and after a call (with some other app, Google Maps maybe?), it should really work with our app, too. We are not doing anything out of the ordinary there. The only difference in those two scenarios is that our app is connected with wireless sensors when a call is received, and the other app (Google Maps) is not. Maybe somehow this trips the system.
Here is an article we found which mentions Samsung devices having problems with GPS after getting a call: https://www.autoevolution.com/news/the-gps-nightmare-on-android-auto-continues-with-no-fix-in-sight-145633.html. This might be related to your case, too. Unfortunately the only solution we see at this time is to wait for some system update to fix the issue.
Thanks for the feedback! Sorry we couldn't help more.
I found that when I receive a phone call (Samsung S10+ Unlocked - Sprint) all the sensors cut out. The app didn't track any sensor - gps, speed, cadence or heart rate (ant+). The track ended up being .8 miles short of the actual distance of the ride.
Is this expected behavior or something that shouldn't be happening? I know that when I take a call when driving the gps keeps tracking, so am just wondering.
Thanks!