This forum has been archived. All content is frozen. Please use KDE Discuss instead.

KDE connect cannot detect my phone

Tags: None
(comma "," separated)
eugdr
Registered Member
Posts
4
Karma
0

KDE connect cannot detect my phone

Thu Apr 18, 2019 1:14 am
Hello
I installed KDE connect on my linux box (UBUNTU 16.04 LTS with Unity)
uname -a
Linux <hostname> 4.13.0-32-generic #35~16.04.1-Ubuntu SMP Thu Jan 25 10:13:43 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
KDE connect indicator version is 0.1-0~41~ubuntu16.04.1 from LP-PPA-vikoadi

My phone is Pixel 3, Android 9, KDE connect client version is 1.12

The device never appears in the list of recognized devices on kdeconnect settings
I wonder what should be done or checked. Are there any recommendations on how to get more diagnostics (especially from the phone).
Maybe there are logs available or a way to run service and client in debug mode
Any help/advice would be appreciated.

See diagnostics below
A bit of diagnostics (the required ports are allowed in iptables, firewall is not running)

1. devices are on the same network and I can mutually ping each other.
2.
ps -ef|grep kdec
1813 1308 0 Apr16 ? 00:00:10 /usr/lib/x86_64-linux-gnu/libexec/kdeconnectd
3.
sudo netstat -tunelp | grep -i kdeconnect
tcp6 0 0 :::1714 :::* LISTEN 1000 27877 1813/kdeconnectd
udp6 0 0 :::1714 :::* 1000 22490 1813/kdeconnectd
udp6 0 0 :::55005 :::* 1000 27878 1813/kdeconnectd
4.
sudo ufw status
Status: inactive
5.
netcat -z -v 192.168.2.11 1714-1764
netcat: connect to 192.168.2.11 port 1714 (tcp) failed: Connection refused
netcat: connect to 192.168.2.11 port 1715 (tcp) failed: Connection refused
Connection to 192.168.2.11 1716 port [tcp/*] succeeded!
netcat: connect to 192.168.2.11 port 1717 (tcp) failed: Connection refused
netcat: connect to 192.168.2.11 port 1718 (tcp) failed: Connection refused
netcat: connect to 192.168.2.11 port 1719 (tcp) failed: Connection refused
netcat: connect to 192.168.2.11 port 1720 (tcp) failed: Connection refused
netcat: connect to 192.168.2.11 port 1721 (tcp) failed: Connection refused
netcat: connect to 192.168.2.11 port 1722 (tcp) failed: Connection refused
netcat: connect to 192.168.2.11 port 1723 (tcp) failed: Connection refused
netcat: connect to 192.168.2.11 port 1724 (tcp) failed: Connection refused
netcat: connect to 192.168.2.11 port 1725 (tcp) failed: Connection refused
netcat: connect to 192.168.2.11 port 1726 (tcp) failed: Connection refused
netcat: connect to 192.168.2.11 port 1727 (tcp) failed: Connection refused
netcat: connect to 192.168.2.11 port 1728 (tcp) failed: Connection refused
netcat: connect to 192.168.2.11 port 1729 (tcp) failed: Connection refused
netcat: connect to 192.168.2.11 port 1730 (tcp) failed: Connection refused
netcat: connect to 192.168.2.11 port 1731 (tcp) failed: Connection refused
netcat: connect to 192.168.2.11 port 1732 (tcp) failed: Connection refused
netcat: connect to 192.168.2.11 port 1733 (tcp) failed: Connection refused
netcat: connect to 192.168.2.11 port 1734 (tcp) failed: Connection refused
netcat: connect to 192.168.2.11 port 1735 (tcp) failed: Connection refused
netcat: connect to 192.168.2.11 port 1736 (tcp) failed: Connection refused
netcat: connect to 192.168.2.11 port 1737 (tcp) failed: Connection refused
netcat: connect to 192.168.2.11 port 1738 (tcp) failed: Connection refused
netcat: connect to 192.168.2.11 port 1739 (tcp) failed: Connection refused
netcat: connect to 192.168.2.11 port 1740 (tcp) failed: Connection refused
netcat: connect to 192.168.2.11 port 1741 (tcp) failed: Connection refused
netcat: connect to 192.168.2.11 port 1742 (tcp) failed: Connection refused
netcat: connect to 192.168.2.11 port 1743 (tcp) failed: Connection refused
netcat: connect to 192.168.2.11 port 1744 (tcp) failed: Connection refused
netcat: connect to 192.168.2.11 port 1745 (tcp) failed: Connection refused
netcat: connect to 192.168.2.11 port 1746 (tcp) failed: Connection refused
netcat: connect to 192.168.2.11 port 1747 (tcp) failed: Connection refused
netcat: connect to 192.168.2.11 port 1748 (tcp) failed: Connection refused
netcat: connect to 192.168.2.11 port 1749 (tcp) failed: Connection refused
netcat: connect to 192.168.2.11 port 1750 (tcp) failed: Connection refused
netcat: connect to 192.168.2.11 port 1751 (tcp) failed: Connection refused
netcat: connect to 192.168.2.11 port 1752 (tcp) failed: Connection refused
netcat: connect to 192.168.2.11 port 1753 (tcp) failed: Connection refused
netcat: connect to 192.168.2.11 port 1754 (tcp) failed: Connection refused
netcat: connect to 192.168.2.11 port 1755 (tcp) failed: Connection refused
netcat: connect to 192.168.2.11 port 1756 (tcp) failed: Connection refused
netcat: connect to 192.168.2.11 port 1757 (tcp) failed: Connection refused
netcat: connect to 192.168.2.11 port 1758 (tcp) failed: Connection refused
netcat: connect to 192.168.2.11 port 1759 (tcp) failed: Connection refused
netcat: connect to 192.168.2.11 port 1760 (tcp) failed: Connection refused
netcat: connect to 192.168.2.11 port 1761 (tcp) failed: Connection refused
netcat: connect to 192.168.2.11 port 1762 (tcp) failed: Connection refused
netcat: connect to 192.168.2.11 port 1763 (tcp) failed: Connection refused
netcat: connect to 192.168.2.11 port 1764 (tcp) failed: Connection refused

6.

ls -al ~/.config/kdeconnect/
total 16
drwxrwxr-x 2 username username 4096 Apr 16 23:34 ./
drwx------ 25 username username 4096 Apr 17 20:53 ../
-rw-rw-r-- 1 username username 69 Apr 16 23:34 config
-rw------- 1 username username 1708 Apr 15 23:18 privateKey.pem

7.
kdeconnect-cli -l
0 devices found
User avatar
claydoh
Registered Member
Posts
1170
Karma
9
OS
The actual kdeconnect package version in 16.04 is probably way too old for the android app to begin with. 0.8 is from 2015, and there is nothing newer available, even in PPAs, as far as I can discover.

You might try putting your linux PCs ip address in the phone app and see if that works, but I think many of the features won't work.


claydoh, proud to be a member of KDE forums since 2008-Oct, and KDE user since 2001
eugdr
Registered Member
Posts
4
Karma
0
I tried to add the ip manually. It didn't help.
Do you know whether there is a way to install an older android kde connect release?
I couldn't figure out how to do it.
User avatar
claydoh
Registered Member
Posts
1170
Karma
9
OS
f-droid probably has older apks for it, you'd have to download it and manually install, and not auto update.


Actually, doing better searching brings this:
https://launchpad.net/~webupd8team/+arc ... /+packages
much fresher versions of both kdeconnect and the indicator. If this does not work, there may be other issues.


claydoh, proud to be a member of KDE forums since 2008-Oct, and KDE user since 2001
eugdr
Registered Member
Posts
4
Karma
0
Thanks. I'll give it a try tonight
First I guess I'll try to install a newer kdeconnect on my Ubuntu and if it doesn't work maybe I'll try an older android apk if I can find one
Maybe I should consider upgrading Ubuntu to 18.
Just afraid some other stuff might stop working
eugdr
Registered Member
Posts
4
Karma
0
after downgrading my android app to 1.8.4 it became functional.
1.10 is recognised but problematic,for instance keyboard in virtual input does not work. 1.11 is not detected.
thank you very much for your help.
i should probably still consider ubuntu upgrade,but at least it can wait a bit
anandk
Registered Member
Posts
1
Karma
0
try disabling firewall by

sudo ufw disable

then try to connect hope it works
haxguru
Registered Member
Posts
1
Karma
0
@anandk It worked! Thank you!


Bookmarks



Who is online

Registered users: abc72656, Bing [Bot], daret, Google [Bot], lockheed, Sogou [Bot], Yahoo [Bot]