Linux Client   BETA

1 – Download and Install the new DroidCam Client.

The Linux client is developed and built in an Ubuntu environment. An rpm package is provided on a best effort basis.
Only standard 64-bit (amd64/x86_x64) binaries are provided.
Flatpak  –   A Flatpak package is not yet available, but planned.

Debian/Ubuntu  –  droidcam_client_amd64.deb (50MB)

wget -O /tmp/droidcam_client_amd64.deb
sudo apt install -f /tmp/droidcam_client_amd64.deb

Fedora/RHEL  –  droidcam_client_amd64.rpm (50MB)

wget -O /tmp/droidcam-client.x86_64.rpm
sudo dnf install /tmp/droidcam-client.x86_64.rpm

If the client fails to launch, ensure you have the AppIndicator gnome shell extension installed, and enabled:
sudo dnf install gnome-shell-extension-appindicator gnome-extensions-app
Reboot, then use gnome-extensions-app to enable AppIndicator (tray icons).


You will need the v4l2loopback module for video sharing with other apps. This allows you to create "virtual video devices", which applications will detect as ordinary video devices. [1]

Debian / Ubuntu
sudo apt install linux-headers-$(uname -r) v4l2loopback-dkms

Fedora / RHEL
sudo dnf install$(rpm -E %fedora).noarch.rpm$(rpm -E %fedora).noarch.rpm
sudo dnf install kernel-headers v4l2loopback

Audio [+]

DroidCam can use the Linux ALSA Loopback soundcard for audio. However, there are many nuances with the audio layers on different Linux systems. It's recommended you use a regular microphone and keep droidcam for video only.

To load the ALSA Loopback card, use
sudo modprobe snd_aloop

To use the mic in PulseAudio you can either run
pacmd load-module module-alsa-source source_properties=device.description=DroidCam device=hw:Loopback,1,0 (you may need to adjust the last number; on some systems you need to do this after launching the droidcam client), or by editing /etc/pulse/ as described here.

If the Loopback card takes over your line out, you can set the default PulseAudio sink as shown here.

With Pipewire, open pavucontrol, Configuration tab. There are probably multiple devices called “Built-in Audio”, one of them is droidcam. Choose the profile Pro Audio, go to the Input Devices tab and check which meter reacts to the phone’s audio input (eg. Built-in Audio Pro 1), this is the desired audio input device. Inside pavucontrol you can now set this device as default input or choose it as the input device for individual apps etc.

2 – Launch the client from the Applications menu, and open the 'DroidCam OBS' app on your phone.

3 – In the computer client, click into the centre, or right-click and choose Add > DroidCam.

Make sure your phone is connected to the same network as your computer, and the DroidCam OBS app is open and ready.

The PC Client will search for and display available devices. Click [Refresh Device List] to try again. After 3 attempts, you will be presented with the option to add a device manually.
Ensure multicast is allowed on your Wifi, and try restarting your computer if auto-discovery is failing.

Tick "Enable Audio" box when adding a device to capture audio from the phone as well. Note that audio quality and latency may vary, and using Droidcam for video-only is recommended.

4 – Add your phone, and the DroidCam client will attempt to connect with the DroidCam app. Once active, you can then access the video feed in other programs via the v4l2oopback device (/dev/video[0-9]).

The logs at ~/.config/droidcam-obs-client/logs may help identify issues and the audio/video devices being used.

If you need further help or have any feedback, please contact or @dev47apps on Twitter.