Fogbreaker
You went for a solid walk, you check your phone, and the number is way too low. Or you open two different apps and they disagree by a thousand steps. Something must be broken, right?
Almost never. In nearly every case, your phone isn't miscounting: it just physically didn't see some of your steps, or two apps are reading two different sources. Once you understand how step tracking actually works, both mysteries stop being mysteries. Let's walk through it.
First: your phone counts steps with motion, not GPS
This is the single most misunderstood thing about step tracking, so it's worth getting straight up front.
Your phone counts steps using a tiny motion sensor: an accelerometer, backed by a low-power motion chip. It watches the rhythmic bounce of your body as you walk and pattern-matches that cadence into steps. On iPhone this feeds Apple Health; on Android it feeds Health Connect (and older Google Fit). None of that uses GPS.
GPS does something completely different. It figures out where you are and what path you took (your route and distance) by talking to satellites. It has no idea how many steps you took.
So when people ask "how accurate is GPS step tracking," the honest answer is: GPS doesn't track steps at all. Steps come from the motion sensor. GPS tracks your path. Keeping those two straight explains basically everything below.
Why your phone misses steps
If your count looks low, it's almost always one of these, and they're all about the sensor simply not feeling your steps.
The phone wasn't on your body. This is the big one. Left it on the desk, in a bag on the passenger seat, on the kitchen counter while you paced on a call? No body movement, no steps. The sensor can only count what it physically feels.
Your hands (and the phone) stayed still. Pushing a stroller or shopping cart, gripping a handrail, holding a coffee, or keeping your phone dead-still in a jacket pocket all mute the bounce the sensor is looking for. You're walking; the phone isn't moving the way it expects.
The walk was too short or too slow. Step algorithms are deliberately cautious. They usually want to see several consistent steps in a row before they believe you're actually walking. That's how they avoid counting you fidgeting at your desk as a hike. The trade-off is that very short trips and slow shuffles often get trimmed.
Battery saver or background limits kicked in. Low-power mode, and especially aggressive battery management on some Android phones (Samsung, Xiaomi, Huawei, and others are notorious for it), can suspend background apps and throttle sensors. The steps happen; the app just wasn't allowed to record them.
A permission is missing. If an app never got motion or activity permission, or you revoked its background access, it can't read your steps even though the phone counted them fine.
Why two apps show completely different step counts
Now the other half: same walk, same phone, two different numbers. Neither is lying. They're just not measuring the same way.
They read from different sources. One app might read your phone's built-in hardware step counter. Another runs its own accelerometer algorithm. A third estimates steps from GPS distance divided by your stride length. Three methods, three answers.
They use different sensitivity. Every vendor tunes its own filter. Some are generous and count arm swings or bumps as steps (overcount); some are conservative and drop anything ambiguous (undercount). There's no universal "correct" threshold, so counts drift apart.
The health platform de-duplicates. Apple Health and Health Connect both merge step data from multiple sources (your phone, your watch, other apps) and actively remove overlaps so you're not double-counted. An app that reads the de-duplicated total will differ from one that reports its own raw, un-merged tally.
Your watch and phone see different things. A wrist device catches arm motion your pocketed phone misses, and your phone counts while the watch is off charging. That's why they rarely match to the step. This is also a good chunk of why every app in a roundup of gamified walking apps can show you a slightly different daily number.
Sync and timing lag. Different midnight cutoffs, time zones, and sync delays mean one app may still be catching up while the other has already rolled over.
So how accurate is GPS, really?
Since Fogbreaker uses GPS to reveal your map, this one matters, but remember: it's about your path, not your steps.
Under open sky, consumer GPS is typically accurate to within a few meters. It gets shakier in three situations: dense cities (signals bounce off tall buildings, the "urban canyon" effect), heavy tree cover, and indoors or underground, where it can drift or drop out entirely. That's why a route trace can occasionally look like it cut a corner or wobbled through a building.
For revealing where you've explored, that few-meter precision is more than enough, which is the whole premise behind a fog-of-war walking app: it only needs to know which streets you set foot on, not your position down to the centimeter.
How Fogbreaker keeps your count consistent
Here's the design choice that matters for trust: Fogbreaker doesn't invent its own competing step number. It reads the official step data your phone already keeps: Apple Health on iOS, or the system step counter and Health Connect on Android. So the count you see lines up with the source your phone (and every other well-behaved app) trusts. No mystery second tally to reconcile.
GPS is used for a separate job entirely: clearing the fog and drawing your map as you move. Steps and map are two independent systems, each doing what it's actually good at: the motion sensor for how much you walked, GPS for where. That separation is exactly why the number stays believable, and why the map you fill in while walking every street in your city reflects the ground you truly covered.
A step counter you can trust isn't the one with the highest number. It's the one that matches the source your phone already believes.
How to get the most accurate count
If you want your numbers as tight as they can be, this is the tech-support checklist:
- Keep your phone on your body while you walk: a pocket or armband, not a bag or basket. This alone fixes most "missing steps" complaints.
- Grant motion and location permissions, and leave background access on so tracking doesn't pause when you switch apps.
- Exclude the app from battery optimization (especially on Android), so the system doesn't suspend it mid-walk.
- Keep the app updated: tracking and permission handling improve over time.
- Give it a few steps to warm up: the first handful of a short trip may not register while the algorithm confirms you're really walking.
Get those right and your count gets reliable, which also means the calorie estimates that depend on your steps get more accurate, and your standing in any step challenge with friends is actually fair.
The bottom line
Your phone almost certainly isn't broken. If it's missing steps, it usually just wasn't on you, or a setting got in the way. If two apps disagree, they're reading different sources with different rules. Normal, not wrong. And GPS was never counting your steps in the first place; it's mapping your path.
Fogbreaker leans into that: it trusts your phone's own step data instead of competing with it, and saves GPS for the fun part: watching your city light up as you go.
