https://bugs.kde.org/show_bug.cgi?id=513536
[email protected] changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #35 from [email protected] --- KDE Connect's bluetooth backend's "on by default" behavior might be causing more issues than its worth for the majority of KDE users. Not only did `kdeconnectd` bluetooth scanning cause audio issues on my system, but also seriously interfered with my connection to a wifi AP and degraded the throughput by an order of 10. Judging by the bugs on this tracker surrounding this particular backend it may be worth exploring an approach where bluetooth support could be explicitly enabled, with some sort of post-installation popup for users explaining that this requires constant scanning to function (not unlike the popup for new plasma releases). Keeping this in the background is leading to system behavior that is egregiously difficult for a non-technical user to diagnose. Additionally, the regression from 25.12.1 seemingly not respecting configuration options correctly is making this even worse for users of KDE Connect (see: https://bugs.kde.org/show_bug.cgi?id=516170, the proposed commit reversal should be looked at, as this still persists in 26.04.1). It would not surprise me to see some distributions patch this manually and simply disable the backend by default, which would be an unfortunate outcome given that KDE wants this functionality exposed enough to not have to dig through configuration files to enable it. -- You are receiving this mail because: You are watching all bug changes.
