The sensor that never clocks off
You're driving through a tunnel, phone mounted on the dash, navigation running. The GPS signal dies. Forty seconds of concrete overhead, no satellites, nothing. And yet the little arrow keeps moving, tracing the curve of the tunnel like it knows exactly where you are.
It does. Sort of. And the barometer in your pocket is part of why.
That tiny chip has been sampling atmospheric pressure roughly once per second since you left the house. Screen off, no weather app open, nobody asked it to. It just kept going. The question isn't whether it's running. It's why it genuinely cannot stop.
Altitude is the thing GPS alone can't solve
GPS is brilliant at placing you on a flat map. Latitude and longitude, solved. But the vertical figure is genuinely bad: typical GPS altitude readings carry errors of 10 to 50 metres under good conditions, worse in urban canyons where signals bounce off buildings like light in a hall of mirrors.
Ten to fifty metres is the difference between the third floor and the seventh floor.
For turn-by-turn navigation in a multi-storey car park, that's useless. Full stop.
The barometer fixes this because atmospheric pressure drops by roughly 1 hectopascal for every 8 metres of altitude gain at sea level. Clean, fast, reliable. Fused with GPS, it lets the phone resolve your vertical position to within 1 or 2 metres. The process is called sensor fusion, and it runs at the operating system level, not inside any single app. That's the first reason the barometer reads continuously: the location stack needs it on standby so the calculation doesn't lag the moment you open Maps.
The indoor positioning problem
Outdoor GPS works. Indoors, it falls apart completely.
Signals attenuate through concrete and steel, and the phone is left guessing. Modern phones compensate with Wi-Fi positioning, Bluetooth beacons, and the barometer. In a large airport or shopping centre, knowing you're on floor three rather than floor one is genuinely useful for routing, and no Wi-Fi signal can tell you that. The barometer can.
Google's indoor maps feature, Apple's similar capability in supported venues, and various third-party SDKs all draw on barometric data to assign a floor number. The phone needs a continuous pressure baseline to make that call the moment you open an app. If the sensor only woke up on demand, there'd be a 2 to 3 second lag while it settled.
So the sensor stays warm. That's just good engineering.
Dead reckoning and the bit between GPS fixes
Back to that tunnel. The phone blends accelerometer data, gyroscope data, and barometric pressure into a dead-reckoning estimate while GPS is blind. The barometer's role is narrow but critical: it detects whether you're descending into the tunnel (pressure rises slightly) or climbing out of it, keeping the vertical component of the position honest.
This runs on a dedicated sensor hub, a low-power co-processor that handles the barometer and its siblings while the main CPU sleeps. Power draw is often under 1 milliwatt. The phone barely notices it's happening.
What people assume is happening (and why they're wrong)
The most common assumption is that continuous sampling is a weather data play, feeding some cloud service your local pressure readings in aggregate. This does happen with some apps, and networks like Weather Underground have historically crowdsourced pressure data from phones to improve hyperlocal forecasts. But that's a side effect, not the reason the sensor runs.
The other assumption is battery drain. It really isn't, and this one annoys me because it sends people down rabbit holes of killing background processes that accomplish nothing useful.
The barometer is a microelectromechanical sensor (MEMS), physically tiny, on that dedicated low-power hub. The GPS radio pulls 15 to 30 milliwatts when active. The barometer at continuous sampling draws less power than the LED lighting your notification light.
Picture two people who bought the same flagship phone on the same day: one obsessively kills background processes, one leaves everything default. Neither will see a measurable battery difference attributable to the barometer. The obsessive one just has slower GPS cold-starts and a false sense of control.
Your phone hitting 20% by dinner is losing charge to the display, the cellular modem, and background app refresh. The barometer is essentially free.
Reading your own numbers
On Android, apps like Physics Toolbox Suite show you the live barometric reading updated in real time. On iOS, Barometer Graph does the same. Open one now and watch the number.
Above 1000 hPa? Low elevation, fair weather. Well below 1000 hPa, you're either at altitude or under a low-pressure system. That number is the same one your phone's location stack has been quietly logging all day, every day.
The sensor is sensitive enough that walking up a single flight of stairs produces a detectable shift, around 0.12 hPa. That's how fitness trackers count floors with reasonable accuracy, which is also why Apple Watch and most Wear OS devices carry the same sensor for the same reason.
Ask yourself: when did you last think about any of this while climbing stairs?
The quiet infrastructure underneath everything
The barometer is a good example of a design philosophy that gets almost no credit: some sensor data is so cheap to collect and so broadly useful that running it always beats spinning it up on demand.
Your phone is full of these continuous, invisible readings. The accelerometer that detects when you've picked up the device. The proximity sensor that knows when it's face-down on a table. The barometer keeping your floor number honest. None of them are glamorous. None of them appear in the spec sheet headline.
Pull any one of them out, though, and the things you take for granted start quietly breaking. Navigation lags. Stair counts drift. Tunnel routing freezes mid-corridor.
The atmosphere has been pressing down on your phone all day. Your phone, to its credit, has been pressing back.