I use the Droidcam software to use my android phone as a webcam. I have been using it in HD mode just fine for a few years now. However, for some reason, recently it’s stopped loading the module with the correct resolution parameters. It may or may not have coincided with one of their new releases. But I’ve uninstalled and downgraded to the previous version that was working and it still has the same problem (SD resolution).
I’ve reached out to the software developer, but it’s not obvious it’s anything to do with their code since even the previous version which was working fine is now no longer working. So I’m wondering if a recent OpenSuse update (usual Leap 15.5 update repos) has changed some way module parameters are loaded at boot.
If I remove the module and re-insert it manually using: sudo insmod /lib/modules/uname -r/kernel/drivers/media/video/v4l2loopback-dc.ko width=1920 height=1080 then it works OK again. Until reboot, when it returns to SD resolution.
Any suggestions for troubleshooting this further please?
I’m using this on Tumbleweed and haven’t found it to be an issue. Something that I would check is that v4l2loopback_dc is mapped to the correct /dev/video* device node. If v4l2loopback is loading, Droidcam can use that as well, and that will load at a lower resolution.
If you’re using the droidcam-cli program, try running it pointing to /dev/video1 instead of /dev/video0 (assuming /dev/video1 exists - you can ls /dev/video* to see if that’s the case.
It’s similar if you’re using the GUI application, but testing with the CLI might be simpler as a test.
As a workaround (though I’d like to try and solve it properly if possible), could I just call a script after boot to remove and re-insert the module? Where would be best to put that script? I tried putting something in /etc/X11/xinit/xinitrc.d/but it didn’t seem to work.
Ah! Running sudo dracut -f --regenerate-all has sorted it. Assuming that’s the right command, do you think I should run that every time I try and install a new version of droidcam?