GSM location gets priority over GPS location
I realize that the position code inside Ingress is a delicate one, but I think it needs some tuning. Very often my ingress location jumps to some specific spot, which isn't my location. It can easily be a few hundred meters away. I assume this is a location based on GSM signal triangulation, not GPS. I can move around and it still jumps to that same location. This can happen in the middle of nowhere, in wide open fields. And it can take minutes before it might jump back to my real location. If it takes too long, it might tell me "no location". Note that this is ONLY in ingress, other apps like google maps, are very precise in determining my location, there is no visible jitter. The Android app "GPS status" shows that I have a fix on 25 satellites, so clearly the GPS is not the problem. That program also tells me the horizontal dilution of precision (HDOP) is like 1.2 or 1.4, which according to https://en.wikipedia.org/wiki/Dilution_of_precision_(navigation) is excellent quality.
Attached is an extreme example. The starting point of the blue cycling line is in the lower right. This is where Ingress stopped tracking my position. Half way I started GPS-status and made a quick snapshot. The end point of the blue line, where the red marker is, is the point where ingress picked up my location again. The inset in the two screenshots is from Google maps navigation, which had no trouble whatsoever to follow the my correct location. Note this isn't in a forest or near buildings at all.
While being desperate, I discovered that sometimes it helps to switch WiFi tracking on or off. Hitting that switch seems to trigger ingress, into changing its mind, but it often doesn't help. Note in this particular example there isn't any wifi signal in range, so the wifi tracking itself is irrelevant in this case.
One could assume that when the GPS location is inaccurate, Ingress might use the GSM based location. So I suspect that the algorithm is a bit too eager to use the GSM position. It should instead keep using the still pretty accurate GPS position.
This is just one example, but I have many more. It is getting really frustrating to have to wait 5 minutes next to a portal before Ingress finally set me at the correct position (sometimes for a short moment). I hope you can adjust some parameter in your algorithm so it doesn't jump that quickly to GSM based location but keeps to GSM.
- on an sony xz2 compact running Android 10