Skip to content

FreqMapper v1.0.9

Summary

FreqMapper v1.0.9 adds private mobile crash and support reporting, clearer Android wardrive-start guidance, and restored iOS wardrive reconnect and status behavior.

What's new

  • On Android, choose “Public summary” or “Private report” when sending feedback. “Public summary” allows a sanitized title and user-written summary to appear in FreqMapper-Feedback. “Private report” keeps the report out of public feedback for private review by FreqMapper maintainers.
  • Android crash reports now default to private support rather than public feedback. Sending remains optional, and a pending crash report stays on your device until you send it. The report includes error details, app and device versions, and a redacted diagnostic timeline, excluding route points, current location, channel keys, message contents, and Bluetooth addresses.
  • iOS gains private crash reporting and support diagnostics.

Improvements

  • Android feedback explanations now distinguish public summaries from private supporting information. Optional reply contact, diagnostics, attachments, and operator notes remain private regardless of the selected report visibility.
  • Android support confirmations distinguish a newly created private report from a report added to an existing investigation. Matching crash reports can contribute private diagnostic evidence to an existing investigation without posting that evidence publicly.
  • Android retains your report visibility choice when a report is queued for later submission. Older queued reports and reports from older apps do not automatically gain consent for the new private diagnostic-sharing behavior.
  • Android support diagnostics prioritize crashes, connection and radio problems, enrollment and channel issues, region lookup failures, and blocked wardrive starts over repetitive progress messages. This helps preserve relevant troubleshooting details when report space is limited.
  • Android wardrive-start diagnostics now include readiness checks, region lookup timing, and the reason a start was allowed or blocked. Region lookup failures are recorded by category rather than copying potentially sensitive error messages.
  • Android diagnostic timelines contain fewer repetitive location-upload entries, distinguish changed upload failures, and record when uploads resume.

Fixes

  • Restores iOS wardrive reconnect and status behavior.
  • Android handles an unidentified connected radio as a blocked wardrive start with clear guidance: reconnect the radio, wait for “Ready,” and try again.
  • Android now handles a missing active region or missing saved offline region as an explained blocked start rather than an unhandled start error. Messages distinguish an area without an active region from a phone that needs to connect and save a region before starting offline.
  • Android no longer treats a blank saved region as a usable offline region.
  • Other Android wardrive setup failures now show “The wardrive could not start” with guidance to check the readiness items on the map and retry.
  • Android clears a previous location-upload error after uploads recover, provided that error is still the current issue.
  • Public feedback now strips marked private diagnostic content from titles, reproduction steps, and expected results as well as actual results, helping prevent private diagnostics from appearing in public summaries.

What you need to do

If Android shows “Connect once before starting offline,” connect the phone to the internet and start once in the region to save it for offline use. When sending feedback, check whether you want “Public summary” or “Private report,” and review screenshots before attaching them.

Mobile availability

Android changes are prepared as version 0.1.108 (build 109) for a separate Google Play closed-test release, but no Play upload or tester availability is evidenced yet. No iPhone build containing the iOS changes is evidenced in TestFlight or the App Store.

Known limitations

An Android wardrive cannot start online where there is no active FreqMapper region. Offline starts require a saved region or usable offline approval; a saved region alone permits Silent Recon, not Active Patrol. Ordinary Android feedback defaults to “Public summary,” so select “Private report” if you do not want a public summary. Automatic text redaction removes common channel-key, Bluetooth-address, and coordinate-pair patterns; screenshots still need your review.