Skip to content

Releases: myshak1/HamLogBridge

HAMLogBridge v1.0.2

Choose a tag to compare

@myshak1 myshak1 released this 11 Oct 13:35

The app is now called HAMLogBridge, with larger text, a new Events tab and a much clearer connection setup. Installs over v1.0.0 and v1.0.1 and keeps your log and settings.

What's new

  • New name. The app is HAMLogBridge everywhere: launcher, top bar, About, notification.
  • Larger text. Every text in the app is one step bigger. The decode table on Monitor now sizes its columns to the font, so nothing overlaps, also with Android's large-font setting, and the message column gets more room than before.
  • LogBook tab. The Log tab is now called LogBook.
  • New Events tab. The full event trace (packets received, rejected packets with their source, connection changes, logged QSOs) moved here from Monitor, with a Clear button. Monitor now has more room for decodes.
  • Clearer connection setup. Setup → Connection now shows:
    • what is connected, e.g. Connected to X6100 from 192.168.1.50, last packet 5s ago, or what the app is waiting for;
    • what each connection mode means;
    • for Wi-Fi, the exact address and port to enter in the radio;
    • for Bluetooth, a Choose radio button and a shortcut to Android's Bluetooth settings.
  • Correct phone address. The address shown in Setup and About is now the Wi-Fi or hotspot address, never the mobile-data one.
  • Rewritten README describing every feature and how it works.

Install

Download HAMLogBridge-v1.0.2.apk below and install it on Android 8.0 or newer. Keep battery optimization off for the app (Settings → Apps → HAMLogBridge → Battery → Unrestricted).

Known limitations

  • Uploaders are not yet tested against all live services. If an upload fails, tap the QSO in LogBook to see the server's reply.
  • No LoTW. Share the ADIF file and sign it with TQSL on a PC, or let Cloudlog/Wavelog sync with LoTW.
  • API keys and passwords are stored unencrypted in the app's private storage and are included in Android backups.
  • The local ADIF file is removed when the app is uninstalled. Share it first.

HamLog Bridge v1.0.1

Choose a tag to compare

@myshak1 myshak1 released this 11 Oct 11:52

Bug-fix release. Installs over v1.0.0 without uninstalling (same signing key).

Fixes

  • FREQ written with a comma on non-English phones. On e.g. a Polish-locale phone, QSOs from QSO Logged messages were sent as FREQ 14,074000, which loggers reject. Frequency is now always formatted with a dot.
  • QSOs with non-ASCII characters silently lost. The ADIF parser counted field lengths in characters instead of bytes, so a record like <NAME:7>Michał<CALL:6>DL1ABC lost its CALL and the QSO was dropped without a trace.
  • Richer Logged ADIF record sometimes discarded. Packets were processed in parallel, so type 12 could be handled before type 5 was stored and was then ignored as "already logged". Packets are now processed one at a time, in arrival order.
  • "Start with the phone" on Android 15. The service no longer uses the dataSync type, which Android 15 forbids to start at boot and limits to 6 hours a day. It now runs as connectedDevice only.
  • No more login storms with a wrong password. After a logger rejects a QSO (e.g. bad API key or password), the remaining queued QSOs for that logger are not sent in the same run, so 50 queued QSOs mean 1 failed login instead of 50. Fix the settings and tap "Retry". After a temporary error (no network, server down), the rest of the queue waits without using up retry attempts.
  • Log no longer at risk on future updates. Removed the database fallback that would have erased the QSO log and the upload queue on the first schema change.

Install

Download HamLogBridge-v1.0.1.apk below and install it on Android 8.0 (API 26) or newer. Keep battery optimization disabled for the app (Settings → Apps → HamLog Bridge → Battery → Unrestricted).

Known limitations

  • Debug-signed APK. A future release signed with a release key may require uninstalling first.
  • Uploaders are untested against live servers. If an upload fails, check the message in the Log screen.
  • No LoTW support. Export the ADIF file and sign it on a PC, or let Cloudlog sync with LoTW.
  • API keys and passwords are stored unencrypted in the app's private storage, and are included in Android backups.

HamLog Bridge v1.0.0

Choose a tag to compare

@myshak1 myshak1 released this 04 Oct 06:23

First public release of HamLog Bridge: an Android app that listens for WSJT-X UDP traffic (e.g. from a modified Xiegu X6100 with FT8 over WiFi, or WSJT-X/JTDX on a PC), records QSOs and forwards them to online logs.

Features

  • WSJT-X Message Protocol listener on UDP port 2237 (unicast, broadcast and optional multicast), running as a foreground service.
  • Tolerant decoder. It also handles simplified firmware that sends only some of the Status fields.
  • QSO logging from QSO Logged (type 5) and Logged ADIF (type 12), with deduplication by CALL | minute (UTC) | band.
  • Upload targets: Cloudlog / Wavelog, QRZ.com Logbook, Club Log, HRDLog.net, eQSL.cc and a generic webhook (ADIF or JSON).
  • Local ADIF file, always written.
  • Upload queue with retries. Temporary errors (no network, 5xx, 429) are retried with backoff. Permanent errors (bad key, 401/403) stop and wait for a manual "Retry".
  • UDP relay. Every received packet is forwarded byte for byte to GridTracker, Log4OM, N1MM etc. on a PC.
  • Monitor screen with live decodes and an Event trace of rejected packets for troubleshooting.

Install

Download HamLogBridge-v1.0.0.apk below and install it on Android 8.0 (API 26) or newer. You may need to allow installing apps from unknown sources.

After installing, disable battery optimization for the app (Settings → Apps → HamLog Bridge → Battery → Unrestricted). Otherwise some phones put the UDP socket to sleep.

Known limitations

  • Debug-signed APK. You may need to uninstall this version before installing a future release signed with a release key.
  • Uploaders are untested against live servers. Request formats follow each service's API documentation. If an upload fails, check the message shown in the Log screen.
  • No LoTW support. Uploading to LoTW requires signing with a TQSL certificate. Export the ADIF file and sign it on a PC instead, or let Cloudlog sync with LoTW.
  • API keys and passwords are stored unencrypted in the app's private storage.