Suggest you try setting Provider to gps When you set the gps, immediately LockProvider when using devices >Android11 (as is your Pixel)
Also, I suspect using the green Lat/Lon blocks might introduce issues. You might have better results using the orange Lat/Lon block in the LocationChanged event.
I suspect that these use different values since Google introduced the fused Provider.
Edit: preliminary tests indicates these yield the same values. ![]()
Keep in mind the MIT Location sensor probably uses only the US satellite constellations when determining location. Google Maps uses multiple constellations that might improve their reported location precision. It might be time for MIT to consider updating the satellites it can use to obtain a satellite fix. ![]()
Make sure you set Screen1.AskForPermission to Permission FineLocation.
There is a bug in the DistanceToLineString and there may be an issue with DistanceToPoint, see Distance on Map point point and point to line not equal - #3 by SteveJG .
I don't understand your code placing ALL the hole distance Blocks in the LocationChanged event so I agree with @ChrisWard that is a possible issue.
