Skip to content
ok1cdjPublic

About

A ham radio logger with a single, smart input line. One line recognizes what you type — callsign, band/mode, report, serial, locator, award reference — so you can log a QSO with almost no taps. A web app first, wrapped in an Android WebView shell as an APK.

Resources

Stars

3 stars

Watchers

0 watching

Forks

Repository files navigation

kQSO icon

kQSO

A ham radio logger with a single, smart input line. One line recognizes what you type — callsign, band/mode, report, serial, locator, award reference — so you can log a QSO with almost no taps. It runs as a web app (offline PWA), as an Android app and as an iOS app for iPhone and iPad (the same web app in a native shell).

It runs on any phone, tablet or computer, and has an e-ink display mode as well (tuned on the Mudita Kompakt, 480×800).

Get it on Google Play Download on the App Store

Buy Me a Coffee

How it logs

Android phone: a SOTA activation on OE/SB-257 — four QSOs, a band change from 40 m to 20 m, a callsign suggestion, then the QSO list

SOTA activation (phone, OE/SB-257): a whole QSO on one line (DD2TC 55 T57), call + report, 20m to change band, a call picked from the suggestions, and the QSO list at the end.


Android tablet: IARU R1 VHF contest as OL0M — a full QSO with QRB, a locator from the callsign database, SSB to CW with the keyer macros, a QSO entered piece by piece, a dupe, then the QSO list and the map

VHF contest (tablet, OL0M, IARU R1 2024, sped up 1.25×): a full QSO with QRB and points, a locator filled in from the callsign database, cw with the keyer's macros, a QSO entered piece by piece (call ⏎ 082 ⏎ locator ⏎ ⏎), a dupe, then the QSO list and the map.

Features

  • One smart input line with its own alphabetical keyboard (a hardware keyboard works too); a preview under the line shows what will be saved.
  • Log profiles: activation (SOTA / GMA / POTA / WWFF / TOTA / BOTA), general, VHF contest (serials, locators, IARU R1 scoring, EDI export), satellite (one log per pass).
  • ON4KST chat in a VHF contest log: stations with QRB, bearing and QRV bands, skeds, writing from the log line; native in the apps, through a relay on the web.
  • Bands 160 m to 76 GHz; microwaves can be typed in GHz (24G).
  • Callsign database: suggestions and locator prefill from a bundled set plus your own worked stations; the VHF set (from the ČRK contest logs) knows the bands each station is QRV on; DUPE warning.
  • QSO map and contest statistics, offline; optional rain radar for rain scatter.
  • Export ADIF (and EDI per band), push to your own Wavelog.
  • Crash-safe: every QSO is written at once; an unfinished one comes back after a restart.
  • CW keyer (M5-ESP32-keyer) and Icom radios over CI-V (beta) — the IC-705 over its Bluetooth, any Icom on a USB cable / CT-17 (Chrome / Edge on a computer) or through the keyer: macros, ESM, band / mode / frequency from the radio, voice memories, transverters.
  • CW decoder (Android and iOS apps, web in Chrome / Edge on a computer): DeepCW decodes the radio's audio (USB sound card, the phone's microphone) or a WebSDR / KiwiSDR tab; a tap puts a call, report or locator into the line.
  • E-ink and standard display, light and dark theme, English and Czech.

Details of each feature are below; the full manual with screenshots is in the app (Settings → About → Manual) and on the web: English · česky.

Screenshots

Mudita Kompakt (e-ink): logging a satellite pass Mudita Kompakt: log list with the Wavelog push result Android phone, dark mode: RS-44 pass, callsign suggestions and the parse preview

Mudita Kompakt (e-ink, APK) · Android phone (dark mode, suggestions + parse preview)

Android tablet: VHF contest in CW with the keyer macros, the recent QSOs and a locator suggestion

Android tablet, VHF contest in CW: keyer macros, the recent QSOs beside the keyboard, a locator suggested from the callsign database

How to log

Type a whole QSO on one line; press Enter to fold parts into the QSO, Enter on an empty line to save it. Only the callsign is required.

40m ssb                    band + mode (sticky until changed)
24G cw                     microwaves in GHz (→ 1.25cm), also 10G, 76G…
OK1ABC                     callsign → saves with defaults
OK2XYZ OK/ZC/001           worked station + SOTA reference (→ OK/ZC-001)
OK2XYZ OKR/1001            lookout tower, TOTA (→ OKR-1001); POTA CZ/0001, WWFF OKFF/0001
OK2XYZ OL/LI/001           GMA-only summit (→ OL/LI-001, MY_SIG=GMA)
DL5ABC 55 JO60UN           received report + locator
G8AHK/P PETR               name (General profile)
1832 OK1ABC                HHMM first = manual UTC time
OK1ABC ⏎ JN79US ⏎ ⏎        fill piece by piece, empty Enter saves
W                          (alone) discard the unfinished QSO
D                          (alone) delete the last saved QSO, after a confirm

The received report is a bare number, the sent report is T57; both default per mode (59 on SSB/FM, 599 on CW). In the VHF-contest profile a bare number is the serial (58123 = report 58 + serial 123):

2m ssb
OK1ABC 007 JO60UN          serial + locator → preview shows QRB (points)

On a satellite log the exchange is report + locator (9A5Y 59 JN86); typed band tokens are ignored. See Settings → How to log in the app for the full grammar.

Feature details

  • One input line, own 6×7 alphabetical keyboard (no system keyboard; a hardware keyboard works too). A parse preview under the line shows what will be saved.

  • Bands 160m…70cm and microwaves up to 76 GHz: 23cm 13cm 9cm 6cm 3cm 1.25cm 6mm 4mm (ADIF names; EDI PBand 1,3…76 GHz). Microwaves can be typed in GHz — 1G 2G 3G 5G 10G 24G 47G 76G — handy for 24G, since the keyboard has no dot.

  • Log profiles, chosen when a log is created:

    • Activation (SOTA / GMA / POTA / WWFF / TOTA lookout towers / BOTA bunkers) — your references are set when the log is created, several at once (a summit + POTA parks + a WWFF area …), and export also gives one file per reference; the worked station's reference is logged for S2S.
    • General — adds the name.
    • VHF contest — serials, 6-char locator required, IARU R1 scoring (below).
    • Satellite — one log per pass; the bird (RS-44, SO-50, ISS, QO-100…) is picked at creation and sets uplink/downlink band and SAT_NAME.
  • Callsign database: suggestions and locator prefill from a bundled set per profile (VHF contest / chasers / satellites) plus your own worked stations, kept apart from the logs; export / import (merge) / delete in Settings.

  • DUPE warning: same call + band + mode; VHF contest same call + band (any mode); satellite same call + bird. It warns; in a VHF contest logging a dupe asks first, and the earlier QSO then becomes ERROR.

  • Line commands: W discards the unfinished QSO, D deletes the last saved one (a VHF contest never deletes: it strikes the QSO out as ERROR — kept with its serial, 0 points, an ERROR row in the EDI), E edits it. Hardware keyboard shortcuts: Ctrl+Enter saves, Alt+W / D / H / E / X / M / L / Q, F5–F8 F11 F12 the macros, PgUp / PgDn the CW speed (all in the in-app help).

  • VHF contest scoring: 1 point per km between locator centres (111.2 km/°, truncated + 1), each station once per band. QRB shows in the preview; the QSO list has points per QSO, a score line per band (QSO · points · WWL · ODX) and a search (call, serial, locator); the contest panel's rate is live (QSOs per hour from the last 10).

  • QSO map (VHF contest, satellite): a dot per worked locator with the call, the Maidenhead grid and your QTH over bundled Natural Earth coastlines and borders (1:10m Europe, 1:50m world) — works offline; calls can be switched off. Tap the map for that spot's locator, QRB and azimuth from your QTH (JO61SF · 141 km · 333°).

  • Rain radar on the VHF-contest map (rain scatter, 3 cm; off by default): the current RainViewer frame under the map, refreshed in the background while the map is open — greys on e-ink (as in kRadar), colours elsewhere, 5 levels from dBZ.

  • Contest statistics: per band points, average per QSO and the band's top 10.

  • Export: ADIF per log (all bands); VHF contest also EDI (REG1TEST), one file per band — contest name/section asked at export, station fields remembered.

  • Wavelog push: General, Satellite and VHF-contest logs can be sent to your own Wavelog (API v2, Wavelog 3.1+) with one tap in the log list — never automatically; duplicates are skipped by Wavelog, so resending is safe. Set up URL + a wl2_ token (scopes qso:write, station:read) in Settings; no server CORS setup needed.

  • Storage that survives: every QSO is appended to the log file at once; an unfinished QSO is kept in a crash journal and offered back after a restart. Web: OPFS (persistent storage requested); APK: .adi files in app storage.

  • CW keyer over Bluetooth (beta) (APK, or web in Chrome / Edge; off by default): the M5-ESP32-keyer — in CW the strip offers the macros CQ (DE in S&P) EX TU ? MY REF/LOC/INF (F5–F8 F11 F12, also on the chat / map / QSO list screens), STOP while sending (also Esc), RUN / S&P (R / S) with own macros per log profile (editable in Settings), S20 = 20 WPM until disconnect, default speed in Settings, C = connect again, K text = send text, K = CW keyboard mode, ESM (Enter sends the macros, as in N1MM; ESM), A3 = CQ repeat 3 s after each CQ (RUN; Esc / another macro ends it); {RST} / {NR} go out as cut numbers (5NN, T18). Tested with the M5-ESP32-keyer v2; please report bugs on GitHub Issues.

  • Icom radios over CI-V (beta) (off by default; Settings → Radio): the IC-705 over its Bluetooth LE (Android / iOS app), any Icom on a serial port — its own USB or a CT-17 / USB–CI-V cable, through Web Serial (Chrome / Edge on a computer; the bus rate and the radio's address are found by themselves; untested on a real radio so far), or any Icom through the M5-ESP32-keyer on the radio's CI-V jack (keyer firmware 2.1.0+, its CIVTX / CIVRX tunnel; Android / iOS app, Chrome / Edge — one keyer link for CW and the radio). Radio definitions (web/src/core/rigmodel.ts) give each model its bands, tuning range and CI-V functions: IC-705, IC-706 / MkII / MkIIG, IC-910 (optional 23 cm unit), IC-9700, IC-7300, IC-7610, IC-7100; the model goes by the CI-V address found or is chosen in Settings. Tested so far: IC-705 (Bluetooth), IC-706MkII and IC-910 (keyer; Android, iPad, browser). Band, mode and the exact frequency (ADIF FREQ) follow the radio, a typed band / mode tunes it (F28300 = 28.300 MHz; a band the radio doesn't work isn't tuned — only the log switches and QSOs are logged on it, and nothing keys the radio; transverters per band in Settings → XVERT), and CW macros go out through the radio's own keyer (CI-V) where it has one (IC-705, 7300, 9700, 7610, 7100; older radios are keyed by the M5 keyer's wire), with the same strip as the M5 keyer; in SSB / FM the strip offers T1–T4, the radio's voice TX memories (IC-705, 7300, 9700, 7610; e.g. a recorded CQ), with STOP. IC-705 first connection: radio MENU → SET → Bluetooth Set → Pairing Reception. Via the keyer: CI-V Transceive on in the radio. The radio must be in CW (else kQSO says so); with break-in off only the sidetone sounds. Safety: CW is handed over in parts of up to 30 characters; if the link drops while sending, the radio still finishes the part it has (the M5 keyer stops at once).

  • CW decoder (Android and iOS apps, web in Chrome / Edge on a computer; off by default; Settings → CW decoder, Alt+U; outside Chrome the audio is resampled to 9600 Hz in core/cw/resample.ts, as WebKit can't record into a 9600 Hz AudioContext): DeepCW by e04 (MIT), a CTC neural network over a spectrogram, run by onnxruntime-web (WASM, one thread) in a worker (web/src/core/cw/, web/src/ui/cw/). The runtime and the models are not in the bundle or the APK: deploy.yml puts them under cw/ (web/scripts/cwdata.py: the models from e04/deepcw-engine at a fixed commit, the WASM from node_modules; sizes and SHA-256 pinned in web/src/core/cw/assets.json, the hash in each file name) and the app downloads them on demand into OPFS, checks the hash, then works offline. Input: getUserMedia (the radio's USB sound card, no echo cancellation / noise suppression / AGC) at 9600 Hz, or another tab through getDisplayMedia. It runs only in an open log in CW; the narrow model reads the 3 spectrogram bins at the CW pitch, the wide one 400–1200 Hz. Tuning indicator from DeepCW's per-bin CW detector. Android / iOS: later (microphone permissions, CPU on a phone).

  • E-ink / standard display modes (the APK starts in e-ink), keep-screen-on while logging, EN / CS UI (by the system language).

  • Anonymous usage statistics (web only): screen views and a few action names (log created with its profile, ADIF/EDI export, Wavelog push) go to a self-hosted Umami (stats.ok1cdj.com) by a plain fetch — no tracker script, no cookies, never any log content (no calls, locators, QSOs). Off in the APK and in dev; switchable in Settings; dropped when offline.

  • Rain radar (when switched on): the map fetches tiles from RainViewer (api.rainviewer.com, tilecache.rainviewer.com) — your IP and the map area, no log data. "Weather data by RainViewer" is shown on the map. Off = no request.

Out of scope: ADIF import (the flow is log → export → forget).

Development

TypeScript + Vite + Vitest, no runtime dependencies (static bundle, no CDN) — with one exception: onnxruntime-web (pinned), loaded only by the CW decoder's worker once the user turns it on; its WASM is downloaded on demand, not bundled.

cd web
npm ci
npm test          # the whole core: parser, ADIF, EDI, scoring, calldb, Wavelog… (Vitest)
npm run typecheck # 4 projects: core / browser / worker / sw
npm run dev       # dev server at /
npm run build     # production build to web/dist (base /)

Layout:

web/
├── src/core/       parser, model, ADIF, EDI, scoring, calldb — pure logic, no DOM
├── src/db/         bundled callsign sets (vkv / sat / awards TSV)
├── src/platform/   the ONLY storage access (web: OPFS worker; APK: KQSONative bridge)
├── src/theme/      design tokens for e-ink / standard display modes
├── src/ui/         screens, keyboard, i18n (en/cs)
├── src/sw.ts       service worker (offline-first, web only)
└── tests/          Vitest
app/                Android WebView shell (Kotlin, AGP 9, minSdk 30, compileSdk 37)

Android shell

app/ (com.ok1cdj.kqso) serves the bundled web build locally through WebViewAssetLoader. The KQSONative bridge gives native storage (logs as .adi files), SAF export, the system file picker (callsign DB import) and keep-screen-on; INTERNET is only for the Wavelog push. Local build needs JDK 17+ with javac (e.g. Android Studio's JBR) and an Android SDK via sdk.dir in local.properties:

cd web && npm run build       # web bundle → copied into app assets at build time
cd ..
export JAVA_HOME=/opt/android-studio/jbr
./gradlew :app:assembleRelease  # signed when local.properties has the signing.* keys
./gradlew :app:assembleDebug    # debug build (different signature → uninstall first)

Deploy & release

  • Web: push to main → GitHub Actions (deploy.yml: npm ci, typecheck, test, build) → web/dist deployed to GitHub Pages, custom domain kqso.ok1cdj.com (DNS: CNAME kqso → ok1cdj.github.io). The build uses base /.
  • APK: bump versionCode / versionName in app/build.gradle.kts, add the store release notes fastlane/metadata/android/{en-US,cs-CZ}/changelogs/<versionCode>.txt (≤ 500 characters, the Google Play release notes), rename ## [Unreleased] in CHANGELOG.md to ## [1.7] – date, then push a v* tag (git tag v1.7 && git push origin v1.7) → release.yml builds the web, signs the release APK and attaches it to a GitHub Release as kqso-<versionName>.apk, with that CHANGELOG section as the release notes (the release fails if the section is missing). It can also be run by hand (workflow_dispatch) — that only uploads the APK as a build artifact.

Signing needs repository secrets (Settings → Secrets and variables → Actions), like the rest of the app family:

secret value
KEYSTORE_BASE64 base64 -w0 keystore/kqso.jks
KEYSTORE_PASSWORD keystore password
KEY_ALIAS key alias (kqso)
KEY_PASSWORD key password

The keystore (keystore/kqso.jks, gitignored, backup outside the repo) was created once with the command below — keep it stable across releases (otherwise updates fail on a signature mismatch). Locally the same values go into local.properties as signing.storeFile, signing.storePassword, signing.keyAlias, signing.keyPassword.

keytool -genkeypair -v -keystore keystore/kqso.jks -alias kqso \
  -keyalg RSA -keysize 4096 -validity 10000

License

GPL-3.0 — see LICENSE. Privacy policy: https://kqso.ok1cdj.com/privacy.html

The CW decoder builds on DeepCW and deepcw-engine by e04 (MIT; notice in web/src/core/cw/LICENSE-DeepCW.txt); the runtime is ONNX Runtime Web (MIT).

About

A ham radio logger with a single, smart input line. One line recognizes what you type — callsign, band/mode, report, serial, locator, award reference — so you can log a QSO with almost no taps. A web app first, wrapped in an Android WebView shell as an APK.

Resources

Stars

3 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages