I made another tour with Google location service instead of Android (what is the difference between both?).
This is the tour. We started near Oberkochen in the Swebian East Alb and the destination was also set there. It was a round tour.
The tour was good until I got to Monheim where several road stoppage occured. Driving through them was not possible.
I first tried to find manually a another way, but there were also road stoppages. I had to make a bigger detour. Because it was difficult to identify in which direction the gps showed and I couldn’t bring it in line with the reality, I used the skip next waypoint function to get a new calculated route around this. I even stopped and made new waypoints too. Nothing helped, I didn’t get calculated a correct route back to my destination.
In the screenshot you can see that the gps recording didn’t happen for quite a while. There are many lacks in between, but the gps signal was not lost, it was active on the screen all the time and moved correctly.
The usage of skipping waypoints some times more then resulted in the exchange of my destination from Oberkochen to Monheim. I wasn’t aware of this while driving, just saw this after the tour. I had to stop using kurviger at this time and used my other app Navigon Cruiser to easily find my way home, because I was bugged out by this behaviour and didn’t want to lose more time to guess what happened.
The movement of the destination to antoher area is a big error in my point of view and should never happen. The destination should NEVER be deleted by skipping waypoints. I hope this can be fixed.
The strange thing is also the lacks in the gps recording. Here the change from Android to Google location service obviously didn’t help because in the previous tour the same problem happened with Android location service.
My setting for GPS recording is this
Could the lowest recording speed maybe be the problem? This is set to 3 km/h which is pedestrian speed. When the app cannot identify the correct speed and therefore doesn’t record?