Bug 371518

Summary: pairing between android device and pc works, but no modules are available
Product: [Applications] kdeconnect Reporter: pscholz
Component: commonAssignee: Albert Vaca Cintora <albertvaka>
Status: RESOLVED WORKSFORME    
Severity: normal CC: aleixpol, pscholz
Priority: NOR    
Version First Reported In: 1.0   
Target Milestone: ---   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description pscholz 2016-10-23 10:42:58 UTC
My phone and my desktop have no problem finding themselves and pairing each other, but not a single service is offered afterwards.

On desktop side, the tray applet says that there is no information on accu. When I try to ping my phone, nothing happens.

The phone client only shows a blank screen. When I go to module settings, all settings are activated, but all module descriptions just say that this module is not supported by the device.

This behaviour occurs only on/with my desktop, which has an arch installed with kde 5.8. The connection between my phone and my notebook (ubuntu14.04, kde 4.13) is working as expected (and really good indeed).



Reproducible: Always

Steps to Reproduce:
1. Install newest Android-version from f-droid
2. sudo pacman -S kdeconnect
3. pair devices

Actual Results:  
recognize that devices are successfully paired, but you can't do a thing, not even ping your device.

Expected Results:  
offer to control media, offer the touchpad control, and all the othe stuff...

I do not really know how to debug this, but here are some things I tried:

(After killing already running kdeconnectd)

$ /usr/lib/kdeconnectd                    
kdeconnect.core: KdeConnect daemon starting
kdeconnect.core: onStart
kdeconnect.core: KdeConnect daemon started
kdeconnect.core: Broadcasting identity packet
kdeconnect.core: Socket connected
kdeconnect.core: TCP connection done (i'm the existing device)
kdeconnect.core: Starting server ssl (I'm the client TCP socket)
kdeconnect.core: Socket connected
kdeconnect.core: TCP connection done (i'm the existing device)
kdeconnect.core: Starting server ssl (I'm the client TCP socket)
kdeconnect.core: Socket succesfully stablished an SSL connection
kdeconnect.core: It is a known device "OnePlus One"
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
QObject::connect: No such signal QDBusAbstractInterface::messageReceived(QString,QString)
kdeconnect.plugin.sftp: add to dolphin
kdeconnect.plugin.sftp: Created device: "OnePlus One"
kdeconnect.core: Socket succesfully stablished an SSL connection
discarding unsupported package "kdeconnect.capabilities" for "OnePlus One"

if I do things such as...

$ kdeconnect-cli -d ff35f74a3d57d75e --list-commands
$ kdeconnect-cli -d ff35f74a3d57d75e --ping
$ kdeconnect-cli -d ff35f74a3d57d75e --ring

...in a different terminal, nothing happens. In the terminal with the daemon it adds:

kdeconnect.plugin.ping: sendPing: true

nothing more...
Comment 1 Aleix Pol 2018-01-16 22:50:04 UTC
Can you still reproduce the issue?
Please make sure that the Android version you have is the latest.
Comment 2 pscholz 2018-01-17 09:09:34 UTC
(In reply to Aleix Pol from comment #1)
> Can you still reproduce the issue?
> Please make sure that the Android version you have is the latest.

No, only had this issue on Arch, which I don’t use anymore. Now using "KDE neon", everything runs fine.

Thanks
Comment 3 Christoph Feck 2018-01-17 20:40:21 UTC
Thanks for the update; closing.