Package Details: droidcam 1:1.8.2-1

Git Clone URL: (read-only, click to copy)
Package Base: droidcam
Description: A tool for using your android device as a wireless/usb webcam
Upstream URL:
Keywords: Android webcam
Licenses: GPL
Submitter: marquicus
Maintainer: CodeXYZ (LevitatingRein, lazerl0rd)
Last Packager: CodeXYZ
Votes: 124
Popularity: 2.84
First Submitted: 2011-06-29 20:31 (UTC)
Last Updated: 2022-02-22 20:02 (UTC)

Required by (0)

Sources (4)

Pinned Comments

Latest Comments

jkhsjdhjs commented on 2022-06-28 13:30 (UTC)

The Intel Indirect Branch Tracking (IBT) feature, available for 11th and higher gen Intel processors, has been enabled with Linux 5.18, causing the v4l2loopback_dc module to fail to load:

traps: Missing ENDBR: init_module+0x0/0x1000 [v4l2loopback_dc]

A workaround is of course disabling IBT by passing ibt=off as a kernel parameter. Link to upstream issue:

mmg commented on 2022-06-21 04:23 (UTC)

If v4l2loopback isn't found after a kernel update, reinstalling droidcam does not seem to work, but forcing yay -Syu v4l2loopback-dc-dkms with a clean build should do the trick.

ZappaBoy commented on 2022-02-24 10:36 (UTC)

@CodeXYZ I've been using it for 2-3 days now and it seems to work without problems.

CodeXYZ commented on 2022-02-22 20:03 (UTC) (edited on 2022-02-22 20:03 (UTC) by CodeXYZ)

Thank you @ZappaBoy that saved me so much time :)

[EDIT] BTW I didn't test this at all so make sure you lmk if it's working

ZappaBoy commented on 2022-02-22 12:19 (UTC) (edited on 2022-02-22 12:21 (UTC) by ZappaBoy)

I hope i'm doing it right. Updated to version 1.8.2; Moved from aramg/droidcam to dev47apps/droidcam

diff --git a/.SRCINFO b/.SRCINFO
index 578ea5f..2de4ab7 100644
--- a/.SRCINFO
+++ b/.SRCINFO
@@ -1,9 +1,9 @@
 pkgbase = droidcam
        pkgdesc = A tool for using your android device as a wireless/usb webcam
-       pkgver = 1.8.1
+       pkgver = 1.8.2
        pkgrel = 1
        epoch = 1
-       url =
+       url =
        arch = x86_64
        license = GPL
        makedepends = libappindicator-gtk3
@@ -13,11 +13,11 @@ pkgbase = droidcam
        source = droidcam.desktop
        source = dkms.conf
        source = droidcam.conf
-       source =
+       source =
        sha256sums = 90dd73cf146fae0de0c11b46e97412d2aaca50ec879e1be2d793261e853dd0d3
        sha256sums = 1e91f58ae83d433d32b483b14f1bb39cc245d2ace711b12c894de27dd2ea3413
        sha256sums = 1d4b3ff98b4af9de77a24d1b6fad6e004deadf1f157eb800aa878ba1e7693dac
-       sha256sums = SKIP
+       sha256sums = a5a5601efc60ae5e60e189f9ec8c73dab5579e6fdeebdcb9b809b6befb416ecc

 pkgname = droidcam
        depends = alsa-lib
diff --git a/PKGBUILD b/PKGBUILD
index a3aa4d6..bd399ed 100644
@@ -5,25 +5,25 @@

 pkgname=('droidcam' 'v4l2loopback-dc-dkms')
 pkgdesc='A tool for using your android device as a wireless/usb webcam'
 makedepends=('libappindicator-gtk3' 'gtk3' 'ffmpeg' 'libusbmuxd')

-        "${pkgbase}-${pkgver}.zip::${url}/archive/v${pkgver}.zip"
+        "${pkgbase}_${pkgver}.zip::${url}/archive/v${pkgver}.zip"

-            '79321e89f5514467c462bed574adb2434ebe758276d3203f69e8bdf176aab8cf')
+            'a5a5601efc60ae5e60e189f9ec8c73dab5579e6fdeebdcb9b809b6befb416ecc')

 prepare() {
   # Generate the module loading configuration files 

artemklevtsov commented on 2022-01-24 06:42 (UTC)

libappindicator-gtk3 now runtime dependency. Droidcam won't start without it.

srahman5317 commented on 2022-01-19 16:42 (UTC)

@CodeXYZ Working on my end. Thank you very much. Very much appreciate it

CodeXYZ commented on 2022-01-18 16:51 (UTC)

I cant test rn but let me know if its working!

srahman5317 commented on 2022-01-14 19:54 (UTC)

Apologies. Don't mean to rush you. Take your time. As long as there maintainers, I am happy and grateful. Life happens bud - get to it when you can.

CodeXYZ commented on 2022-01-13 16:06 (UTC)

Thank you for asking srahman5317 No, I've just been busy. I'll get this updated today asap!

srahman5317 commented on 2022-01-13 15:27 (UTC)

This package has been marked as out of date, and I believe there is a newer version of droidcam available. Is there an issue with the newer versions or is the issue with maintainence? Just asking.

nilsw commented on 2021-12-21 16:50 (UTC) (edited on 2021-12-21 16:52 (UTC) by nilsw)

@lazerl0rd why does your patch provide V4L2LOOPBACK-MODULE? I thought v4l2loopback-dmks is the one to provide it?

CodeXYZ commented on 2021-12-15 04:49 (UTC)

I'm not sure if you want to be co mantainer but since you added your name on that diff I'll add you as one anyway @lazerl0rd I'll update this package in the next coming days if I get time but do feel free to update it if you'd like :-)

lazerl0rd commented on 2021-11-26 21:02 (UTC)

Could you merge this patch, please? I've added two links just in case one fails.

Ammako commented on 2021-10-21 01:17 (UTC)

A user here is reporting that the loopback device is breaking pulseaudio for them

Just thought I would mention it

victorkur commented on 2021-10-01 22:59 (UTC)

@rachejazz I still got the same error. Don't know if this helpful but it worked flawlessly on a debian system I had used earlier.

CodeXYZ commented on 2021-09-16 14:43 (UTC)

Yeah I'm pretty confused about that. I'll see if I have time to work on this package this week. Let me know what else is wrong with it.

rachejazz commented on 2021-09-14 19:36 (UTC)

v4l2loopback was not loaded by default on my arch for some reason. I did have to install and load it manually. Otherwise, it gave this error:

Error: Droidcam/v4l2loopback device not found (/dev/video[0-9]).
Did it install correctly?
If you had a kernel update, you may need to re-install.
Audio loopback device not found.
Is snd_aloop loaded?
Client v1.8.0
adb: error: internal error
Error: Error adding adb forward!

Does anyone think keeping v4l2loopback as a necessary dep should be considered? I have read in the comments that v4l2loopback-dkms is optional. So why is droidcam installing it?

santilococo commented on 2021-09-08 00:40 (UTC)

@alerque Thank you very much!

alerque commented on 2021-08-10 16:01 (UTC)

@santilococo This package can be uninstalled using pacman just like any other package you install. It does not load the module, so however you loaded it on your system should be reversed by you. There are several potential ways that could happen. If you did nothing, then you don't have to do anything after installing. If you loaded it manually some way, reverse what you did.

santilococo commented on 2021-08-10 14:31 (UTC)

Hi! Do you have a script for uninstalling? (Unloading the loopback module for example). TY.

ChrisLane commented on 2021-08-05 10:14 (UTC)

As @simona has said, the dependency should be changed to v4l2loopback-dkms. Having a different module interfering with other applications for me.

CodeXYZ commented on 2021-07-31 23:52 (UTC)

Looks like it's still in /usr/bin @alerque Thanks for the tip though :-)

alerque commented on 2021-07-30 12:52 (UTC)

When you update to 1.8.0 be sure to configure the PREFIX, upstream changed the default to be /usr/local but for packages this should be /usr.

CodeXYZ commented on 2021-07-13 02:25 (UTC)

It's been so long and I'm so rusty. Had to learn all the basics again ha! Should be good now let me know otherwise.

modnoob commented on 2021-07-09 13:15 (UTC)

As lots of people here already mentioned libappindicator-gtk3 should be part of the required dependency. The build fails without it. Please commit a change for that.

simona commented on 2021-06-05 15:25 (UTC)

The client works with the standard v4l2loopback module, and installing v4l2loopback-dc is optional. Standard v4l2loopback usage examples. The standard v4l2loopback module is already available on most distros. Better change deps to v4l2loopback* ?

simona commented on 2021-06-05 15:11 (UTC)

droidcam is ok also with v4l2loopback-dkms (community) instead v4l2loopback-dc-dkms ?

insign commented on 2021-05-21 18:10 (UTC)

Easy fix for manjaro.

CodeXYZ commented on 2021-05-12 20:49 (UTC)

Sorry, I haven't had a working laptop for a bit now, so even though I can probably update and fix the package, I don't have a reliable was to build and test it at the moment. I am reading the comments here about it though.

invidian commented on 2021-05-12 09:09 (UTC)

Hmm, perhaps splitting out one more package, namely "droidcam-cli" would be a way to go here then. So "droidcam" can depend on all GUI-related libraries. This will still allow people to install CLI-only version. What do you think?

julio.b commented on 2021-05-11 19:02 (UTC)

I agree with @s1lv3r this package fails without libappindicator-gtk3.

s1lv3r commented on 2021-05-05 14:51 (UTC) (edited on 2021-05-05 14:56 (UTC) by s1lv3r)

I believe libappindicator-gtk3 should be added to the required deps instead of the optional deps

JLSalvador commented on 2021-05-04 09:01 (UTC)

This new version requires app-indicator.h from the package libappindicator-gtk3.

aleemont commented on 2021-03-19 23:18 (UTC)

The only way to make droidcam work at first shot and without need to worry about anything is this: Follow instructions and it'll take less than one minute (download included)

invidian commented on 2021-03-14 21:26 (UTC)

I believe linux-headers should be added as dependency.

@lorcap see why headers should not be in dependencies.

==> WARNING: backup entry file not in package : etc/modprobe.d/droidcam.conf

This seems indeed like a bug. This file should only be backed up for v4l2loopback-dc-dkms package, not for both of them.

lorcap commented on 2021-03-14 21:12 (UTC)

I believe linux-headers should be added as dependency.

It took me a while to figure out why droidcam complained about a missing kernel module despite the package compilation and installation succeeded. Then I reinstalled the package and noticed the following error:

==> Unable to install module v4l2loopback-dc/1.7.2 for kernel *: Missing kernel headers.

which I fixed by installing linux-headers.

lorcap commented on 2021-03-14 21:06 (UTC) (edited on 2021-03-14 21:07 (UTC) by lorcap)

When running makepkg, I get the following warning:

==> Checking for packaging issues...
==> WARNING: backup entry file not in package : etc/modprobe.d/droidcam.conf

cheru commented on 2021-02-24 02:33 (UTC) (edited on 2021-02-24 02:35 (UTC) by cheru)

Could you add v4l2loopback-dkms as an alternative dependency to v4l2loopback-dc-dkms, since either of those packages will do the job?

patchcard2 commented on 2021-01-23 12:57 (UTC)

@invidian Yes that seems to be the cause for my problem. Removing it via modprobe -r snd-aloop brings my internal soundcard back. For now I decided to just remove snd-aloop from /etc/modules-load.d/droidcam.conf and try to use my internal microphone instead of the one of my smartphone.

invidian commented on 2021-01-20 17:09 (UTC)

@patchcard2 perhaps this is because we load snd-aloop kernel module?

patchcard2 commented on 2021-01-20 17:01 (UTC)

For some reason, after installing this package ALSA did not recognize my internal soundcard anymore: snd_hda_intel 0000:00:1b.0: cannot find the slot for index 0 (range 0-1), error: -1

invidian commented on 2021-01-14 17:02 (UTC)

@maximbaz thanks for explanation! I replaced ../.. with ${srcdir} then.

maximbaz commented on 2021-01-14 16:37 (UTC)

@invidian: it fails as hexhu describes when you build in isolated environment in chroot, e.g. install devtools package and run extra-x86_64-build.

I would suggest avoid using relative paths and just use ${srcdir} in place of ../../

invidian commented on 2021-01-14 16:31 (UTC)

@biker The link is correct. We build multiple packages using single repository, as the source of both packages is the same.

invidian commented on 2021-01-14 16:31 (UTC)

@gbc921 did you try loading v4l2loopback or v4l2loopback-dc kernel module? Because the former is indeed provided by "v4l2loopback-dkms" package and the latter is provided by "v4l2loopback-dc-dkms".

invidian commented on 2021-01-14 16:29 (UTC)

@hexhu I've tried building the package in Arch Linux Docker image (Dockerfile in this package repository) and things work just fine. How do you invoke package building so you hit this issue?

hexhu commented on 2021-01-14 08:48 (UTC)


==> Starting package_droidcam()...
/dev/shm/makepkg/droidcam/src/droidcam-1.7 /dev/shm/makepkg/droidcam/src
install: cannot stat '../../droidcam.desktop': No such file or directory
==> ERROR: A failure occurred in package_droidcam().

for 1:1.7-1.

Please change line 55-56 of PKGBUILD to

  install -Dm644 "../${pkgbase}.desktop" "$pkgdir/usr/share/applications/${pkgbase}.desktop"
  install -Dm644 "../${pkgbase}.conf" "${pkgdir}/etc/modules-load.d/${pkgbase}.conf"

as a fix.

Also v1.7.1 has just been released, which dropped 'appindicator' (systray icon) support.

gbc921 commented on 2021-01-11 00:17 (UTC)

On my system I had to install v4l2loopback-dkms as well to be able to load the module. Not sure it is due to using linux-lts.

Is this true for anybody else?

biker commented on 2021-01-01 15:17 (UTC)

Would expect "Git Clone URL" linking to " instead of ""!?

Vertolet commented on 2020-12-15 13:13 (UTC)

For Manjaro users and anyone else having issues:

invidian commented on 2020-12-13 11:21 (UTC)

Hey @madskjeldgaard. libappindicator is marked as optional, as you may run Droidcam from CLI only. Maybe it would make sense to create a droidcam-cli or droidcam-gtk packages...

madskjeldgaard commented on 2020-12-13 10:09 (UTC)

should libappindicator be a non-optional dependency? I tried running without it and got errors so I think it is required.


cyberpunkrocker commented on 2020-12-05 10:38 (UTC)

Why droidcam-icon.png is installed in /opt ?

tioguda commented on 2020-11-08 14:27 (UTC)

I tested with v4l2loopback-dkms on my Manjaro (yes, I read the pinned comment) and I needed to change three things, remove videodev in /etc/modules-load.d/droidcam.conf, leave only v4l2loopback in place of v4l2loopback-dc (that was obvious).

The third modification is to add /etc/modprobe.d/droidcam.conf to the droidcam package, the program works without this change, but the user cannot change the resolution.

Without the above changes my system has errors to start, I'm not complaining, I'm just passing on the information, maybe it can be useful.


invidian commented on 2020-11-06 10:17 (UTC)

With 1.6 supporting both, I think it would be preferable to drop the goofy custom loopback module and just depend on the regular v4l2loopback module / package.

I updated to 1.6, but didn't add v4l2loopback support yet, as I'm not sure how to handle it yet and we discuss it with other maintainers.

In the meanwile, one can manually install v4l2loopback-dkms package, unload v4l2lookback-dc module and load v4l2loopback to try it out.

alerque commented on 2020-11-05 07:37 (UTC)

With 1.6 supporting both, I think it would be preferable to drop the goofy custom loopback module and just depend on the regular v4l2loopback module / package.

ngoonee commented on 2020-10-15 09:16 (UTC)

Could you add snd-aloop to droidcam.conf so sound works a bit more OOTB?

invidian commented on 2020-10-07 20:58 (UTC)

@fourier No, as stated in

fourier commented on 2020-10-07 20:56 (UTC)

@invidian thanks, that's what I did. But shouldn't the headers be installed as a dependency?

invidian commented on 2020-10-07 19:52 (UTC)

@fourier you must install kernel headers for the kernel you have installed in order to use DKMS, for example "linux-headers" if you use "linux" package for your kernel. See for more details.

fourier commented on 2020-10-07 19:43 (UTC)

Tried to install, but failed with

==> Unable to install module v4l2loopback-dc/1.5 for kernel *: Missing kernel headers.

invidian commented on 2020-10-01 21:55 (UTC) hmm, I don't know what could be the cause then. This repo contains a Dockerfile which I use to test builds on fresh machines, to make sure all dependencies are included. Maybe try manually cloning the repository and building from there? commented on 2020-10-01 15:48 (UTC)


I have the latest available version installed:

$ yay -Qi libjpeg-turbo | grep Version
Version         : 2.0.5-2

invidian commented on 2020-10-01 10:26 (UTC) maybe you have outdated version of "libjpeg-turbo"? It seems compiler picks the version, which do not have "tjGetErrorStr2" defined, which has been added in 1.5.3+: commented on 2020-10-01 06:47 (UTC) (edited on 2020-10-01 06:48 (UTC) by

Building droidcam fails on my machine:

==> Starting build()...
g++ -std=c++11 -x c++ -Wall -fPIC -no-pie src/droidcam-cli.c src/connection.c src/settings.c src/decoder.c src/decoder_snd.c src/decoder_v4l2.c src/av.c src/usb.c -lturbojpeg `pkg-config --libs --cflags libswscale libavutil` -lspeex -lasound -lpthread -lm -lusbmuxd-2.0 -o droidcam-cli
g++ -std=c++11 -x c++ -Wall -fPIC -no-pie src/droidcam.c src/resources.c src/connection.c src/settings.c src/decoder.c src/decoder_snd.c src/decoder_v4l2.c src/av.c src/usb.c `pkg-config --libs --cflags gtk+-3.0` `pkg-config --libs x11` `pkg-config --cflags --libs appindicator3-0.1` -lturbojpeg `pkg-config --libs --cflags libswscale libavutil` -lspeex -lasound -lpthread -lm -lusbmuxd-2.0 -o droidcam
src/droidcam.c: In function ‘void the_callback(GtkWidget*, gpointer)’:
src/droidcam.c:227:63: warning: ‘void gtk_menu_popup(GtkMenu*, GtkWidget*, GtkWidget*, GtkMenuPositionFunc, gpointer, guint, guint32)’ is deprecated: Use '(gtk_menu_popup_at_widget, gtk_menu_popup_at_pointer, gtk_menu_popup_at_rect)' instead [-Wdeprecated-declarations]
  227 |    gtk_menu_popup(GTK_MENU(menu), NULL, NULL, NULL, NULL, 0, 0);
      |                                                               ^
In file included from /usr/include/gtk-3.0/gtk/gtklabel.h:34,
                 from /usr/include/gtk-3.0/gtk/gtkaccellabel.h:35,
                 from /usr/include/gtk-3.0/gtk/gtk.h:33,
                 from src/droidcam.c:11:
/usr/include/gtk-3.0/gtk/gtkmenu.h:138:9: note: declared here
  138 | void    gtk_menu_popup    (GtkMenu        *menu,
      |         ^~~~~~~~~~~~~~
src/decoder.c: In function ‘int decoder_init()’:
src/decoder.c:111:37: error: ‘TJXOPT_COPYNONE’ was not declared in this scope; did you mean ‘TJXOP_NONE’?
  111 |     jpg_decoder.transform.options = TJXOPT_COPYNONE | TJXOPT_TRIM;
      |                                     ^~~~~~~~~~~~~~~
      |                                     TJXOP_NONE
In file included from src/decoder.c:19:
src/decoder.c: In function ‘void process_frame(JPGFrame*)’:
src/decoder.c:279:61: error: ‘tjGetErrorCode’ was not declared in this scope; did you mean ‘tjGetErrorStr’?
  279 |             errprint("tjDecompressHeader3() failure: %d\n", tjGetErrorCode(;
      |                                                             ^~~~~~~~~~~~~~
src/common.h:40:39: note: in definition of macro ‘errprint’
   40 | #define errprint(...) fprintf(stderr, __VA_ARGS__)
      |                                       ^~~~~~~~~~~
src/decoder.c:280:30: error: ‘tjGetErrorStr2’ was not declared in this scope; did you mean ‘tjGetErrorStr’?
  280 |             errprint("%s\n", tjGetErrorStr2(;
      |                              ^~~~~~~~~~~~~~
src/common.h:40:39: note: in definition of macro ‘errprint’
   40 | #define errprint(...) fprintf(stderr, __VA_ARGS__)
      |                                       ^~~~~~~~~~~
src/decoder.c:311:54: error: ‘tjGetErrorCode’ was not declared in this scope; did you mean ‘tjGetErrorStr’?
  311 |         errprint("tjDecompressToYUV2 failure: %d\n", tjGetErrorCode(;
      |                                                      ^~~~~~~~~~~~~~
src/common.h:40:39: note: in definition of macro ‘errprint’
   40 | #define errprint(...) fprintf(stderr, __VA_ARGS__)
      |                                       ^~~~~~~~~~~
make: *** [Makefile:39: droidcam-cli] Error 1
make: *** Waiting for unfinished jobs....
src/decoder.c: In function ‘int decoder_init()’:
src/decoder.c:111:37: error: ‘TJXOPT_COPYNONE’ was not declared in this scope; did you mean ‘TJXOP_NONE’?
  111 |     jpg_decoder.transform.options = TJXOPT_COPYNONE | TJXOPT_TRIM;
      |                                     ^~~~~~~~~~~~~~~
      |                                     TJXOP_NONE
In file included from src/decoder.c:19:
src/decoder.c: In function ‘void process_frame(JPGFrame*)’:
src/decoder.c:279:61: error: ‘tjGetErrorCode’ was not declared in this scope; did you mean ‘tjGetErrorStr’?
  279 |             errprint("tjDecompressHeader3() failure: %d\n", tjGetErrorCode(;
      |                                                             ^~~~~~~~~~~~~~
src/common.h:40:39: note: in definition of macro ‘errprint’
   40 | #define errprint(...) fprintf(stderr, __VA_ARGS__)
      |                                       ^~~~~~~~~~~
src/decoder.c:280:30: error: ‘tjGetErrorStr2’ was not declared in this scope; did you mean ‘tjGetErrorStr’?
  280 |             errprint("%s\n", tjGetErrorStr2(;
      |                              ^~~~~~~~~~~~~~
src/common.h:40:39: note: in definition of macro ‘errprint’
   40 | #define errprint(...) fprintf(stderr, __VA_ARGS__)
      |                                       ^~~~~~~~~~~
src/decoder.c:311:54: error: ‘tjGetErrorCode’ was not declared in this scope; did you mean ‘tjGetErrorStr’?
  311 |         errprint("tjDecompressToYUV2 failure: %d\n", tjGetErrorCode(;
      |                                                      ^~~~~~~~~~~~~~
src/common.h:40:39: note: in definition of macro ‘errprint’
   40 | #define errprint(...) fprintf(stderr, __VA_ARGS__)
      |                                       ^~~~~~~~~~~
make: *** [Makefile:42: droidcam] Error 1
==> ERROR: A failure occurred in build().
error making: droidcam (v4l2loopback-dc-dkms)

invidian commented on 2020-09-30 08:17 (UTC)

@pickfire thanks for noticing, you are right. I added "libappindicator-gtk3" as optional dependency now, as we do the same with "gtk3", given that "droidcam-cli" works without both of those packages.

I wonder, perhaps this optional dependencies should be dropped and just added as regular dependencies.

pickfire commented on 2020-09-30 03:15 (UTC) (edited on 2020-09-30 03:15 (UTC) by pickfire)

libappindicator-gtk3 is a dependency, not just make dependency. Otherwise, droidcam

droidcam: error while loading shared libraries: cannot open shared object file: No such file or directory

invidian commented on 2020-09-19 12:35 (UTC)

jonseitz I suspect that happens, because you have "." in your PATH, so local "install" script takes precedence over "global" "install" binary. I'll fix that, it seems like a reasonable case.

jonseitz commented on 2020-09-19 01:26 (UTC)

Ran into an issue installing just now, getting the following error:

==> Starting package_droidcam()...
~/builds/droidcam/src/droidcam-1.3/linux ~/builds/droidcam/src
Invalid parameters: '-Dm755' and 'droidcam'
==> ERROR: A failure occurred in package_droidcam().

It seems that the issue is that the calls to install ... in the package scripts were referencing the install script in src/droidcam-1.4/linux/, instead of /sbin/install. I was able to get it working by changing the PKGBUILD to:

diff --git a/PKGBUILD b/PKGBUILD
index 5dd52df..61cf9d4 100644
@@ -54,12 +54,12 @@ package_droidcam() {
   pushd ${pkgbase}-${pkgver}/linux

   # Install droidcam program files
-  install -Dm755 "${pkgbase}" "$pkgdir/usr/bin/${pkgbase}"
-  install -Dm755 "${pkgbase}-cli" "$pkgdir/usr/bin/${pkgbase}-cli"
-  install -Dm644 icon2.png "$pkgdir/usr/share/pixmaps/${pkgbase}.png"
-  install -Dm644 "../../${pkgbase}.desktop" "$pkgdir/usr/share/applications/${pkgbase}.desktop"
-  install -Dm644 "../../${pkgbase}.conf" "${pkgdir}/etc/modules-load.d/${pkgbase}.conf"
-  install -Dm644 "$pkgdir/usr/share/licenses/${pkgbase}/LICENSE"
+  /sbin/install -Dm755 "${pkgbase}" "$pkgdir/usr/bin/${pkgbase}"
+  /sbin/install -Dm755 "${pkgbase}-cli" "$pkgdir/usr/bin/${pkgbase}-cli"
+  /sbin/install -Dm644 icon2.png "$pkgdir/usr/share/pixmaps/${pkgbase}.png"
+  /sbin/install -Dm644 "../../${pkgbase}.desktop" "$pkgdir/usr/share/applications/${pkgbase}.desktop"
+  /sbin/install -Dm644 "../../${pkgbase}.conf" "${pkgdir}/etc/modules-load.d/${pkgbase}.conf"
+  /sbin/install -Dm644 "$pkgdir/usr/share/licenses/${pkgbase}/LICENSE"

 package_v4l2loopback-dc-dkms() {
@@ -68,22 +68,22 @@ package_v4l2loopback-dc-dkms() {
   local install_dir="${pkgdir}/usr/src/${_pkgname}-${pkgver}"

   # Copy dkms.conf
-  install -Dm644 dkms.conf "${install_dir}/dkms.conf"
+  /sbin/install -Dm644 dkms.conf "${install_dir}/dkms.conf"

   # Set name and version
   sed -e "s/@_PKGNAME@/${_pkgname}/" -e "s/@PKGVER@/${pkgver}/" -i "${install_dir}/dkms.conf"

   # Install module loading configuration
-  install -Dm644 "${pkgbase}.modprobe.conf" "$pkgdir/etc/modprobe.d/${pkgbase}.conf"
+  /sbin/install -Dm644 "${pkgbase}.modprobe.conf" "$pkgdir/etc/modprobe.d/${pkgbase}.conf"

   # Install module source
   cd ${pkgbase}-${pkgver}/linux/v4l2loopback

   for d in $(find . -type d); do
-    install -dm755 "${install_dir}/$d"
+    /sbin/install -dm755 "${install_dir}/$d"

   for f in $(find . -type f ! -name '.gitignore'); do
-    install -m644 "$f" "${install_dir}/$f"
+    /sbin/install -m644 "$f" "${install_dir}/$f"

Possibly it's something specific to my system, but dropping this here in case anyone runs into the same.

Amirmohammad commented on 2020-07-13 20:02 (UTC) (edited on 2020-12-14 18:15 (UTC) by Amirmohammad)

first, I wanted to thank the maintainers. Secondly, there is an easy fix for manjaro users. You just need to install kernel headers specific to your kernel version. So after installing linuxXX-headers, reboot and then install droidcam.I've tested it and it works perfectly fine. Best of luck!

acutbal commented on 2020-07-09 10:19 (UTC) (edited on 2020-07-09 10:22 (UTC) by acutbal)

@LenLord That's the problem, I've already did this before to try the installation of DroidCam: [albert@ThinkPad ~]$ sudo ln -s /usr/lib/ /usr/lib/libusbmuxd-2.0

And the build still the crashes...

UPDATE: I've found the issue, it missed the .so in libusbmuxd-2.0

Regards and thank you very much!!

LendLord commented on 2020-07-09 10:03 (UTC) (edited on 2020-07-09 10:03 (UTC) by LendLord)

@acutbal As I wrote early to link you need to specify location where is libusbmuxd and execute "sudo ln -s YOUR_LIB_LOCATION /usr/lib/" replace YOUR_LIB_LOCATION with your path

acutbal commented on 2020-07-09 09:56 (UTC)

@LenLord Thank you very much for your help, I've found libusbmuxd.

I've searched on the Arch wiki how to link a file from an AUR package but I haven't found it. Please, could you suggest me a place where to learn it? Thank you very much and regards.

LendLord commented on 2020-07-09 09:42 (UTC) (edited on 2020-07-09 09:50 (UTC) by LendLord)

@acutbal Try to find in your system and link it. Command - whereis libusbmuxd

acutbal commented on 2020-07-09 09:40 (UTC)

@LenLord Yes, it's installed, v.2.0.1-1. Weird...


LendLord commented on 2020-07-09 09:37 (UTC)

@acutbal did you install libusbmuxd? if not install and link it, if needed.

acutbal commented on 2020-07-09 09:32 (UTC)

@LenLord I've tried your suggestion but it doesn't work, the build still crashes. I've searched on my system the file "lusbmuxd-2.0" and it doesn't exist.


LendLord commented on 2020-07-07 17:52 (UTC)

@flashy sudo ln -s /usr/lib/ /usr/lib/ try it

flashy commented on 2020-07-07 10:14 (UTC)

@invidian I have read the pinned comment, however the patch breaks the build on manjaro with "/usr/bin/ld: cannot find -lusbmuxd-2.0". I'm not entirely sure where to report this if not here.

invidian commented on 2020-07-06 11:39 (UTC)

Thanks for reporting @dwzg. I didn't have a chance to check building on fresh installation due to poor internet connection. I added missing dependency now.

dwzg commented on 2020-07-06 11:27 (UTC) (edited on 2020-07-06 11:29 (UTC) by dwzg)

Installation of the newest version of v4l2loopback-dc-dkms gives an error about a missing header file "usbmuxd.h". This can be fixed by installing libusbmuxd. I guess this is a missing make dependency.

ngoonee commented on 2020-07-04 08:28 (UTC) is available now if you're interested. Basically obs-specific plugin (needs a different android app too).

invidian commented on 2020-06-25 10:40 (UTC)

Thanks @maximbaz. I pushed the update which introduces split package.

maximbaz commented on 2020-06-25 09:32 (UTC)

invidian I have approved the request, please go ahead with creating a split package :)

micwoj92 commented on 2020-06-16 21:31 (UTC)

@lorcap DKMS optionally depends on 4 headers available in main repos, regular, LTS, hardened and zen. That's kinda expected to have one of these installed if you use DKMS

lorcap commented on 2020-06-16 21:13 (UTC)

I had to install core/linux-headers for having the module properly built and installed. I believe that PKGBUILD misses a 'depends' on 'linux-headers'.

alerque commented on 2020-06-08 09:11 (UTC)

Split packaging from the droidcam package as droidcam-dkms sounds like the best way to go to me. Thanks for working on getting this cleaned up.

invidian commented on 2020-06-08 08:39 (UTC)

@ShayBox, this package is a kernel module used by droidcam, but packaged separately, so we can use DKMS hooks, so it does not break during kernel upgrades.

IMO 'droidcam-dkms' for package name is a bit counter-intuitive.

Actually, this package was not created very thoroughly, so I requested a merge into the 'droidcam' itself, so we can use split packaging feature there, to build both this one and the Droidcam itself.

LevitatingRein commented on 2020-06-08 08:30 (UTC)

@M.Srikannth, we currently have no solution. We might have to ask the developers to solve it, they'd understand the issue better.

shaybox commented on 2020-06-07 23:47 (UTC) (edited on 2020-06-08 00:00 (UTC) by shaybox)

Please don't source un versioned files (icon2.png, in a non git package if possible, add the file to the repository, use a set commit, or skip verification.

shaybox commented on 2020-06-07 23:45 (UTC) (edited on 2020-06-07 23:45 (UTC) by shaybox)

What is the point of this package when droidcam, droidcam-dkms, and droidcam-dkms-git exist, is this a custom build of v4l2loopback by the dev of droidcam? or is this a kernel module for droidcam, if the prior, please provides and conflicts v4l2loopback, if the latter, do the same for the above packages.

invidian commented on 2020-06-06 21:50 (UTC)

@micwoj92 oops, I'm aware of that, my bad, sorry!

micwoj92 commented on 2020-06-06 21:38 (UTC)

Hey man, when you update package version, you should set pkgrel to 1

M.Srikanth commented on 2020-06-06 13:05 (UTC)

@LevitatingRain,is there any progress in getting snd-aloop to work?

Terence commented on 2020-06-03 16:21 (UTC)

Cool, thanks!

invidian commented on 2020-06-03 16:20 (UTC)

@Terence thanks for suggestion, added. I just saw this pattern today in some other package ;)

Terence commented on 2020-06-03 14:38 (UTC)

Hey, can you make the URL point to instead? This is a more useful link as you can see what changed between version. Also now instead of ${pkgname}-${pkgver}.zip::${pkgver}.zip" you can use: ${pkgname}-${pkgver}.zip::${url}/archive/${pkgver}.zip"

invidian commented on 2020-06-03 09:45 (UTC)

@caleb it builds from Git tag from Github, how is this URL unversioned? The tags on GitHub should not be modified after publishing. How is it not installing the right version then? The md5 sums of source files for kernel modules all matches, if you compare them from the package and right git tag.

alerque commented on 2020-06-03 09:09 (UTC)

Please use the Github sources with taggged versions, this is using an unversioned upstream URL that breaks the checksum on update and currently isn't installing the version the package claims to be.

LevitatingRein commented on 2020-06-02 14:13 (UTC) (edited on 2020-06-02 14:13 (UTC) by LevitatingRein)

@M.Srikanth, we are still working on a solution to get sound working. Simply adding snd-aloop to droidcam.conf makes the module load but snd-aloop also needs to be configured to use the loopback soundcard, which the ID of changes when you remove/add other soundcards. The solution provided by droidcam sets the ID at install time but this very error prone.

M.Srikanth commented on 2020-06-01 11:10 (UTC)

Can you add snd-aloop to droidcam.conf

grazzolini commented on 2020-06-01 10:50 (UTC)


I have some plans on bringing this to the official repos, but not completely sold on this yet. I'll switch to git sources, and, as much as I hate using epochs, I don't see a way around it.

The versioning come from the way upstream used to release on their official website, it had that versioning. Since they switched to using only "latest", I have been arbitrarily increasing the pkgver.

simona commented on 2020-06-01 10:45 (UTC)

now ok :-))))

invidian commented on 2020-06-01 10:29 (UTC)

I fixed the source URL for 1.2, please make sure you're downloading new source archive when building.

M.Srikanth commented on 2020-06-01 10:15 (UTC) (edited on 2020-06-01 10:32 (UTC) by M.Srikanth)

@caleb,I thought that it was downloading the same zip as in but now I realised it is different(by binary zip I meant the contents of the zip is a droidcam binary). (But still that issue remains with the zip from though)

EDIT:It actually was the same thing as in until 1 hour ago

alerque commented on 2020-06-01 10:13 (UTC)

The sources for this seem to be available here. Since the sources are available I think this needs to use them — or get renamed as -bin. I think you'll need an epoch to downgrade the version, but where is the 6.x versioning coming from anyway?

alerque commented on 2020-06-01 10:07 (UTC) (edited on 2020-06-01 10:09 (UTC) by alerque)

@M.Srikanth The zip file itself is binary (all compressed archive formats are) but the contents in the sources from this repository. Of course it has has a Makefile!

M.Srikanth commented on 2020-06-01 08:37 (UTC) (edited on 2020-06-01 08:43 (UTC) by M.Srikanth) is a binary zip. But for some reason it has a Makefile (which fails).Also the directory layout is changed and support for audio is added.So the PKGBUILD should be rewritten.

simona commented on 2020-06-01 08:03 (UTC)

==> Starting build()... /home/barfin/.cache/yay/droidcam/PKGBUILD: line 29: cd: droidcam-1.2/linux: No such file or directory ==> ERROR: A failure occurred in build(). Aborting... Error making: droidcam

borh commented on 2020-06-01 05:43 (UTC)

The current PKGBUILD is downloading the wrong source file from the Github repo (the correct one is The following package download string (+ redownload and rehashing) fixes the build failure that miss_barfin got for me:


miss_barfin commented on 2020-06-01 04:10 (UTC)

==> Starting build()... /home/barfin/.cache/yay/droidcam/PKGBUILD: line 29: cd: droidcam-1.2/linux: No such file or directory ==> ERROR: A failure occurred in build(). Aborting... Error making: droidcam

invidian commented on 2020-05-30 05:56 (UTC)

Thanks for insights @malbeth. It is indeed the case. If found that the PKGBUILD wiki page says, that downloaded source file must have unique name, so I changed it now

LevitatingRein commented on 2020-05-30 00:34 (UTC)

AwesomeHaircut, again we only have to change the filename. I'll make a commit with the change sometime tomorrow. I'll also look into the sound script.

Alad commented on 2020-05-29 22:41 (UTC)

Anyone setting SRCDEST with makepkg will have similar issues.

CodeXYZ commented on 2020-05-29 22:40 (UTC)

Neither Yay or any other aur helper are officially supported. The makepkg command is the only way I test and only way i support.

malbeth commented on 2020-05-29 21:39 (UTC)

Like Foxboron said, this package fails to update if using an AUR manager with a cache (like yay), since the file name never changes (doesn't include the pkg version) the latest file doesn't get downloaded and the build fails at the checksum check.

Please update the PKGBUILD file with his solution.

malbeth commented on 2020-05-29 21:38 (UTC)

This package fails to update when using an AUR manager with a cache (like yay), since the file name never changes (doesn't include the pkg version) the latest file doesn't get downloaded and the build fails at the checksum check.

CodeXYZ commented on 2020-05-29 18:04 (UTC)

The dkms dependency will be worked on upstream, but that will hopefully come soon and there won't be a need for loading.

grazzolini commented on 2020-05-29 14:44 (UTC)


The version on github is 1.1. This is a problem. The fact is, upstream never bothered with consisting versioning.

LevitatingRein commented on 2020-05-29 11:18 (UTC)

I just tried removing all yay's cache manually and that worked. I did notice v4l2loopback-dc doesn't get loaded automatically though.

invidian commented on 2020-05-29 11:12 (UTC)

@LevitatingRein I just tried building with yay with removed cache and everything seems to work.

LevitatingRein commented on 2020-05-29 10:11 (UTC)

Yay complains that has a wrong sha512sum. Building the package manually works though.

invidian commented on 2020-05-29 09:39 (UTC)

Thanks @Kalq, sorry about that. I pushed new version with added proper dependencies. If you use only the CLI version, then gtk2 is only needed while building, so I'm not sure if it should be added to the dependencies. I leave it in makedepends for now.

Marc.2377 commented on 2020-05-29 04:28 (UTC)

@grazzolini, I understand you plan to switch this to pure source; in the meantime, why not pulling the release tag from GitHub? See

Kalq commented on 2020-05-28 22:25 (UTC)

Hi, I think libjpeg-turbo, alsa-lib, ffmpeg, and gtk2 should be makedepends. I couldn't get it to work without them. I think gtk2 is not optional.

invidian commented on 2020-05-28 21:00 (UTC) (edited on 2020-05-28 21:01 (UTC) by invidian)

@miss_barfin thanks for the heads up. I'm looking into the "install-sound" script right now and it seems to me that it's rather hacky. E.g, if you change number of sound cards in your system, it will break anyway.

The reason the script does not work is because v4l2loopback-dc-dkms installs /etc/modprobe.d/v4l2loopback-dc.conf, instead of /etc/modprobe.d/droidcam.conf. I guess doing sudo ln -s /etc/modprobe.d/v4l2loopback-dc.conf /etc/modprobe.d/droidcam.conf should work around that.

miss_barfin commented on 2020-05-28 17:21 (UTC)

problem, audio doesn't work you need to run "install-sound" script after installation in order to use audio but i can't really do it because it thinks the droidcam isn't installed because it can't find the file "/etc/modprobe.d/droidcam.conf"

CodeXYZ commented on 2020-05-28 13:47 (UTC)

There's been lot of changes to this package in the last couple weeks. There's also been changed to droidcam itself. Sorry for the delays and remember we all do this in our free time.

There's been an actual release by the droidcam dev, so hopefully that means things stabilize for now.

LevitatingRein commented on 2020-05-28 11:19 (UTC) (edited on 2020-05-28 11:57 (UTC) by LevitatingRein)

We now depend on v4l2loopback-dc-dkms, but now we are also depending on invidian to update that package in time. And it seems like the sha512sums are already outdated...

Can't we just depend on v4l2loopback-dkms instead? Edit: No we can't Droidcam refuses to use that one.

Alad commented on 2020-05-27 08:57 (UTC) (edited on 2020-05-27 08:58 (UTC) by Alad)

Manjaro is spam here, and the maintainer already said he can't install a different distribution just to support some users. Manjaro users: Please refrain from making further comments and use Manjaro support channels instead.

Foxboron commented on 2020-05-27 08:33 (UTC)

I have unpinned and removed the pinned comment suggesting people to install the make with sudo make install. This is silly. This is a packaging problem where the author does not account for a shared SRCDEST.

This is solved with "${pkgname}-${pkgver}.zip::${pkgname}/archive/${_pkgver}.zip". Any other workarounds are wrong.

miss_barfin commented on 2020-05-25 20:30 (UTC)

i flagged this out of date but i saw that you're already aware of the change thanks for packaging it

grazzolini commented on 2020-05-25 16:06 (UTC)

Upstream switched from putting versioned files on their website, to using a fixed name that has no version information. It only says "latest". So, everytime they update their version on the website, the checksum on the PKGBUILD will be outdated. This is not an issue with the package itself, but with the way upstream release. I plan on changing to a pure source package soon, once I get this building from source but, until then, if you get a checksum error, download from their website and change the PKGBUILD.

t0m5k1 commented on 2020-05-25 15:52 (UTC) (edited on 2020-05-25 15:53 (UTC) by t0m5k1)

Managed to get this to install after side stepping verification (Big Trust issue!!)

I see the following:

:: Running post-transaction hooks...

(1/3) Arming ConditionNeedsUpdate...

(2/3) Install DKMS modules

==> dkms install droidcam/6.7.7 -k 5.6.14-arch1-1

(3/3) Updating the desktop file MIME type cache...

❯ sudo insmod v4l2loopback-dc.ko width=320 height=240

insmod: ERROR: could not load module v4l2loopback-dc.ko: No such file or directory

❯ file /lib/modules/5.6.14-arch1-1/v4l2loopback-dc.ko

/lib/modules/5.6.14-arch1-1/v4l2loopback-dc.ko: cannot open `/lib/modules/5.6.14-arch1-1/v4l2loopback-dc.ko' (No such file or directory)

I see others having a similar issue, Why is this failing to build the module? What's missing from your package that's stopping this?

This is the only kernel I use so no need to ask "Is that the kernel you've booted?"

I decided to do a system wide find: sudo find / -name "v4l2loopback-dc.ko"

Still not found!!!!

What are you doing?

yura121 commented on 2020-05-25 07:17 (UTC)

rus ==> ОШИБКА: Исходные файлы не прошли проверку целостности! Не удалось собрать droidcam-dkms

en ==> ERROR: Source files did not pass the integrity check! Failed to collect droidcam-dkms

Arndroid commented on 2020-05-17 18:43 (UTC)


Of course, sorry for being so cryptic. When I run "sudo modprobe v4l2loopback-dc" I get that error message, like @artemklevtsov.

It could possibly fix the issue I'm having currently on Manjaro 20.0.1. (on 5.4, 5.5, 5.6 and 5.7) The issue is; if I start DroidCam I get the following error: Error: Device not found (/dev/video[0-9]). Did you install? [OK]

I totally assume it is something I butchered in my environment, somehow, but I thought, since @artemklevtsov is trying a solution similar to what I've found elsewhere, it might be somehow related to recent updates kernel side.

grazzolini commented on 2020-05-17 13:30 (UTC)


Never got any errors like this, can you be more specific?

Arndroid commented on 2020-05-17 13:08 (UTC)

Has there ever been a solution for the v4l2loopback_dc Exec / Bad address errors?

arjan5 commented on 2020-05-08 20:31 (UTC)

Hi, the checksum for seems to be incorrect, which means the package can't be installed. Could you please correct it?

tulipo commented on 2020-05-08 10:04 (UTC) (edited on 2020-05-08 10:21 (UTC) by tulipo)

Also with the workaround doesn't work....

i get

Registering webcam device modprobe: ERROR: could not insert 'videodev': Invalid argument

EDIT: It worked... I need just to reboot a try again.... Thanks a lot...

M.Srikanth commented on 2020-05-05 04:11 (UTC)

Note:Some AUR helpers do not redownload as it has the same name and then complain it has wrong md5sum

kamelie1706 commented on 2020-05-04 17:59 (UTC)

works works works ;-)

CodeXYZ commented on 2020-05-04 17:44 (UTC)

fixed fixed

kamelie1706 commented on 2020-05-04 16:44 (UTC) (edited on 2020-05-04 17:21 (UTC) by kamelie1706)

nope still issue with droidcam.tar.bz2 checksum This is what I get

sha1sum droidcam.tar.bz2

6660efa36255780000cef7992e441dd4b63c3bba  droidcam.tar.bz2

md5sum droidcam.tar.bz2

5ff0e772a76befba4e37e03101b611d7  droidcam.tar.bz2

This is the same key given by the official by the official package

echo "5ff0e772a76befba4e37e03101b611d7" | md5sum -c --
# OK?



The last key looks wrong to me ...

This works like a charm!


CodeXYZ commented on 2020-05-04 15:00 (UTC)

Is this working for you guys? I checked and it updated but the checksums matched.

kamelie1706 commented on 2020-05-03 21:04 (UTC) (edited on 2020-05-03 21:11 (UTC) by kamelie1706)


Using arch: makepkg - o fails

It cannot validate (md5sums check) droidcam.tar.bz2

Same error wether I try wiki instruction to install AUR package or your workaround.

Thx for maintaining this package.

NB: droicam seems to work now also on ios.

laggykiller commented on 2020-05-03 15:54 (UTC)

Same problem with @ManjaroUsar. Using 5.6.8-arch1-1.

ManjaroUsar commented on 2020-05-02 20:48 (UTC)

It gives me a ==> ERROR: One or more files did not pass the validity check! when I install it (I tried with yay and the pamac gui). I use manjaro on Linux 56 kernel, and I had the headers installed. The download snapshot method gave the same error.

LevitatingRein commented on 2020-05-01 16:17 (UTC)

I'll do some extra testing on Arch and if it works I'l add the patch. (As soon as I am behind my terminal).

bestfriend commented on 2020-05-01 16:10 (UTC)

montefuscolo's fix worked for me. Thanks. 5.4.35-1-Manjaro.

montefuscolo commented on 2020-04-28 12:18 (UTC) (edited on 2020-04-28 12:33 (UTC) by montefuscolo)

I did this changes on Manjaro

index d254e50..17734da 100644
@@ -52,7 +52,8 @@ package() {

   # Install kernel module and config files
   cd v4l2loopback
-  MODPATH="/usr/lib/modules/$(uname -r | sed 's/.[0-9]+-[0-9]+//')/extramodules"
+  extramod="/usr/lib/modules/$(uname -r | sed 's/.[0-9]+-[0-9]+//')/extramodules"
+  MODPATH="$(readlink -f $extramod)"
   install -Dm644 v4l2loopback-dc.ko.gz        "$pkgdir$MODPATH/v4l2loopback_dc.ko.gz"
   install -Dm644 "$pkgname.modules-load.conf" "$pkgdir/usr/lib/modules-load.d/$pkgname.conf"
   install -Dm644 "$pkgname.modprobe.conf"     "$pkgdir/etc/modprobe.d/$pkgname.conf"
diff --git droidcam.install droidcam.install
index 5216762..1aeaaa9 100644
--- droidcam.install
+++ droidcam.install
@@ -1,5 +1,6 @@
 post_install() {
   insmod /lib/modules/"$(uname -r)"/extramodules/v4l2loopback_dc.ko.gz
+  depmod -a

 post_upgrade() {

It shows /lib/modules/5.6.7-1-MANJARO/extramodules/v4l2loopback_dc.ko.gz: Unknown symbol in module, but it works.

bertogs commented on 2020-04-24 14:18 (UTC)

sudo modprobe v4l2loopback_dc

Fixed the Unknown symbol in module error for me after install. And it works after that.

noraj commented on 2020-04-23 15:11 (UTC)

I agree with @Scindix

(1/1) installing droidcam                                                                                                                                           [######################################################################################################] 100%
insmod: ERROR: could not insert module /lib/modules/5.6.5-arch3-1/extramodules/v4l2loopback_dc.ko.gz: Unknown symbol in module                                                                                                                                                   
error: command failed to execute correctly

I'm on arch, vanialla kernel and have the same error.

Also while removing the package:

(1/1) removing droidcam                                                                                                                                             [######################################################################################################] 100%
rmmod: ERROR: Module /lib/modules/5 is not currently loaded
error: command failed to execute correctly

commented on 2020-04-22 13:26 (UTC)

The v4l2loopback_dc doesn't get updated with the kernel properly. You have to reinstall droidcam everytime you kernel updates... Would be nice, if dkms would be implemented

Scindix commented on 2020-04-22 11:09 (UTC)

I'm getting an error during installation:

insmod: ERROR: could not insert module /lib/modules/5.5.13-arch2-1/extramodules/v4l2loopback_dc.ko.gz: Unknown symbol in module
error: command failed to execute correctly

I tried compiling the module from source and then invoking insmod manually. But the same error occurs. Not knowing much about kernel modules I have no clue how to fix this.

smokehead commented on 2020-04-22 09:46 (UTC)

@henriquelalves wow it worked! though it didnt worked with Yay, but i was able to install using sudo sh ./install , thanks brother!

henriquelalves commented on 2020-04-22 00:45 (UTC) (edited on 2020-04-22 00:45 (UTC) by henriquelalves)

@smokehead, I had the same problem during make on Manjaro ("No targets specified and no makefile found"). I was actually missing the linux54-headers (just installed it with pacman -S linux54-headers). The installation worked after that. Link where I found the solution:

aramus commented on 2020-04-14 17:23 (UTC)

I am on linux5.7 kernel and I also cant install. I get errors for VFL_TYPE_GRABBER not being declared.

CodeXYZ commented on 2020-04-12 20:02 (UTC)

I wondered that too when I adopted the package. I think it's against Aur guidelines to do it exactly the same way. I've experimented with it and it's definitely doable.

LevitatingRein commented on 2020-04-12 12:14 (UTC)

@milk I am wondering why the installer doesn't use the installer that comes with the program, which should handler a lot of extra driver stuff and tell you this automatically. Anyway I could add that if I find the time.

milkii commented on 2020-04-10 12:26 (UTC)

Maybe worth adding a post install echo of the resolution changing instructions.

milkii commented on 2020-04-10 11:45 (UTC) (edited on 2020-04-10 11:47 (UTC) by milkii)

Edit: I did a clean build and it built :)

JJK commented on 2020-04-10 08:05 (UTC)

I have the same issue as milk.

LevitatingRein commented on 2020-04-09 21:40 (UTC)

milk, I didn't have the same issue you are facing, which is odd. I recommend you run makepkg with the --skipchecksums flag.

LevitatingRein commented on 2020-04-09 21:08 (UTC)

They might've already updated the latest version since my commit. I'll update the md5 hash in a couple of minutes.

milkii commented on 2020-04-09 20:56 (UTC)

Currently getting:

==> Validating source files with md5sums...
    droidcam.desktop ... Passed
    icon2.png ... Passed
    droidcam.tar.bz2 ... FAILED
==> ERROR: One or more files did not pass the validity check!

LevitatingRein commented on 2020-04-08 16:19 (UTC) (edited on 2020-04-08 16:20 (UTC) by LevitatingRein)

Like M.Srikanth mentioned I started using the new source. I am currently compiling the latest kernel so I can test it. But it's all working on 5.5.5-zen.

Andrius commented on 2020-04-08 15:41 (UTC) (edited on 2020-04-08 16:02 (UTC) by Andrius)

For me too.. With Kernel 5.6.2 and 5.6.3, it fails to build

M.Srikanth commented on 2020-04-07 03:57 (UTC)

With Kernel 5.6 ,it fails to build

TecMunky commented on 2020-04-03 13:24 (UTC)

@tomvigl - that readlink change did not work for me. I had to use the solution from

@montefuscolo - although your solution appeared to work, I could not change the resolution at all - it was stuck at 320x240 ...uugggghh

@AwesomeHaircut - the pinned workaround works fine - now I am able to change the resolution as described at

thanks all.

tomvigl commented on 2020-04-03 08:09 (UTC)

@AwesomeHaircut: You just have to add readlink and it won't affect the installation in arch. MODPATH=$(readlink -f "/usr/lib/modules/$(uname -r | sed 's/.[0-9]+-[0-9]+//')/extramodules")

CodeXYZ commented on 2020-04-03 01:39 (UTC)

I don't want to say "Manjaro is not supported" but that's what is officially true. The module loading is depended on where you have your extra modules folder that can be, and probably is, different on manjaro. I have to make sure it works on Arch first and foremost. I just don't have time to install manjaro right now to test.

Having said that, you can load the module manually by going into the source directory no matter which distro you're using. I won't be making any changes, but I'll make a short tutorial for manjaro, as well if you're using a kernel that has a different extra modules folder.

TecMunky commented on 2020-04-03 00:33 (UTC)

@androide7461 and @montefuscolo -- thanks - now it is connected

Now i just have to figure out how to use it.

thanks again

androide7461 commented on 2020-04-03 00:07 (UTC)

@TecMunky: Try the solution from @montefuscolo. It worked for me. There are no errors what so ever now. Thanks @montefuscolo!

TecMunky commented on 2020-04-02 19:32 (UTC) (edited on 2020-04-02 19:35 (UTC) by TecMunky)

@tomvigl - I got the same error @androide7461 got when executing the "modprobe" command -- "modprobe: FATAL: Module v4l2loopback_dc not found in directory /lib/modules/5.5.13-1-MANJARO"

what now?

@android7461 - that is not what I meant - but I don't use yay. I simply deleted the entire droidcam directory, then extracted the snapshot again, edited the build file, then executed the make command.

Also, I did not get any errors during installation. My error came when I executed the modprobe command.

montefuscolo commented on 2020-04-02 14:16 (UTC)

I had to modify this line on Manjaro Linux, running kernel 5.4

MODPATH="/usr/lib/modules/extramodules-$(uname -r | sed 's/.[0-9]\+-[0-9]\+//')"

androide7461 commented on 2020-04-02 10:59 (UTC)

@TecMunky I deleted my cache with "yay -Sc" and reinstalled with "yay --editmenu -S droidcam". I hope this was the way you meant. But now I get this error when I'm installing it: "insmod: ERROR: could not insert module /lib/modules/5.5.13-1-MANJARO/extramodules/v4l2loopback_dc.ko.gz: Unknown symbol in module error: command failed to execute correctly" It's installed nonetheless. But when I try to open it I get the same error as TecMunky. Then I checked if the module is loaded like tomvigl said with: "lsmod | grep v4l2loopback_dc". It returns nothing, so I guess it's not loaded. After that I write: "modprobe v4l2loopback_dc" and get this error: "modprobe: FATAL: Module v4l2loopback_dc not found in directory /lib/modules/5.5.13-1-MANJARO". Which makes kind of sense because I think it wasn't installed properly.

tomvigl commented on 2020-04-02 09:18 (UTC)

You have to check if the module is loaded: lsmod | grep v4l2loopback_dc If not - add the module with: modprobe v4l2loopback_dc

TecMunky commented on 2020-04-02 00:15 (UTC) (edited on 2020-04-02 00:22 (UTC) by TecMunky)

tomvigl: That worked for me. -- THANKS

androide7461: first you have to delete the extracted directory, then extract the snapshot again --> THEN modify line 58 to use "readlink -f"

But now, I need to learn how to use it ...

When I start the droidcam client I get a popup saying "Device not found (/dev/video[0-]). Did you install it?"

tomvigl commented on 2020-04-01 16:21 (UTC)

Check if the right linux-header is installed: pamac search linux-headers | grep $(uname -r | cut -d "-" -f 1,2)

If there is nothing like [Installed] you have to install it: pamac install linux[0-9][0-9]-headers

Shaka2u1u commented on 2020-04-01 14:56 (UTC)

@AwesomeHaircut I had already earlier mentioned that I downgraded to the old LTS kernel. Still nothing of the mentioned here works. Still am waiting on a CLEAR answer about how and where to add this makepkg -si

Exact location and short tut, please, and I am okay trying it again.

androide7461 commented on 2020-04-01 14:49 (UTC)

I changed my pkgbuild as you said but it didn't work for me :(

tomvigl commented on 2020-04-01 14:19 (UTC)

I also had problems installing droidcam on Manjaro with kernel 5.5.13-1-MANJARO! The problem was that extramodules is a symlink. The Solution is to resolve the symlink with "readlink -f".

Change the build file in line 58: MODPATH=$(readlink -f "/usr/lib/modules/$(uname -r | sed 's/.[0-9]+-[0-9]+//')/extramodules")

TecMunky commented on 2020-03-31 02:11 (UTC)

I have looked at all the comments about my issue (I think), but am still having a problem installing this package. I get the following message:

error: failed to commit transaction (conflicting files) droidcam: /usr/lib/modules/5.5.13-1-MANJARO/extramodules exists in filesystem (owned by linux55)

So I downloaded the snapshot and tried "makepkg -si" - and got the exact same error

CodeXYZ commented on 2020-03-29 14:15 (UTC) (edited on 2020-03-29 14:20 (UTC) by CodeXYZ)

Maybe this wiki page can get you out of your confusion @Saka2u1u

Again, no need for workarounds or manual installs. Whatever you normally use for installing things should work now.

Shaka2u1u commented on 2020-03-29 05:41 (UTC)

Actually I think no one even says where and how to use the makepkg -si with which code... Nothing works, enough time wasted. Removed.-

Arndroid commented on 2020-03-28 21:28 (UTC)

I was indeed missing the linux-headers package.

I went ahead and installed 5.5, and the 5.5 headers (I don't know why it wasn't installed along with it), and that seems to make thing work wonders again.

Completely different issue. Thanks a ton for the help.

CodeXYZ commented on 2020-03-28 21:11 (UTC)

It's about both; it should match exactly. It looks like you're booting from a different kernel version than the kernel headers you have installed. If you install linux 5.5 make sure you also install the linux5.5-headers. Otherwise make sure you're booting with the correct kernel and have linux_version-headers corresponding to it. In your grub or syslinux boot file, you have to make sure you're booting the correct kernel. This wiki link might help?

Arndroid commented on 2020-03-28 20:50 (UTC) (edited on 2020-03-28 21:27 (UTC) by Arndroid)

Cool, the output of the those for me is:

pacman -Qi linux-headers|grep Version Version : 5.4.28-1

uname -r 5.4.24-1-MANJARO

Should uname -r not have the "-MANJARO" part in it perhaps, or is it just about the version number? I still have the same issue after a reboot, I can update to 5.5 fwiw.

CodeXYZ commented on 2020-03-28 20:34 (UTC)

From what i've seen, there's nothing specific to manjaro from keeping this from working. No need for downloading a snapshot or anything else anymore :-] it should all be working as normal @Arndroid You probably have to reboot. Make sure your system is up to date, specifically your kernel and kernel-headers, and try again. You want to make sure uname -r matches pacman -Qi linux-headers|grep Version

Arndroid commented on 2020-03-28 20:18 (UTC)

@AwesomeHaircut thank you for the support.

I downloaded the snapshot and run the makepkg -si command: ==> Validating source files with md5sums... droidcam.desktop ... Passed icon2.png ... Passed ==> Validating source_x86_64 files with md5sums... droidcam.tar.bz2 ... Passed ==> Extracting sources... ==> Starting prepare()... ==> Starting build()... make -C /lib/modules/uname -r/build M=pwd make[1]: warning: jobserver unavailable: using -j1. Add '+' to parent make rule. make[1]: Entering directory '/usr/lib/modules/5.4.24-1-MANJARO/build' make[1]: No targets specified and no makefile found. Stop. make[1]: Leaving directory '/usr/lib/modules/5.4.24-1-MANJARO/build' make: [Makefile:4: all] Error 2 ==> ERROR: A failure occurred in build(). Aborting...

As you can see, I do use Manjaro, is this the cause of the issue I have? It does seems very similar to the issues others have recently mentioned.

If I can provide further info, please let me know.

LevitatingRein commented on 2020-03-28 17:24 (UTC)

Ah nice work @AwesomeHaircut.

CodeXYZ commented on 2020-03-28 17:11 (UTC)

fixed?! You guys let me know please :]

CodeXYZ commented on 2020-03-28 14:14 (UTC)

I don't mean edit the PKGBUILD @Shaka2u1u I mean instead of running yay -S pkgname or octopi -S pkgname You download a snapshot of this aur. (On the top right of this page, above "Search Wiki" and below "View PKGBUILD / View Changes") Once you have the files, cd into the directory with the PKGBUILD in it and then run makepkg -si

These instructions are generalized for anyone else that might need them, since you already have it downloaded :]

Shaka2u1u commented on 2020-03-27 01:48 (UTC)

Preparing... Cloning droidcam build files... Checking droidcam dependencies... Resolving dependencies... Checking inter-conflicts...

Building droidcam... ==> Making package: droidcam 6.7.5-2 (Fr 27 Mär 2020 00:38:32 CET) ==> Checking runtime dependencies... ==> Checking buildtime dependencies... ==> Retrieving sources... -> Found droidcam.desktop -> Found icon2.png -> Found droidcam.tar.bz2 ==> Validating source files with md5sums... droidcam.desktop ... Passed icon2.png ... Passed ==> Validating source_x86_64 files with md5sums... droidcam.tar.bz2 ... Passed ==> Removing existing $srcdir/ directory... ==> Extracting sources... ==> Starting prepare()... ==> Removing existing $pkgdir/ directory... ==> Starting build()... ==> ERROR: PKGBUILD does not exist. ==> ERROR: A failure occurred in build(). Aborting... All there is. Maybe I have problems to install any files connecting to the Kerne modules....

Shaka2u1u commented on 2020-03-26 22:29 (UTC)

inside the build files I ve changed make to makepkg -si It helped nothing sadly

build() { cd "$pkgname/v4l2loopback" makepkg -si gzip -f v4l2loopback-dc.ko }

MastroRuggiero commented on 2020-03-26 21:57 (UTC)

Hello, even after commit 4586966807ed i'm getting the /dev/video[0-9] error and the cat complaint. My system is up to date with linux-headers version matching kernel version. I installed the package using makepkg -si. Any clue of what's going on? I also have the optional dependencies installed and up to date.

Cheers, M.

moepwizzy commented on 2020-03-23 12:14 (UTC)

After a kernelupdate I had to reinstall this, to get everything working again. Is there a way around that?

seboss666 commented on 2020-03-23 07:09 (UTC)


I'm getting this error :

:: Procéder à l’installation ? [O/n] 
(1/1) vérification des clés dans le trousseau                                                                                  [-----------------------------------------------------------------------------] 100%
(1/1) vérification de l’intégrité des paquets                                                                                  [-----------------------------------------------------------------------------] 100%
(1/1) chargement des fichiers des paquets                                                                                      [-----------------------------------------------------------------------------] 100%
(1/1) analyse des conflits entre fichiers                                                                                      [-----------------------------------------------------------------------------] 100%
erreur : la validation de la transaction a échoué (conflit de fichiers)
droidcam : /usr/lib/modules/5.4.24-1-MANJARO/extramodules est déjà présent dans le système de fichiers (appartenant à linux54)

It says that the extramodules folder already exists in the system. Git says in the cache folder that master is 4586966807ed.

Not sure why it's trying to take ownership on the folder ?

itiel commented on 2020-03-19 08:12 (UTC)

Thanks, it's working now.
When installing, i'm still getting the

cat: /usr/lib/modules/extramodules-5.5-2/version: No such file or directory

Any idea what that is about?

CodeXYZ commented on 2020-03-18 16:38 (UTC)

Great that helps a lot, I will push a change for the update since that's what seems to be happening :-)

itiel commented on 2020-03-18 07:05 (UTC) (edited on 2020-03-18 07:06 (UTC) by itiel)

@AwesomeHaircut my system is up to date, and i have the same version of linux-headers as the kernel.
Weirdly enough, when i'm trying to use makepks -si instead of yay, i've got:

==> Validating source_x86_64 files with md5sums...    
    droidcam.tar.bz2 ... FAILED    
==> ERROR: One or more files did not pass the validity check!    

thanks for your help.

CodeXYZ commented on 2020-03-18 03:53 (UTC)

What do you use for installing this package? @Bitts311

@itiel Make sure you have linux headers for your current system installed and have your system up to date. The PKGBUILD will be looking for headers for whatever kernel your system is running and that may need a reboot.

@everyone running Manjaro or using a aur helper Installing this using makepkg -si and see how far you get :-]

itiel commented on 2020-03-17 12:15 (UTC)

I have been trying to install droidcam for 2 days without success.
When installing, i get cat: /usr/lib/modules/extramodules-5.5-2/version: No such file or directory, but the installation continues. I cant figure out where is this cat comes from, and my kernel is

$ uname -r
$ 5.5.9-arch1-2

when i'm trying to start droidcam, i have the error:

Device not found (/dev/video[0-9]).
Did you install it?

I've tried everything that i can think of, but without success. can anybody help me?

Bitts311 commented on 2020-03-17 09:32 (UTC)

==> Проверка файлов source с использованием md5sums... droidcam.desktop ... Готово icon2.png ... Готово ==> Проверка файлов source_x86_64 с использованием md5sums... droidcam.tar.bz2 ... Готово ==> Распаковка исходных файлов... ==> Запускается prepare()... ==> Запускается build()... make -C /lib/modules/`uname -r`/build M=`pwd` make[1]: предупреждение: сервер заданий недоступен: используется -j1. Добавьте «+» к правилу в родительском make. make[1]: вход в каталог «/usr/lib/modules/5.5.8-1-MANJARO/build» make[1]: *** Не заданы цели и не найден make-файл. Останов. make[1]: выход из каталога «/usr/lib/modules/5.5.8-1-MANJARO/build» make: *** [Makefile:4: all] Ошибка 2 ==> ОШИБКА: Произошел сбой в build(). Прерывание... Hello, how install programm? Manjaro x64 XFCE, Linux 5.5

Shaka2u1u commented on 2020-03-10 05:39 (UTC)

@LevitatingRein I have this obivously not only with this package, while I uninstalled others likev412 module already

Would you not consider this as the point to lok at: "No targets specified and no makefile found. Stop. make[1]: Leaving directory"? It should be a relevant folder been created, but it wasnt. So mistake comes from Kernel or other kernel dependent installations, doesn't it? (I blinded some parts of the higher paths, taking out username for public here)

I saved for example this output: make -C /lib/modules/uname -r/build M=pwd make[1]: warning: jobserver unavailable: using -j1. Add '+' to parent make rule. make[1]: Entering directory '/usr/lib/modules/5.4.22-1-MANJARO/build' make[1]: No targets specified and no makefile found. Stop. make[1]: Leaving directory '/usr/lib/modules/5.4.22-1-MANJARO/build' make: [Makefile:4: all] Error 2 ==> ERROR: A failure occurred in build(). Aborting...

Building v4l2loopback-dkms...
==> Making package: v4l2loopback-dkms 0.12.3-2 (Sa 29 Feb 2020 15:42:36 CET)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Found v0.12.3.tar.gz
==> Validating source files with sha256sums...
    v0.12.3.tar.gz ... Passed
==> Removing existing $srcdir/ directory...
==> Extracting sources...
  -> Extracting v0.12.3.tar.gz with bsdtar
==> Removing existing $pkgdir/ directory...
==> Starting build()...
Building v4l2-loopback driver...
make -C /lib/modules/`uname -r`/build M=/run/media/ffgg/LENOVO1/AUR_build/pamac-build/v4l2loopback-dkms/src/v4l2loopback-0.12.3 modules
make[1]: Entering directory '/usr/lib/modules/5.4.22-1-MANJARO/build'
make[1]: *** No rule to make target 'modules'.  Stop.
make[1]: Leaving directory '/usr/lib/modules/5.4.22-1-MANJARO/build'
make: *** [Makefile:43: v4l2loopback.ko] Error 2
==> ERROR: A failure occurred in build().

And this: Full log written to /123/123/nnn/nnm/AUR_build/pamac-build/pango-anydesk/src/build/meson-logs/testlog.txt ==> Entering fakeroot environment... ==> Starting package()... ==> Tidying install... -> Removing libtool files... -> Purging unwanted files... -> Removing static library files... -> Stripping unneeded symbols from binaries and libraries... -> Compressing man and info pages... ==> Checking for packaging issues... ==> Creating package "pango-anydesk"... -> Generating .PKGINFO file... -> Generating .BUILDINFO file... -> Generating .MTREE file... bsdtar: Failed to set default locale -> Compressing package... /usr/bin/makepkg: line 723: /run/media/ffgg/LENOVO1/AUR_build/pamac-build/pango-anydesk/pango-anydesk-1:1.43.0-2-x86_64.pkg.tar.xz: Invalid argument bsdtar: Failed to set default locale bsdtar: Write error ==> ERROR: Failed to create package file.

LevitatingRein commented on 2020-03-09 22:10 (UTC)

@Shaka2u1u I was able to build this package fine on Arch just now. I think this is a Manjaro specific issue, and I am having trouble with realizing what might cause it.

Shaka2u1u commented on 2020-03-09 09:59 (UTC) (edited on 2020-03-09 10:08 (UTC) by Shaka2u1u)

Hi, most probably due to the earlier mentioned problems, I dont get it to upgrade on manjaro: Preparing... Cloning droidcam build files... Checking droidcam dependencies... Synchronizing package databases... Resolving dependencies... Checking inter-conflicts...

Building droidcam... ==> Making package: droidcam 6.7.5-2 (Mo 09 Mär 2020 10:54:34 CET) ==> Checking runtime dependencies... ==> Checking buildtime dependencies... ==> Retrieving sources... -> Found droidcam.desktop -> Found icon2.png -> Found droidcam.tar.bz2 ==> Validating source files with md5sums... droidcam.desktop ... Passed icon2.png ... Passed ==> Validating source_x86_64 files with md5sums... droidcam.tar.bz2 ... Passed ==> Removing existing $srcdir/ directory... ==> Extracting sources... ==> Starting prepare()... ==> Removing existing $pkgdir/ directory... ==> Starting build()... make -C /lib/modules/uname -r/build M=pwd make[1]: warning: jobserver unavailable: using -j1. Add '+' to parent make rule. make[1]: Entering directory '/usr/lib/modules/4.19.107-1-MANJARO/build' make[1]: No targets specified and no makefile found. Stop. make[1]: Leaving directory '/usr/lib/modules/4.19.107-1-MANJARO/build' make: [Makefile:4: all] Error 2 ==> ERROR: A failure occurred in build(). Aborting...

No idea why it gives this problem still, cause I already rolled back to kerne 4.19


artemklevtsov commented on 2020-03-01 05:01 (UTC)

@LevitatingRein, the package have logically splited parts: kernel module and binary utility progrom. DKMS-module will be update module every time for the all installed kernels (when install or update kerenel). Also note droidcam in this packages is simply precompiled binary so more correctly call it droidcam-bin.

LevitatingRein commented on 2020-02-06 21:21 (UTC)

@artemklevtsov, that's an interesting idea. I have never worked with shared packages before. What are the benefits to your solution?

LevitatingRein commented on 2020-02-06 21:20 (UTC)

Finally my fixes have been pushed, if anyone still faces issues please let me know.

LevitatingRein commented on 2020-02-06 02:29 (UTC)

@AwesomeHairbut, I made a disown request for the package a while back, it was now finally accepted, but I wasn't made co-maintainer apparently. If you could make me maintainer that'd be great, then I can finally push my fixes to this repo.

CodeXYZ commented on 2020-02-06 01:28 (UTC)

I don't understand what's going on with the ownership of this package but I'm reclaiming for now. I'll be sure to update it within the next 24 hours now that I have time to so again :-)

grazzolini commented on 2020-01-20 00:30 (UTC)


Ever since kernel 5.4 this version of the module has stopped working. I have created a droidcam-dkms-git version of the package that install the tools from the 6.7.5 version, but the module code is pulled in from git. When upstream makes a new release, I'll update this one.

artemklevtsov commented on 2020-01-19 15:41 (UTC) (edited on 2020-01-20 06:30 (UTC) by artemklevtsov)

@LevitatingRein thanks it works for me.

I suggest to split the package to droidcam-bin and droidcam-dkms parts.

Code shared in the repo:

Changes as patch:

artemklevtsov commented on 2020-01-19 15:14 (UTC) (edited on 2020-04-23 03:28 (UTC) by artemklevtsov)

Module no loaded with message:

$ sudo modprobe v4l2loopback-dc
modprobe: ERROR: could not insert 'v4l2loopback_dc': Bad address

Module built success:

$ sudo find /usr/lib/modules/ -name '*v4l2loopback*'   
$ uname -r

LevitatingRein commented on 2020-01-16 16:01 (UTC) (edited on 2020-01-16 16:31 (UTC) by LevitatingRein)

I fixed the sources link, here is my fork:

And here's a link to the PKGBUILD commit as a patch:

Edit: I also added the fix @yochiwarez mentioned to the repository. You can download that commit as a patch here:

LothaireFR commented on 2019-12-04 09:01 (UTC)

Why xanmod kernel, and 4.9, and 4.14, and 3.16 ? This is madness !

yochiwarez commented on 2019-10-30 02:41 (UTC) (edited on 2019-10-30 05:00 (UTC) by yochiwarez)

for those who have this error Device not found (/dev/video[0-9]). change MODPATH in the pkgbuild file, like this : MODPATH="/usr/lib/modules/$(uname -r | sed 's/.[0-9]+-[0-9]+//')/extramodules"

it will work after reboot.

deathangel908 commented on 2019-09-30 09:49 (UTC)

Same issue, Error: Device not found (/dev/video[0-9]). I installed and loaded v4l2loopback-dkms, it didn't help.

Shaka2u1u commented on 2019-09-04 03:03 (UTC)

Hi, I run into the exact same problem of Error: Device not found (/dev/video[0-9]). Yes, my kernel goes along the headers ... This is my dif from the build: diff --git a/PKGBUILD b/PKGBUILD index fba59b6..a3d8c03 100644 --- a/PKGBUILD +++ b/PKGBUILD @@ -54,7 +54,7 @@ package() {

# Install kernel module and config files cd v4l2loopback - MODPATH="/usr/lib/modules/extramodules-$(uname -r | sed 's/.[0-9]+-[0-9]+//')" + MODPATH="/usr/lib/modules/extramodules-5.0.21-rt16-MANJARO" install -Dm644 v4l2loopback-dc.ko.gz "$pkgdir$MODPATH/v4l2loopback_dc.ko.gz" install -Dm644 "$pkgname.modules-load.conf" "$pkgdir/usr/lib/modules-load.d/$pkgname.conf" install -Dm644 "$pkgname.modprobe.conf" "$pkgdir/etc/modprobe.d/$pkgname.conf" diff --git a/droidcam.install b/droidcam.install index accab0a..d3ad595 100644 --- a/droidcam.install +++ b/droidcam.install @@ -1,6 +1,6 @@ post_install() { - _extramodules="extramodules-$(uname -r | cut -f-2 -d'.')-$(uname -r|sed -e 's/.*-//g')" - depmod $(cat /usr/lib/modules/${_extramodules}/version) + _extramodules="extramodules-5.0.21-rt16-MANJARO" + depmod $(cat /usr/lib/modules/extramodules-5.0.21-rt16-MANJARO) }

post_upgrade() {

flortsch commented on 2019-08-22 22:02 (UTC) (edited on 2019-08-22 22:22 (UTC) by flortsch)

The module is installed into the wrong directory when using recent kernel versions I guess. I had to change the PKGBUILD and droidcam.install to point to "/usr/lib/modules/extramodules-ARCH".

bubuntux commented on 2019-08-10 04:28 (UTC)


Error: Device not found (/dev/video[0-9]). Did you install it?


CodeXYZ commented on 2019-07-21 15:15 (UTC)

Updated :-)

dolour commented on 2019-07-21 08:39 (UTC) (edited on 2019-07-21 08:42 (UTC) by dolour)

Actual md5 for the x64 package: "9507c0b738f427c5f1dde7b2a364fdfb"

@abdulhakeem: Just replace the "md5sums_x86_64" value in your build files. Assuming your running 64bit ofc, otherwise manually download the 332bit one, run md5sum on it and replace the value for i686 accordingly.

abdulhakeem commented on 2019-06-13 18:00 (UTC)

@fadysghatas how to update the checksums so the package will install?

fadysghatas commented on 2019-04-12 15:47 (UTC) (edited on 2019-04-12 15:47 (UTC) by fadysghatas)

New checksums for 32 and 64 versions are : (x32) 928f2e9eefee5e076eec16b1f7c12992

(x64) 984b068a87f28d6326ca1e064f4fc584

these should replace the first value in md5sums and md5sums_x86_64 respectively.

fadysghatas commented on 2019-04-12 15:47 (UTC)

New checksums for 32 and 64 versions are : 32: 928f2e9eefee5e076eec16b1f7c12992 64: 984b068a87f28d6326ca1e064f4fc584

these should replace the first value in md5sums and md5sums_x86_64 respectively.

ToxicAvenger commented on 2019-04-12 10:16 (UTC)

Its out of date, alright. How to compile it??

recolic commented on 2019-03-14 05:31 (UTC)

Here's updated PKGBUILD and install script. I have no permission to this repo so I'm posting it here. Hope it helps!

recolic commented on 2019-03-14 05:17 (UTC)

The module doesn't compile under linux 5.0. I have fixed the problem here, and you may use this patch directly.

Please update soon because ArchLinux kernel already goes 5.0.x

Blackflighter commented on 2019-01-12 05:23 (UTC)

Instead of the following line in the PKGBUILD: MODPATH="/usr/lib/modules/extramodules-$(uname -r | sed 's/.[0-9]+-[0-9]+//')"

This should be used instead, to allow for the module installation to work properly: MODPATH="/usr/lib/modules/extramodules-$(uname -r | sed 's/.*-//g')"

The droidcam.install file also needs modifying here: _extramodules="extramodules-$(uname -r | cut -f-2 -d'.')-$(uname -r|sed -e 's/.*-//g')"

To be replaced instead with: _extramodules="extramodules-$(uname -r | sed 's/.*-//g')"

This should get the proper name without including the version.

gilcu3 commented on 2018-09-17 15:33 (UTC)

as for kernel 4.18, the PKGBUILD needs a slight change to fix error: cat: /usr/lib/modules/extramodules-4.18-zen/version: No such file or directory that file is currently in /usr/lib/modules/extramodules-zen/

So version numbers got dropped from folder name

Kuchiriel commented on 2018-07-15 16:45 (UTC)

==> Iniciando build()... make -C /lib/modules/uname -r/build M=pwd make[1]: Entering directory '/usr/lib/modules/4.17.5-1-MANJARO/build' make[1]: No targets specified and no makefile found. Stop. make[1]: Leaving directory '/usr/lib/modules/4.17.5-1-MANJARO/build' make: [Makefile:4: all] Error 2 ==> ERRO: Uma falha ocorreu em build(). Abortando... ==> ERRO: Makepkg não conseguiu compilar droidcam.

CodeXYZ commented on 2018-05-04 15:53 (UTC)

Please make sure you reboot if you have updated your kernel.

mani.zaeim commented on 2018-05-04 05:45 (UTC)

make -C /lib/modules/uname -r/build M=pwd make[1]: warning: jobserver unavailable: using -j1. Add '+' to parent make rule. make[1]: /lib/modules/4.16.5-1-ARCH/build: No such file or directory. Stop. make: [Makefile:4: all] Error 2 ==> ERROR: A failure occurred in build(). Aborting... ==> ERROR: Makepkg was unable to build droidcam. ==> Restart building droidcam ? [y/N] ==> ---------------------------------

CodeXYZ commented on 2018-03-16 19:25 (UTC)

Ah great! I actually have to do a few things more than that but it should be straightforward thanks!

EbKeth commented on 2018-03-12 00:15 (UTC)

Issue has been resolved on this project's Git: Just need a package update for the new md5sums.

CodeXYZ commented on 2018-02-25 14:24 (UTC)

EbKeth can you try adding v4l2loopback-dkms as a dependecy? make sure you install

EbKeth commented on 2018-02-25 00:19 (UTC)

Package will not compile on linux 4.15, included v4l2loopback module has not been updated to the new kernal timer API.

sistematico commented on 2018-02-12 10:37 (UTC)

@binaryplease same error here:

CodeXYZ commented on 2017-04-13 22:55 (UTC)

Can you elaborate @binaryplease

pablo1 commented on 2017-04-13 21:53 (UTC)

I get an error with systemd trying to load the module 'v4l2loopback_dc'.

CodeXYZ commented on 2016-12-19 17:57 (UTC) (edited on 2016-12-19 17:58 (UTC) by CodeXYZ)

This is weird. Somehow the last commit didn't commit correctly? I had upped it to 9 as well as updated the MD5 but only the MD5 got changed. Anyways it's fixed now and I'll be sure to look closely at the changes since they don't always commit. I'm sure I messed up somewhere haha. [EDIT] It *was* my fault! :D

spsf64 commented on 2016-12-19 16:36 (UTC)

@Awesomehaircut, pkgrel=8 should be pkgrel=9 ? I think this is why octopi is reporting it out of date

samuelporcellis commented on 2016-12-19 13:25 (UTC)

Oh sorry, Octopi is Manjaro's (arch based distro) graphical package manager, which has this yaourt updater, I think I might be opening a topic on Manjaro's forum about this issue then.

CodeXYZ commented on 2016-12-16 16:01 (UTC)

What's octopi? I was gonna update this package but I don't think the developer has himself updated this since november. He doesn't have a changelog or anything of the sort so it's tricky to find out about it. The timestamps say november though. I would reinstall.

samuelporcellis commented on 2016-12-15 15:56 (UTC)

It is showing a message on Octopi that there is an update, but my version is up to date, and that message does not disappear. What can I do?

CodeXYZ commented on 2016-09-09 16:13 (UTC)

You need to make sure you have the headers for the kernel you're currently running. Make sure 'pacman -Q linux' --add -lts or-ck if appropriate --and 'uname -r' show the same version. If you just upgraded reboot.

JohnnyDeacon commented on 2016-09-09 03:37 (UTC)

==> Starting build()... make -C /lib/modules/`uname -r`/build M=`pwd` make[1]: Entering directory '/usr/lib/modules/4.7.2-1-MANJARO/build' make[1]: *** No targets specified and no makefile found. Stop. make[1]: Leaving directory '/usr/lib/modules/4.7.2-1-MANJARO/build' make: *** [Makefile:4: all] Error 2 ==> ERROR: A failure occurred in build(). Aborting... :: failed to build droidcam package(s)

CodeXYZ commented on 2016-07-21 05:12 (UTC)

Thanks a lot for that Jame San! I made you a co maintainer and you can update changes. I'll merge them first thing in the morning; unless you're a bit faster than me haha

jamesan commented on 2016-07-12 22:25 (UTC)

The current source tarball is rather old, I gather, and the latest package builds without encountering that same warnings treated as errors. Running a diff between the current (v4.1) and latest (v6.0) tarballs reveals a significant number of code changes in implementing the v4l2loopback_dc kernel module, which appears to be a custom and simplified modification of the official mainline v4l2loopback kernel module. Please find changes returning this package to working order here: I also cleaned up the package in general and managed to: - eliminate patching of upstream code as target lines are no longer present; - remove conflict or dependency on v4l2loopback kernel module (i.e. it's unaffected by the presence of v4l2loopback-dkms); - added support for i686 architecture as its supported by a parallel package upstream; - eliminated all dependencies as the binary executables are statically linked (I suspect the gtk2 dependency is uneeded); - rearranged lines and separated the logic into the prepare(), build(), and package() functions. The entire set of changes can be found in a series of commits here: with the repo located here: There's no mechanism for pull/merge requests in the AUR, but I can push my commits into the repo if you add me as co-maintainer (or you can fork that repo of mine and DIY).

CodeXYZ commented on 2016-07-06 21:29 (UTC) (edited on 2016-07-06 21:48 (UTC) by CodeXYZ)

Sorry about not replying, I don't use this often but I do want to make sure it's at working haha. Let me know how it goes @jamesan. If anyone wants to test the prebuilt package I'll make it available on my website. I'll see if I can put a repo too.

jamesan commented on 2016-07-05 08:02 (UTC)

I'm struggling with the identical error (exact log output as posted) posted by nipsky, which presents when compiling the v4l2loopback_dc kernel module as the last step in the package() function. I'm also using the CK patchset variant of the same kernel version as nipsky: 4.6.3-1-ck There's reference to droidcam's upstream build process fails at this kernel module for versions of the Linux kernel above 3.18/3.19. Let me see if this error vanishes if I boot up with a 3.xx kernel.

nipsky commented on 2016-07-01 20:14 (UTC)

I get an error trying to build the package: make -C /lib/modules/`uname -r`/build M=`pwd` make[1]: warning: jobserver unavailable: using -j1. Add '+' to parent make rule. make[1]: Entering directory '/usr/lib/modules/4.6.3-1-ARCH/build' CC [M] /tmp/makepkg/droidcam/src/v4l2loopback/v4l2loopback-dc.o /tmp/makepkg/droidcam/src/v4l2loopback/v4l2loopback-dc.c:2331:30: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types] .vidioc_s_std = &vidioc_s_std, ^ /tmp/makepkg/droidcam/src/v4l2loopback/v4l2loopback-dc.c:2331:30: note: (near initialization for ‘v4l2_loopback_ioctl_ops.vidioc_s_std’) /tmp/makepkg/droidcam/src/v4l2loopback/v4l2loopback-dc.c:2351:30: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types] .vidioc_s_audio = &vidioc_s_audio, ^ /tmp/makepkg/droidcam/src/v4l2loopback/v4l2loopback-dc.c:2351:30: note: (near initialization for ‘v4l2_loopback_ioctl_ops.vidioc_s_audio’) /tmp/makepkg/droidcam/src/v4l2loopback/v4l2loopback-dc.c:2353:30: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types] .vidioc_s_audout = &vidioc_s_audout, ^ /tmp/makepkg/droidcam/src/v4l2loopback/v4l2loopback-dc.c:2353:30: note: (near initialization for ‘v4l2_loopback_ioctl_ops.vidioc_s_audout’) cc1: some warnings being treated as errors make[2]: *** [scripts/ /tmp/makepkg/droidcam/src/v4l2loopback/v4l2loopback-dc.o] Error 1 make[1]: *** [Makefile:1429: _module_/tmp/makepkg/droidcam/src/v4l2loopback] Error 2 make[1]: Leaving directory '/usr/lib/modules/4.6.3-1-ARCH/build' make: *** [Makefile:4: all] Error 2 ==> ERROR: A failure occurred in package(). Aborting... ==> ERROR: Makepkg was unable to build droidcam.

capoeira commented on 2016-04-30 22:26 (UTC)

I get a "file or folder not found" window. clicking on ok will freeze the software. using 5.1 but writing here because discussion is here.

djmattyg007 commented on 2016-04-09 00:14 (UTC)

@AwesomeHaircut no package should ever modify anything in /home. Example configuration files belong in /usr/share. You should then add a message in a post_install() script about where to find an example config file.

CodeXYZ commented on 2016-03-09 18:57 (UTC)

@erikvanvelzen thanks it should be updated now. I didn't add the settings because aur packages shouldn't modify the ~ folder. I might be wrong though.

erikvanvelzen commented on 2015-11-15 00:35 (UTC)

Below is a diff for droidcam 6.0 (version in AUR is currently 4.1) It also creates the file ~/.droidcam/settings I hope someone can update --- PKGBUILD_old 2015-10-28 12:00:33.036382004 +0100 +++ PKGBUILD 2015-11-15 02:24:08.440670180 +0100 @@ -1,11 +1,11 @@ # Maintainer: Daniel Nagy <danielnagy at gmx de> pkgname=droidcam -pkgver=4.1 -pkgrel=2 +pkgver=6.0 +pkgrel=3 _kver="`uname -r | cut -d"." -f1,2`-ARCH" pkgdesc='A tool for using your android device as a wireless/usb webcam' -arch=('i686' 'x86_64') +arch=('x86_64') url='' license=('custom') depends=( 'bluez-libs' 'gtk2') @@ -19,15 +19,12 @@ sha1sums=( 'f85b3f34f98908bd1327df0ea0e650dcbdcb07e9') -## as of 2013-10-29 these hash sums worked. But as of 2014-02-03 somethings changed and -## the new hash sums are listed below. -## [[ "${CARCH}" = "i686" ]] && _arch="x86" && sha1sums+=('64fad1b28169f1f5a3cdd03175fac5973fe5d0ef') -## [[ "${CARCH}" = "x86_64" ]] && _arch="x64" && sha1sums+=('982ecb2fb2c30adc2fb7f3a2c250ce65b5d40777') +## as of 2015-11-11 only x64 is available for droidcam version 6.0 +# [[ "${CARCH}" = "i686" ]] && _arch="x86" && sha1sums+=('5b00632275a2c09551d1c72703732150b1f685fe') +[[ "${CARCH}" = "x86_64" ]] && _arch="x64" && sha1sums+=('0c1d6c7b0298e5ec935aa1a93a80529d8a02c9a9') -[[ "${CARCH}" = "i686" ]] && _arch="x86" && sha1sums+=('5b00632275a2c09551d1c72703732150b1f685fe') -[[ "${CARCH}" = "x86_64" ]] && _arch="x64" && sha1sums+=('79166f6439a1bebfd83c8a1190cf67065c60951e') +source+=("${_arch}.tar.gz") -source+=("${_arch}.tar.gz") package() { # Install droidcam binary file @@ -60,4 +57,8 @@ _extramodules="extramodules-$(uname -r | cut -f-2 -d'.')-$(uname -r|sed -e 's/.*-//g')" MODPATH="${pkgdir}/usr/lib/modules/${_extramodules}/" install -Dm644 v4l2loopback-dc.ko "$MODPATH/v4l2loopback_dc.ko" + + # settings file + mkdir ~/.droidcam + touch ~/.droidcam/settings }

abstrakct commented on 2015-10-29 13:15 (UTC)

@laegnur (and others): you need the correct version of linux-*-headers (matching your kernel) installed to build the v4l2loopback module - for me it was linux-ck-k10-headers.

leledumbo commented on 2015-07-01 11:50 (UTC)

> this is problematic because some people might have v4l2loopback-dkms installed Can it be made that either v4l2loopback-dkms or v4l2loopback package is installed is fine? The preference could be whatever you choose.

laegnur commented on 2015-05-27 17:18 (UTC)

I don't now why is this error. I updated the system and with the new kernel it works... :\

laegnur commented on 2015-05-27 16:42 (UTC)

==> Iniciando «package()»… make -C /lib/modules/`uname -r`/build M=`pwd` make[1]: Entering directory '/usr/lib/modules/4.0.3-1-ARCH/build' make[1]: *** No targets specified and not found makefile. Stopped. make[1]: Leaving directory '/usr/lib/modules/4.0.3-1-ARCH/build' Makefile:4: recipe for target 'all' failed make: *** [all] Error 2 ==> Error: Failed in«package()». Stopping… ==> ERROR: Makepkg was unable to build droidcam.

nagy commented on 2014-12-13 04:00 (UTC)

this is problematic because some people might have v4l2loopback-dkms installed. I think i will include a message in the post-install function.

PreparationH67 commented on 2014-12-04 18:50 (UTC)

Since this is setup to require the v4l2loopback module can that be added at a dependency or include a message that that needs to be installed?

petRUShka commented on 2014-09-11 19:16 (UTC)

Please, add message to .install file that it is necessary to create ~/.droidcam dir and ~/.droidcam/settings file. Otherwise droidcam gui will raise an "No such file" error.

nagy commented on 2014-08-28 18:58 (UTC)


jamesan commented on 2014-08-28 01:31 (UTC)

Just built this using ackalker's PKGBUILD and droidcam.install (and the OP's droidcam.desktop) to upgrade to version 4.1-1. Works like a charm without the v4l2loopback dependency.

ackalker commented on 2014-08-22 00:37 (UTC)

Forgot to add: droidcam.install: This just does a depmod with proper arguments, otherwise modinfo/modprobe might not work properly.

ackalker commented on 2014-08-22 00:32 (UTC)

There is a new version out. If you want, you can use my updated PKGBUILD: It also fixes the depends array, v4l2loopback doesn't exist as a package and isn't needed.

nagy commented on 2014-08-18 15:09 (UTC)

thank you.

petRUShka commented on 2014-08-17 15:07 (UTC)

Hello. There are two problems: 1) There is no cli version installed 2) There are errors with custom kernels like linux-pf Soultions: 1) Add `install -m755 "$srcdir"/${pkgname}-cli "$pkgdir"/usr/bin/${pkgname}-cli` 2) Replace install -Dm644 v4l2loopback-dc.ko \ "$pkgdir/usr/lib/modules/extramodules-$_kver/v4l2loopback_dc.ko" by _extramodules="extramodules-$(uname -r | cut -f-2 -d'.')-$(uname -r|sed -e 's/.*-//g')" MODPATH="${pkgdir}/usr/lib/modules/${_extramodules}/" install -Dm644 v4l2loopback-dc.ko "$MODPATH/v4l2loopback_dc.ko" whole PKGBUILD:

capoeira commented on 2014-06-18 21:48 (UTC)

so, the settings file is in /usr/share/droidcam/ it has to be moved to ~/.droidcam/

capoeira commented on 2014-06-17 12:36 (UTC)

capoeira commented on 2014-06-17 12:10 (UTC)

.droidcam es also missing....doesn't work at all - it's not in root folder, nore home

capoeira commented on 2014-06-17 11:27 (UTC)

not working ootb the dc module has to be added by hand

nagy commented on 2014-05-17 13:33 (UTC)

thanks for reporting. i have edited to PKGBUILD . can you confirm that it works now ? This package could also be adapted to use dkms instead.

test0 commented on 2014-05-16 22:56 (UTC)

systemd-modules-load is complaining in logs: "Failed to find module 'v4l2loopback_dc width=320 height=240'", and the module is not loaded at all (it is in the right place and working when loading manually with modprobe). According to module parameters, such as 'width' and 'height' should be set like 'options v4l2loopback_dc width=320 height=240' in /etc/modprobe.d/droidcam.conf, not in /usr/lib/modules-load.d/droidcam.conf directly. After moving options to modprobe.d problem is gone and $ grep "" /sys/module/v4l2loopback_dc/parameters/* /sys/module/v4l2loopback_dc/parameters/height:240 /sys/module/v4l2loopback_dc/parameters/width:320 (looks like parameters are being set correctly).

nagy commented on 2014-02-03 22:37 (UTC)

looks like they also released the source of this i will make a PKGBUILD that builds from source then.

nagy commented on 2014-02-03 22:24 (UTC)

apparently they changed something in the file v4l2loopback-dc.c. the last modification date tells 16.12.2013 . anyway, i changed the hash sums but left the old ones and also a note about it.

jamesan commented on 2014-02-03 20:23 (UTC)

The SHA-1 hashes for both 32- and 64-bit tarballs are incorrect. The upstream version hasn't changed, so I don't know what's caused the hash change.

notthesun commented on 2013-10-30 11:36 (UTC)

works good with the absolute path...thanks for the tip ;)

nagy commented on 2013-10-29 21:35 (UTC)

did you reboot ? try that and otherwise try to load the module by absolute path. dont forget the parameters. # insmod /usr/lib/modules/extramodules-3.11-ARCH/v4l2loopback_dc.ko width=320 height=240 maybe dmesg gives some errors that you can post.

notthesun commented on 2013-10-29 19:30 (UTC)

i've follow your instruction but i can't get droidcam to works...when i try to modprobe v4l2loopback_dc i get the module not found error but the module is in the right place

nagy commented on 2013-10-27 19:15 (UTC)

i finally got it to work. this definitely needs a wiki article or at least some readme. I will write it these days. in short what you have to do: after building this package... - reboot or load the modules videodev, v4l2loopback, v4l2loopback_dc by hand using modprobe. But for the v4l2loopback_dc module you need to add a "width" and "height" parameter. these can be 320x240 or more. this should give you /dev/video0 or /dev/video1 - install the app on your phone. search in the google play store for droidcam. there is a free and a paid version. both should work. - if you are in the "video" group you can do $ droidcam otherwise you will need to run it as root: # droidcam this should popup a gui in which you can enter your device's ip and port. then press connect and you should see the camera starting on your device. thats it. you can test the video using vlc for example : $ vlc v4l2:///dev/video1:width=320:height=240

nagy commented on 2013-10-10 19:20 (UTC)

it actually looks like it tries to build v4l2loopback itself, wich should be fulfilled by pulling it in as a dependency. droidcam ships with a webcam-driver that depends on v4l2loopback to register the android cam as a webcam, called "v4l2loopback-dc". i have installed the corresponding app on my phone but i have not gotten it to work yet. I need to debug this a little bit more, sorry.

Xemertix commented on 2013-10-10 12:09 (UTC)

any news? in the file "install" there are the steps needed to build the module... it seems it needs the source of v4l2loopback

nagy commented on 2013-10-05 16:20 (UTC)

i have added a systemd file and removed the old rc initscript. But i have not tested this with my phone yet. I think i will write a wiki page on how to use this properly soon.

Xemertix commented on 2013-10-05 15:27 (UTC)

please fix....

capoeira commented on 2012-12-29 02:23 (UTC)

oooooh yes, please fix

beardedlinuxgeek commented on 2012-12-05 19:59 (UTC)

Could you add an update to use systemd? I get these errors on install: /etc/rc.d/droidcam: line 3: /etc/rc.conf: No such file or directory /etc/rc.d/droidcam: line 4: /etc/rc.d/functions: No such file or directory /etc/rc.d/droidcam: line 49: stat_busy: command not found /etc/rc.d/droidcam: line 51: stat_done: command not found /etc/rc.d/droidcam: line 56: stat_busy: command not found /etc/rc.d/droidcam: line 62: stat_done: command not found /etc/rc.d/droidcam: line 3: /etc/rc.conf: No such file or directory /etc/rc.d/droidcam: line 4: /etc/rc.d/functions: No such file or directory /etc/rc.d/droidcam: line 17: stat_busy: command not found /etc/rc.d/droidcam: line 29: add_daemon: command not found /etc/rc.d/droidcam: line 30: stat_done: command not found

marquicus commented on 2012-06-28 13:49 (UTC)

fixed, thanks

zlowly commented on 2012-06-28 03:52 (UTC)

[[ "${CARCH}" = "i386" ]] && _arch="x86" && sha1sums+=('5cec41421d60eb5c32e5eab9399dd80b38a2337d') in above line, i386 should be i686.

marquicus commented on 2012-06-18 15:43 (UTC)

thank you Guixu758, updated

Guichu commented on 2012-06-17 21:38 (UTC)

UPDATE PKGBUILD: pkgver:3.5 x86 Sha1sum: 5cec41421d60eb5c32e5eab9399dd80b38a2337d x64 Sha1Sum: 770f9645fcd4fd3273fede19df6cc075e4607835

OldShatterhand commented on 2012-04-05 14:44 (UTC)

Fixed Tar-Achive with PKGBUILD, patches etc. included is available here: Seems to work so far. (Thx stomp_stopmclap for mentioning what has to be fixed)

commented on 2012-03-24 19:24 (UTC)

I fixed the earlier error from the pastebin by compiling the droidx64.tar.gz file by adding the following line into droidcam/webcam/droidcam_v4l.c: #include <linux/module.h>

commented on 2012-03-23 19:24 (UTC)

There are several errors with this package. Firstly, if the used linux kernel is not the same version as the linux-headers version, the kernel cannot compile. Secondly, in /etc/rc.d/droidcam, line 21: /sbin/insmod ${DRIVER_LOCATION}/${DROIDCAM_V4L}.ko width=${WIDTH} height=${HEIGHT} should call /usr/bin/insmod or link it if it does not exist. Kernel module cannot compile. Please find the error result here:

gbc921 commented on 2012-03-03 05:00 (UTC)

The Sha1Sum for x64 had been modified to: 74d56cd3165692aa480545e20a9a7479c0f245f1 Here is the updated PKG: By the way, the kernel module is not working yet. Thanks.

marquicus commented on 2012-01-26 14:37 (UTC)

I think it could be because the replacement of module-init-tools by knod, problem reported to

commented on 2012-01-20 18:45 (UTC)

can't compile with Linux kernel 3.2.1-1-ARCH .... Compiling Droidcam kernel module [BUSY] [DONE] :: Loading Droidcam kernel module [BUSY] insmod: can't read '/lib/modules/3.2.1-1-ARCH/kernel/drivers/media/video/droidcam_v4l.ko': No such file or directory [FAIL] cat /tmp/droidcam-install.log [code] -- INSTALL: Building DrodCam v4l driver.. make: Entering directory `/usr/src/linux-3.2.1-1-ARCH' CC [M] /usr/src/droidcam-3.2.1/webcam/droidcam_v4l.o /usr/src/droidcam-3.2.1/webcam/droidcam_v4l.c: In function 'vidioc_s_fmt_cap': /usr/src/droidcam-3.2.1/webcam/droidcam_v4l.c:266:1: warning: multi-line comment [-Wcomment] /usr/src/droidcam-3.2.1/webcam/droidcam_v4l.c: At top level: /usr/src/droidcam-3.2.1/webcam/droidcam_v4l.c:515:12: error: 'THIS_MODULE' undeclared here (not in a function) /usr/src/droidcam-3.2.1/webcam/droidcam_v4l.c:516:2: warning: initialization from incompatible pointer type [enabled by default] /usr/src/droidcam-3.2.1/webcam/droidcam_v4l.c:516:2: warning: (near initialization for '') [enabled by default] /usr/src/droidcam-3.2.1/webcam/droidcam_v4l.c:517:2: warning: initialization from incompatible pointer type [enabled by default] /usr/src/droidcam-3.2.1/webcam/droidcam_v4l.c:517:2: warning: (near initialization for 'droidcam_fops.release') [enabled by default] /usr/src/droidcam-3.2.1/webcam/droidcam_v4l.c:616:22: error: expected ')' before 'int' /usr/src/droidcam-3.2.1/webcam/droidcam_v4l.c:617:22: error: expected ')' before 'int' /usr/src/droidcam-3.2.1/webcam/droidcam_v4l.c:619:20: error: expected declaration specifiers or '...' before string constant /usr/src/droidcam-3.2.1/webcam/droidcam_v4l.c:620:15: error: expected declaration specifiers or '...' before string constant /usr/src/droidcam-3.2.1/webcam/droidcam_v4l.c:621:16: error: expected declaration specifiers or '...' before string constant make[1]: *** [/usr/src/droidcam-3.2.1/webcam/droidcam_v4l.o] Error 1 make: *** [_module_/usr/src/droidcam-3.2.1/webcam] Error 2 make: Leaving directory `/usr/src/linux-3.2.1-1-ARCH' [/code] with /etc/rc.d/droidcam setup i got: :: Removing Droidcam kernel module [DONE] :: Compiling Droidcam kernel module [DONE] BUT same error

marquicus commented on 2011-10-17 05:28 (UTC)

thanks Aerion, updated

Aerion commented on 2011-10-16 12:06 (UTC)

The dependency kernel26-headers needs to be renamed to linux-headers, following the recent name change.

marquicus commented on 2011-08-06 23:18 (UTC)


commented on 2011-08-06 22:10 (UTC)

15ea7e17d8953b69977e1f3eec818cb6 droidcam-x86.tar.gz That's the actual md5, changed it in the PKGBUILD and now it generates the package and pacman installs it. I assume that the developer made an update in his package.

commented on 2011-08-06 21:56 (UTC)

Validating source files with md5sums... droidcam-x86.tar.gz ... FAILED droidcam.rc ... Passed droidcam.desktop ... Passed install.patch ... Passed ==> ERROR: One or more files did not pass the validity check! I would be glad to help if needed, i'm newbie in arch but i want to learn, do i need to change the md5 that is in the PKGBUILD? i dont know which one is the droidcam-x86.tar.gz one or how to check the actual md5