You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm getting some strange video freezing every few seconds in H.264 mode. It's smooth for about 10 seconds, and freezes for 2-3 seconds, and then repeats. In MJPEG mode, everything is just very choppy.
My network connection is perfectly fine, ping times are well under 10ms. Also, it used to work fine in December, before I updated to 2.1.5 earlier today, I think. Here's the version details:
Image Version v1.3.0
Application Version 2.1.5
dmesg shows a lot of messages like:
[ 677.118828] configfs-gadget gadget: usb_gadget_wakeup
[ 677.118936] dwc2 4340000.usb: wakeup: signalling skipped: is not allowed by host
[ 677.118949] configfs-gadget gadget: usb_gadget_wakeup
[ 677.182376] dwc2 4340000.usb: wakeup: signalling skipped: is not allowed by host
[ 677.182393] configfs-gadget gadget: usb_gadget_wakeup
[ 677.182478] dwc2 4340000.usb: wakeup: signalling skipped: is not allowed by host
[ 677.182489] configfs-gadget gadget: usb_gadget_wakeup
Is there a way to downgrade back to 2.1.2 or 2.1.3 to test it?
The text was updated successfully, but these errors were encountered:
li20034
changed the title
Strange Video Freezing
Strange Video Freezing in H.264 mode
Jan 24, 2025
Thank god I'm not crazy. I just got NanoKVM and been having the same issue. H264 a lot of times black screen and when it does load, it seems to freeze after few seconds and unfreezes on repeat. MJPEG always loads but it's rly laggy and even showing around 10 FPS. I've also fully reflashed sdcard that came with it.
I'm getting some strange video freezing every few seconds in H.264 mode. It's smooth for about 10 seconds, and freezes for 2-3 seconds, and then repeats. In MJPEG mode, everything is just very choppy.
My network connection is perfectly fine, ping times are well under 10ms. Also, it used to work fine in December, before I updated to 2.1.5 earlier today, I think. Here's the version details:
dmesg shows a lot of messages like:
Is there a way to downgrade back to 2.1.2 or 2.1.3 to test it?
The text was updated successfully, but these errors were encountered: