Why Google Maps Timeline Shows the Wrong Activity (and How to Fix It)

Your morning walk shows up as a 4 km drive. Your bus commute is logged as cycling. A 30 second trip to the mailbox never appears at all. If your Google Maps Timeline keeps guessing your transport mode wrong, you are not doing anything wrong, and your phone is not broken. Activity detection is a probability guess, and it misfires in predictable places.

I have tested this on both an Android phone and an iPhone over hundreds of logged trips, and the pattern is consistent: it is excellent on long highway drives, mediocre in dense cities, and unreliable on transit and short hops. This guide explains why, walks you through the corrected steps for the new on-device Timeline, and is honest about when you should stop relying on Timeline entirely.

The 2025 change that broke a lot of old advice

Most articles still tell you to "visit google.com/maps/timeline on desktop." That advice is dead. Here is what actually changed, and why it matters for fixing wrong activity.

Google moved Timeline from the cloud onto your individual device. The web version of Timeline was shut down on June 9, 2025, and Timeline on a computer no longer exists. Your location history now lives only on the phone that recorded it.

That move had three consequences people are still discovering:

• Only about 90 days of history were migrated by default. If you never enabled cloud backup before your personal cutoff, history older than roughly three months may have been deleted. A separate technical fault in March 2025 wiped some users' Timeline data entirely, and only people who had turned on encrypted cloud backup could recover it.
• Timeline is now per-device. Two phones no longer feed one shared history. The Timeline on your Android phone and the one on your iPad are separate.
• You edit on the phone, not the web. Every correction, including transport mode, now happens inside the Maps app.

Takeaway: if a tutorial sends you to a desktop browser to fix Timeline, it was written for a version of Maps that Google retired. Do everything below on your phone.

Sources for these dates: Google's own Manage your Google Maps Timeline help page, and reporting from 9to5Google and Android Police.

How activity detection actually works

Google never asks how you traveled. It infers it from two signals.

1. Speed and movement pattern from GPS. Your phone logs a string of coordinates with timestamps. Divide distance by time and you get speed. Walking sits around 3 to 5 km/h, cycling 15 to 25 km/h, and driving 30 km/h and up.
2. Motion sensors via Android's Activity Recognition. Your accelerometer and gyroscope produce a fingerprint for each activity. Google's on-device model sorts that fingerprint into categories such as Still, On foot, Walking, Running, On bicycle, In vehicle, and Tilting (the same set the Android Activity Recognition API exposes to fitness apps).

When those two signals agree, detection is accurate. When they disagree, the algorithm has to pick one, and that is where the wrong guesses come from.

You can sanity-check the speed half of this yourself. Open our GPS Coordinates tool while you move and watch how the reading jumps. If your coordinates leap several meters between refreshes while you are standing still, that same jitter is what feeds Timeline a fake speed.

Why detection goes wrong (the real reasons)

1. Cities scramble GPS

In a downtown core, your phone's signal bounces off glass towers before it reaches the antenna. This is multipath error, and it makes your logged position teleport. A 5 meter jump that happens in one second reads as 18 km/h, so a slow walk past skyscrapers can look like a bike or a crawling car. Dense urban areas are the single biggest cause of wrong activity.

2. A bus at walking speed looks like walking

Sitting on a bus stuck in traffic produces almost no body motion and a low average speed. To the sensors, that is indistinguishable from a stroll. Trains, ferries, and moving walkways all create patterns that detection was not designed to separate cleanly, which is why transit gets misread so often.

3. Short trips never reach confidence

A two minute hop to the corner store does not give the model enough data points to commit to a mode. Brief movements frequently show up as the wrong activity or do not register as a trip at all.

4. Where you carry your phone

Activity recognition reads your gait through the phone's sensors. A phone bouncing in your hand while you walk produces a noisier signal than one sitting quietly in a pocket, and a phone in a cupholder while you drive reads differently from one in your hand. Consistency helps the model; constant repositioning hurts it.

5. Passenger versus driver

Timeline cannot reliably tell whether you drove or rode. Both produce identical In-vehicle sensor data, so a car ride as a passenger is logged the same as one where you were behind the wheel.

Takeaway: detection is a best guess from speed and motion. It is strong on open highways and weak exactly where most daily errors happen, which is cities, transit, and short trips.

How to correct a wrong trip (current on-device steps)

These steps reflect the 2026 on-device Timeline, which is the only version that still exists.

Android

1. Open the Google Maps app.
2. Tap your profile picture or initial (top right), then tap Your Timeline.
3. Use the date picker to open the day with the wrong trip.
4. Tap Edit, then Edit day.
5. Scroll to the incorrect entry. From here you can fix the place and the time of a stop, and remove or adjust segments that are wrong.
6. Tap Save.

Honest note: Google's own help page documents editing the place and the time of an entry, but it does not currently describe a clean one-tap toggle to swap a trip from "Driving" to "Walking" the way the old web Timeline let you. On the on-device version, transport-mode correction is more limited than it used to be. If your only goal is a correct mode label, the most reliable fix is prevention (see the next section), not after-the-fact editing.

iPhone and iPad

1. Open the Google Maps app.
2. Tap your profile picture, then Your Timeline.
3. Open the day, tap Edit, then Edit day.
4. Adjust the place or time of the incorrect entry and tap Save.

The iOS flow mirrors Android, with the same limitation on mode correction. When you save an edit, Maps may ask whether to share that correction with Google to improve detection; that choice is yours and does not change whether the edit sticks on your device.

The reliable fix: set the mode before you move

After-the-fact editing is fiddly. The cleaner approach is to tell Maps the mode up front so it records the trip correctly the first time.

1. Open Google Maps and tap Directions.
2. Pick your destination.
3. Select the correct mode at the top: Driving, Walking, Cycling, Transit, or Two-wheeler (availability varies by country).
4. Tap Start and let navigation run.

When you actively navigate in a chosen mode, that is what Timeline records. For any trip you genuinely need logged correctly, start navigation rather than trusting passive detection. It costs ten seconds and removes the guesswork.

Improve passive detection going forward

If you would rather not start navigation every time, give the detector better data.

Grant the sensor permissions it needs

Android:

• Settings, then Apps, then Google Maps, then Permissions.
• Allow Physical activity (this is the permission that lets Activity Recognition classify walking, cycling, and driving).
• Set Location to Allow all the time and turn on Use precise location.

iPhone:

• Settings, then Privacy & Security, then Motion & Fitness, and enable it for Google Maps.
• Settings, then Privacy & Security, then Location Services, then Google Maps, set to Always and turn on Precise Location.

Without the Physical activity (Android) or Motion & Fitness (iOS) permission, Maps loses half its signal and falls back to GPS speed alone, which is the noisier of the two.

Tighten up GPS accuracy

Better coordinates mean fewer fake speeds. Keep Wi-Fi and Bluetooth scanning on so your phone can cross-reference nearby networks, avoid heavy battery-saver modes during trips, and recalibrate your compass when location feels off. Our step-by-step walkthrough is here: How to Calibrate Your Phone's Compass and GPS. If you want the full picture on what affects GPS precision, see the Complete GPS Accuracy Guide.

Carry the phone consistently

Pocket for walking and running, mount or cupholder for driving. A steadier carry gives the sensors a cleaner gait fingerprint.

When a dedicated app beats Timeline

Timeline is a free bonus feature, not a measurement instrument. If your records carry real consequences, a purpose-built tracker is the honest recommendation. Here is the comparison, with current pricing verified against each vendor.

The pattern is simple. Timeline answers "roughly where was I and how did I probably get there." A dedicated app answers "exactly how far, how fast, and in what mode, with a record I can defend." If the answer needs to survive a tax audit or a training plan, pay for the right tool. Pricing above is from MileIQ and reporting at MileageWise; plans change, so confirm current rates before you subscribe.

Takeaway: Timeline is a free convenience layer. For anything you would be upset to get wrong, set the mode manually or use a tracker designed for that job.

Privacy and cleanup

Activity detection requires continuous location plus motion sensing, so it is worth knowing your controls.

• Auto-delete now defaults to 3 months. In Your Timeline, open Location & privacy settings to choose 3, 18, or 36 months, or keep until you delete.
• Cloud backup is opt-in and encrypted. Turn it on from the cloud icon in Your Timeline if you ever want to recover history after switching phones. Given the March 2025 data-loss incident, this is the only thing that protects your history.
• Turn it off entirely if the tradeoff is not worth it: in Your Timeline, open settings and pause or delete location history. Navigation still works without Timeline recording.

If you are weighing this against broader tracking concerns, GPS vs IP Location Explained covers what each method can and cannot see about you.

Frequently Asked Questions

Can I still fix my Timeline on a computer?

No. The web version of Timeline was shut down on June 9, 2025. All viewing and editing now happens inside the Google Maps app on your phone, under your profile picture, then Your Timeline.

Why did my old Timeline history disappear?

When Google moved Timeline on-device, only about 90 days of history were migrated by default. If you never enabled cloud backup before your personal cutoff, older history may have been deleted. A separate fault in March 2025 also wiped some users' data, and only those with encrypted cloud backup could recover it.

Can I change a trip from driving to walking after the fact?

Partly. On the current on-device Timeline you can edit the place and time of an entry under Edit, then Edit day. Google's help docs no longer describe a clean one-tap mode swap like the old web version had, so the most reliable way to get the right mode is to start navigation in that mode before you travel.

Why does Maps think I was driving when I was walking?

Almost always GPS error in a city. Signal bouncing off tall buildings makes your logged position jump, and a several-meter jump in one second reads as driving speed. Granting the Physical activity (Android) or Motion & Fitness (iOS) permission gives Maps a second sensor signal that reduces these mistakes.

Why does my bus or train ride show as walking?

A vehicle moving at low speed in traffic produces little body motion and a low average speed, which the sensors read as walking. Transit is one of the hardest cases for automatic detection, and it varies a lot by region.

Does turning on the Physical activity permission really help?

Yes. That permission is what lets Android's Activity Recognition classify your motion as walking, cycling, or in a vehicle. Without it, Maps relies on GPS speed alone, which is the noisier signal and the main source of city errors.

Is Timeline accurate enough for business mileage or expense reports?

Not really. Timeline is a best-guess feature with no audit trail. For tax-grade records, a dedicated tracker such as MileIQ logs every drive automatically and exports IRS-formatted reports. Use Timeline for a rough memory of your day, not for anything financial.

How do I stop Maps from tracking my activity at all?

Open Your Timeline in the Maps app, go into settings, and pause or delete location history. You can also set auto-delete to the shortest window. Navigation and search still work with Timeline turned off.

The bottom line

Wrong activity in Timeline is not a bug you can fully eliminate, because it is a probability guess working with imperfect GPS and sensor data. My honest take in one sentence: treat Timeline as a free, approximate diary, and the moment a trip actually matters, either start navigation in the correct mode or hand the job to a dedicated tracker. Grant the motion permission, keep precise location on, and your day-to-day accuracy will improve, but do not ask a best-guess feature to do a measurement tool's work.

Want to verify your phone is reporting position correctly during a test walk? Check live readings on our GPS Coordinates page or Find My Location tool.

Related Articles:

• How to Calibrate Your Phone's Compass and GPS
• Complete GPS Accuracy Guide
• GPS vs IP Location Explained
• Fix Location Services Not Working on iPhone
• Fix Location Services on Android