WO Mic For Linux Use Your Phone as a Microphone

WO Mic can turn an Android phone or iPhone into a microphone for a compatible Linux computer. The legacy Linux client receives audio from the phone over Wi-Fi or Bluetooth and writes it to an ALSA loopback device that recording and communication applications can use as a microphone input.

Before downloading it, there is an important limitation to understand: WO Mic no longer officially supports Linux. The current official FAQ says Linux is no longer supported, while the developer’s older Linux page is still online and continues to link to the x86_64 AppImage and its original setup instructions.

This guide explains how to check your architecture, run the legacy AppImage, load the ALSA loopback module, connect by Wi-Fi or Bluetooth, test the microphone, and diagnose common audio-routing problems. The article is intentionally complete without screenshots.

Download FREE microphone for Linux

WO Mic for Linux: Quick Summary

Linux Support Table
Item Current Information
Official Linux support No longer supported
Available Linux file Legacy AppImage
File name micclient-x86_64.AppImage
Architecture x86_64 only
Linux connection methods Wi-Fi and Bluetooth
Linux USB support Not documented
Audio routing ALSA loopback using snd-aloop
Compatibility Not guaranteed on current systems

System Requirements and Compatibility For WO Mic On Linux

Before continuing, confirm that you have:

  • An x86_64 Linux system
  • The WO Mic mobile application installed on your phone
  • Wi-Fi access or Bluetooth pairing
  • Permission to load the snd-aloop kernel module
  • Support for running AppImage files

Check your computer’s architecture:

 

If the result is aarch64, arm64, i686 or another architecture, the legacy AppImage is not designed for that system.

 

The developer’s legacy page lists x86 64-bit architecture only. This does not guarantee that the AppImage will work on every modern x86_64 distribution. 

 

 

Is WO Mic Still Available for Linux?

Yes. At the time this guide was reviewed, the developer’s older Linux page still linked to the following file:

However, availability and official support are different. The file remaining online does not mean Linux is still an actively supported platform. The most accurate description is: an unsupported legacy Linux AppImage is still hosted on the developer’s older website.

Do not describe the file as community-maintained unless a reliable source identifies the project or community that maintains it. The official pages do not make that claim.

Where Should You Download the Linux AppImage?

Use the developer’s legacy Linux page rather than an unofficial download mirror or a repackaged file. This website does not develop or maintain the WO Mic Linux client and cannot provide official technical support for it.

Download FREE microphone for Linux

Before You Start

Make sure you have the following:

  • An x86_64 Linux computer.
  • The WO Mic mobile app installed on your phone.
  • A Wi-Fi connection, or Bluetooth when using a compatible Android phone.
  • Permission to load the snd-aloop kernel module.
  • A terminal application and permission to run the downloaded AppImage.

The legacy Linux page lists x86 64-bit architecture only. It does not provide a separate ARM, ARM64, or 32-bit Linux build.

Check Your Linux Architecture

Open a terminal and run:

The expected result is:

If the command returns aarch64, arm64, armv7l, i386, i686, or another architecture, the available legacy AppImage is not designed for that system.

Download and Install the WO Mic Linux Client

Download the file named micclient-x86_64.AppImage from the developer’s legacy Linux page. After the file downloads, open a terminal in the folder that contains it.

For example, when the file is in your Downloads folder, run:

Make the AppImage executable:

This command gives Linux permission to run the file as an application. You can check its permissions with:

Enable the ALSA Loopback Sound Module

The legacy Linux client writes the incoming phone audio to an ALSA loopback device. This device acts as a virtual sound card that other applications can use as a microphone source.

Load the loopback module:

Check whether the module loaded:

List the available recording devices:

Look for a card or device containing the name Loopback. The card and device numbers can differ between systems, so note the values displayed on your computer.

Connect Your Phone To Linux

The developer’s legacy Linux instructions document two connection methods: Wi-Fi and Bluetooth. USB is not documented for the Linux AppImage.

Option 1: Connect WO Mic Through Wi-Fi

Connect the phone and Linux computer to the same local Wi-Fi network. Open WO Mic on the phone, select Wi-Fi as the transport, start the server, and note the IP address displayed by the app.

From the folder containing the AppImage, run:

Replace 192.168.1.100 with the actual IP address displayed in the WO Mic mobile app. For example:

Keep the terminal window open while using the phone as a microphone. If the connection succeeds, the client should begin writing the incoming audio to the ALSA loopback device.

Option 2: Connect WO Mic Through Bluetooth

The legacy Linux page also includes a Bluetooth command. The current official transport table lists Bluetooth for the Android app but not for the iOS app, so iPhone users should use Wi-Fi.

Pair the Android phone with the Linux computer first. Then find the phone’s Bluetooth address. Its location varies by Android version and manufacturer, but the legacy instructions refer to Settings > About phone > Status > Bluetooth address.

Run:

Replace xx:xx:xx:xx:xx:xx with the phone’s actual Bluetooth address. For example:

If the connection fails, confirm that Bluetooth is enabled on both devices, the phone is paired, and the address is correct.

Test Your Phone Microphone

After connecting the client, record a short test file:

Speak into the phone for several seconds, then press Ctrl+C to stop the recording.

Play the same file:

If you hear your voice, the client and selected loopback device are working. The example uses 48,000 Hz, mono, and 16-bit audio, matching the audio format described by WO Mic.

What if the Recording Device Command Fails?

Run the following command again:

Check the card and device numbers assigned to the Loopback device. The example uses CARD=Loopback, DEV=1, and SUBDEV=0, but your system may assign different values. Adjust the device string according to the output shown on your computer.

Use WO Mic With OBS, Discord, Zoom, or Other Applications

After the terminal recording works, open the audio settings in the application where you want to use the phone. Look for an input source with a name such as Loopback, ALSA Loopback, or a Loopback monitor/source.

Select the appropriate loopback input and use the application’s microphone-test or recording feature. If the application was open before you loaded snd-aloop, close and reopen it because some applications scan for audio devices only when they start.

Troubleshooting WO Mic on Linux

Because Linux is no longer officially supported, the same setup may behave differently across current systems. Work through these checks in order.

The AppImage Does Not Open

Make sure the file is executable:

Confirm the architecture:

The result must be x86_64 for the available legacy build. If the terminal reports a missing library, mounting error, or AppImage compatibility problem, consult the documentation for your Linux distribution rather than installing random packages from unofficial sources.

The Loopback Device Does Not Appear

Load the module again:

Then check the module and recording devices:

If no Loopback device appears, the problem is related to the kernel module or audio configuration, not the phone’s IP address.

WO Mic Does Not Connect Over Wi-Fi

Check the following:

  • The phone and computer are connected to the same local network.
  • The IP address in the command matches the address displayed in the mobile app.
  • The WO Mic server is running on the phone.
  • A VPN is not interfering with local-network traffic.
  • The router is not using guest-network, client-isolation, or AP-isolation settings.
  • The firewall is not blocking the connection or incoming audio traffic.

The official WO Mic FAQ identifies firewall blocking as a possible cause of Wi-Fi audio connection problems.

The Client Connects, but There Is No Sound

First confirm that the Loopback device exists:

Then test it directly with the arecord command in the testing section. If terminal recording works but another application receives no audio, select the correct Loopback input in that application and restart the application after connecting WO Mic.

Audio Is Delayed, Interrupted, or Robotic

Try the following:

  • Keep the WO Mic mobile app active while testing.
  • Close applications using a large amount of CPU or network bandwidth.
  • Temporarily disable a VPN.
  • Move the phone and computer closer to the Wi-Fi router.
  • Restart the phone app and Linux client.
  • Test Bluetooth as an alternative when using Android.

Do not promise that Bluetooth will always be more stable. It is simply another connection method to test when Wi-Fi is unreliable.

Should You Run the WO Mic AppImage as Root?

Start the client normally:

The developer’s legacy page suggests trying the program as root when serious glitches occur:

However, sudo gives the AppImage broader system access. Treat this as a last troubleshooting step, not the normal launch method or a general performance recommendation.

Using WO Mic With PipeWire

The legacy WO Mic instructions are based on ALSA and the snd-aloop module. They do not provide a complete PipeWire-specific configuration. On a system that uses PipeWire, ALSA devices may be exposed through PipeWire and managed by a session manager such as WirePlumber, so device names and routing can differ.

First confirm that ALSA can see the loopback device:

Then inspect the devices and sources managed by WirePlumber:

The official WirePlumber documentation describes wpctl status as a command that displays the current PipeWire devices, sinks, sources, filters, and streams.

You can also inspect the PulseAudio-compatible server when the pactl command is available:

If Loopback Appears in arecord but Not in Your Application

  1. Close and reopen the application.
  2. Run wpctl status and look for a Loopback-related source or node.
  3. Check the application’s microphone-selection menu again.
  4. Log out and back in, or restart the user audio session using your distribution’s supported method.
  5. Consult the PipeWire or WirePlumber documentation for your distribution when routing still fails.

If Loopback Does Not Appear Anywhere

Reload the ALSA module and check both ALSA and PipeWire views:

Possible causes include a kernel-module problem, ALSA configuration, PipeWire routing, application input selection, permissions, AppImage compatibility, or limitations of the unsupported legacy client. Do not state that PipeWire is automatically the cause.

How WO Mic Works on Linux

The WO Mic mobile app captures audio from the phone microphone and sends it to the legacy Linux client through Wi-Fi or Bluetooth. The Linux client writes that audio to the ALSA loopback card created by snd-aloop. Recording, streaming, and communication applications can then select the loopback source as a microphone input.

The audio flow is:

Workflow Diagram
Phone Microphone
↓
WO Mic Mobile App
↓
Wi-Fi or Bluetooth
↓
Legacy Linux AppImage
↓
ALSA Loopback Device
↓
OBS, Discord, Zoom, or another application

Limitations of WO Mic on Linux

  • Linux is no longer officially supported.
  • The available AppImage is for x86_64 systems only.
  • No ARM, ARM64, or 32-bit Linux build is listed.
  • USB is not documented for the Linux AppImage.
  • The current transport table does not list Bluetooth for the iOS app.
  • Compatibility with current distributions, kernels, and audio configurations is not guaranteed.
  • PipeWire routing and device names can differ between systems.
  • Official Linux updates and technical support are not guaranteed.
  • Running the AppImage as root increases its system access.

These limitations do not mean the client will always fail. They mean users should treat it as older, unsupported software rather than a current Linux release.

What Can You Use if WO Mic Does Not Work?

If the legacy AppImage does not work after you verify the architecture, connection, loopback device, and application input, consider another phone-to-microphone application with current Linux support, a browser-based audio-streaming solution, a PipeWire-native network-audio setup, a standard USB microphone, or a wired headset with a built-in microphone.

Avoid adding specific alternative products to this article without current research and real testing. A separate alternatives guide is a better place for a properly verified comparison.

Frequently Asked Questions

Is WO Mic still officially supported on Linux?

No. The current official WO Mic FAQ says Linux is no longer supported. However, the developer’s older Linux page still links to a legacy x86_64 AppImage and setup instructions.

At the time this page was reviewed, the developer’s older Linux page still linked to micclient-x86_64.AppImage. The file remaining available does not mean it is actively maintained or officially supported.

The official pages do not identify it as community-maintained. Describe it as an unsupported legacy AppImage still hosted on the developer’s older Linux page.

The legacy client may work on a compatible x86_64 Ubuntu system, but compatibility is not guaranteed. Results can depend on the Ubuntu version, kernel, AppImage support, ALSA, and PipeWire configuration.

The AppImage may run on compatible x86_64 installations, but the developer no longer claims current Linux support. Do not assume that every 64-bit distribution or release will work.

The developer’s legacy page provides an x86_64 AppImage and does not list an ARM or ARM64 Linux build.

Wi-Fi is the relevant transport because the current WO Mic transport table lists Wi-Fi for iOS but does not list Bluetooth for iOS. Remember that the Linux client itself is unsupported.

The legacy Linux client includes a Bluetooth command. The current official transport table lists Bluetooth for Android but not for iOS.

USB is not documented on the legacy Linux page. Its Linux instructions cover Wi-Fi and Bluetooth only.

Load snd-aloop, run arecord -l, and confirm that a Loopback device appears. On PipeWire systems, also run wpctl status and select the appropriate Loopback source inside the application.

It may work with applications that can select the ALSA or PipeWire loopback source as a microphone input. The exact source name and routing depend on the system configuration.

Do not make an absolute safety guarantee. Use the developer’s legacy page rather than an unofficial mirror, and remember that the Linux client is no longer officially supported.