UGREEN 25173 Error: VIDIOC_STREAMOFF error code 19

[Rickxbox]

First off love your work Awawa, been running HyperHDR for years now.

I've recently upgraded my system to:
-Pi 4b (had this one)
-UGREEN 25173
-EZ-SP12H21
-Adafruit ItsyBitsy RP2040 with SK6812
-HyperHDR version: 22.0.0beta1

I keep running into the same problem. The USB capture card keeps stopping for some reason i cant find. My old MS2130 in the previous setup did not have this problem. I googled the error but no solutions yet.

The error log when it happens:
2026-03-16T20:10:27.198Z [MUXER0] Set visible priority to 254
2026-03-16T20:10:27.198Z [HYPERHDR0] New priority[254], previous [240]
2026-03-16T20:10:27.198Z [COLORS0] The InfiniteProcessing is set to: disabled
2026-03-16T20:10:35.682Z [V4L2:UGREEN 25173:] Throws error nr: VIDIOC_DQBUF error. Video stream is probably broken. Refreshing list of the devices. error code 19, No such device
2026-03-16T20:10:35.683Z [V4L2:UGREEN 25173:] VIDIOC_STREAMOFF error code 19, No such device
2026-03-16T20:10:35.689Z [V4L2:UGREEN 25173:] Stopped
2026-03-16T20:10:35.690Z [V4L2:UGREEN 25173:] Found capture device: /dev/video15
2026-03-16T20:10:35.691Z [V4L2:UGREEN 25173:] Found capture device: /dev/video21
2026-03-16T20:10:35.692Z [V4L2:UGREEN 25173:] Found capture device: /dev/video14
2026-03-16T20:10:35.692Z [V4L2:UGREEN 25173:] Found capture device: /dev/video22

First I was thinking the Pi4 was not supplying enough current so i orded a PI usb hub with power.
This did not solved the problem.
The workaround to solve is to reboot the Pi or enable/disable the capture.

[awawa-dev]

Hi! I still suspect the power supply or the USB cable. I’ve been using this grabber for over a year without any issues - previously on Bookworm and now on Trixie. I don’t use a hub, just the official power supply, but USB hubs are often a source of trouble for grabbers on RPi.

The first thing you should do is check dmesg logs for any power-related warnings. Another thing is to try a different USB 3.1 cable; these grabbers (just like Elgato ones) are very picky about cable quality.

[awawa-dev]

Since restarting grabber works after it disappear for a moment, you can try 'Auto resume' option in the grabber configuration - but it's only a workaround not the proper solution.

[Rickxbox]

I'm using the official Pi supply 3A, i could get a 5A from the Pi5 but i not sure if that will supply something extra?
I will swap the USB cable again that connects to the grabber. I used the stock cable and a other spare one. Not sure if that was a 3.1 cable do.

I will do some testing and come back :)

Edit:
How do i check dmesg logs?
Is that just the logs tab in hyperhdr?

[awawa-dev]

dmesg command in the Rpi OS CLI

[Rickxbox]

Small update:
With the stock cable from the capture card there are no power errors in the dmesg log.
06:42 was the system boot time, 14:30 the error.

[Tue Mar 17 06:42:58 2026] brcmfmac: brcmf_cfg80211_set_power_mgmt: power save disabled
[Tue Mar 17 06:43:01 2026] warning: `NetworkThread' uses wireless extensions which will stop working for Wi-Fi 7 hardware; use nl80211
[Tue Mar 17 06:43:02 2026] bcmgenet fd580000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off
[Tue Mar 17 14:30:27 2026] usb 2-2: USB disconnect, device number 2
[Tue Mar 17 14:30:30 2026] usb 2-2: new SuperSpeed USB device number 3 using xhci_hcd
[Tue Mar 17 14:30:30 2026] usb 2-2: LPM exit latency is zeroed, disabling LPM.
[Tue Mar 17 14:30:30 2026] usb 2-2: config 1 has an invalid interface number: 7 but max is 4
[Tue Mar 17 14:30:30 2026] usb 2-2: config 1 has no interface number 4
[Tue Mar 17 14:30:30 2026] usb 2-2: New USB device found, idVendor=3188, idProduct=1000, bcdDevice= 1.00
[Tue Mar 17 14:30:30 2026] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[Tue Mar 17 14:30:30 2026] usb 2-2: Product: UGREEN 25173
[Tue Mar 17 14:30:30 2026] usb 2-2: Manufacturer: ITE
[Tue Mar 17 14:30:30 2026] usb 2-2: SerialNumber: 00000001
[Tue Mar 17 14:30:30 2026] usb 2-2: Found UVC 1.10 device UGREEN 25173 (3188:1000)
[Tue Mar 17 14:30:30 2026] hid-generic 0003:3188:1000.0002: hiddev96,hidraw0: USB HID v1.11 Device [ITE UGREEN 25173] on usb-0000:01:00.0-2/input7

What I did because i'm waiting for a new 3.1 cable to arrive is hook the capture card up to the usb 2.0 port on the Pi.
Its now working for 24hours. So its atleast usb3.0/cable problem. Could of-coarse still be a power problem as maby the capture card could draw more power because it has more capability on that speed.

Tomorrow I'm getting a new cable from Anker. Well see :)

[awawa-dev]

On USB 2.0, the grabber operates at half-capacity, limiting modes, formats, bandwidth and power consumption.

[Rickxbox]

So got a new cable but the problem persist. Not sure what to test next.
I can hook the grabber up to my PC and check if it keeps beeing detected.
Maby do a RMA?
Other power supply?

[Thu Mar 19 20:06:24 2026] warning: `NetworkThread' uses wireless extensions which will stop working for Wi-Fi 7 hardware; use nl80211
[Thu Mar 19 20:06:25 2026] bcmgenet fd580000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off
[Fri Mar 20 05:51:41 2026] usb 2-2: USB disconnect, device number 2
[Fri Mar 20 05:51:41 2026] xhci_hcd 0000:01:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
[Fri Mar 20 05:51:44 2026] usb 2-2: new SuperSpeed USB device number 3 using xhci_hcd
[Fri Mar 20 05:51:44 2026] usb 2-2: LPM exit latency is zeroed, disabling LPM.
[Fri Mar 20 05:51:44 2026] usb 2-2: config 1 has an invalid interface number: 7 but max is 4
[Fri Mar 20 05:51:44 2026] usb 2-2: config 1 has no interface number 4
[Fri Mar 20 05:51:44 2026] usb 2-2: New USB device found, idVendor=3188, idProduct=1000, bcdDevice= 1.00
[Fri Mar 20 05:51:44 2026] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[Fri Mar 20 05:51:44 2026] usb 2-2: Product: UGREEN 25173
[Fri Mar 20 05:51:44 2026] usb 2-2: Manufacturer: ITE
[Fri Mar 20 05:51:44 2026] usb 2-2: SerialNumber: 00000001
[Fri Mar 20 05:51:44 2026] usb 2-2: Found UVC 1.10 device UGREEN 25173 (3188:1000)
[Fri Mar 20 05:51:45 2026] hid-generic 0003:3188:1000.0002: hiddev96,hidraw0: USB HID v1.11 Device [ITE UGREEN 25173] on usb-0000:01:00.0-2/input

[awawa-dev]

It would be a good idea to test this on a Linux PC. That way, you can rule out the Raspberry Pi's power supply if it crashes there too. Theoretically, it could be a kernel issue, but I haven't seen this behavior on my end on either Bookworm or Trixie.

[ToncTheBaldie-max]

Hey @awawa-dev same thing just happened to me. I was running a version 21.0 until I decided today to update to newest version. The moment I updated it I lost the ability on video capture to choose my UGREEN 25173. It just stays on automatic and hyperhdr isn't detecting the capture card? I reinstalled the new version a couple of times and unplugged everything and replugged and it's still not showing? Any ideas on what it could be?

[awawa-dev]

Latest RPI OS (21-04-2026) works fine for my ugreen. SD image has been just released today for HyperHDR v22beta2.

[ToncTheBaldie-max]

Awesome I think my SDcard may have been faulty it's all back up and running now 🙌

[Rickxbox]

I have little experience with Linux/Debian. I will try to install Debian/Trixie on a different system and see what happens.