Maciek Borzecki c252180609 | 7 years ago | |
---|---|---|
extra | 7 years ago | |
src | 7 years ago | |
test | 8 years ago | |
.dir-locals.el | 8 years ago | |
.gitignore | 10 years ago | |
.travis.yml | 8 years ago | |
LICENSE | 10 years ago | |
Makefile.am | 8 years ago | |
README.md | 7 years ago | |
configure.ac | 9 years ago | |
gdb-script.in | 8 years ago | |
mconnect.conf | 10 years ago | |
mconnect.desktop.in | 10 years ago | |
mconnect.spec | 10 years ago |
mconnect - KDE Connect protocol implementation in Vala/C
GLib and Gio should be available even on trimmed down systems. Vala is really needed only at build time. OpenSSL does the packet encryption/decryption at the protocol level, while Json-glib does packet parsing. Libnotify is responsible for displaying shell popups.
Build dependencies (using package names as found in Fedora):
or see extra/travis-build
in the source tree for example installation
commands. Once build deps are in place, run:
autoreconf -if
./configure --prefix=<your favorite prefix>
make
make install
# or make DESTDIR=<somedir> install if you want to inspect what
# gets installed
NOTE: manual configuration file is no longer needed
A sample configuration file is provided in source tree, see
mconnect.conf
. It will get installed to ${datadir}/mconnect/
(usually corresponding to /usr/share/mconnect/
) by default. Once
mconnect
starts it will pick the default file and make a copy of it
in user's config directory, specifically ~/.config/mconnect/
.
A device described in it's own group and listed in main.devices
, has
to match exactly with incoming identity packets. However, since
deviceId
is not known beforehand, neither shown in KDE Connect
Android application, only name
and type
are used for matching.
mconnect comes are 2 separate programs, the daemon - mconnect
and a D-Bus
client mconnectctl
.
Start it by running:
$ mconnect -d
The daemon starts listens on 0.0.0.0:1714
for incoming UDP packets. Once an
identity packet (a sort of a handshake) is received, a connection to the
sender's address will be made. Known devices are cached in
~/.cache/mconnect/devices
.
List discovered devices:
$ ./mconnectctl list-devices
Devices:
/org/mconnect/device/0 673ac2db27d2a331 - Motorola Moto G Maciek
Accept a device (previously done only through the configuration):
$ ./mconnectctl allow-device /org/mconnect/device/0
Show device details:
$ ./mconnectctl show-device /org/mconnect/device/0
Device
Name: Motorola Moto G Maciek
ID: 673ac2db27d2a331
Address: 192.168.1.103:1716
Type: phone
Allowed: true
Paired: true
Active: true
Connected: true
The API is not documented. Use D-Feet or busctl to introspect and invoke methods manually.
A Gnome Shell extension is available here: https://github.com/andyholmes/gnome-shell-extension-mconnect or via the GNOME extensions page: https://extensions.gnome.org/extension/1272/mconnect/
It may be required to either temporarily disable the firewall or open up UDP port 1714.
An example service definition for firewalld is
provided in extra/firewalld/mconnect.xml
directory. The file needs to be
copied into /etc/firewalld/services
.