You can’t calibrate a GPS speedometer app the way you calibrate a car speedometer, and you don’t need to. A car multiplies wheel turns by an assumed tire size, so when the tire changes, a correction factor fixes it. A phone measures ground speed and position from satellite signals, with no tire or gear in the chain, so there’s no constant error to correct. An app’s “calibration” slider just adds a fixed error of your own.
What does improve accuracy is the setup: precise location turned on, a phone that can see the sky, a settled fix before you start, and the app kept on screen. Then you can test the result against a known speed or distance. Done properly, phone GPS is typically within a couple of km/h on speed and within 1 to 2% on distance over 10 km or more of open road.
Why can’t you calibrate GPS? #
Calibration fixes errors that are the same every time. A car speedometer has one: if your tires are 3% bigger than the factory size, the dash is 3% low at every speed until you correct it.
GPS errors aren’t like that. Your phone measures the Doppler shift in each satellite’s signal as you move and works out your velocity from it. When the signal is good, the speed is good. When the sky is blocked or signals bounce off buildings, the reading wobbles or jumps, but it doesn’t read 4% high every time. A multiplier can’t fix a random error, and on a good day it adds a permanent one.
Distance works the same way. A GPS app adds up the straight lines between position fixes. It runs a little short on twisty roads and loses whatever it can’t see, like a tunnel, but a scale factor can’t tell a tunnel from a straight road.
Speedometer GPS has no offset or calibration setting for that reason. It shows the speed your phone’s receiver reports, averaged over the last five one-second readings, and puts the fix quality on screen so you can see when to trust it.
Which “calibration” tips don’t help? #
A lot of advice online mixes up different sensors.
| Tip | What it really does | Helps GPS speed or distance? |
|---|---|---|
| Waving the phone in a figure 8 | Recalibrates the compass behind a map’s direction beam | No |
| Entering a correction factor | Scales every reading by a fixed amount | Usually makes it worse |
| Matching the app to your dashboard | Copies the car’s built-in high reading | Makes it less accurate |
| Restarting the phone | Clears a stuck location service | Only if GPS was stuck |
| Leaving Wi-Fi on | Helps the phone find its rough position faster | Slightly, at the start |
| Turning on precise location | Gives the app full-accuracy positions | Yes |
Does the figure-8 motion calibrate GPS? #
No. The figure 8 is the most repeated tip of the lot, and it recalibrates the magnetometer: the small compass chip that tells the phone which way it is pointing when you’re standing still. Nearby magnets and metal throw that chip off, which is why the beam on a map’s blue dot goes wide or points the wrong way after the phone has sat on a magnetic mount.
GPS works out your speed from the satellite signals and your direction of travel from how your position changes. Neither uses the magnetometer, so no amount of waving changes your speed, your position or your trip distance.
How to do a figure 8 properly #
- Step away from magnets and metal. Move a few steps from cars, steel railings and speakers, and take the phone out of a magnetic case or mount.
- Open a map so you can see the blue dot and its beam.
- Trace a figure 8 in the air several times, turning your wrist so the phone tilts and rotates through different angles rather than staying flat.
- Check the beam. It should narrow and point the way you’re facing. If not, repeat once or twice more.
Google’s help page for Maps puts it plainly: “Make a figure 8 until the beam becomes narrow and points in the right direction. You only have to do this a few times.” On Android, Google Maps also offers a Live View calibration from the blue dot, though whether it opens depends on Street View coverage where you are. The same motion works on iPhone and Android, and only when the direction looks wrong. There’s no schedule to keep.
Why the compass drifts, and why the heading still freezes #
Magnetic car mounts and cases with magnets are the usual culprits, along with the car’s own metal and electronics, speakers, steel desks and standing next to a bridge or a parking garage. If the beam is wrong in one place only, the place is the problem.
One symptom people blame on the compass isn’t the compass at all. In Speedometer GPS the heading under the readout comes from the GPS course, not the magnetometer, and it updates only while you’re moving faster than about 1 metre per second (3.6 km/h, a brisk walk). Stop at a light and it holds the last good bearing instead of spinning. A figure 8 changes nothing there.
How to set up your phone for the most accurate reading #
Do these before you set off, not on the move.
- Turn on precise location. iPhone: Settings > Privacy & Security > Location Services > the app > Precise Location on, as Apple describes. Android: Settings > Location > App location permissions > the app > Use precise location. On most Android phones, Google Location Accuracy under Location services also speeds up the first fix.
- Mount the phone where it can see the sky. Near the top or bottom of the windshield, on the dash, or on a bike’s handlebars. A cup holder, door pocket, glovebox or trouser pocket costs you satellites. Some heat-reflective windshields weaken GPS, and an uncoated patch, often behind the mirror, helps.
- Open the app a minute before you leave. The first fix after a long time indoors is the weakest. In Speedometer GPS, wait for the GPS pill under the readout to show GOOD (within 10 m) or EXCELLENT (within 5 m).
- Keep the app on screen. Speedometer GPS uses location only while it’s open, with no background tracking, and by default keeps the screen on while you track. If the phone locks, readings stop.
- Turn off aggressive battery saving and keep the phone cool. Savers can slow location updates, and a hot phone throttles. A car charger and a shaded spot beat any power-saving mode.
- Update the phone. Operating system updates often include location fixes.
What affects GPS accuracy? #
| Factor | Effect | What to do |
|---|---|---|
| View of the sky | The biggest factor by far | Mount high, away from metal |
| Fix quality | Poor fixes give noisy speed | Wait for a good fix before starting |
| Tall buildings, cliffs | Reflected signals, jumpy readings | Watch the signal indicator |
| Trees | Weakened signals, short distance | See the tree-cover guide below |
| Tunnels and garages | No reading at all | Use the vehicle’s speedometer |
| Acceleration and braking | Smoothed readings trail by a second or two | Read at a steady speed |
| Approximate location | Coarse, unusable speed | Turn on precise location |
| Very low speed | Position noise is a big share of the reading | Expect some wobble when crawling |
How to test your app against a known speed #
These checks need a passenger to read and time, never the driver.
On a road with distance markers, hold a steady speed and have your passenger time the gap between two markers, then compare with what the app showed.
| Steady speed | Time for 1 mile | Time for 1 km |
|---|---|---|
| 30 mph (48.3 km/h) | 120 s | 74.6 s |
| 50 mph (80.5 km/h) | 72 s | 44.7 s |
| 60 mph (96.6 km/h) | 60 s | 37.3 s |
| 100 km/h (62.1 mph) | 57.9 s | 36.0 s |
At a steady 60 mph a mile takes exactly a minute, which makes that the easiest check. Stopwatch reaction time is the biggest error, so time several markers and average. If the phone agrees, your setup is good.
If the phone reads a few percent below the car’s dashboard at every speed, that’s the dashboard reading high, which is normal. Checking a speedometer with GPS turns that gap into a number.
How to test your app against a known distance #
- Pick a distance you trust more than the phone. Several highway markers in a row (5 to 10 miles, since single markers aren’t always exact), a straight road measured on a desktop map, or a certified course. Longer is better: over 1 km one bad fix can be 1% on its own, and over 10 km it barely registers.
- Set up while parked and wait for a strong fix.
- Reset the trip and press Start as you pass the start point. If you’re driving, have a passenger handle the buttons.
- Drive the course at a normal, steady speed of at least 20 km/h (12 mph). The reason is below.
- Press Stop at the end and note the distance. Repeat twice more, ideally at different times of day, and average the results.
Work out the error as (app distance − true distance) ÷ true distance × 100.
| Average error | What it means |
|---|---|
| Within 1% | As good as phone GPS gets |
| 1 to 3% | Normal on routes with trees, buildings, stops or tight curves |
| More than 3% short | Signal gaps: a tunnel, dense forest or a phone that lost the sky |
| More than 3% long | Drift while stopped, or zigzag from reflected signals in a city |
If the three runs disagree with each other by more than a percent or two, the signal on that route is the problem, not the app.
Why is my distance too short? #
- Tunnels and garages. No signal means no distance. Speedometer GPS also throws out any jump of more than 200 m between fixes. That stops a glitch from adding a phantom kilometre, but it also means the distance through a long tunnel isn’t added back when the signal returns.
- Tree cover. Leaves weaken signals enough that fixes get rejected. GPS under trees covers what helps.
- Winding roads. Straight lines between one-second fixes cut corners, and an app that records less often cuts more.
- Slow speeds. Speedometer GPS ignores steps under 5 m between fixes so a parked phone doesn’t collect phantom distance. At one fix per second that threshold is 18 km/h (11 mph), and below about that speed the app under-counts badly. Its trip distance is meant for driving, riding and boating, not walking or slow jogging.
Why is my distance too long? #
- Drift while stopped. A parked phone’s position wanders a few metres, and a naive app adds that up. Speedometer GPS ignores movement under 5 m between fixes, and under 10 m once you’ve been still, so drift rarely inflates its trips.
- Reflected signals. Between tall buildings the position can zigzag across the street. Test on open routes.
If your GPS and car odometer still differ after a clean test, why GPS trip distance doesn’t match your odometer explains which one to believe.
How to tell when a reading is wrong #
Trust the number less when:
- The GPS pill shows POOR or SEARCHING.
- You’ve just come out of a tunnel or garage and the phone is reacquiring satellites.
- You’re among tall buildings and the reading jumps with no change in your speed.
- You’ve just opened the app, so the fix hasn’t settled.
- You’re braking or accelerating hard, since the smoothed reading trails for a moment.
If no valid fix arrives for five seconds, Speedometer GPS drops the speed to zero and shows SEARCHING rather than freezing on the last value, so a stale number never looks live.
Use GPS to calibrate your car or bike instead #
The useful direction is the reverse: GPS is the reference you calibrate wheel-based instruments against.
- Car speedometer and odometer. If the dash shows 100 km/h while GPS shows 96 at a steady speed with a good fix, the speedometer reads about 4% high. After a tire size change the error can run the other way.
- Bike computer. Compare its distance with GPS over a long, open route and adjust the wheel circumference setting.
- Boat log. A paddle wheel or pitot speed sensor can be checked against GPS on still water with no current.
Frequently asked questions #
Do GPS speedometer apps need to be calibrated? #
No. GPS measures ground speed directly from satellite signals, with no tire size or gear ratio to correct. Accuracy comes from a clear view of the sky and a good fix. An app offset only makes sense if you want to copy your car’s dashboard error on purpose.
Does calibrating the compass with a figure 8 improve GPS accuracy? #
No. The figure 8 corrects the magnetometer, which tells the phone which way it is facing. GPS position and speed come from satellite signals and never touch it. A figure 8 improves the direction beam on a map, not your speed or distance.
How accurate is phone GPS for speed and distance? #
At a steady speed with a clear sky and a good fix, speed is typically within a couple of km/h of your true speed, often closer than a car’s dashboard. Distance at driving or cycling speed is usually within 1 to 2% over 10 km or more. Both get worse among tall buildings, under dense trees and in tunnels.
Can I add a correction factor in Speedometer GPS? #
No. The app shows GPS speed as measured, smoothed over five readings, with the fix quality on screen. GPS errors change with conditions, so a factor that fixes a forest drive would throw off an open highway.
Why does my GPS speedometer show movement when I’m parked? #
GPS positions wander by a few metres even when you’re still, and that wander can show up as 1 or 2 km/h. It’s noise, not motion. Speedometer GPS ignores small position changes between fixes, so a parked phone doesn’t add distance to your trip.