Mobile apps and updates
This is the starting point for FreqMapper Android and iPhone releases. Use the platform pages for the complete history, release dates, changes, and suggested tester checks.
Current releases and tester builds
| Platform and channel | Version | Build date | Main changes |
|---|---|---|---|
| Android private installer (development OTA) | 0.1.106 (107) | October 2, 2026 | Android 15 edge-to-edge, system-inset, and display-cutout compatibility |
| Android Google Play internal-test candidate | 1.0 (123) | October 13, 2026 | Public 1.0 version, Watcher map labels, TCP radios, offline wardrives, and native crash diagnostics |
| iPhone TestFlight | 0.1.0 (779) | September 24, 2026 | Improved feedback, account/app-data deletion, safer Active Patrol, and reorganized Help links |
Android 1.0 (123) is prepared for the guarded Google Play internal-testing action. It has not been published to closed testing, open testing, or production. It retains the package name, signing identity, and increasing build-code sequence needed to update existing Google Play installations. Android 0.1.109 (114) remains the latest closed-test artifact while the 1.0 candidate completes testing.
Google Play and TestFlight control when a processed build becomes available to each enrolled tester. The table identifies the latest documented build for each channel; it does not bypass store processing or staged availability.
Choose a platform
Android
The Android release history records every documented Android version from the original mapper foundation through the latest Google Play build. Recent versions include complete changes and tester checks; rapid early private-test builds are retained in a compact archive.
Android Google Play closed test
Join the FreqMapper beta group with the Google account used on your phone. Then accept the Google Play test invitation and install or update FreqMapper through Google Play.
Before replacing a private installer build, finish pending uploads and link the app to your profile. Switching signing channels can require uninstalling; that removes local trip history, pending uploads, and saved Bluetooth selections.
The private signed installer remains available separately. See Android OTA Notes for the current OTA version, complete release notes, installation behavior, update policy, and eventual retirement status.
iPhone
The iPhone release history records builds confirmed in App Store Connect, including their internal and external beta status. It deliberately does not treat every Git-derived build number as a public TestFlight release.
How version numbers work
Android uses a version name followed by a numeric build code, such as 0.1.96 (97). The private installer and Google Play may temporarily show different latest versions while releases are tested or staged.
The iPhone app currently uses marketing version 0.1.0 plus a Git-derived build number. Many intervening numbers are repository milestones rather than separate TestFlight uploads, so the iPhone history lists only builds confirmed in App Store Connect and distinguishes builds available for testing from those that were only processed. Completed source changes are added when their build is confirmed there.
Reporting a problem
Include the platform, exact version/build, phone model, operating-system version, radio model and firmware, approximate time, and the action that failed. Screenshots of the map or a redacted Activity screen are useful. Never include invite keys, channel keys, API tokens, Bluetooth identifiers, private coordinates, or message content.
See Troubleshooting for recovery steps or use the Send feedback link at the top of this Help site.