Native AllStarLink Client for Android — v1.1
WT / App Authentication · Direct IAX2 / IAXRpt · Node Mode
Android 12+ · 64-bit ARM / arm64-v8a
⬇ Download the latest Android APK
View the latest release and release notes
Windows version: Microsoft Store
AllStar Transceiver v1.1 — Android main operating screen
AllStar Transceiver connects your Android phone to the AllStarLink amateur radio network. It includes Favorites, node/callsign lookup, Connected Nodes, PTT, VOX, audio controls, Activity messages, and background/screen-off session support.
Get the APK only from the official GitHub Releases page. Download AllStarTransceiver-Android.apk from the v1.1 release.
- Download the APK from the official release.
- Verify its SHA-256 using the Verify the APK SHA-256 instructions below. Compare it with the checksum published for that exact APK.
- Open the APK from Downloads. If asked, allow installation from your browser or file manager. Review any Play Protect warning before proceeding.
- Follow the installation prompts, then open AllStar Transceiver.
Already have an earlier APK (v1.0 or v1.1)? Install this APK over it — do not uninstall the existing app first. An uninstall can erase Favorites, settings, saved profiles, and AndroidKeyStore-protected remembered passwords. A normal update requires the same package identity and signing certificate.
The Android app is distributed through GitHub, not Google Play. A network connection and microphone permission are needed. Some networks restrict the UDP/IAX traffic used for AllStar connections.
| Mode | Identity | Password or secret |
|---|---|---|
| WT / AA | Your AllStarLink Portal callsign | Your AllStarLink website password |
| IAX2 | The destination node's authorized IAX username | That node's IAX secret |
| NM | Register As: an AllStar node you own | That node's AllStarLink Node Password |
The three passwords are different and are not interchangeable.
WT now uses AllStarLink App Authentication with your usual callsign and website password. A fresh, one-time-use token is requested for each connection. There is no separate AA password and no need to configure a Direct IAX login or Node Mode identity.
- Open Settings → Web Transceiver Account.
- Enter your callsign, website password, and matching password confirmation.
- Choose Remember Credentials if desired, then tap Save.
- On the main screen select WT, enter the Destination Node, and tap Connect.
AppAuth changes how WT authenticates, not how you talk to other nodes.
Use this when a node operator provides an IAX username and secret. An IAX login is associated with its specific destination node; you may save multiple profiles.
- Open Settings → Direct IAX2 / IAXRpt → Add Direct IAX Login.
- Enter the destination node, IAX username (often
iaxrpt), IAX secret, and matching confirmation. - Normally leave automatic AllStarLink IAX host/port lookup ON. It locates the appropriate host and UDP port, which might not be 4569.
- Only if required by the destination operator, turn off automatic lookup and enter a manual hostname/IP and UDP port. Called Context is normally blank; Called Extension can use
%NODE%for the destination node number. - Save the login and Settings. Choose IAX2 and the saved profile, then tap Connect.
Reset Defaults restores typical technical fields (username iaxrpt, automatic lookup on, host %NODE%.nodes.allstarlink.org, port 4569, blank context, extension %NODE%) without erasing your destination node or IAX secret. Removing a profile can leave Favorites that need editing.
Node Mode uses the identity of an AllStar node you own. It does not use your Portal password or an IAX secret.
- In Settings → Node Mode → Add Node, enter the owned node number and its AllStarLink Node Password, twice.
- Save the identity and Settings. You can save multiple owned-node identities.
- Select NM, choose Register As (your owned identity), enter the Destination Node, and tap Connect.
Register As and Destination Node are different: the destination must not equal the Register-As node. Avoid competing registrations of the same identity from multiple devices. Removing an owned identity may require updating related Favorites.
Select WT, IAX2, or NM; enter or choose the required node/profile; tap Connect. Watch the connection status and Activity panel for success or errors. Use Disconnect to end the session and unkey.
Settings: Save stores valid changes; Cancel or Android Back leaves unsaved edits behind. Password confirmation must match even if Remember Credentials is off.
- HOLD: press and hold PTT to transmit; release to unkey.
- TOGGLE: tap once to key and again to unkey.
- VOX: speech above the threshold keys automatically, with Attack and Hang timing and a Maximum Transmit safety limit.
If you tap manual PTT while VOX is active, the app unkeys, exits VOX, switches to TOGGLE, and remains unkeyed; the next tap keys normally. Always make sure PTT is unkeyed when finished. Disconnect or connection loss also releases transmit.
Adjust Receive Volume for incoming audio and Microphone Gain for transmitted audio. The Mic Level indication helps check microphone input.
VOX controls: Threshold (speech sensitivity), Attack (time before keying), Hang (time before unkeying), and Maximum Transmit (safety cutoff). VOX Reset Defaults: Threshold 8%, Attack 120 ms, Hang 700 ms, Maximum Transmit 180 seconds. Tap Save to keep reset values.
Audio Reset Defaults restores Receive Volume and Microphone Gain to 100%; it does not erase passwords, Favorites, or profiles.
Use a headset when possible to avoid received audio retriggering VOX.
Favorites store a destination plus its connection mode and, when needed, its IAX profile or Node Mode identity. The same node may appear in multiple Favorites for different modes. You can add a Favorite manually or from Connected Nodes, then connect, edit, remove, or open its callsign in QRZ.
Connected Nodes / Stations can expand to show linked nodes and stations. Node Lookup and Callsign Lookup help find destinations; a callsign may own more than one node. Check the selected node number before connecting or saving a Favorite.
The Activity view reports connection progress, errors, and radio/session events; consult it first when troubleshooting. Optional spoken disconnect notification can alert you when a session ends.
The Android app supports continuing an active connection in the background or with the screen off, subject to Android permissions and device power management. Moving between Wi-Fi and cellular can interrupt IAX/UDP connections; reconnect if needed. The app includes connection-loss and transmit-unkey safeguards.
SHA-256 verifies that your downloaded file matches the exact file published by the project. The 64-character APK checksum changes when a new APK is built or signed. It is not the same as the signing-certificate fingerprint.
On a Windows computer:
- Download the APK from the official GitHub release.
- Open File Explorer, navigate to the folder containing the downloaded APK (usually Downloads).
- Click the File Explorer address bar, type
powershell, and press Enter. This opens PowerShell in that folder. - Run this command for the v1.1 APK:
Get-FileHash .\AllStarTransceiver-Android.apk -Algorithm SHA256- Compare all 64 characters of the displayed hash with the v1.1 APK SHA-256 published on the GitHub release page. They must match exactly. If PowerShell cannot find the APK, check the folder and exact downloaded filename.
Official Android v1.1 APK SHA-256:
6846160F4952462DF6B061E8A1A205B7A66BF2ACB59B1D18D0D2611A14507FBC
If the values differ, do not install the file; download it again from the official release. The older v1.0 checksum does not verify v1.1.
Official Android production signing-certificate SHA-256:
66BE7641C9E9F5A0AE796BC25541E64BFBD43FBB4E5F23CEF4386ADF4A6DF1F0
This identifies the signing certificate, not the APK's file contents. That fingerprint stays the same across official updates even though each APK file has a different SHA-256.
| Problem | Check |
|---|---|
| WT / AppAuth login fails | Correct AllStarLink callsign and website password; check Activity and network access |
| IAX2 fails | Correct destination-specific IAX username/secret, profile, hostname/port and any required context/extension |
| NM fails | Owned Register As node, correct Node Password, and a different Destination Node |
| Password mismatch in Settings | Enter both password fields identically, regardless of Remember Credentials |
| No receive audio | Connection status, Receive Volume, phone audio route, and network |
| No or weak transmit audio | Microphone permission, PTT state, microphone gain, and input level |
| VOX keys unexpectedly | Raise threshold or use a headset to prevent speaker feedback |
| Connection drops during Wi-Fi/cellular change | Check Activity and reconnect |
| Favorite connects in wrong mode | Edit its saved WT/IAX2/NM mode and associated profile or identity |
If a problem persists, note the phone model, Android/app version, connection mode, Wi-Fi or cellular, and the relevant Activity message. Never share passwords, IAX secrets, or Node Passwords.
Favorites, profiles, mode choices, audio/VOX settings, and opted-in remembered credentials are held locally. Avoid posting screenshots or logs containing private information. Remembered passwords use protected local storage; uninstalling may erase data and stored credentials.
For support, contact KC3KMV on QRZ.