As @anon88919003 said, I’ve been testing the kernel module and the grabber it’s detected but does not show any input while trying to capture an screenshot. I expect to test it thoroughly during the weekend.
I’m testing it on a S905 device with a Fushicai grabber, so I cannot test STK1160, but If you want to check if it works on yours, here’s a link to an update file with the kernel module based in latest master. S905 only, do not install it in other devices!
Try adding an udev rule to assing your device to /dev/video0
Run:
CoreELEC:~ # lsusb
Bus 001 Device 004: ID 2341:8036 Arduino SA Leonardo (CDC ACM, HID)
Bus 001 Device 003: ID 1997:2433
Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 002: ID 1b71:3002 Fushicai USBTV007 Video Grabber [EasyCAP]
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Note down your device ID, in this case 1b71:3002
Create a udev rule file, ie: /storage/.config/udev.rules.d/25-video-device.rules and add the following content changing your particular device IDs
just tried that but still no video0 device.
here my lsusb output:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 05e1:0408 Syntek Semiconductor Co., Ltd STK1160 Video Capture Device
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
i think the stk1160 module is missing which was in earlier version included in the hauppage driver add-on.
a modinfo usbtv just give me Fushicai USBTV007:
filename: /lib/modules/3.14.29/kernel/drivers/media/usb/usbtv/usbtv.ko
license: Dual BSD/GPL
description: Fushicai USBTV007 Video Grabber Driver
author: Lubomir Rintel
alias: usb:v1B71p3002ddcdscdpiciscipin
depends: videobuf2-core,videodev,videobuf2-vmalloc,v4l2-common
intree: Y
vermagic: 3.14.29 SMP mod_unload aarch64
It helps indeed, I’ll take a look into it. Unfortunately the kernel driver and the one in dvb-latest are different versions, hence the lack of support for your hardware on 3.19. The newer one crashed on my hardware.
Would you mind to test this other build with module from dvb-latest and PM me with dmesg and hyperion logs?
Drivers are not enabled on nightly builds, as they don’t fully work. However I could share one of my personal builds if you’re interested on testing it. Driver loads and capture device is recognized by Hyperion but I couldn’t get it capturing anything
Are there any news?
I have an Fushicai UTV007 and an STK1150 USB Video Grabber. I tried them both with Coreelec 9.0.2 stable, and nightly 20190519, with all three DVB drivers on my Odroid C2, but no combination showed a /dev/video0 output…
Anything else, I could try?
It would be nice, to have a grabber working with ambilight^^
i have to update my C2. For now Libreelec 8 is installed, because for me it is nessessary to have a working “Fushicai USBTV007 Video Grabber [EasyCAP]” or “STK1150 USB Video Grabber”.
Have anyone succses to get the “Video Grabber” working?
Same here. I just moved from libreElec (Raspberry pi3) To odroid n2.
Ambilight works fine with internal grabber and apa102 leds connected to an arduino.
I want to have ambilight on external sources. Are there any news about this problem ?
CoreELEC:~ # lsusb
Bus 002 Device 002: ID 05e3:0620 Genesys Logic, Inc.
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 1b71:3002 Fushicai USBTV007 Video Grabber [EasyCAP]
Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
i think the problem is hyperion.ng !
i tried with normal hyperion and there the external grabber worked, but internal grabber made problems.
You all know that the hyperion.ng + Amlogic issue got solved a while ago?
I am not the developer of hyperion.ng so you may have to take a look to the hyperion forum.
I guess the external grabber is just not ported to hyperion.ng.
hmm ok maybe i need the newest hyperion.ng version.
How can i check what hyperion.ng version i have ?
i installed hyperion.ng from the coreELEC Repository. how is it workling ? when the hyperion.ng team releases a new version…do you have to update the addon in coreELEC? Or does the addon get automatically the newest version?
A pity, I can’t get the grabber to run with the stable one or with the nightly one. Therefore Hyperion cannot be used with CoreElec at the moment. Maybe you should post this directly on the website coreelec.org, then I would have saved my time. So I say goodbye and go back to libreelec. Maybe I should use my RPI3 instead of the Odroid C2 again.