1. Forum
  2. Usenet
  3. LINUX.DEBIAN.MAINT.KDE

  • KDE Connect started working

    From Gary Dale@21:1/5 to All on Mon Oct 10 07:10:01 2022
    I've had the kdeconnect app on my desktop and on my Samsung phone for at
    least a couple of years without ever having them able to see each other. Yesterday evening I was looking at the notices on my phone and saw that kdeconnect had found my desktop computer! It couldn't connect to it, but
    when I used my desktop to initiate the pairing, it worked.

    To be clear, all I've been doing is the normal updates (Debian/Bookworm
    & the Android phone) and haven't even looked at kdeconnect since my
    initial failure to get it to work.

    My home networking hasn't changed either. In fact it's been weeks since
    I even logged into the router.

    I'm not sure why it suddenly started working the way everyone said it
    should when I first tried it, but kudos to the developers for whatever
    they did to fix the problem I was having.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Borden@21:1/5 to All on Mon Oct 10 08:50:02 2022
    10 Oct 2022, 00:13 by gary@extremeground.com:

    I've had the kdeconnect app on my desktop and on my Samsung phone for at least a couple of years without ever having them able to see each other. Yesterday evening I was looking at the notices on my phone and saw that kdeconnect had found my desktop
    computer! It couldn't connect to it, but when I used my desktop to initiate the pairing, it worked.

    To be clear, all I've been doing is the normal updates (Debian/Bookworm & the Android phone) and haven't even looked at kdeconnect since my initial failure to get it to work.

    My home networking hasn't changed either. In fact it's been weeks since I even logged into the router.

    I'm not sure why it suddenly started working the way everyone said it should when I first tried it, but kudos to the developers for whatever they did to fix the problem I was having.

    Is it possible that your firewall reconfigured under the hood? If they couldn't see each other, that suggests a firewall blockage. Port Authority (https://f-droid.org/en/packages/com.aaronjwood.portauthority/) can tell you whether your computer is even
    discoverable. If it's not there, then that's the first place to go troubleshooting.

    If your Samsung (I'll try not to hold it against you) can find your computer's open KDEConnect port, then troubleshooting should focus on the KDEConnect settings in your Samsung (Ugh. I can feel another black mark on my soul). Some services need fiddling
    before you can use them. Others, like those that rely on Akonadi, don't work at all.

    Did I mention that I don't care for Samsung?

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Gary Dale@21:1/5 to Borden on Mon Oct 10 18:00:01 2022
    On 2022-10-10 02:42, Borden wrote:
    10 Oct 2022, 00:13 by gary@extremeground.com:

    I've had the kdeconnect app on my desktop and on my Samsung phone for at least a couple of years without ever having them able to see each other. Yesterday evening I was looking at the notices on my phone and saw that kdeconnect had found my desktop
    computer! It couldn't connect to it, but when I used my desktop to initiate the pairing, it worked.

    To be clear, all I've been doing is the normal updates (Debian/Bookworm & the Android phone) and haven't even looked at kdeconnect since my initial failure to get it to work.

    My home networking hasn't changed either. In fact it's been weeks since I even logged into the router.

    I'm not sure why it suddenly started working the way everyone said it should when I first tried it, but kudos to the developers for whatever they did to fix the problem I was having.

    Is it possible that your firewall reconfigured under the hood? If they couldn't see each other, that suggests a firewall blockage. Port Authority (https://f-droid.org/en/packages/com.aaronjwood.portauthority/) can tell you whether your computer is even
    discoverable. If it's not there, then that's the first place to go troubleshooting.

    If your Samsung (I'll try not to hold it against you) can find your computer's open KDEConnect port, then troubleshooting should focus on the KDEConnect settings in your Samsung (Ugh. I can feel another black mark on my soul). Some services need
    fiddling before you can use them. Others, like those that rely on Akonadi, don't work at all.

    Did I mention that I don't care for Samsung?

    Yes, I went through all that when I initially tried KDEconnect. I
    haven't touched the firewall since. And I haven't updated the router
    firmware. It's probable that something has changed on the phone,
    computer or both.

    It's been a weird couple of days. Yesterday, my Kodi setup on my
    Raspberry Pi fixed itself too. Again, I hadn't touched it in about a
    week but when I tried it yesterday, everything was working again.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Soren Stoutner@21:1/5 to All on Mon Oct 10 10:17:06 2022
    Copy: gary@extremeground.com (Gary Dale)

    I can't speak to why your setup hasn't been working in the past, but I can
    tell you that KDE Connect has worked for me for years between my Pixel phones and my Debian testing systems.

    On Monday, October 10, 2022 8:55:42 AM MST Gary Dale wrote:
    On 2022-10-10 02:42, Borden wrote:
    Yes, I went through all that when I initially tried KDEconnect. I
    haven't touched the firewall since. And I haven't updated the router firmware. It's probable that something has changed on the phone,
    computer or both.

    --
    Soren Stoutner
    soren@stoutner.com
    -----BEGIN PGP SIGNATURE-----

    iQIzBAABCgAdFiEEJKVN2yNUZnlcqOI+wufLJ66wtgMFAmNEU5IACgkQwufLJ66w tgOARw/+K2olKdGCaO+k3JFdurRvsMXCAfbzwlVyQEmlWRFKHqn7KlXqFYb7Hexv WqGBBpyFjGEWe+VJdt1O50YZv2ByZMbahDOS5TvY21cPGT9iRttgXuQgjYJ1xIlk F7qfov8nYRYu8BBNfhydp6e+GAWuePcKvdceKFkfT8U6bStbzIC40YA87ia8LfR4 zokLApK76HMA3Ywcw+mxyxI67y+lJ9LnCiYh0ecWhYLdDFhFpYxF0OB1VPJMyonf CcvWcn/v5Y27RAOYj53cDCOKEIckXI0QqK/zhQ05tSgTqoWg8d3Je6lLmYyy6Sui VQC4Znby1cypTgosAzBdYfOzSBUutYHRmB7ODRiMgr8JqNyZSIXSbGaUyUkkxqKq vC2g7xKTpzd9g3UDxoBgOoidcKfKeGYiu8Vi4QuZ9eeC598TUcp09k3funMqM07r xxCwAiRKLOday5LLki6Rzx1cSdVytrTDRJAG2sLgKaRYU/vmA+htRFnYhjy2//mF nFzBthZ3QjqdCtNBSet/IRyerG8e0YlpJtLJ+t7JsNHmneNGxw2nkUaIWIz2NMts OsgvBahMsnOm8uzAqIgUINFLfXjTYOr/c/nJc2dtuYyPw9JzFlKb4Rbx1ec7tZeG oIymeeSieFEfHnNvx87veUStfJ0RJh+uxRfIYIytl3XjS/MRrSE=
    =PZCZ
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Borden@21:1/5 to All on Mon Oct 10 22:10:01 2022
    10 Oct 2022, 11:55 by gary@extremeground.com:
    Yes, I went through all that when I initially tried KDEconnect. I haven't touched the firewall since. And I haven't updated the router firmware. It's probable that something has changed on the phone, computer or both.

    It's been a weird couple of days. Yesterday, my Kodi setup on my Raspberry Pi fixed itself too. Again, I hadn't touched it in about a week but when I tried it yesterday, everything was working again.

    I figured you did the obvious, but wanted to suggest it just in case. Sounds like a firewall matter to me, especially if devices are "magically" fixing themselves.

    One of the reasons I refuse to buy a Samsung phone is because they use their own firmware fiddling software instead of the perfectly usable ADB. Now that KDEConnect is (somewhat) working, are there features that aren't? I use a Pixel, so I'm curious what
    lockdowns other manufacturers might put on the OS that might affect KDEConnect.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)