Repository navigation
HamLog Bridge v1.0.1
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 Loggedmessages were sent asFREQ 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>DL1ABClost itsCALLand the QSO was dropped without a trace. - Richer
Logged ADIFrecord 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
dataSynctype, which Android 15 forbids to start at boot and limits to 6 hours a day. It now runs asconnectedDeviceonly. - 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.