Android Kloudlogger client app to connect to my Kloudlogger online logbook. Works with both smartphones and tablets. It will also work with Cloudlog!
I make programs for myself if nothing exists that i exactly want. If they turn out to be half decent, i will share them with the world.
I'm not a programmer! I just program for fun and to create something i need.
A full featured amateur radio QSO logging client for Kloudlogger/Cloudlog remote servers, with integrated DX cluster connectivity, QO-100 satellite finder, and real time server synchronisation.
- Fast entry — Callsign, frequency, mode, RST sent/received, and optional notes.
- Live sync — QSOs upload to your Kloudlogger/Cloudlog server automatically.
- Contest mode — Toggle to track serial numbers per contest.
- QRZ lookup — Fetch caller info from QRZ.com (API credentials required).
- Frequency and mode locking — Lock to a single frequency, mode, or both.
- Real-time sync — Upload QSOs to the server as you log them (User configurable delay).
- Server status — Connection indicator with activity LEDs for ping, uplink, and downlink.
- Public logbook — View your shared logbook via your Kloudlogger/Cloudlog public slug.
- Status monitoring — See sync status and server connectivity at a glance.
- Live spot stream — Persistent telnet connection to public DX clusters (DX Spider, AR-Cluster, etc).
- Band filtering — Filter spots by any amateur radio band from 2200m through 1mm wavelength.
- Spot posting — Post DX spots directly to the cluster with your callsign!
- AR camera mode — Live camera feed with augmented reality overlay.
- Precise look angles — Real time azimuth and elevation to QO-100.
- Sensor fusion — Accelerometer + magnetometer with aggressive low pass filtering for smooth tracking.
- Compass tape — Bearing scale across top of screen and elevation tape on right edge.
- Sun/Moon overlay — Displays the Sun and Moon at their current positions.
- Off-screen indicator — Arrow shows direction when satellite is behind you.
- Multi-orientation — Works in portrait and landscape and auto corrects for device rotation.
- Session view — Browse all logged QSOs in the current session.
- QSO detail — View and edit individual log entries.
- Daily stats — Live count of QSOs today and average rate per hour when 2 or more QSO's are made.
- Android: API level 24 (Android 7.0) or higher.
- Permissions: Internet (for connection to the remote Kloudlogger/Cloudlog server), GPS (for QO-100 satellite finder and fall back Maidenhead locator), Camera (for QO-100 AR mode).
- Server: Cloudlog or Kloudlogger instance (self hosted or cloud).
- Optional: QRZ.com account for caller lookup.
Simple! Download and run the APK from releases section.
- Open Settings → Server
- Enter your Hostname (e.g.,
kloudlogger.comore.g 192.168.0.2 if you are using internal LAN only) - Paste your API Key (from your Kloudlogger/Cloudlog server's user profile)
- Enter your Station ID (numeric, from your Kloudlogger/Cloudlog server setup)
- Enter your Public Logbook Slug (just the slug; if your public URL is
https://kloudlogger.com/visitor/MYLOG, enterMYLOG) - Choose HTTP or HTTPS If you have signed your own certificate using NGINX for example, then choose HTTPS. If you connect to your server only within your LAN locally, then choose HTTP. If you operate remotely and access your server via your public IP address, then select HTTP.
- Tap TEST SERVER CONNECTION to verify
- Open Settings → QRZ
- Enter your QRZ.com username and password
- Tap TEST QRZ CREDENTIALS
- Open Settings → DX Cluster
- Enter Host (default:
dxspider.co.uk) - Enter Port (default:
7300) - Enter Cluster Login (optional; uses your callsign if empty)
- Enter Password (optional; only needed if your cluster requires it)
- Tap TEST CLUSTER CONNECTION to verify
Popular open clusters:
- `dxspider.co.uk:7300 (DX Spider, callsign-only)
- `dxc.k0xm.com:7300' (DX Spider)
- `ve7cc.net:23' (VE7CC Cluster)
- `gb7djk.dxcluster.org:7300' (DX Spider)
- Open Settings → Station
- Enter your Callsign (used for QRZ lookup, cluster login, and satellite finder location fallback)
- Enter your Maidenhead Grid (e.g.,
IO91VH; used if GPS is unavailable or disabled)
- On the main screen, fill in:
- Callsign (required) — DX station you contacted
- Frequency (MHz) (required) — Operating frequency
- Mode (optional) — SSB, CW, FT8, etc. (locked or unlocked)
- RST Sent / Received (optional) — Reception reports
- Notes (optional) — Any comments
- Tap LOG QSO — the entry is saved locally and queued for upload to the Kloudlogger/Cloudlog remote server.
- Tap CLR to clear the form
- QSOs upload automatically on a schedule (default: every 30 seconds after a new entry)
- Watch the ↑ UP LED on the server status bar — it flashes when data is being sent
- Watch the ↓ DOWN LED — it flashes when the server responds
- If sync fails, check Settings → Server and tap TEST SERVER CONNECTION
The server status strip shows:
- ● (dot) — Connection state (green = connected, red = disconnected)
- Server status text — Current state and last message
- ● PING — Flashes every 60 seconds when the server is pinged
- ● ↑ — Flashes when the app sends data (QSO, cluster command)
- ● ↓ — Flashes when the server/cluster responds
- Tap DX Cluster from the menu
- Wait for the cluster to connect (watch the green dot)
- Spots from other operators appear live as they are posted
- Filter by band using the All bands dropdown
- To post your own spot:
- Enter the DX Callsign (the station you're spotting)
- Enter the MHz frequency
- Enter a Comment (optional, e.g., "CQ DX", "EU", "IOTA EU-005")
- Tap POST SPOT TO CLUSTER
- Watch for "✓ Spot for..." confirmation on success
- Tap QO-100 Finder from the menu
- Allow Camera and Location permissions
- Point your phone at the sky:
- Green ring = satellite is on-screen and on-target (within 5° of center)
- Red ring = satellite is on-screen but off-target
- Arrow off-screen = satellite is behind you or out of frame
- Compass tape (top) — magnetic bearing; cross-hairs = center of view
- Elevation tape (right) — altitude angle above horizon; +5° to +45°+
- Sun & Moon — shown as coloured overlays at their current positions
- Look angles (top of screen) — precise AZ/EL, range, and visibility status
- Rotate your phone to portrait or landscape — the overlay auto-corrects. It can take a few secconds to gain accuracy after doing this.
- Tap ⋮ (menu) → Server Logbook to view your shared public logbook (requires public slug in Settings)
- Tap ⋮ (menu) → Logbook to browse all QSOs logged in this session
- Check hostname: Ensure it's reachable and doesn't include
http://orhttps:// - Check API key: Copy it directly from your server's user profile, without extra spaces
- Test separately: Tap Settings → TEST SERVER CONNECTION to debug
- Firewall: If self-hosted, ensure the port (usually 80 or 443), or whatever port you have your Kloudlogger/Cloudlog instance running on is open and reachable through any firewalls and is reachable from outside of your network.
- Check cluster: Tap Settings → DX Cluster → TEST CLUSTER CONNECTION
- Common issue: Some clusters require a password — check with the cluster sysop
- Reconnect: On the DX Cluster page, tap RECONNECT
- Wrong cluster: Try
dxspider.co.uk:7300if yours is flaky
- Calibrate compass: Wave your phone in a figure-8 motion in the air (Android sensor calibration)
- Magnetic interference: Move away from metal objects (building, car, equipment)
- Fallback location: If GPS doesn't have a lock, the app uses the Maidenhead grid from Settings
- Check server: Tap Settings → TEST SERVER CONNECTION
- Check sync status: The server status text on the main screen shows the last sync result
- Network: Ensure you have internet connectivity (Wi-Fi or mobile data)
- Local queue: Tap the Logbook menu to see QSOs — they're stored locally even if sync fails. There is a coloured band to the left of each QSO. Red- not yet uploaded to the remote server, Amber in the process of being uploaded and green, the QSO has been successfully uploaded to the remote server.
- Language: Kotlin
- UI Framework: Android AppCompat + Material Design
- Database: SQLite (local QSO storage)
- Networking: OkHttp3 (Kloudlogger API), raw sockets (telnet for DX cluster)
- Sensors: Accelerometer + Magnetometer fusion (device orientation)
- Camera: Camera1 API (QO-100 finder AR overlay)
- DX Cluster: Persistent telnet connection with intelligent login/auth handling; regex parsing of DX Spider spot format
- Sensor Fusion: Low-pass filtered accelerometer + magnetometer; aggressive smoothing (alpha=0.04) for stable tracking
- Satellite Math: Precise look angle calculation for QO-100 at 25.9°E; 3D projection onto camera sensor plane
- Astronomy: Simplified Meeus algorithms for Sun and Moon positions (±0.5° accuracy)
| Permission | Purpose |
|---|---|
INTERNET |
Server sync, QRZ lookup, DX cluster telnet |
ACCESS_FINE_LOCATION |
GPS for QO-100 finder look angles |
ACCESS_COARSE_LOCATION |
Network-based location fallback |
CAMERA |
QO-100 AR overlay display |
ACCESS_NETWORK_STATE |
Monitor internet connectivity |
Chris M7JEX (Somerset, UK)
This software is provided 'as is' for the community. Please do not sell or modify this software.
- QRZBook: qrzbook.net
- Kloudlogger: kloudlogger.com
- Qrz: qrz.com
Q: Can I use this with Cloudlog?
A: Sure! Kloudlogger is Cloudlog compatible; my app works with both.
Q: Does the app work offline?
A: Partially. You can log QSOs offline and they're stored locally. Once you have internet, they'll sync to the server. DX cluster and QRZ lookup obviously require internet. Telepathy is not yet supported!
Q: Can I edit a QSO after logging?
A: Yes. Open the Logbook, tap a QSO, and tap the edit pencil icon.
Q: How often does the app sync to the server?
A: Default is 30 seconds after a new QSO. You can change this in Settings → Server → Auto-sync delay.
Q: The DX cluster keeps disconnecting.
A: Some clusters have time-outs or require periodic keep-alives. Try a different cluster from the suggestions in the settings, or check with your cluster sysop.
Q: QO-100 finder shows wrong angles.
A: Calibrate your phone's compass (figure-8 wave motion). Magnetic interference from nearby metal will throw it off. Make sure you've entered your location correctly in Settings.
Q: Can I post to multiple clusters?
A: Not simultaneously. The app connects to one cluster at a time, but you can manually switch clusters in Settings and reconnect.