mconnect not working - phone can't see PC - PC can't see phone

[moviuro]

Hi,

I tried to use mconnect but, well, it failed.

Situation:

• PC and phone are on 192.168.0/24 and can ping each other.
• computers got mconnect-git-386.1cd7b43 from the AUR
• phone got https://play.google.com/store/apps/details?id=org.kde.kdeconnect_tp
• PCs are running Archlinux (up-to-date)
• Phone is a Nexus 5X running Android O (up-to-date)

Issues:

• PC can't see phone:

$ mconnectctl list-devices
No objects were found

• phone can't see PCs
• PCs can't see each other
• there is no traffic on ports 1714-1716. # tcpdump -tttnei wlan0 portrange 1714-1764 stays silent the whole time
• PCs do seem to work, somewhat.

PC1$ mconnect -d
PC2# nmap -sU -p 1714 <IP of PC1>

PC1: # runs mconnect, and receives some malformed packets from PC2
(mconnect:4185): Json-CRITICAL **: json_node_get_object: assertion 'JSON_NODE_IS_VALID (node)' failed
** Message: packet.vala:114: failed to parse message: '', error: Missing root object

** (mconnect:4185): CRITICAL **: packet_get_pkt_type: assertion 'self != NULL' failed

** (mconnect:4185): CRITICAL **: packet_get_pkt_type: assertion 'self != NULL' failed
** Message: discovery.vala:85: unexpected packet type (null) from device 192.168.0.24

(mconnect:4185): Json-CRITICAL **: json_node_get_object: assertion 'JSON_NODE_IS_VALID (node)' failed
** Message: packet.vala:114: failed to parse message: '', error: Missing root object

** (mconnect:4185): CRITICAL **: packet_get_pkt_type: assertion 'self != NULL' failed

** (mconnect:4185): CRITICAL **: packet_get_pkt_type: assertion 'self != NULL' failed
** Message: discovery.vala:85: unexpected packet type (null) from device 192.168.0.24

PC2:
# nmap -sU -p 1714 192.168.0.24

Starting Nmap 7.60 ( https://nmap.org ) at 2017-12-03 21:04 CET
Nmap scan report for 192.168.0.24
Host is up.

PORT     STATE         SERVICE
1714/udp open|filtered sesi-lm

Nmap done: 1 IP address (1 host up) scanned in 2.20 seconds

• Waiting doesn't help

$ mconnect -d
** (mconnect:487): DEBUG: config.vala:46: config search dir: /home/moviuro/.config/mconnect
** (mconnect:487): DEBUG: config.vala:46: config search dir: /usr/local/share/mconnect
** (mconnect:487): DEBUG: config.vala:46: config search dir: /usr/share/mconnect
** Message: config.vala:58: loaded configuration from /home/moviuro/.config/mconnect/mconnect.conf

** (mconnect:487): WARNING **: share.vala:42: failed to create downloads directory: Invalid argument
** INFO: share.vala:47: downloads will be saved to 
** (mconnect:487): DEBUG: core.vala:43: init core
** INFO: core.vala:59: supported interfaces: kdeconnect.telephony, kdeconnect.notification, kdeconnect.share.request, kdeconnect.battery, kdeconnect.mousepad.request, kdeconnect.ping
** (mconnect:487): DEBUG: discovery.vala:40: start listening for new devices at: 0.0.0.0:1714
** (mconnect:487): DEBUG: application.vala:85: activate
** (mconnect:487): DEBUG: devicemanager.vala:57: try loading devices from device cache /home/moviuro/.cache/mconnect/devices
[A long moment passes, at the same moment, the KDE Connect app is active on the phone]
^C

strace mconnect -d gives: the following output http://sprunge.us/MgCK ; but I'm not able to interpret any of this.

Any idea with what's wrong?

[andyholmes]

Android O support is questionable in the Android App. There's a phabricator task tracking and issue with a recent commit but it hasn't been reviewed and certainly isn't in the stable Play Store release. There's also an unmerged branch update/android-o.