Troubleshooting

If something looks odd, start here. Most map questions have a simple explanation, and a blank cell is often the system being careful rather than the system being broken.

I made a mapping test but nothing appeared

Check these in order:

1. Confirm the Android or iPhone app had a current phone GPS fix and the radio says connected.
2. Confirm the radio has been enrolled with a region invite key; reconnect it if the managed channel did not finish preparing.
3. Give the receipt and map a little time to refresh.
4. Check whether approved Watchers are active in that region. They can verify without a public map position.
5. If the test had no independent Watcher receipt, it will not be coverage evidence.

My phone lost internet during a wardrive

Leave the wardrive running and keep the phone connected to the radio. Saved items upload automatically after the phone reports usable internet; you do not need to resend the radio tests. On iPhone, reopening FreqMapper also triggers a retry. Keep the app installed and include the redacted Wardrive sync events in a support report if items remain queued after connectivity returns.

My invite key will not apply

The enrollment action is deliberately unavailable until the app has a fully connected, synchronized radio. Connect it first, then try the code again. If it is rejected, ask the FreqMapper community for a current code or enrollment help.

My radio says it is enrolled on another phone after reinstalling

A normal in-place update keeps the app's installation identity. Android uninstall or clearing app data removes its installation identity. On iPhone the identity is stored in Keychain and may survive reinstalling on the same phone, but this is not guaranteed; changing phones requires a new installation.

Sign in on the website and check Settings → Profile & data in the app: the app itself must show that it is linked. Check Advanced → Connection details too; development and production have separate profiles and radio registrations. If the earlier app was linked to that same profile on the same service, link the replacement app if needed, then scan for and connect the radio. FreqMapper will retry a connected radio after linking and can restore its regional enrollment without another invite key. Saved Bluetooth selections are local and must be selected again after reinstalling. Radios from an unlinked installation—or a different profile—still require administrator recovery so another person cannot claim them. Uploaded wardrives remain on that service; pending uploads are local and are lost on uninstall. Before switching Android from the private installer to Google Play, follow the migration steps.

My Android phone finds the radio but will not finish connecting

First close Meshtastic and any other app or phone that may already be connected to the radio, keep the radio nearby, and try again from FreqMapper's Radio tab. FreqMapper automatically retries one ordinary transient Bluetooth failure.

If the Radio tab says Android's saved pairing may be stale, tap Open Bluetooth settings, find that radio, and choose Forget or Unpair. Return to FreqMapper, scan again, tap the radio, and approve Android's pairing prompt if it appears. This can be needed after flashing, resetting, or replacing a radio because Android may retain pairing information that no longer matches it.

If it still fails, use Submit diagnostics to support from the Radio tab. The optional report includes redacted pairing state, connection duration, PhoneAPI stage, and recent BLE events without including the Bluetooth address, channel keys, packet contents, or route coordinates.

My Watcher is not on the map

First, a Watcher must have real MQTT receipt evidence before FreqMapper can recognize it. To be placed on the public map, it also needs a current public Position Packet that resolves to an active region and the operator must allow public placement.

Watchers without a known location can still be useful. They stay out of the public map until their regional placement is known.

A Watcher is in the wrong region

Regions are based on each Watcher's own valid location and the approved regional boundary. Contact the regional team with the node identity and the correction needed. Do not assume the region that received a packet is the physical location of the sender or Watcher.

The map looks blank or out of date

Reload once and check the map's Live indicator. The public map intentionally uses an empty state when there is no verified evidence. It does not invent a coverage overlay from generic node-position traffic just to make the map look busy.

If the service is healthy but a known region remains empty, report the region code and approximate time in Discord.

If only certain layers are missing, open Settings on the browser map. Check the neighbour, boundary, and status-box switches. Coverage grid detail changes automatically with zoom. On mobile, check Settings → Map & appearance for coverage, Watcher, and current-boundary display choices.

I need to change or delete trip data

Use the Android or iPhone Trips tab to review completed wardrives. Use Settings → Profile & data → Erase local trip history to remove phone-only history and waiting uploads after the trip ends. Use the website profile's Wardrive sessions section to inspect uploaded trip details.

To remove personal server data, use Delete account or app data in mobile Settings. A linked app opens whole-account deletion on the website; an unlinked app can delete only its own data. Choose immediate deletion or the seven-day cancellation window. Coverage already contributed remains without your identity attached. See Privacy and data before continuing, and never post private coordinates in public chat.

Last updated: 2026-09-24