KDE Connect
KDEConnect client for SailfishOS
This KDE Connect client is built from the upstream source of the KDE Connect project. Because of this, some additional KDE KF5 libraries will be installed with it.
It is to be considered an alpha release. If you notice that it stops working, or disconnects from your KDE desktop, then check in the home folder for a stacktrace.txt which may help with debugging the daemon.
Supports:
- Notifications
- MPRIS Remote
- MPRIS Client
- Remote Mouse
Other plugins will be enabled over time as the client stabilises.
Instructions:
- Ensure both machines are on the same network
- Initiate pairing from one device, and accept the pair on the other.
- If pairing from desktop to phone, just click on the notification to pair
- Once paired, you can test the connection with a 'ping' command
Known Issues:
- MPRIS client only works from a device with the mpris remote plugin, like the kirigami app or another sailfish device
- The daemon seems to die occasioanlly. Im looking into this as a top priority
(potential fix in 0.1.1)
Bug reports:
Please file bugs at https://bugs.kde.org/ using the kdeconnect product, and sailfishos as the component.
Screenshots:
Category:
Keywords:
Application versions:
| Attachment | Size | Date |
|---|---|---|
 kdeconnect-sfos-0.1-1.armv7hl.rpm | 4.69 MB | 27/08/2018 - 23:09 |
| kdeconnect-sfos-0.1.1-1.armv7hl.rpm | 4.69 MB | 10/09/2018 - 23:32 |
| kdeconnect-sfos-1.3.1fixupcrash.20181022212530.fee7166-1.armv7hl.rpm | 4.42 MB | 23/10/2018 - 00:41 |
Changelog:
1.3.1-1
Changed version to match KDE Connect version
Removed clipboard plugin
0.1.1
Potential fixes for daemon loosing connection. Feeback welcome
Device refresh menu action
Daemon logging to ~/kdeconnectd.log
0.1
Initial release
Comments
HansRoulade
Fri, 2024/05/17 - 11:57
Permalink
Wish there was an aarch64 build of it...
ade
Fri, 2024/05/17 - 13:02
Permalink
Why not use https://openrepos.net/content/r1tschy/sailfish-connect ?
Sailfish-connect is an excellent kde-connect app imho.
levone1
Fri, 2020/09/11 - 09:19
Permalink
Fix white screen issue:
zypper in libKF5ConfigCore5 libKF5I18n5Termitebug
Wed, 2019/09/11 - 11:09
Permalink
White screen also here on XA2 Plus.
sdiconov
Thu, 2019/08/29 - 11:40
Permalink
Unable to run. Displays white screen only. Jolla1 & Jolla C.
itoss
Sat, 2019/02/02 - 21:12
Permalink
i got some error while installing on SFOS ( Sailfish OS 3.0.1.11 (Sipoonkorpi) ) :
pkcon search KDE
Searching by details
Refreshing software list
Querying
Finished
Installed desktop-file-utils-0.23+git1-1.2.4.jolla.armv7hl (installed) Utilities for manipulating .desktop files
Installed kcalcore-qt5-4.10.2+9git17-1.4.2.jolla.armv7hl (installed) Port of KDE kcalcore calendar library
Available kdeconnect-sfos-1.3.1+fixup+crash.20181022212530.fee7166-1.armv7hl (PK_TMP_DIR) KDEConnect client for Sailfish
Installed libkf5archive-5.41.0+git3-1.3.2.jolla.armv7hl (installed) KDE Frameworks 5 Tier 1 addon with archive functions
Installed mkcal-qt5-0.4.4-1.6.5.jolla.armv7hl (installed) Extended KDE kcal calendar library port for Maemo
root@Sailfish:/home/nemo> pkcon install kdeconnect-sfos-1.3.1+fixup+crash.20181022212530.fee7166-1.armv7hl
Resolving [ ] (0%) Package not found: kdeconnect-sfos-1.3.1+fixup+crash.20181022212530.fee7166-1.armv7hl
Command failed: This tool could not find any available package: No packages were found
if i try to install via downloaded file and local install i got another error fro missing packages which are not available from the SFOS repos (pkcon install qt5-qtscript) :
pkcon install-local kdeconnect-sfos-1.3.1fixupcrash.20181022212530.fee7166-1.armv7hl.rpm
Installing files
Testing changes
Finished
Fatal error: nothing provides libKF5ConfigCore.so.5 needed by kdeconnect-sfos-1.3.1+fixup+crash.20181022212530.fee7166-1.armv7hl
piggz
Sat, 2019/02/02 - 22:20
Permalink
First try a pkcon refresh, and install from the repository.
Failing that, the other library packages, like config core etc are in my openrepos repository.
thisisme
Mon, 2018/12/31 - 22:28
Permalink
Great!
superkongen
Tue, 2018/11/06 - 20:31
Permalink
Dev sorted it out for me. Thanks!
In terminal, type :
pkcon install qt5-qtscript
superkongen
Tue, 2018/11/06 - 18:14
Permalink
Could not install it.
"an error occurred"
Thaodan
Tue, 2018/10/23 - 07:18
Permalink
Is there a replacement for the clipboard plugin on Sailfish OS?
piggz
Tue, 2018/10/23 - 10:27
Permalink
No, i believe the problem is that QClipboard doesnt work on Wayland (yet?)
Karry
Wed, 2018/10/03 - 13:23
Permalink
Hi piggz. Thank you for this application! Daemon seems to be unstable little bit. Here is my bugreport: https://bugs.kde.org/show_bug.cgi?id=399333
Please continue with development! :-)
piggz
Tue, 2018/10/23 - 10:27
Permalink
Please test out the new version, and sorry for the dela in publishing it
piggz
Wed, 2018/10/03 - 18:24
Permalink
thanks for the useful info, its very useful. iirc, clipboard doesnt work on wayland so that wiill be why, i`ll disable it and re-release
Karry
Thu, 2018/10/25 - 09:02
Permalink
Yeah, clipboard plugin was the cause. Removing it fix the crashes. But it would be nice to have it functional :-)
Thaodan
Tue, 2018/09/11 - 01:12
Permalink
Can you log to $XDG_CACHE_HOME/kdeconnectd.log instead?
piggz
Tue, 2018/09/11 - 20:16
Permalink
Sure
Can I get some ffedback on how well/stable the daemon is at the moment?
Cheers
Thaodan
Sat, 2018/10/06 - 17:55
Permalink
Sure.
Enable buggs on your fork an I'll report any errors I notice.
For example the app always resets the volume of players to 40% on every new track/selecting the player.
The paired device is not always found when opening the app.
Also the current device should be listed on the first page and the aviable device list should be on the swipe right page I think.
pdelfes
Tue, 2018/08/28 - 19:21
Permalink
More useless trash, i see.
pisarz1958
Tue, 2018/08/28 - 21:40
Permalink
I see you started clearly labeling your garbage, useless comments. :)
piggz
Tue, 2018/08/28 - 20:28
Permalink
Go on.... ?
ade
Tue, 2018/08/28 - 13:27
Permalink
Thanks for your effort! Having read https://github.com/R1tschY/harbour-sailfishconnect/issues/1 , it is not entirely clear to me what the future plans are. But my impressing is both Sailfish port attempts will not be merged?
piggz
Tue, 2018/08/28 - 20:34
Permalink
Seems that way ... we both started work in private, and have taken different directions. I see both have advantages, but are different code bases. sailfishconnect is a more 'pure' sailfish client, in that it does not have external dependancies, and would likely be accepted in the jolla store. My version is developed upstream as part of kdeconnect, but because of that, has dependancies on kde libraries. The advantage it brings is the whole of the kdeconnect team working on it, and all the upstream plugins.