https://bugs.kde.org/show_bug.cgi?id=441830
Maxim Egorushkin <maxim.yegorush...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |n...@kde.org
--- Comment #5 from Maxim Egorushkin <maxim.yegorush...@gmail.com> ---
(In reply to valdikss from comment #4)
> (In reply to Maxim Egorushkin from comment #3)
> > A workaround to configure TCP keepalive timeout for kdeconnectd until the
> > application makes this timeout configurable:
> > https://github.com/max0x7ba/kdeconnect-powersave-keepalive
>
> Could you please make a test of cellphone battery consumption with 5 second
> keep-alives vs longer keep-alives please?
The developers must provide justification for these rather frequent TCP
keepalive messages when communicating with battery-powered devices. Without
justification I consider this hard-coded 5-second TCP keepalive timeout
leftover debugging code that the developers forgot to remove.
There is no value for this timeout which works for any and all use cases. This
timeout must be user-configurable.
> I was asked to justify the modification in
> https://invent.kde.org/network/kdeconnect-kde/-/merge_requests/
> 447#note_388849, but always forgot to make a clean test.
I cannot do that for you, I am sorry.
IMO, it is rather the authors who must justify the rather short TCP keepalive
timeout and prove that it doesn't result in increased battery drain.
--
You are receiving this mail because:
You are watching all bug changes.
