https://bugs.kde.org/show_bug.cgi?id=441830
--- Comment #11 from Maxim Egorushkin <maxim.yegorush...@gmail.com> --- (In reply to Simon Redman from comment #8) > (In reply to Maxim Egorushkin from comment #5) > > The developers must provide justification for these rather frequent TCP > > keepalive messages when communicating with battery-powered devices. > > As in the PR vladikss linked: If the keepalive is set higher, it will > falsely tell users that the phone is connected when it is in fact not. The problem the desktop kdeconnect tries to solve with its uber-frequent TCP keep-alives is detecting whether the user mobile device is still connected or not. That's a genuine and common problem, and it has long been solved. The uber-frequent TCP keep-alives kdeconnect uses to solve this recurrent problem isn't the right solution or best practice, precisely because it drains mobile device battery. There are different solutions for this problem in different mobile OSs. kdeconnect authors should use those, instead of spamming those battery draining incessant TCP keep-alives. Numerous messenger apps solve this problem, none drains the battery as bad as kdeconnect does. > Please do the test as requested by vladikss. Without some evidence that a > change actually makes a difference, it's just a random number. I am not the author, maintainer or QA of kdeconnect. That's why vladikss' request to expend my time and effort to do tests or experiments for him sounds rather wild to me. I have taken the time to provide an accurate description of the problem, root cause analysis and a working solution. That's the best I can do for kdeconnect. Conceptually, I have shown you the light. Whether to follow the light or stay in the dark is up to kdeconnect authors and maintainers. I don't care if they prefer staying in the dark. -- You are receiving this mail because: You are watching all bug changes.
