KDE Connect instead of a mouse, or the pitfalls of the first connection

It turned out that I was on a trip, and in order to pass the time, I took my old faithful friend with me - a netbook ASER Aspire one AOA110 с #!++ on board.

Since I haven’t used it for a very long time, I completely forgot about the faulty touchpad cable.
Of course, I didn’t take a mouse with me, but I really wanted to use the browser comfortably, and I decided to use the application KDE Connect as an alternative to the mouse. It would seem that everything is simple: install the application on both devices, get connected - and use it to your health. But it was not there ... In general, first things first.

Install and launch the application from the Play Market on the smartphone

KDE Connect (screenshot)

Install and run the application on a netbook:

sudo apt install kdeconnect
kdeconnect-indicator

We connect devices (IMPORTANT!) to the same local network. It doesn’t matter if it’s wi-fi or a USB connection (my smartphone was a USB modem for a netbook).

We run kdeconnect-indicator in the console, update the list of available devices on the phone - and ...

Nothing... (screenshot)

Google helps me find answer: regular firewall, included in advance by me and forgotten. I disable it as unnecessary. Who needs to leave the firewall turned on.

sudo ufw disable

And we see that the netbook appeared in the list of available devices. (screenshot)

Select your device and click "Request pairing".

We send a pairing request - and see on the netbook monitor:

pairing request:(screenshot)

We see it, but we can’t do anything - the buttons are not switched / activated by TAB, as well as by other keys.

Application developers provide for pairing using a console application

kdeconnect-cli -a 

gives us a list of available devices in the form:
- Galaxy A3: lij7dc380v8f1000 (in touch)

kdeconnect-cli --pair -d id

then we confirm the pairing on the smartphone and use the functions of the application.
But this is not about my #!++ - only paired devices are displayed in it, perhaps everything is due to the old version of kdeconnect-cli 1.3.3.

In general, I learned about the tool xdotol (his Mon) and decided to use it - we need two actions from it:

# - переместить курсор на координаты XXX YYY
xdotool mouse XXX YYY

# - кликнуть левой кнопкой "Принять"
xdotool click 1 

It remains to pick up XXX and YYY… (screenshot)

To see the position of the cursor, click on context menu key and use the application function we need.

Thank you for your attention, I hope this information will help to avoid similar problems.

Source: habr.com