Why Your Blue Dot Jumps Downtown

Drive into the middle of any big city with tall glass buildings and watch your blue dot lose its mind. It slides a block east. It puts you inside a parking garage you're driving past. Then it snaps back like nothing happened.

That's not a bug in your phone. That's radio waves bouncing off a skyscraper, arriving a few hundred nanoseconds late, and a receiver doing math on a lie it can't detect.

Understanding what's actually going on takes about ten minutes, and it changes how you use the thing. So let's take it apart.

The signal is a timestamp and nothing else

There are roughly 31 working GPS satellites, orbiting about 12,550 miles up, circling the Earth twice a day. Each one carries atomic clocks — rubidium and cesium — and each one broadcasts a continuous message on 1575.42 MHz that says, in effect, I am satellite number nine, here's where I am in my orbit, and the time right now is exactly this.

That's it. One-way. The satellite has no idea you exist and never will.

Your phone picks up that timestamp, compares it to what time it thinks it is, and multiplies the difference by the speed of light. Radio travels about one foot per nanosecond, which is the number that makes this whole business hard. A timing error of a millionth of a second puts you a thousand feet from where you're standing.

With one satellite, you know you're somewhere on a sphere. Two spheres intersect in a circle. Three narrow it to a couple of points, one of which is absurd — usually out in space — so it gets thrown away.

The fourth satellite fixes your phone's terrible clock

Three satellites should be enough for three dimensions. It isn't, because your phone doesn't have an atomic clock. It has a cheap quartz oscillator, the same kind in a wristwatch, and it drifts.

So the receiver treats its own clock error as a fourth unknown and solves for it. That's why you need four satellites for a real 3D fix, and it's the quiet genius of the system: every phone on Earth gets atomic-clock timing for free, without carrying an atomic clock. Your phone isn't just finding out where it is. It's finding out what time it is, to within billionths of a second, a few times per second, all day.

Modern phones also listen to Galileo (Europe), GLONASS (Russia), BeiDou (China), and depending on where you are, QZSS or NavIC. Different constellations, same trick. More satellites in view means a better geometric spread, and geometry matters as much as signal strength. Four satellites clustered in one patch of sky give a worse fix than four spread wide.

Einstein isn't optional here

The satellites are moving fast, which makes their clocks tick slow. They're also far from Earth's mass, in weaker gravity, which makes their clocks tick fast. The gravity effect wins.

Net result: a GPS clock runs about 38 microseconds per day faster than one on the ground. Left uncorrected, that's around seven miles of position error building up every single day. The satellites are deliberately set to the wrong frequency before launch so they land on the right one in orbit.

General relativity isn't a physics-class curiosity. It's a firmware setting on a satellite so your food delivery finds your driveway.

Why the first fix used to take forever

The satellite's full orbital data takes a while to broadcast — you're listening to a slow drip of bits from a signal so weak it arrives below the background noise floor. The receiver digs it out by correlating against a code it already knows, which is a story for another day.

Your phone cheats. It downloads the orbital predictions over cellular or Wi-Fi in a fraction of a second, so instead of hunting blindly for satellites it already knows which ones are overhead and roughly where. That's assisted GPS, and it's the difference between a fix in two seconds and a fix in forty-five.

Turn off cellular data in a national park, hand the phone a cold start under tree cover, and you'll meet the old behavior again. Stand still. Give it thirty seconds of open sky.

Indoors, it's not space at all

Walk into a mall and GPS is basically done. Those signals don't do concrete.

What takes over is a database of Wi-Fi routers. Every access point broadcasts a unique hardware address as part of normal operation, whether or not you connect to it. Phones and mapping cars have been recording those addresses alongside GPS positions for years, building a map of which router lives roughly where. Your phone hears six routers it recognizes, and the database says all six live in a specific building on a specific block.

That's why your location still works indoors with Wi-Fi switched off — Android keeps a separate "Wi-Fi scanning" setting that listens without connecting. Turn it off and watch your indoor accuracy fall apart.

Cell towers do the same thing more crudely. Bluetooth beacons do it more finely, which is how a store knows you're standing in the seasonal aisle.

And if your phone has a barometer, it's using air pressure to guess what floor you're on.

The dead reckoning nobody tells you about

Go into a tunnel and your dot keeps moving. There's no signal down there. Your phone is using the accelerometer and gyroscope to estimate how far you've gone since the last real fix, and the map software is snapping you to the tunnel because that's the only road you could possibly be on.

Map matching is doing a lot of heavy lifting in general. Raw GPS in a city is messier than your screen suggests. The software pins you to the nearest plausible road and hides the noise.

One thing it can't fake: which way you're facing while standing still. Heading comes from the magnetometer, a real compass, and it gets confused by magnets. If your blue dot's cone points the wrong way, the culprit is usually the magnetic car mount or the case with the wallet ring in it. Wave the phone in a figure-eight a few times and it recalibrates.

What to actually do with this

• Give it sky. Under a metal roof, in a canyon, between two towers — that's a hardware problem, not a software one. Step out.
• Some windshields block it. Heat-reflective and heated windshields have a metallic layer that eats the signal. If your dash mount reads worse than your pocket, that's why.
• Airplane mode doesn't kill GPS on most phones. The receiver only listens. Download offline maps first, then you get a working map with no signal at all.
• Check your permissions. "Always" access is the one that matters. A flashlight app has no business knowing where you sleep. Set everything you can to "While Using."
• Precise versus approximate. Both platforms let you hand an app a rough neighborhood instead of an exact point. A weather app is fine with the neighborhood.
• If accuracy suddenly degrades, toggle location off and on. It forces a fresh fix instead of coasting on stale assisted data.

The part worth sitting with is this: nothing up there's watching you. Those satellites shout the time into the void and never hear a word back. Every bit of the tracking happens on the ground, in the apps you said yes to.

Which means the sky is free. Your phone is the part with the loyalties.