Help

Answers to the most common questions. Not listed? Email us at daniel.ehrhardt@codext.de.

For passengers and trip planning

In Germany, drivers must not use a speed camera warner while driving (§ 23 (1c) StVO). OpenBlitzer is meant for passengers and for planning. The app is not available in Switzerland.

How do warnings work?

The app continuously compares your GPS position, speed and heading with the fixed cameras stored on the device and the current community reports. All of this happens on your phone.

  • How far it looks ahead depends on your speed: 300 m below 60 km/h, 500 m below 90 km/h, 800 m below 130 km/h, 1,200 m above that.
  • When a camera or report lies ahead, a banner shows the type, distance and speed limit, with a chime, a spoken announcement and vibration.
  • A second alert follows shortly before the camera: 150 m before it in town, 300 m before it on fast roads.
  • If you drive faster than the limit plus your tolerance (3 km/h by default), the app beeps until you slow down.

Use the demo drive in the app to see and hear it without driving.

Why does the driving direction matter?

Many cameras only measure one direction, and many roads run close to each other. Without direction, the app would warn about cameras on the opposite carriageway, on a parallel road or behind you. So OpenBlitzer only warns when a camera lies roughly ahead in your direction of travel (within 35 degrees) and, where known, measures your direction.

The app derives your heading from GPS from about 10 km/h. When standing still or at walking pace the heading is imprecise.

Does the app warn in the background?

Yes. With the screen off or with a navigation app in front, OpenBlitzer keeps warning with sound, voice and vibration. Music or navigation prompts get quieter for a moment.

  • iPhone: The “While Using the App” permission is enough. While the app warns in the background, iOS shows the location indicator in the status bar.
  • Android: The app runs as a foreground service and shows a persistent notification. Some manufacturers stop background apps to save power; if that happens, exclude OpenBlitzer from battery optimisation.
How much battery does OpenBlitzer use?

GPS and a bright screen use the most power. In the background or with the screen off, consumption is much lower. On longer trips we recommend a charging cable. Fixed cameras are stored on the device, so on the road the app only uses a little mobile data for live reports.

How do I report a camera, a traffic jam or a hazard?

Tap the report button on the map and choose the type: mobile camera, traffic jam end, accident, roadworks, hazard, road closure, poor visibility or new fixed camera. It never takes more than two taps. The app uses your position and heading at the moment you tap.

If the same kind of report already exists within 200 m for your direction, yours counts as a confirmation. To prevent abuse, each device can submit up to 12 reports per hour.

How do I confirm or remove a report?

After you pass a report, the app asks “Still there?”. Tap Yes if it is still there or No if nothing was there. The question disappears by itself after 12 seconds. The app does not ask about your own reports.

  • Yes extends the report by its full lifetime, for example 2.5 hours for a mobile camera.
  • Once a report has two more No votes than Yes votes, it is removed. The person who reported it counts as one Yes.
  • Each device has one vote per report; if you vote again, the latest vote counts.
A fixed camera is missing or wrong. What can I do?

If a camera is missing, report it in the app as a “new fixed camera”. Once three different devices confirm it, it becomes part of the fixed data. Even better for everyone: add or fix it in OpenStreetMap. Our server picks up changes from OpenStreetMap once a week.

Does the app work offline?

Yes, for fixed cameras. They are stored on the device and warn without signal. Live reports need a connection; reports that were loaded stay cached for their lifetime. The map itself also needs a connection for new areas.

How do I run my own server?

The server lives in the same repository as the app, in server/. It runs on Bun with a single SQLite file and is built as a Docker image. A compose file is in deploy/.

  • On first start the server imports the fixed cameras from OpenStreetMap through the Overpass API, then again every week. If an import fails, the previous data is kept.
  • A secret salt makes sure install IDs are only stored as hashes; an admin token lets you delete reports.
  • The API is described in docs/API.md.

The step-by-step guide, including how to connect the app to your server, is in the README on GitHub.

What does OpenBlitzer cost, and how is it funded?

The app is free, with no ads, no subscription and no in-app purchases. Codext GmbH runs the server. The source code is MIT licensed on GitHub.

Why is OpenBlitzer not available in Switzerland?

Switzerland prohibits warnings about traffic checks by law, for passengers too. That is why the app is not available in the stores there.

Contact

Questions, feedback or found a bug? Email us at daniel.ehrhardt@codext.de. You can also report bugs and ideas as an issue on GitHub.

Wrong or abusive reports in the app? Vote No or email us and we will remove them.