Blog · By Avinash Verma · 2026-10-11

How IndiaRoad Map detects potholes

IndiaRoad Map can notice a pothole while you drive and warn the next driver before they reach it, using only the sensors already inside your phone. Here is how it works, what leaves your phone, how warning timing is worked out, and the limits. For a general guide to these apps and what to look for, read how pothole detection apps work, and how to choose one.

The two sensors that do the work

Every Android phone has two motion sensors the app relies on.

• The accelerometer measures how the phone speeds up, slows down and moves up and down. When your wheel drops into a pothole and hits the far edge, the phone feels a sharp downward drop followed by a jolt.
• The gyroscope measures rotation. It helps the app tell a road impact apart from the phone simply being turned, picked up or swung around.

With GPS for position and speed, these are enough to recognise three kinds of road problem:

• Pothole: a short, sharp drop.
• Speed breaker: a short, sharp rise.
• Bad road: several separate hits in a short stretch of road, rather than one big one.

The same pothole feels much harsher at 60 km/h than at 20 km/h, so detection thresholds are adjusted for speed. When you are almost stopped, or the phone is rotating sharply (say, you pick it up), detection pauses so handling the phone isn't mistaken for a pothole.

Car and Bike profiles

A car and a two-wheeler feel the road very differently. A car's suspension soaks up a lot; a bike passes more of every bump to the handlebar mount. IndiaRoad Map has a Car mode and a Bike mode, and each keeps its own detection settings, so tuning one doesn't upset the other. Bike mode also changes routing: bike routes avoid expressways where two-wheelers aren't allowed.

Sensitivity from 1 to 10

Every vehicle, phone and mount is different, so detection sensitivity is adjustable from 1 to 10, with separate sliders for potholes, speed breakers and bad road.

• Higher numbers (towards 10) catch smaller hits, but may also flag minor bumps.
• Lower numbers (towards 1) only react to strong hits, so you get fewer false detections but may miss smaller potholes.

Too many false potholes? Lower it a step or two. Obvious potholes missed? Raise it.

Auto-calibration on start

A phone in a mount can sit at any angle: upright, tilted back, or flat. The app needs to know which way is "down" to separate vertical jolts from braking and turning. When detection starts, IndiaRoad Map calibrates itself: with the phone mounted and the vehicle still, it learns the direction of gravity and how much background noise the sensor has. Keep the phone still for a few seconds while this happens. If the phone is moving during calibration, the app keeps the previous calibration instead.

What is shared and what stays on your phone

The raw sensor readings are processed on your phone and stay on your phone. They are not uploaded.

When the app detects a hazard, only the hazard and its location are shared, for example "pothole at this point". That is what other drivers see on the map and are warned about. Hazards you report stay on the map even if you later delete your account, but without your name.

When you are warned: the 10-second rule

A warning is only useful if it gives you time to react. IndiaRoad Map warns you, by voice and on screen, about 10 seconds before you reach a hazard, and never closer than 100 m.

The distance is simply your speed multiplied by 10 seconds, with 100 m as the minimum. Some worked examples:

• At 60 km/h you cover about 16.7 m every second, so 10 seconds is about 167 m. You hear the warning roughly 167 m before the pothole.
• At 90 km/h you cover 25 m every second, so the warning comes 250 m ahead.
• At 30 km/h you cover about 8.3 m every second, so 10 seconds would be only about 83 m. That is below the minimum, so the warning comes at 100 m instead, which gives you a little more than 10 seconds.

Speed cameras get a longer lead: about 15 seconds ahead, and at least 200 m. At 90 km/h, for example, that is 375 m.

Warnings are only given for hazards ahead of you in your direction of travel, so you aren't warned about a pothole on the other side of a divided road or one you have already passed.

Honest limits

Phone-based detection works well, but it isn't perfect. These are the main things that affect it:

• The phone mount matters most. A phone loose in a cup holder, on a seat or in a pocket rattles and slides, which can create false hits or blur real ones. A firm mount on the dashboard, windscreen or handlebar gives the cleanest readings.
• Very slow speeds. At walking pace, a pothole produces only a gentle movement that can be hard to tell apart from normal vibration, and detection pauses when you are almost stopped. Crawling through a potholed stretch in traffic may not register every pothole.
• Not every bump is a pothole. Expansion joints on flyovers, railway crossings, manhole covers and broken road edges can all produce a pothole-like jolt. The app separates potholes, speed breakers and bad road, but some misclassifications will happen.
• It can't detect what you don't hit. If you steer around a pothole, the sensors feel nothing. That is why manual reporting matters too: tap the report-hazard button and choose the hazard type.
• Sharing needs internet. Search, routes and sharing hazards need a data connection. IndiaRoad Map does not offer offline navigation.

Putting it together

Your phone feels the jolt, the app decides what it was, and only that result and its location are shared. The next driver heading that way is warned about 10 seconds before reaching it, never closer than 100 m, on the phone or through Android Auto. IndiaRoad Map is free on Google Play (it shows ads) and works in English and Hindi.