Skip to content

FreqMapper v1.0.17

Summary

Android release history now documents FreqMapper 1.0 (build 115), a prepared Google Play closed-testing candidate. The Android app has not been uploaded or published, so this is not an announcement of mobile availability.

What's new

  • The Android release history includes a 1.0 entry with the candidate’s status, update compatibility, supported features, and testing guidance. The app release overview also identifies 1.0 (115) as a closed-testing candidate rather than an available download.

Improvements

  • Android 1.0 preserves the direct Google Play update path from the 0.1 series, without requiring an uninstall.
  • Preparations for wider Google Play testing and public release now require using the same Android build already supplied to closed testers, rather than a replacement build.
  • Android diagnostic support now includes information that can help investigate native crashes and app-not-responding reports when the app’s dependencies provide it.
  • The Android 1.0 documentation describes positioned Watchers on the Map with their Meshtastic short names, and saved Meshtastic TCP radio connections using a hostname or IP address with port 4403 by default.
  • The Android 1.0 documentation explains that Active Patrol and Silent Recon can start without a FreqMapper server connection when the required saved region and offline approval are available. Encrypted GPS and radio evidence stays queued locally, and uploads resume when a connection capable of reaching the FreqMapper server returns.

Fixes

None in this release.

What you need to do

Nothing. The update is already available.

Mobile availability

Android 1.0 (build 115) is prepared as a Google Play closed-testing candidate, but it has not been uploaded or published. This release does not make it available through closed testing, open testing, or public Google Play distribution. No new private-installer Android build or iPhone build is evidenced.

Known limitations

Starting Active Patrol or Silent Recon without the FreqMapper server requires the saved region and offline approval. Queued evidence cannot upload until a connection can reach the FreqMapper server. The additional Android diagnostic information is available only when dependencies supply it.