Skip to content

FreqMapper v1.0.12

Summary

FreqMapper v1.0.12 improves Android and iPhone recovery after switching apps or briefly losing internet, keeps an already loaded map visible during connection interruptions, and reduces unnecessary map updates. These changes will reach mobile users when testing builds containing them are published.

What's new

None in this release.

Improvements

  • Android and iPhone recheck the FreqMapper connection when you return to the app. A failed server check gets one automatic retry after five seconds, without immediately replacing an existing connected status with an offline warning.
  • On Android and iPhone, the map refreshes after returning to the app or reconnecting while Map is open, so you can pick up with updated coverage.
  • Android pauses map rendering and map-data refreshes while another tab is open or the app is in the background. This reduces unnecessary map work without changing the active wardrive's background location collection.
  • iPhone avoids redrawing coverage and markers for unrelated app changes. During busy receive traffic, received-marker redraws are grouped at roughly quarter-second intervals while counters continue updating, reducing unnecessary map work.
  • TestFlight and Google Play tester notes can describe changes since a selected earlier build and use wording suited to the testing channel, making it clearer what changed between builds.

Fixes

  • Android and iPhone wait five seconds and check whether internet has returned before reporting a network loss as “FreqMapper is offline.” Brief interruptions no longer immediately trigger that warning.
  • Android and iPhone keep an online map that has already loaded visible during a server or network interruption, rather than immediately replacing it with a blank canvas.
  • On iPhone, returning to an active wardrive with a disconnected radio resumes automatic reconnection when no connection attempt is already underway.
  • On iPhone, returning to the app checks whether a TCP radio connection is still responding. An unresponsive connection is disconnected and sent through automatic reconnection instead of leaving the wardrive waiting on a connection that only appears active.

What you need to do

To receive these changes, install a testing build containing v1.0.12 when it becomes available in your testing channel.

Mobile availability

These changes are for Android and iPhone. They become available when builds containing v1.0.12 are published to Google Play testing and TestFlight, respectively. No newly published mobile build containing this release is evidenced. Android 0.1.109 (113) is listed as a prepared internal-testing candidate, not a confirmed available update. No new iPhone build number is evidenced, and the Android private installer channel is unchanged.

Known limitations

Keeping the map visible during an interruption requires an online map to have loaded during the current app session. Offline Mode still uses the blank map canvas, as does starting without a server connection before an online map has loaded. A connection loss that persists beyond the grace period can still produce an offline warning.