Another way to use Digital Radio Modes if you do not have an RF Radio = DroidStar on Linux Mint 22 (Wilma) (Part 2)

In November 2023 I described how to install DroidStar on you mobile phone (cellphone) to work digital radio modes.  Click HERE to read Part 1.

In Part 2 (this article) I will be looking at installing DroidStar on a PC running Linux Mint 22 (Wilna).

What is DroidStar?

DroidStar is an open-source digital voice client application for Android, iOS, Windows, and Linux that allows amateur radio operators to connect to various digital voice modes—including DMR, D-Star, Fusion (YSF/FCS), M17, P25, NXDN, and AllStarLink (IAX2)—directly from their device without needing a radio or hot spot. It connects to reflectors via IP and supports software vocoders. 

Key Features of DroidStar:

• No Radio Required: Enables access to digital networks directly from a smartphone or computer.
• Multi-Mode Support: Supports DMR, D-Star, C4FM (Fusion), M17, P25, and NXDN.
• AllStarLink: Functions as an IAX2 client to connect to AllStar nodes.
• Hardware Support: Compatible with AMBE USB devices (e.g., DVSI, DVstick 30) and MMDVM modems.
• Platforms: Available on the Google Play Store, iOS/Android, and via source code for desktop.

How it Works:

 
You do not need a hotspot for DroidStar to work, however you will have to sign-up for a DMR ID if you do not have one yet.  You will also have to register  with BrandMeister whose servers will enable you to link to different digital radio modes. 

 

Register HERE to obtain a DMR ID

Register HERE to gain access to BrandMeister

DroidStar Vocoder Plugins Downloads (Needed for audio and TX to work)

Setting up a BrandMeister Password  (Read more)

The above registrations need to be done before installing DroidStar.  Google is your friend here to assist you in getting registered.
 

DroidStar connects to M17, Fusion (YSF/FCS, DN and VW modes are supported), DMR, P25, NXDN, D-STAR (REF/XRF/DCS) reflectors and AllStar nodes (as an IAX2 client) over UDP. It is compatible with all of the AMBE USB devices out there (ThumbDV, DVstick 30, DVSI, etc). It also supports MMDVM modems and can be used as a hotspot, or as a stand-alone transceiver via direct mode to the MMDVM device. This software is open source and uses the cross platform C++ library called Qt. It will build and run on Linux, Windows, MacOS, Android, and iOS. 

 

Installing DroidStar on Linux Mint 22 (Wilna):

 

To install DroidStar on Linux Mint, the recommended method is using Flatpak via Flathub, as it manages dependencies easily. Alternatively, you can compile from source or use a pre-compiled binary if familiar with make. It requires a valid amateur radio callsign and DMR ID to operate. 

Preferred Method : Installing via Flatpak (Recommended)

    Open a terminal and run:
  
sudo flatpak install flathub io.github.nostar.DroidStar

 

You must ensure that the Vocoder Plugin  is installed.  For my system I installed the following Vocoder:

 

http://pizzanbeer.net/droidstar/plugins/vocoder_plugin.linux.arm64

 

How to install the Vocoder?

Open DroidStar by launching the application from the Menu - Sound and Video - DroidStar.  Once open go to Settings and scroll down to the Vocoder URL slot.  Copy the above pizzanbeer url link into the slot and click the Download vocoder button.  The vocoder will be downloaded.

Setup DroidStar for use:

With DroidStar still open go to the Main heading.  Select DMR, S2, CCo, BM_6551_South_Africa and TGID:  65522.  Now go to Settings.  Add your callsign, DMRID, ESSID = 01, BrandMeister Password and Location.  Scroll down to Update hosts and Update ID files by clicking on the TABS.  The log will show you the updates.  Leave other settings as is. (default)

We are nearly ready to use DroidStar.  If your Vocoder or Soundcard settings is not setup correctly Droidstar will crash (program close on  desktop)

 

Lets look at the audio setup of DroidStar:

 

Linux Mint 22 uses AlsaMixer for audio purposes. I use alsamixer for Qtel Echolink Client and it works fine.  However I found that DroidStar on my machine "preferred" PulseAudio.  I am sure that you can use Alsa instead but DroidStar keep on crashing if I tried to use it on my machine.  

 

Therefor I had to stop Alsa from directly controlling the audio hardware and force DroidStar to use PulseAudio.  

To stop ALSA and use PulseAudio in DroidStar on a Linux system, you need to ensure PulseAudio is running and properly configured to handle the audio routing, allowing it to act as the intermediate server between DroidStar and the underlying ALSA drivers.

 

Here are the steps to switch from ALSA to PulseAudio:

 

1. Ensure PulseAudio is Running 

 

If PulseAudio was disabled or replaced by ALSA, restart it:

Open a Terminal window and enter

sudo pulseaudio --start

2. Configure DroidStar for PulseAudio

• Open DroidStar.
• Go to the settings or audio configuration menu.
• Locate the input and output device settings.
• Select PulseAudio (or default) rather than selecting direct ALSA hardware devices (like hw:0,0).

3. Ensure PulseAudio Takes Control of ALSA 

 

If ALSA is grabbing the hardware exclusively, PulseAudio cannot function. To force PulseAudio to take control, you may need to prevent ALSA from autospawning, or kill existing ALSA processes if they are blocking it.

• Check/Kill PulseAudio: pulseaudio -k
• Restart PulseAudio: pulseaudio --start
• Ensure it's loaded: pactl info


Forcing DroidStar to use PulseAudio generally applies to running the application on Linux-based systems (like Raspberry Pi or desktop Linux) rather than Android, where DroidStar typically uses the native Android Audio HAL

.

On Linux, DroidStar is a Qt application and will default to PulseAudio if it is active on the system. If it is not defaulting to it, you can force it using environment variables.

 

Using

SDL_AUDIODRIVER=pulseaudio before launching DroidStar on Linux is a common workaround to force the application to use the PulseAudio sound server, which can resolve issues where the app fails to initialize audio or has no sound output. 

 

Run DroidStar from your terminal with the following command:

We are using the Flatpak version of DroidStar, you may need to use:


flatpak run --env=SDL_AUDIODRIVER=pulseaudio io.github.nostar.DroidStar

Why this is necessary:

• SDL2 Backend Selection: Modern SDL2 applications often need to explicitly be told to use pulseaudio rather than pulse (which is for older SDL1.2) to work correctly, particularly on newer Linux distributions.
• Fixing Audio Issues: If DroidStar shows it is receiving packets (RX) but you have no sound, or if it crashes on startup, it is likely unable to properly connect to your system's audio output.
• Vocoder Requirements: For modes like D-Star, DMR, and Fusion, DroidStar requires a vocoder plugin to function, which should be downloaded and configured in the settings tab.

Troubleshooting Audio Issues:

 

If DroidStar is connected but has no audio output, it might be using the wrong sound card.

• Use pavucontrol: Install and open pavucontrol (PulseAudio Volume Control) while DroidStar is running and connected. You can select the specific input/output device under the "Recording" or "Playback" tabs for the DroidStar app.
• Check Build Dependencies: Ensure your Linux system has the proper PulseAudio development libraries installed before compiling:

sudo apt install libpulse-dev

• ALSA still grabbing device: If PulseAudio isn't taking over, ensure that you do not have autospawn = no set in your /etc/pulse/client.conf.

cd /etc/pulse (enter)

sudo nano client.conf  (enter)

 

Move curser to autospawn =yes and ensure that it is set to yes.

 

Reboot your computer and start DroidStar.  You should be in business using DroidStar on DMR.

I currently use DroidStar to monitor my personal DMR Repeater TalkGroup 65522 which is permanently connected to AllStar and Echolink via the ZS1I DMR Bridge.  More information available HERE.

Finally:

DroidStar is a fun, free and easy way to experiment with the digital radio modes. If you have an Android, IOS or PC and have an interest in playing around with digital radio modes, then get going with DroidStar. 

That's it!  You can now use DroidStar on Linux Mint 22 (Wilna) to access DMR and the ZS Link Netwerk.

Enjoy!!

Images:  Click on images for larger view.

 

How to setup and run Qtel - the QT Echolink Client on Linux Mint 22 (Wilma)

More and more radio amateurs are moving away from the Windows OS and many are using Linux Mint.  I have successfully used Linux Mint for several years now on three different machines currently in the Shack with no major issues.  Now what is Linux Mint.  In short Linux Mint is a community-developed Linux distribution based on Ubuntu. First released in 2006, Linux Mint is often noted for its ease of use, out-of-the-box functionality, and appeal to desktop users. It comes bundled with a selection of free and open-source software.  I successfully run amateur radio software on the machines currently operational in the Shack.

I do have Echolink installed on a Windows machine but not on any of the Linux Mint machines.  Nowadays I am not a great fan of Echolink but must admit that it can come in handy at times. Having said that, AllStarLink is my preferred VOIP with far better audio quality than Echolink. I however decided to install the Qtel Echolink Client on Linux Mint 22 (Wilma) as a backup should the need arise.  I could have gone for the traditional Echolink install using WineHQ but was not in the mood to fiddle around with Wine at the time.

I had to fiddle around a bit with the settings of the computer's internal Soundcard and also opening the Router Ports but that you also do when setting up the Windows version of Echolink.  For those interested to run Echolink on Linux Mint here is how I setup the computer, software, hardware and Internet Router.

Qtel Echolink Setup:

Computer:  Dell Optiplex 990 (i5-2500S 64 Bit 8 Gig Ram)

Operating System:  Linux Mint 22 Wilma

Echolink Software: Qtel Echolink Client V1.2.4

Router:  Huawei B525 LTE

SoundCard:  Internal Souncard - HDA Intel PCH

 

Download and Installing Qtel in Linux Mint:

 

Go to Menu - Adminstration - Synaptic Package Manager - Open - Enter Password - Search - Qtel - Search.

Select Package - Qtel and Qtel-icons - Apply

Qtel will be installed as well as icons.

Reboot PC after installation.

 

Qtel Setup:

 

Go to Menu - Internet - Right click Qtel -Add Qtel to desktop - Click on Qtel Icon - Once open go to - Settings - Qtel Settings - User Info - Complete Info.

 

Callsign = ZS1I - L

Name = Johan

Password = XXXXX

Retype Password = XXXXX

Location: Mossel Bay

Network:

Servers: servers.echolink.org

Sound:

Microphone Audio Device = alsa:default

Speaker Audio Device = alsa:default

Sampling Rate = 48 000

Leave rest untouched - Default

Click OK

You should be ready now to open the ports for your router to work the outside world via Echolink.

Go to your Router: 

 

I use a Huawei B525 LTE Router

In you browser type in IP address of you router - 192.168.8.1

Login using username and password

Once logged in see images below for and indication of what needs to be changed in order to open the ports for Echolink.

 

 

Remember to reboot your router after you completed the setup.

You are now ready to use the Qtel Echolink Client.  We just need to setup the computer's Soundcard.

Optiplex 990 Soundcard Setup:

 

 

On the bottom right of your computer's screen, left click on  the speaker icon.  Window will open.  Click on sound settings. 

Ensure all slides are fully open

Leave other settings as default

Test sound - Click on Button and listen for audio.  If you hear audio on the left or right speaker your computer's soundcard is working.

Time to look at alsamixer:

Open Terminal

We use alsamixer - alsa sound control

Type alsamixer at the $ prompt

$ alsamixer  (enter)

Alsamixer V1.2.9 will open

Ensure that all sliders are set to maximum in the beginning.  Can always later re-set the sliders for good quality audio.

Card:  HDA Intel PCH

Chip:  Realtek ALC269VB

Select F6 - Sound Card - default:0

HDA Intel PCM - Select - Esc

NB - Ensure that Line Out is 00

NB - Ensure that Rear Mic is 00

I use the internal Soundcard of the Dell Optiplex 990 Computer

Qtel Echolink Client should now be working

Go back to Qtel

Go to Conferences and select *Echotest* 

Right click and select  "Add Selected to Bookmarks"

Echotest will be added to bookmarks and show on Qtel main screen.

Add your favorite stations as above

To connect double click on bookmark station or right click and connect to selected.

Echotest server will now be active once connected.

Congratulations Qtel Echolink Client is now working on Linux Mint.

Enjoy!!

NEW!! - "Saturday Afternoon Amateur Radio On-The-Air Activities from the Southern Cape Area"

Image:  "ZS1I Deep Space Communication Dream"  - In the world of amateur radio, ZS1I is a call sign uniquely assigned to a station in South Africa, specifically near the coastal town of Mossel Bay. By placing this identifier on the DSCA-9 Deep Space Array, we've transformed this futuristic hub into a massive, interplanetary "Ham Radio" station.  Imagine a future where local South African amateur radio operators aren't just bouncing signals off the Ionosphere, but are instead managing high-gain relays for explorers out past the Kuiper Belt.   (Click on image for larger view.)

Saturday afternoon is prime time for amateur radio, offering opportunities for many radio activities on and off the air.  For a while now myself and Curtis ZS6CMO get together on a Saturday afternoon at 15h00 to test and experiment using a wide variety of equipment in a variety of activities. 

Saturday afternoon amateur radio activities, particularly on the ZS Link Network in South Africa, offer a mix of adventures and relaxing experiences. I therefor decided to invite radio amateurs to join the "Saturday Afternoon Amateur Radio On-The-Air  Activities".  Please take note that this is not a structured / stereo type net or event.  It will therefor not be advertised or announced on a regular basis.  It will be a casual and informal event.  In the past it happened several times that there was no testing or experimenting or activities happening.  This is fine and the next Saturday afternoon activities were active again.

Based on recent activities, here are some top activities to fill your Saturday afternoon in future:

Activity list to be discussed on future Saturday afternoons:

•     Amateur Radio Call Signs
•     International Radio Alphabet
•     International Morse Code
•     Morse Code Battleships Game
•     Amateur Radio Q-codes
•     Amateur Radio RST-codes
•     Amateur Radio Abbreviations and Jargon
•     Coordinated Universal Time
•     Amateur Radio Bands
•     Amateur Radio Log Books
•     Amateur Radio Operating Procedures
•     Amateur Radio Operation
•     Amateur Radio HF Communications
•     Amateur Radio VHF/UHF Communications
•     Amateur Radio Repeater Communications
•     Amateur Radio VOIP Communications
•     Amateur Radio AllStar Communications
•     Amateur Radio MMDVM Communications 
•     Amateur Radio Satellite Communications
•     Amateur Radio SSTV Reception via ISS
•     Amateur Radio Direction Finding
•     Radio Frequency Interference Hunt
•     Emergency Radio Procedures
•     Electronic Components
•     Electronic Kit Construction
•     Electronics Lab
•     Microcontroller Lab
•     Solar Power Lab
•     Amateur Radio Antenna Construction
•     Amateur Radio Station Construction
•     Amateur Radio Digital Communications
•     Software Defined Radio
•     Amateur Radio Reboot Activities
•     Amateur Radio Echolink Communications
•     Amateur Radio Homebrew Construction
•     Amateur Radio Emergency Communications
•     Amateur Radio Contest Activities
•     Amateur Radio DX
•     Amateur Radio Innovation
•     Amateur Radio Red Tape and Regulatory Burdens
•     Amateur Radio Antenna Restrictions
•     Amateur Radio Spectrum Management
•     Amateur Radio Ethics
•     Amateur Radio News Bulletins
  

Please contact me to add your own activities to this page. Send a picture and description of your Amateur Radio activities.  Email - Click HERE

How do I connect to the ZS-Link Network to use the system / network?

• Echolink - Connect to ZS1I-R.  ZS1I-R is connected to the 49355 AllStar Hub that also host the ZS1I DMR Bridge/Repeater Network.
• AllStar - Connect to node 49355 ZS1I via AllStar.
• VHF Simplex - 145.550 Mhz Simplex in the Mossel Bay Area.  Remember the 88.5 khz CTCSS Tone.
• Aasvoëlkop Repeater - RF Frequencies = 145.625 Mhz RX, 145.025 Mhz TX 88.5 hz CTCSS
• Echolink Aasvoëlkop Repeater  = ZS1SB-L Node: 123760
  
• Any other Echolink, AllStar, Repeater or Linked station that is connected to the ZS1I-R or 49355 at the time you are connected. 

Finally: 

NEW!!  -  "Saturday Afternoon Amateur Radio On-The-Air  Activities from the Southern Cape Area"

DAY OF THE WEEK - Saturday Afternoons

TIME - 15h00 SAST

PLACE -  ZS Link Network

FORMAT - Not a structured / stereo type net or event.

NO-ACTIVITY - Some Saturday afternoons their might not be any activities.  Tune in again next Saturday.

IMPORTANT:  No recordings will be made for later listening.  Therefor do not miss an event!

 

Amateur Radio is not a Hobby; It is an Obsession!

 Image:  Amateur Radio Communication Innovation (Click on image for larger view.)

Nico ZS4N visit Mossel Bay for a well deserved Amateur Radio Holiday!!

The title of this article might seem odd to many radio amateurs but through the years when my brother in law, Nico ZS4N visit me we have a tradition which dates back to the early 90's.  We play amateur radio when we get together.  The XYL's and Juniors do their own thing but we play "Draadjie, Draadjie" as the XYL's call it when we get together.  This time it was no different.

Through the years we played radio from:

• Rhodes - Rally and Mountain Excursions
• Drakensberg Mountains - Daily Amateur Radio Excursions
• Barkley East - General Amateur Radio
  
• Aliwal North - General Amateur Radio
• Bloemfontein - SARL AGM, General Amateur Radio and Weather Chasing/Photography
  
• Mossel Bay - General Amateur Radio
• Buffalo Bay, Knysna - Amateur Radio Holiday Excursion
  
• De Rust - Mobile VHF Simplex Experimentation between Mossel Bay and De Rust
  

 Amateur Radio Activities during this latest visit:

• HF Mobile Operation - Screwdriver Antenna
  
• VHF / UHF Operation - Repeaters, Nodes and DMR Repeater
  
• 6m Experimentation with the newly constructed Delta Loop Antenna.  Thank you to Fred ZS5SAM/1 in Barrydale for making all the effort to assist with the experimentation using a 4 Element Yagi and 100 w on 6 Meters.
  
• Homebrew Construction - 49:1 Balun 100 watts - Constructed by Nico ZS4N.
  
• HF Rag Chewing - Yaesu FT450 and Yaesu FT817
  
• Erecting and setting up an HF  Field Station - Rally Trap Antenna / Linked Dipole for 20, 30, 40 and 80 Meters (Link Dipole = 20 + 30 Meters.  Rally Trap = 40 + 80 Meters)  Homebrew Traps using 25 mm PVC former and RG174.
  
• Check all antennas - prune and tune - when necessary - EFHW Dipole Antenna
  
• Playing with a variety of amateur radios, repeaters, nodes, links etc. - ZS Link Network
  
• Antenna Experimentation - EFHW + Delta Loop + Rally Trap + Linked Dipole - 5 to 100 Watt
  
• 6 Meter Beacon Demonstration - Southern Cape New Generation Beacons
  
• Looking into setting up a ProxMox Server - Amateur Radio Dell Server
  
• Traditional Family Braai to "celebrate" the "Draadjie, Draadjie DX-Pedition and Homebrew Indaba" - Family Gathering and Birthday Celebration
  
• Next "Play Amateur Radio" Event - Who knows with the new price of Petrol??
  

Thank you to all the radio amateurs who assisted with all the experiments and also to those who returned our CQ Calls.  Highly appreciated!!

To us amateur radio is not a Hobby but an Obsession when we get together.  Thank you Nico for visiting and for playing amateur radio in Mossel Bay.  We had a ball of a time and I trust that we will continue the "tradition" of "playing" radio every time we get together. 

Images:  Click on images for larger view.