[opensuse] KDE Connect
If you run KDE and have an Android phone, and you haven't heard about this little gem you might want to look into it. Free app for the phone, and a plugin to the KDE system settings panel. I run it on KDE 4.xx on OS 13.2 as well as on KDE5/Plasma 5 on Manjaro Linux. Very slick for sending files, and not having to reach for your phone just see who is sending you messages, clipboard integration, and it even mutes your music on the computer when your phone rings. -- After all is said and done, more is said than done. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
John Andersen <jsamyth@gmail.com> 12/30/15 4:11 PM >>> If you run KDE and have an Android phone, and you haven't heard about this little gem you might want to look into it. Free app for the phone, and a plugin to the KDE system settings
Out of curiosity, do you have to do anything special to get them to connect up? I've got KDE Connect installed on my Galaxy S5 (Lollipop) and oS 13.1 laptop, connected to the same wireless network (no firewall running on the computer during testing just to be safe,) but they don't seem to see each other, even if I manually enter their respective IP addresses. Chris panel. I run it on KDE 4.xx on OS 13.2 as well as on KDE5/Plasma 5 on Manjaro Linux. Very slick for sending files, and not having to reach for your phone just see who is sending you messages, clipboard integration, and it even mutes your music on the computer when your phone rings. -- After all is said and done, more is said than done. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Christopher Myers <cmyers@mail.millikin.edu> [01-11-16 11:21]:
Out of curiosity, do you have to do anything special to get them to connect up? I've got KDE Connect installed on my Galaxy S5 (Lollipop) and oS 13.1 laptop, connected to the same wireless network (no firewall running on the computer during testing just to be safe,) but they don't seem to see each other, even if I manually enter their respective IP addresses.
Chris
John Andersen <jsamyth@gmail.com> 12/30/15 4:11 PM >>> If you run KDE and have an Android phone, and you haven't heard about this little gem you might want to look into it. Free app for the phone, and a plugin to the KDE system settings panel.
I run it on KDE 4.xx on OS 13.2 as well as on KDE5/Plasma 5 on Manjaro Linux. Very slick for sending files, and not having to reach for your phone just see who is sending you messages, clipboard integration, and it even mutes your music on the computer when your phone rings.
I have it connected on my desktop tumbleweed but cannot get it connected on my toshiba laptop, also tw. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/11/2016 08:19 AM, Christopher Myers wrote:
Out of curiosity, do you have to do anything special to get them to connect up? I've got KDE Connect installed on my Galaxy S5 (Lollipop) and oS 13.1 laptop, connected to the same wireless network (no firewall running on the computer during testing just to be safe,) but they don't seem to see each other, even if I manually enter their respective IP addresses.
Chris
No, I didn't have to do anything but install kde connect on my Opensuse box and my Manjaro (arch) box and connection was instant once I turned it on from kde "config desktop" panel. (aka "system settings" on some versions of kde. My Opensuse is KDE 4.14.9 Manjaro is KDE Framework 5.17 - aka Plasma5). I did not have to manually enter my linux boxes via manual IP. The Android app found them automatically, they appear and disappear from the available connection list on the android app almost instantly as they appear on the network. _NOTE:_ The Android kde-connect app also finds other android devices running the KDE Connect app on the same network and you can also pair with them, and send files, and urls, etc. You of course have to accept pairing on the target device the first time, whether that device is android or linux. While I can pair two Linux machines through KDE Connect, there doesn't seem to be any functionality between the the two. You can't even ping each other from the Config Desktop panel in KDE. I've connected with two different mobile devices to the same opensuse machine at the same time. I've connected with an HTC phone and an Acer Tablet - Both running different versions of Android. I've used both wired connections on the linux box, as well as wifi, and I've even switched from wired to wifi and back again and the connections re-established themselves. Some people reporting issues seem to be on Samsung devices. There might be some sort of firewall in the samsung that prevents connection. I don't know, as I don't have a samsung device to test with. My internal network (wired and wifi) is ipv4 only. After you do make a connection from the phone to kde-connect, Do go to Start-gecko, config Desktop, and Open KDEConnect which should appear in the hardware section, and check those things you want allow for each such connection. KDEConnect shows up in SuseFirewall in the pull-down list of services you can allow. When susefirewall is running, it will block kdeconnect unless/until you make that adjustment, and add it to the allowed list. Once that is done, it works fine. I've tested both with and without susefirewall turned on. kdeconnect listens on port 1714, but will quickly move connections off of that port once you accept pairing requests on the linux box. (You do have to be watching the linux box and accept pairing when you first attempt to connect). Port 1714 appears to be officially reserved for instant messageing use. https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xhtml?&page=30 -- After all is said and done, more is said than done. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Awesome, thanks much! After I assigned a sticky IP address on our DHCP server for my laptop's wireless connection and verified that the port was open on my laptop, I was able to manually enter the sticky IP on my phone, and after doing that, it was able to see my laptop and pair successfully. Seems really cool! :D Love the "remote touchpad/keyboard" functionality too! -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/11/2016 11:52 AM, Christopher Myers wrote:
Awesome, thanks much!
After I assigned a sticky IP address on our DHCP server for my laptop's wireless connection and verified that the port was open on my laptop, I was able to manually enter the sticky IP on my phone, and after doing that, it was able to see my laptop and pair successfully.
Seems really cool! :D Love the "remote touchpad/keyboard" functionality too!
One of my linux machines has specific IP addresses assigned in the dhcp server, but the others don't, and it works the same on either. Neither of the Android devices are. I can't think of any obvious reason you would want/have to pair via manual IP entry if everybody is truly on the same subnet. Very strange. -- After all is said and done, more is said than done. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Hmm, the only reason I can think of is that our wireless vlan is a class B (several thousand wireless clients,) so maybe it's just too big to scan? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/11/2016 12:22 PM, Christopher Myers wrote:
Hmm, the only reason I can think of is that our wireless vlan is a class B (several thousand wireless clients,) so maybe it's just too big to scan?
I thought it was message based (advertised), rather than scan based. But quite franky, I don't know. Wireless Vlans often have some peer-to-peer filtering built in, precisely to cut down on the chatter traffic from windows machines, or to prevent hack attacks across the wifi. Especially when you have multiple APs needing to re-broadcast chatter it can kill networks. -- After all is said and done, more is said than done. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* John Andersen <jsamyth@gmail.com> [01-11-16 14:42]: [...]
Some people reporting issues seem to be on Samsung devices. There might be some sort of firewall in the samsung that prevents connection. I don't know, as I don't have a samsung device to test with.
My internal network (wired and wifi) is ipv4 only.
After you do make a connection from the phone to kde-connect, Do go to Start-gecko, config Desktop, and Open KDEConnect which should appear in the hardware section, and check those things you want allow for each such connection.
KDEConnect shows up in SuseFirewall in the pull-down list of services you can allow. When susefirewall is running, it will block kdeconnect unless/until you make that adjustment, and add it to the allowed list. Once that is done, it works fine. I've tested both with and without susefirewall turned on.
Thankyou, that was the missing piece for my toshiba laptop. I had forgotten about the requirement to open the firewall for kdeconnect. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Mon, Jan 11, 2016 at 9:39 PM, John Andersen <jsamyth@gmail.com> wrote:
Some people reporting issues seem to be on Samsung devices. There might be some sort of firewall in the samsung that prevents connection. I don't know, as I don't have a samsung device to test with.
I have Galaxy S4. Tried KDE Connect and it works partially... That is, remote input from telephone works (why could it be needed?) but files are not sent fully. I tried a number of times and after 85-95% of the file the transfer stopped. I'm using AirDroid application to up- and down-load files to/from telephone. It seems working for me (you connect to the telephone from your browser over local network) -- Mark Goldstein -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/12/2016 10:56 AM, Mark Goldstein wrote:
On Mon, Jan 11, 2016 at 9:39 PM, John Andersen <jsamyth@gmail.com> wrote:
Some people reporting issues seem to be on Samsung devices. There might be some sort of firewall in the samsung that prevents connection. I don't know, as I don't have a samsung device to test with.
I have Galaxy S4. Tried KDE Connect and it works partially... That is, remote input from telephone works (why could it be needed?) but files are not sent fully. I tried a number of times and after 85-95% of the file the transfer stopped.
I'm using AirDroid application to up- and down-load files to/from telephone. It seems working for me (you connect to the telephone from your browser over local network)
Two things to check... One is that your phone goes to sleep (screen off) at about that time, and settings in the phone cause it to drop wifi as some sort of ill-conceived power saving measure. Two is that you didn't click the little wrench symbol in the kde-connect settings panel in config desktop KDE Connect settings on Linux. I routinely move files (images mostly) this way from the phone. -- After all is said and done, more is said than done. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Mark Goldstein <goldstein.mark@gmail.com> [01-12-16 13:59]:
On Mon, Jan 11, 2016 at 9:39 PM, John Andersen <jsamyth@gmail.com> wrote:
Some people reporting issues seem to be on Samsung devices. There might be some sort of firewall in the samsung that prevents connection. I don't know, as I don't have a samsung device to test with.
I have Galaxy S4. Tried KDE Connect and it works partially... That is, remote input from telephone works (why could it be needed?) but files are not sent fully. I tried a number of times and after 85-95% of the file the transfer stopped.
I also have S4 and works-for-me ???
I'm using AirDroid application to up- and down-load files to/from telephone. It seems working for me (you connect to the telephone from your browser over local network)
Amoung a few others, AirDroid appears best or at leas5 as-good-as ... But kdeconnect is still handiest as "It is always there". -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (4)
-
Christopher Myers -
John Andersen -
Mark Goldstein -
Patrick Shanahan