GPS Inaccurate since 2025061500 Update

console145

GPS inaccurate ever since I updated my Pixel 6a to 2025061500 this morning.

Its off center to the North from 10 meters (saying a I skipped a turn five seconds before I reach it) up to 200 meters at times.

Its the same issue in Google Maps, Organic Maps, OsmAnd, and Waze.

I've restarted the apps. Rebooted my Pixel. Changed servers in Location Services, SUPL, and PSDS. No change.

EDIT: don't know if relevant but I noticed that the OS didn't optimize apps like it usually does after an update.

GrapheneOS

console145 This is likely not related to the OS update. Which country is this in?

eri8

No notable inaccuracies on my Pixel6 in OsmAnd

GrapheneOS

EDIT: don't know if relevant but I noticed that the OS didn't optimize apps like it usually does after an update.

App optimization is only triggered after relevant OS changes. There were no changes to the kernel or userspace OS in the 2025061500 release, only SoC firmware and cellular radio firmware updates. There was no GNSS firmware update or any changes to the kernel or userspace drivers/services for it. The only thing that's indirectly related to GNSS is that SUPL uses the cellular radio, but SUPL is not responsible for the location estimates and solely accelerates getting a GNSS lock. It won't cause GNSS inaccuracy, it can only cause it to take longer to get a lock.

kb00

I have exactly the same problem with a different device. I use a pixel 6 pro. I noticed it this morning on my way to work - the navigation app was completely bonkers. (HERE Maps, tried it with google maps - same result). I'm in germany btw.

GrapheneOS

https://gpsjam.org/ has a map of ongoing GPS jamming. It's impacting Germany to an extent. This is more likely to be the cause than updating SoC and cellular radio firmware.

kb00

GrapheneOS Hat might be it, i'll continue to check it. But I'm on the other side of germany (next to the netherlands) so I'm completely surrounded by green on that map.

console145

UPDATE:

It seems to fixed itself. I rebooted it again and its accurate. Don't know if the reboot is what did it.

I'm in the US

Will let you know if it acts up again.

PolarThunder

I have a pixel 6a, and also experienced strange behaviour saturday june 14th. I live in Norway and enroute Trondheim, the gps was way off, atleast 50-200 meters. (varied) using OSM. It was actually useless for street navigation.... No SUPL, but the graphene PSDS activated. This has worked fine for a very long time. On the 15th I activated the proxy SUPL in hope of getting the OSM to work navigating the city. It did work, but reading this thread, I think the explanation is something else that just switching on SUPL via proxy. Now I can turn off the supl and have only PSDS and it works. I do use VPN, and on the 14th the exit node was a country in Asia. Not sure if OSM or Graphene use IP to choose correction. Usually I just have a local exit node, just wanted to mention it.

GrapheneOS

PolarThunder IP address doesn't matter.

It likely has to do with widespread GNSS jamming or something similar to that. It could be one of the GNSS constellations purposely or accidentally giving inaccurate info.

lndshrk

It is indeed occurring in the USA (Utah) on a Pixel 7a with "reroute location requests to the os" off.

GrapheneOS

lndshrk Reboot your device.

lndshrk

FWIW, changing the mode to reroute didn't change a thing. An unmodified pixel 6a next to this 7a has the correct location.

Graphene1

Weirdly my 8 experienced the same issue on Sunday morning (UK) Organic maps which I've never had an issue with was crazy, couldn't hold accurate directions whilst driving.

Will try again this week to see if the same behaviour exists.

Standard settings, network location & WiFi scanning not enabled.

Quantum

Graphene1 A little off topic, but you might wanna look into CoMaps. A fork of Organic Maps

area51

have a look at this. It may be the culprit.
https://www.space.com/astronomy/sun/powerful-solar-flare-erupts-from-sun-triggering-radio-blackouts-across-north-america-video

Graphene1

area51 wow interesting

GrapheneOS

area51 This may be a factor but it's probably not the main issue. It's far more likely that one of the GNSS constellation has an issue. It may be intentional. It would be a good idea for us to provide more control over this in the future but it's unclear what's possible with each GNSS chip and associated drivers/services.

soupslurpr

The issue seems to have resolved, at least on my Pixel 7. It does seem likely that it was the solar flare if it has stopped for others as well.

Badrou53

My parents (location: Netherlands) had the same problem. Unmodified Pixel 7a and 8a (i.e., no GrapheneOS).