Frequently asked questions
The short, no-spin version.
Is FreqMapper the same thing as MeshMapper?
No. FreqMapper is a Meshtastic-first project inspired by useful community coverage mapping ideas. It uses Meshtastic packet identities, phone GPS for wardriving, and independent MQTT watcher receipts as evidence.
Does a Position Packet prove coverage?
No. It tells the map where a node reported itself, not where a mapper successfully sent a controlled test. It appears as blue activity only.
Does a feeder have to be a repeater?
No. A feeder/gateway observer is an independent listener that uploads packet receipts to MQTT. It may be a router, client, or other mesh-connected setup. FreqMapper does not assume it is a repeater just because it happens to hear something.
If several watchers hear one packet, does that show its route?
No. It shows several independent observations. Meshtastic may have routed the packet through nodes that are not visible in the receipt data, so FreqMapper does not draw an assumed RF path.
Why are some map areas uncolored?
Uncolored grid is unmeasured. It is not automatically bad coverage and it is not a prediction model.
Can I use the map without the Android app?
Yes. The public map, regions, legend, feeder list, and statistics are available in a browser. The Android app is required only to contribute controlled phone-GPS mapping trips.
How do I get access to the mapping app?
Ask your region administrator for a region invite key. Connect and synchronize your radio first, then enter the key in the app's Settings page. A key may be shared with a small group, have a set use limit, or expire after an event.
Does an invite key give somebody control of my radio?
No. It only enrolls the connected radio with FreqMapper so the app can retrieve its managed wardriving-channel configuration and start mapping sessions. It does not expose your private radio settings, ordinary messages, or channel keys to other users.
Can I map while driving?
Only if it is safe. Use a passenger where possible, prepare the app before moving, and never interact with the phone in a way that distracts from driving. The map can wait.
Can anyone create a region?
Anyone can propose one, but activation is reviewed. The area needs local stewardship, a clean boundary, and independently verifiable feeder evidence.
Why are feeder configuration details not here?
Those details include operational access that should not be copied into a public guide. Contact the Freq51 community team in Discord for feeder onboarding.
Last updated: 2026-08-26