Luckfox Forums

Hey guys, received my picoKVM full (8GB EMMC) and updated to the latest firmware (app 0.1.3 sys 0.1.7) and began testing. I have noticed a few bugs that are serious enough to need a fix. First off my environment;
Network: Gigabit LAN (both KVM and Mac / Linux client)
Firmware: app 0.1.3 sys 0.1.7
Settings: 1080p 60 (also tested 720p no difference), quality medium, h264 and h265 tested, with and without USB audio enabled.
Note: In the screeshots you can see the target device was a nintendo switch, however I did also test with a windows laptop and it was the same.
KVM starts off with a 8-10% cpu use on boot then when first connected immediately goes to 100% CPU with about 83% RAM use. At the beginning connection is stable enough with minimal lag then over the next 5 minutes round trip begins spiking to 400-600ms even and kvm becomes unusable. This is with both h264 and h265 with quality sliders set to the middle(forcing http made no difference). Enabling USB Audio makes things even worse with video cutting completely out after 2 minutes or so. The PicoKVM display shows 100% CPU this entire time with the web interface itself becoming disconnected after a while. Tested on Both my Mac and linux laptops on chrome, brave and safari so this is not a browser issue. As you can see in the screenshots round trip and frame rate become terrible not long after running. What's also interesting even when the HDMI device goes to sleep the KVM remains at 100% cpu use and stays hot (~70) degrees. Have attached that picture too.

Thanks for your feedback. We've preliminarily confirmed the issue. The increased CPU usage during front-end input was caused by monitoring feedback for all operations in the last update to ensure stable HID response. A fix will be pushed within this week.
Also note that enabling USB audio increases latency due to the lack of hardware audio encoding on the main controller — it raises CPU usage, and latency is increased to maintain A/V sync.

Crocodile wrote: ↑2026-06-22 1:50

Thanks for your feedback. We've preliminarily confirmed the issue. The increased CPU usage during front-end input was caused by monitoring feedback for all operations in the last update to ensure stable HID response. A fix will be pushed within this week.
Also note that enabling USB audio increases latency due to the lack of hardware audio encoding on the main controller — it raises CPU usage, and latency is increased to maintain A/V sync.

Thank you! Look forward to the next update. Also helpful to know reg audio