Bug 496878

Summary:	Kdeconnect bluetooth connectivity
Product:	[Applications] kdeconnect	Reporter:	Ravi <ravi480000>
Component:	common	Assignee:	Albert Vaca Cintora <albertvaka>
Status:	RESOLVED UNMAINTAINED
Severity:	normal	CC:	andrew.g.r.holmes, cwo.kde
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Ravi 2024-11-30 20:41:30 UTC

I would like to be able to read and send SMS messages on my Samsung phone from my Ubuntu laptop through bluetooth interface and kdeconnect software.

Followed steps at
https://userbase.kde.org/KDEConnect#Bluetooth_Connectivity

The ‘KDE Connect Settings’ app in Ubuntu laptop is able to see the phone in a paired status.

The ‘KDE Connect’ app on the Samsung phone is unable to see the device corresponding to Ubuntu laptop.

On the laptop, when clicking on ‘Send ping’ button inside the ‘KDE Connect Settings’ app, nothing happens.

Running KDE Connect app version 1.32.5 in Samsung phone.

Using kdeconnect package version 1.4-0ubuntu5 on Ubuntu
OS version 20.04.6 LTS.

Bluetooth interface enabled in laptop:

$ bluetoothctl show | grep ‘Vendor specific’
UUID: Vendor specific (00005005-0000-1000-8000-0002ee000001)

See these messages in /var/log/syslog in laptop:

    Nov 24 12:21:23 adyar org.kde.kdeconnect.daemon.desktop[2518]: kdeconnect.core: Sending onNetworkChange to 1 LinkProviders
    Nov 24 12:21:23 adyar org.kde.kdeconnect.daemon.desktop[2518]: kdeconnect.core: Broadcasting identity packet
...
    Nov 24 11:49:00 adyar kernel: [  690.574147] Bluetooth: Unexpected start frame (len 7)

Comment 1 cwo 2025-01-01 21:18:55 UTC

Your version of kdeconnect is likely too old to work over bluetooth; this was only recently enabled (24.08 I think). The old version should probably still be able to work over wifi. But I would really suggest upgrading.

For this kind of support request, it's also better to start with a post on a discussion forum (your distribution's, or discuss.kde.org), reddit, or similar, as the kdeconnect devs usually don't have the time to troubleshoot issues on individual systems. The bug tracker is best when a bug in kdeconnect has been identified.

I'm closing this as UNMAINTAINED due to the old kdeconnect version; 1.4 is over 5 years old at this point. Feel free to reopen it or open a new bug report if you can reproduce it on a current version (and ideally once the issue has been narrowed down a bit to rule out misconfiguration).