Sailfish Connect

Your rating: None Average: 4.8 (59 votes)

KDE Connect client for Sailfish OS


This application allows you to connect to other devices running KDE Connect. At the moment following set of KDE Connect plugins are supported:

  • Battery - Share battery status with your computer.
  • Clipboard - Share clipboard text content.
  • MPRIS - Control multimedia player from your computer.
  • Share - Send and receive files, text and URLs.
  • Touchpad - Create mouse input from your phone.
  • Keyboard - Create keyboard input from your phone.
  • Notifications - Sends notifications to your computer.
  • Telephony - Send incoming and missed calls to your computer.
  • Commands - Send and receive user-defined shell commands.
  • Remote system volume - Change volume of audio sinks of your computer.

More will follow.

Submit bugs to Github or use Git Reports if you do not own a Github account.

Join for discussion and feedback.

Other KDE Connect Clients 


Known Issues

  • LAN: A connection through USB-Ethernet and developer mode is not possible.


Application versions: 
File harbour-sailfishconnect-0.7.0-1.aarch64.rpm701.62 KB03/06/2024 - 21:09
File harbour-sailfishconnect-0.7.0-1.armv7hl.rpm644.61 KB03/06/2024 - 21:09
File harbour-sailfishconnect-0.7.0-1.i486.rpm732.35 KB03/06/2024 - 21:09
File harbour-sailfishconnect-0.6.2-1.aarch64.rpm891.28 KB18/03/2022 - 21:35
File harbour-sailfishconnect-0.6.2-1.armv7hl.rpm831.16 KB18/03/2022 - 21:35
File harbour-sailfishconnect-0.6.2-1.i486.rpm1002.59 KB18/03/2022 - 21:35
File harbour-sailfishconnect-0.6.1-2.aarch64.rpm887.49 KB04/11/2021 - 01:37
File harbour-sailfishconnect-0.6.1-2.armv7hl.rpm827.43 KB04/11/2021 - 01:37
File harbour-sailfishconnect-0.6.1-2.i486.rpm999.46 KB04/11/2021 - 01:37
File harbour-sailfishconnect-0.6.1-1.aarch64.rpm887.64 KB05/06/2021 - 11:39
File harbour-sailfishconnect-0.6.0-2.armv7hl.rpm847.96 KB09/02/2021 - 21:56
File harbour-sailfishconnect-0.6.0-2.i486.rpm1022.39 KB09/02/2021 - 21:56
File harbour-sailfishconnect-0.5.1-1.armv7hl.rpm269.42 KB15/03/2020 - 14:41
File harbour-sailfishconnect-0.5.1-1.i486.rpm306.92 KB15/03/2020 - 14:41
File harbour-sailfishconnect-0.5-1.armv7hl.rpm267.78 KB04/01/2020 - 16:30
File harbour-sailfishconnect-0.5-1.i486.rpm305.63 KB04/01/2020 - 16:30
File harbour-sailfishconnect-0.4.1-1.armv7hl.rpm254.61 KB10/09/2019 - 21:21
File harbour-sailfishconnect-0.4.1-1.i486.rpm289.61 KB10/09/2019 - 21:21
File harbour-sailfishconnect-0.4-2.armv7hl.rpm250.34 KB18/08/2019 - 21:54
File harbour-sailfishconnect-0.4-2.i486.rpm285.98 KB18/08/2019 - 21:54
File harbour-sailfishconnect-0.3-1.armv7hl.rpm213.11 KB02/03/2019 - 22:58
File harbour-sailfishconnect-0.3-1.i486.rpm239.14 KB02/03/2019 - 22:58
File harbour-sailfishconnect-0.2-2.armv7hl.rpm172.51 KB21/10/2018 - 19:07
File harbour-sailfishconnect-0.2-2.i486.rpm195.04 KB21/10/2018 - 19:07
File harbour-sailfishconnect-0.1-1.armv7hl.rpm150.68 KB10/08/2018 - 23:52


  • Upload of multiple files at once possible
  • Use system keyboard for remote keyboard
  • Unpair action moved to device list page and uses remorse item
  • Upgrade to KDE Connect 24.01.90
  • Fix deprecated linkage to OpenSSL 1.0


  • Disable sandbox for Sailfish 4.4 support


  • Support for aarch64 architecture (#46)
  • Requires Sailfish 4.0


  • Direct use of KDE Connect desktop client as backend instead of own fork
  • Add IPs of custom devices to be searched for (#35)
  • Added command plugins
  • Added remote system volume plugin
  • Replaced transactions page with transaction notifications
  • Fixed remote keyboard for special characters like comma, space, fullstop (#34)
  • Migrated battery plugin to use MCE DBus interface instead of statefs (Fixes installation on Sailfish OS 4.0.1)
  • Fixed album art for Spotify
  • Added Estonian translation (thanks to Priit Jõerüüt)


  • Allow newer TLS versions (#38). Fixes broken GSConnect support for linux distributions using GLib >= 2.64.
  • Fixed monitoring of notifications in release build. (see #37)


  • Added Contacts plugin.
  • Resolve phone numbers to contact names in telephony plugin.
  • Starts now at system start as systemd user service when in background mode
  • Fixed GSConnect not showing notifications without a icon
  • Added translation for Italian (thanks to ghostofasmile)


  • Fix bug of app quiting after file transfer of any kind when screen is off
  • Fix file upload to GSConnect
  • Wake up app regularly to keep TCP connections alive (see #27)
  • Added translation for French and one missing translatable string (thanks to the translators)


  • Added keyboard plugin (thanks to derFogel)
  • Added album art to media player
  • Added possibility to open downloaded file
  • Redesigned device page
  • Enhanced sending notifications
  • File transfers are now more robust (especially large transfers)
  • Changed: Clipboard content must now explicitly pushed (see #7)
  • Added translation for Finnish, Swedish and Polish (thanks to the translators)


  • Added page to show file transfers
  • Added telephony plugin
  • Fixed various bugs to support GSConnect
  • Fixed crash when unpairing
  • Fixed various small bugs


  • Changed name to Sailfish Connect
  • Added setting to control running in background (new default is off)
  • Added notifications for pairing and ping plugin
  • Added touchpad plugin
  • Added share plugin
  • Added notifications plugin prototype
  • Made few ui enhancements
  • Fixed several bugs
  • Added known issue description notice for clipboard plugin
  • Connecting should be more stable


R1tschY's picture

Do you use GSConnect or KDE Connect? For GSConnect it is known that some notifications sended from SailfishConnect are not shown.

objectifnul's picture


R1tschY's picture

The problem should be fixed with version 0.5.1-1.

objectifnul's picture

V0.4-1.1 sends zero-byte files to the phone.

sdiconov's picture

Unable to pair with desktop. Both PC (linux, kde-connect) and jolla1 phone (sailfish connect) are in the same subnet connected to the same router. Ping works, firewalls disabled, but the devices do not see each other and the phone is not detected as a connectabke device.

emchella's picture

have you open the pc firewall port ?

sudo firewall-cmd --zone=public --permanent --add-port=1714-1764/tcp
sudo firewall-cmd --zone=public --permanent --add-port=1714-1764/udp

i have open there and working  for me


R1tschY's picture

Can you install the Android KDE Connect Client to see whether this client can connect?

objectifnul's picture

v0.4-2 seems to be not supported in SailfishX v2.2.0.29 (Unresponsive GUI; all patches disabled). Reverted to v0.3-1 which is OK.

csg1976's picture

Thanks for the update!

akikk88's picture

Finnish support coming?

R1tschY's picture

Finnish translation will come in next release, which will be released end of July or in August.

mugshot's picture

Hi, I noticed that in the media/file selection window, the Select file to send isn't translated. I couldn't find that string in Transifex either.


R1tschY's picture

Hey, thanks for reporting. I just forgot to make the string translatable. Will be fixed in the next release.

JacekJagosz's picture

Any way I could make it run automatically with system startup?

R1tschY's picture

At the moment you have to setup at your own a systemd service. Maybe in the future this is part of the installation process. I did not tested it. Just copied from harbour-sailorgram and adjusted:

  • Activate background mode in SailfishConnect settings.
  • Create file named harbour-sailfishconnect.service in /usr/lib/systemd/user/

ExecStart=/usr/bin/invoker --type=silica-qt5 /usr/bin/harbour-sailfishconnect

  • Then on the command line run:
systemctl-user restart harbour-sailfishconnect.service

Edit: Fixed harbour-sailfishconnect.service

JacekJagosz's picture

I get that error when I run systemctl-user status
harbour-sailfishconnect.service - SailfishConnect
Loaded: error (Reason: Invalid argument)
Active: inactive (dead)

R1tschY's picture

I found the problem. It should be:


ExecStart=/usr/bin/invoker --type=silica-qt5 /usr/bin/harbour-sailfishconnect

murfik's picture

after rm config app work, thank's!

murfik's picture

After update app crash on startup

R1tschY's picture

That's not good :-/

Try to delete the config folder: /home/nemo/.config/harbour-sailfishconnect

Or run SailfishConnect on the terminal: /usr/bin/harbour-sailfishconnect
and send me the output.

eson's picture

What do I need, to send SMS from my linux mint desktop? I have KDE Connect and most things seem to work, but no SMS. I can see the plugin on my phone, but it's not available in KDE Connect on desktop.

R1tschY's picture

I just tested with MConnect and KDE Connect as backend and it worked. At the moment SMS history and contacts is not supported. For example SMS functionality in GSConnect does it not work until this is implemented. But yes, I also do not see it in the KDE Connect plugins dialog. Maybe it's a bug, because it's possible to send messages.

rigo's picture

I have KDE-connect SMS 20.12.1 being empty and the refresh hangs forever. This is opensuse Tumbleweed with SailfishOS Should I submit a bug report? Or is this a feature request? There is no way to send SMS. It just remains an empty box while saying "Loading conversations from device". Refresh does'nt change anything.

R1tschY's picture

Sending SMS is pretty much broken at the moment and never really worked like one would expect.

eson's picture

Ok, thanks! I'll try again.

Btw... I got Swedish translation ready to use, if you confirm my request at Transifex, or do you prefer PR at GitHub?

R1tschY's picture

Transifex is the prefered way. Swedish is now accepted.

objectifnul's picture

There seems to be a size limit for file transfer, but I didn't manage to determine its exact value.

R1tschY's picture

There should not be any. The feature is not as stable as it should, but I'm working on it.

objectifnul's picture

Useful to know, at least for Ubuntu users. These ports must be open on desktop side:

 sudo ufw allow 1714:1764/udp
 sudo ufw allow 1714:1764/tcp
 sudo ufw reload

(see here how to revert those permissions)

eson's picture

That is very generell. I would specify which machine(s)/IP(s) is allowed to connect.

sudo ufw allow proto udp to any port 1714:1764 from 192.168.*.*
sudo ufw allow proto tcp to any port 1714:1764 from 192.168.*.*
sudo ufw reload