The screen follows the task
Current action, wait reason, next event, radio readiness, and slot timing stay visible without exposing routine implementation detail.
The radio disappears. It is you and the messages.
CQFTx turns an Android phone or tablet and a QMX, QDX, IC-705, IC-7300, or IC-7300MK2 into a real digital station. Decoding, radio control, message timing, activity context, and logging live in one interface designed to feel obvious in the field.
Android 8+ · 3.6 MB · debug-signed field-test build · current operator guide included
The interface is built around the operator's intent: see the traffic, choose a station, understand the exchange, and keep the contact moving.
Current action, wait reason, next event, radio readiness, and slot timing stay visible without exposing routine implementation detail.
Once a QSO is intentionally started, CQFTx carries valid message transitions into the correct transmit windows automatically.
All traffic stays chronological while CQs, current-QSO traffic, replies to you, and relevant messages can be filtered without changing workflow state.
Reports, acknowledgements, retries, late replies, closeouts, and logging are tracked as one transaction instead of a string of hurried decisions.
Hunter and Activator share one QSO engine. CQFTx understands whether you called them or they called you, starts at the correct exchange step, and continues without asking for permission before every normal transmission.
A decoded CQ, a POTA/SOTA spot, or actionable directed traffic can become the contact.
The operator starts each CQ run. CQFTx listens for a valid directed response and works one caller cleanly.
The operating card separates what is happening, what comes next, and what could stop it. The operator should not have to infer state from a disabled button or remember which message was last sent.
The tools that support a portable contact are part of the station instead of separate browser tabs and utilities.
Start a park or summit session, keep progress visible, separate its log, and export contacts with the correct activity context.
See current activity for the selected band and mode, then bring a spotted station into the same decode-and-QSO workflow.
View reception context and a map when useful; optional decode reporting stays under operator control.
Rank audio offsets from recent waterfall occupancy and decoded signals, then let the operator choose rather than retuning silently.
Use the Android device's GPS for the synchronized clock and Maidenhead grid, with visible status and manual fallback when GPS is unavailable.
Normal contacts and each POTA/SOTA activity keep their own durable context, with correction, deletion, backup, and ADIF export tools.
CQFTx identifies the attached radio and uses a dedicated driver. It establishes the required digital operating state, verifies what that model can report, and avoids commands that belong to a different radio.
The deepest integration: USB audio and CAT, explicit radio-state setup, supported-band discovery, receiver-health checks, and transmit power/SWR monitoring with latched protection.
Deep integrationCore FT8/FT4 station integration through USB audio and CAT. CQFTx works within the QDX interface and does not pretend unavailable meter or receiver-health data exists.
Core integrationNative CI-V control over USB Serial Port A with USB audio, explicit data-mode setup, frequency and PTT verification, plus transmit power and SWR telemetry.
Native CI-V driverCI-V 94h control over USB virtual COM port A with USB audio, verified USB-D setup, frequency and PTT readback, plus transmit power and SWR telemetry.
Native CI-V 94h supportModel-specific CI-V B6 control over USB virtual COM port A, USB audio, verified USB-D setup, frequency and PTT readback, plus power and SWR telemetry. CQFTx also recognizes an MK2 configured for 94h compatibility.
Native B6h · 94h compatibilityDownload the current Android prerelease and verify it with the published checksum. Version 0.3.72 adds a GPS-ranked nearby-park chooser to POTA activation setup while preserving manual and multi-park entry, online reference validation, and explicit operator confirmation. It also moves POTA automatic spotting, restoration, successful-transmission arming, and QRT handling behind a dedicated activation controller. The complete workflow remains covered by host, simulator, native-audio, release, and Android-device tests.
SHA-256
b490e223eb8a6de54b4c97f809597ab992b30909ff4fc2f4fa2842a3877feb3b