https://bugs.kde.org/show_bug.cgi?id=520578
--- Comment #5 from thexwarr1orsxneo <[email protected]> --- (In reply to Rob Emery from comment #4) > For clarity: > > Intel Dual Band Wireless-AC 7260 -- Bluetooth 4.0 > Realtek RTL8771B Bluetooth Radio -- not sure, could be 5.2, info is sketchy > on that. > TP-Link Bluetooth 5.3 UB5A -- Bluetooth 5.3 > > Do you have a method of getting numbers with regards to the jitter/latency > etc that can show a clear difference between kdeconnectd running vs not? > > I ask because I use a UB5A as my daily-driver bluetooth dongle and using > either my Gulikit NS09 or PS4 controller, I am unable to tell between > kdeconnect with bluetooth enabled vs kdeconnectd stopped. Similarly `evtest` > doesn't show any stutters or glitches in the output, just consistent > returning of results. > > If I play a game, I can't tell between kdeconnectd + bluetooth enabled vs it > stopped either, which makes me think that either I am not experiencing the > issue for some reason or I am not sensitive enough to the behaviour. From > the description it sounds like the latency is so bad that anyone would > obviously notice it, which leans towards the former. With the original DualShock 4, there isn't much input lag using the bluetooth UB5A it's still playable, but minimal jitter it's there. And the jitter is more noticeable with other controllers, especially Chinese and generic ones jitter unplayable I tried with checking the polling rates: https://github.com/marcoster/evhz https://controllertest.io -- You are receiving this mail because: You are watching all bug changes.
