Closed beta
Join the SondeFox beta
SondeFox is in active development, and we're inviting a small group of radiosonde chasers to help us validate it in the field. The beta is closed and invite-based: request a slot by email, and we'll send you a build when one opens.
What the beta is
The main job of this beta is field validation: taking a decoder chain that already works on real hardware and proving it across many phones, cables, antennas, launch sites, and weather. That means the most valuable testers are people who can actually put an SDR in the air path of a sonde.
RF testers
To contribute reception reports you'll need an OTG-capable phone or tablet on Android 10+, an SDR (Airspy Mini/R2 or an RTL-SDR with an R820T/R820T2/R828D tuner, including RTL-SDR Blog V3/V4), a 400โ406 MHz antenna, and a USB-OTG cable; a powered hub is recommended. No root required.
Everyone else
No SDR? Feedback on the UI, the docs, and this website is welcome from anyone. The browser demo is a five-screen mockup of the interface with dummy telemetry (the app itself has seven tabs); no install, no hardware.
What works today, what needs validation
The short version is below; the full per-type breakdown lives in decoder support.
| Decoder | Status | Notes |
|---|---|---|
| RS41 (Vaisala) | Working | Validated end-to-end and cleared for SondeHub telemetry upload. Wider field validation across sites and conditions is what this beta is for. |
| DFM17 (Graw) | Working | Decode validated against SondeHub's multi-station data and cleared for SondeHub telemetry upload. Over-the-air field reports are still welcome. |
| DFM06/09, M10/M20, iMet-4 | In validation | Implemented and tested on synthetic signals; awaiting over-the-air confirmation from testers. These types decode on-device only: SondeHub upload is held until each decode is validated. |
| iMet-54, LMS6, Meisei, MRZ, MTS01 | Roadmap | Planned. Not decodable yet; please don't expect them in beta builds. |
| Chirp monitor | Experimental | Off by default, PHY-only (no decryption of encrypted network traffic), and authorized signals only. See the chirp monitor page. |
Known beta gap: the Spectrum screen's tap-to-tune is designed but not wired up yet. Tapping a peak does not retune the radio; type the frequency into the Tune field and tap Go instead.
What we ask of testers
After each chase (or attempted chase), a short "fly report" by email is the most useful thing you can send. The things we most want to hear:
Decode results
Which sonde types you decoded, and which you saw on the spectrum but couldn't lock. Serial, frequency, and rough distance to the sonde all help.
Signal conditions
Reported SNR, the antenna you used, gain preset, and anything odd: dropouts, drift, interference from local noise sources.
USB quirks
OTG cable and hub combinations, permission prompts, unplug/re-plug behavior, and any "dead spectrum" moments, along with your exact phone model.
Battery & thermals
How long a chase your phone survives with the SDR attached, whether a powered hub was needed, and any thermal throttling you noticed.
Telemetry upload is opt-in, needs a real callsign, and publishes only cleared sonde types (RS41 and DFM17 today); the app only uploads CRC-valid frames. Uploaded data joins the public SondeHub stream, so mark recoveries accurately and keep chase-car sharing (a separate toggle, off by default) deliberate. And the usual chaser rule applies: never trespass to recover a sonde.
How to join
-
Email [email protected]
Include your device model, Android version, which SDR you own (Airspy or RTL-SDR, and which model), and your country/region plus a rough distance to your nearest launch site; it helps us match testers to active sites.
-
Receive an APK and changelog
When a slot opens we reply with a signed beta APK and release notes. Sideload it; Android will ask you to allow installs from your mail or files app.
-
Update as new builds ship
For now, updates arrive as fresh APKs by email: install over the previous build, settings carry over. No store, no auto-update; the changelog tells you what to re-test.
Privacy in the beta
SondeFox does not automatically upload crash logs; sending a field-debug bundle is an explicit action. There are no SondeFox analytics or accounts. Network traffic goes to map providers, the SondeHub API, and, only if you use the opt-in developer capture tools (off by default), the private debug server at debug.sondefox.com. Reading a saved flight's history and fetching landing predictions are read-only, but not automatic by default: predictions require their setting plus a running local chase with eligible radiosonde targets, and enabling Saved Flights Auto-update lets Android make network-constrained exact-history requests in the background about every 15 minutes. SondeHub Live is currently available only in the separately installed SondeFox Test debug build. Production v0.14.0 does not expose the Network Live source or authorize its REST/MQTT runtime. In the debug preview, after its disclosure and network choice, broad 2D views make one bounded snapshot request, while closer 2D views send the viewed map centre and radius and open exact-sonde subscriptions. Native 3D discovery currently fails closed rather than estimating a ground viewport. The debug preview is not restored or run in the background and does not itself upload telemetry. Telemetry upload is opt-in and publishes only cleared types (RS41 and DFM17 today). The user-controlled paths that can send your own GPS position as application data are telemetry upload through uploader_position, the station and chase-car toggles, a manually confirmed recovery report when it uses the phone's current GPS fix, and the developer capture tools. A recovery report also sends coordinates including altitude, callsign or reporter name, recovered/not-found status, notes, a SondeFox recovery-software identifier, and a planned-status flag. Google Maps SDK data handling and the full picture are in Legal & privacy.
SondeFox isn't on Google Play, and there's no public download. A public release will follow once RS41 field validation completes; that is exactly the work this beta exists to finish.
Meanwhile, kick the tires
The demo is a five-screen mockup of the UI that runs in your browser with dummy telemetry. No invite needed.