How to compile kdeconnect from github so that it works?

Question

linux

The kdeconnect-kde directory contains the downloaded sources from the github (belated mirror of Ked's reps)
What I do:
$ cd kdeconnect-kde
$ mkdir build
$ cmake -DQT_QMAKE_EXECUTABLE=/usr/bin/qmake-qt5 -DCMAKE_INSTALL_PREFIX=$(kde4-config --prefix) ./build/
$ cd build
$ make
$ make install
$ ./daemon/kdeconnectd &
Next, I try to connect the phone to the computer using a running daemon and an application on the phone (from the play market). It connects wonderfully, and you can safely do pair and unpair, without a single lag. But! None of the plugins (even ping) work! They seem to disappear into the void. Those. try:
$ ./cli/kdeconnect-cli -d XXXXXXXX --ping
Will be futile, but without a single error message. If you put the application from the debian rep (kdeconnect) and connect with it, then everything works fine. Sinned for any incompatibility in versions and downloaded kdeconnect-android. Compiled, made an APK package. Dropped it on the phone. On the computer at that time there was an application from rap. The same problem. There is a connection, plugins do not work. The plug-in for managing the player partially works (the phone sees which player is running on the computer, but cannot control it). Changing the application on the computer to a freshly compiled one also does not help. Some Beliberda. I'm clearly missing something else that these apps can't run without.
Computer config :
Debian sid
$ uname -a
Linux LIN2 4.5.0-2-amd64 #1 SMP Debian 4.5.3-2 (2016-05-08) x86_64 GNU/Linux
#UPD1
Collected tags 0.9g for a computer and for a phone. The situation is the same. This version should be working. in the turnips are the same versions, specially checked. The same version is in the play store.
#UPD2 Compiled
an application for the phone from the official ked repository with the v0.9g tag. On the computer, there was an application from debian rep (not compiled by me). Works! To check modified the line "Ping!" on your own and everything is as it should! The problem is localized in the desktop part. Since the build is successful, you need to look for the problem in "make install" or something else.