site  contact  subhomenews

DroidCam tested has some issues

April 30, 2022 — BarryK

I posted about DroidCam recently:

https://bkhome.org/news/202204/droidcam-and-deps-compiled-in-oe.html

DroidCam, the executable 'droidcam-cli', is included in Easy 3.4.7, so today have tested it.

I installed DroidCam on my phone, and when it starts, shows the port number, in this case "4747".

Connected through USB cable, with "USB debugging" enabled on the phone.

On the PC:

# modprobe v4l2loopback-dc
# LASTCARD=$(grep -o '^ [0-5] ' /proc/asound/cards | tail -n 1 | tr -d ' ')
# NEXTCARD=$((${LASTCARD}+1))
# modprobe snd-aloop index=${NEXTCARD}
# droidcam-cli adb 4747 -a -v
snd_pcm_open failed: Device or resource busy
Client v1.8.2
Video: /dev/video0
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
connecting to 127.0.0.1:4747

I then ran GUVCView, which is also in Easy, in the Multimedia menu. This accesses the webcam via /dev/video0, and it works, see the phone camera:

img1

Looks good, automatic focus and exposure work well. However, stuck on 640x480 at 25 - 30fps, cannot change that in GUVCView.

I updated to the paid version, DroidCamX, at AU$6.99, which is supposed to handle up to 1080p, but no difference, GUVCView only allows 640x480.

No audio either. DroidCam is ALSA-only, which is annoying, as it is causing that error at startup. I fiddled around, cannot get it to work. Will let it rest, try again tomorrow.

Tags: easy