Repository navigation
Shortwave
Applies to the published v0.3.0-beta.1 release. Device screenshots below came from a PNG-capable build based on later main source; see Screenshot Catalog.
Use an HF-capable receiver route and an antenna suitable for the band.
| Page | Workflow |
|---|---|
| Live | Direct tuning, step, span, filter, spectrum/waterfall, gain and audio controls |
| On Air | Browse schedule information using device UTC; set UTC when prompted |
| Hunt | Scan a broadcast band and inspect the strongest candidates |
| Memory | Save frequencies and labels, mark favorites, edit or delete entries |
| Logbook | Record reception notes, edit entries and export the log |
Memories use SD storage. An On Air listing is a schedule match, not proof of reception or station identification. Hunt candidates require listening and confirmation.
Controls include tuner AGC, supported manual RF gain, RTL AGC, Audio Boost, noise reduction, auto-notch and squelch. Availability depends on the receiver and route. See Gain and Shared Controls.
Current limitation: a dedicated dashboard does not mean a complete HF AM/SSB receiver. This release still uses the Browse/NFM reception path; mode guidance is not a selectable, verified AM/SSB decoder. Broad HF reception and calibration remain experimental.
The five views below show the workflow from tuning to logging. Empty memories and logs are normal on a new SD card.
Use an HF-capable receiver route and an HF antenna, open Shortwave → Live, then tune a known local or scheduled frequency. Treat schedule and Hunt matches as candidates to verify by listening.
These are actual 1280 × 720 Tab5 captures from 29 September 2026, using PNG-capable source 897c60a. They show the interface, not proof of reception. Live and demo refer to capture mode; the source is newer than the published release binary. See Screenshot Catalog for file hashes and provenance.
PR #101: Shortwave dashboard records the interface and SD work. The current generic Browse/NFM reception path remains experimental for HF voice. The published release identifies the installed package. A merged PR or source test alone does not establish live reception on every setup. Screenshots from the later capture build are identified in Screenshot Catalog.