KDEConnect: Difference between revisions
m (Add link to Chrome extension) |
Albertvaka (talk | contribs) |
||
| Line 38: | Line 38: | ||
=== My KDE Connect crashes or restarts when trying to pair with another device === | === My KDE Connect crashes or restarts when trying to pair with another device === | ||
Some times, a corrupt config file may cause KDE Connect to crash when trying to pair with a device. In that case, deleting the config | Some times, a corrupt config file may cause KDE Connect to crash when trying to pair with a device. In that case, deleting the config ~/.config/kdeconnect might help. | ||
=== Can I run KDE Connect without a display server? === | === Can I run KDE Connect without a display server? === | ||
Revision as of 21:18, 12 February 2017
This is the comunity page for KDE Connect. It should contain useful and up to date resources for both users and developers.
What is KDE Connect?
KDE Connect is a project that aims to communicate all your devices. For example, with KDE Connect you can receive your phone notifications on your computer, or just use your phone as a remote control for your desktop. To achieve this, KDE Connect implements a secure communication protocol over the network, and allows any developer to create plugins on top of it. Currently there are KDE Connect clients on KDE, Android and Blackberry, and soon we will support iPhone as well.
Some other cool features in video: https://www.youtube.com/watch?v=KkCFngNmsh0
More info at: http://albertvaka.wordpress.com
Installation
You will most likely find KDE Connect as a package in your distribution's repos. If you use desktop environment other than KDE's Plasma, you might also want to install indicator-kdeconnect, that provides a system tray as a GUI for other desktops.
The app for Android can be found in both the Google Play Store and the free store F-Droid.
If you are a Firefox user, this cool extension might be of your interest.
If you are a Chrome/Chromium (or compatible) user, this extension might be of interest, see the Github page for installation instructions.
Troubleshooting
I have two devices running KDE Connnect on the same network, but they can't see each other
KDE Connect uses dynamic ports in the range 1714-1764 for UDP and TCP. So if you are behind a firewall, make sure to open this port range for both TCP and UDP. Otherwise, make sure your network is not blocking UDP broadcast packets.
ufw
If your firewall is ufw, you can open the necessary ports with:
sudo ufw allow 1714:1764/udp
sudo ufw allow 1714:1764/tcp
sudo ufw reload
Fedora firewall
In Fedora there is a program to configure the firewall. Open Firewall Configuration (the program's filename is firewall-config), and in Zones > Services check the kde-connect service.
My KDE Connect crashes or restarts when trying to pair with another device
Some times, a corrupt config file may cause KDE Connect to crash when trying to pair with a device. In that case, deleting the config ~/.config/kdeconnect might help.
Can I run KDE Connect without a display server?
Yes, you can pass the command line argument `-platform offscreen` to the daemon (eg: `killall -9 kdeconnectd; /usr/lib/libexec/kdeconnectd -platform offscreen`)
My problem is not in this list :(
In case you find a bug and want to report it, you can do so in the KDE bugtracker: http://bugs.kde.org
Development
If you are interested in contributing to KDE Connect, please join the mailing list of the project. You might also want to read Albert Vaca's development blog.
You can find the sources in the following repositories: