Community bug reports, feature requests, and roadmap discussion for FreqMapper — a privacy-aware Meshtastic wardriving and mesh coverage-mapping system.
This repository is FreqMapper's central feedback tracker. It intentionally contains no application source code, deployment files, MQTT credentials, or radio-channel keys. It is where the community can report problems, suggest improvements, and follow the public work backlog.
FreqMapper helps the Meshtastic community collect and visualize coverage evidence while wardriving. It is built around:
- Recording a wardrive using the phone's GPS and a connected Meshtastic radio
- Mapping independently observed packet evidence from approved Watchers
- Showing regional coverage, nodes, Watchers, and evidence quality on the map
- Keeping public coverage useful without publishing private credentials or precise private locations
Use the Bug report form for a reproducible problem. Include:
- What you did and what you expected
- What happened instead
- Your Android/iPhone app version, website browser, or relevant radio details
- Sanitized screenshots or logs, when helpful
Use the Feature request form to explain:
- The wardriving, mapping, Watcher, or radio problem you want to solve
- Your proposed solution
- Alternatives or extra context
Never submit channel keys, PSKs, API keys, tokens, private messages, or precise home/private locations in an issue. See Privacy and reporting before attaching diagnostics.
The tracker covers the Android and future iPhone apps, public map, regional administration, Watcher evidence, and Meshtastic radio workflows. Private implementation and operational configuration remain separate.