Possible Reason for Speedlock Bug - Unity.LocationService
Unity uses a LocationService class to determine location. This service is started (I presume) as the game is loading. However, it does not start immediately, and may take some time to Initialize. While it's initializing, you can still ask for a location, but that location may be inaccurate.
Is Prime waiting for the LocationServiceStatus to be Running before checking location for speedlock purposes, or are they jumping the gun, and reading a stale location, then letting the service change the location when it starts?
This would cause an apparent jump that is reflected in the problems during startup, and if the LocationService is shutting down while backgrounded, but not being checked for status when the app resumes, this would also cause an apparent jump when the service shows the old location until it has finished initialization then snaps to the new location once the system is Running.
Comments
I have the same problem when I hack in public transportation
Huawei P20