0

Would it be feasible to implement Bluetooth in KDE Connect? I do not have a Wifi network at my house and therefore cannot use KDE Connect. If Bluetooth was added you could also be connected anywhere, even if you didn't have Wifi access.

Erm, KDE Connect IS using bluetooth to connect...

Is it? I couldn't get Bluetooth to work... It wanted a Wifi network and wouldn't do anything with Bluetooth.

My bad...

I also couldn't get connections over Bluetooth to work

Bluetooth is up and running. My android smartphone and the PC are paired. The BT interface on the PC is set to be visible. I can transfer files over BT between PC/dolphin and my smatphone. But i can't pair the both devices in KDE Connect. They can't see eachother. If it's really work over BT, what a'm doing wrong ? Must KDE Connect be separatly compiled with BT support ?

KDE Connect version is:

Code: Select all

kdeconnect            1.4-0xneon+18.04+bionic+build24
kdeconnect-plasma      1.3.3-0ubuntu0.18.04.1


Android App: 1.13.7

works for me out of the box, Smartphone is running KDE Connect 1.13.6, on Android 10, sec. patch 01.01.2020, system specs see signature

Do i have an unsupported USB dongle ?

Code: Select all

hciconfig --all
hci0:   Type: Primary  Bus: USB
        BD Address: 00:1B:DC:06:5F:2C  ACL MTU: 310:10  SCO MTU: 64:8
        UP RUNNING PSCAN ISCAN
        RX bytes:271642 acl:3014 sco:10 events:13500 errors:0
        TX bytes:3819600 acl:13138 sco:8 commands:224 errors:0
        Features: 0xff 0xff 0x8f 0xfe 0xdb 0xff 0x5b 0x87
        Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
        Link policy: RSWITCH HOLD SNIFF PARK
        Link mode: SLAVE ACCEPT
        Name: 'xxxx[strike][/strike]'
        Class: 0x1c0104
        Service Classes: Rendering, Capturing, Object Transfer
        Device Class: Computer, Desktop workstation
        HCI Version: 4.0 (0x6)  Revision: 0x22bb
        LMP Version: 4.0 (0x6)  Subversion: 0x22bb
        Manufacturer: Cambridge Silicon Radio (10)


I ca't find any settings to activate or deactivate BT neither in KDE Connect nor in Android app

pairing devices is independent of applications like KDE Connect, either you can pair your PC with your phone or not, the app is just a layer on top of it. My installation is very much vanilla Kubuntu with the bluetooth stack that comes with it, my laptop bluetooth controller is equally standard Qualcom on an old Lenovo Yoga 510:

Code: Select all

hciconfig --all
hci0:   Type: Primary  Bus: USB
        BD Address: 94:E9:79:F8:55:60  ACL MTU: 1024:8  SCO MTU: 50:8
        UP RUNNING PSCAN ISCAN
        RX bytes:390383737 acl:699937 sco:0 events:505195 errors:0
        TX bytes:430131908 acl:504470 sco:0 commands:248 errors:0
        Features: 0xff 0xfe 0x8f 0xfe 0xd8 0x3f 0x5b 0x87
        Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
        Link policy: RSWITCH HOLD SNIFF
        Link mode: SLAVE ACCEPT
        Name: 'xxxxxxxxxxxx'
        Class: 0x3c010c
        Service Classes: Rendering, Capturing, Object Transfer, Audio
        Device Class: Computer, Laptop
        HCI Version: 4.1 (0x7)  Revision: 0x0
        LMP Version: 4.1 (0x7)  Subversion: 0x25a
        Manufacturer: Qualcomm (29)

Are you sure you have bluetooth enabled on your PC?

In other words: do you have bluetooth enabled on both your devices and did you pair them?

I see, your USB Dongle support BT 4.1. Do you know, if this is a requirement for KDE Connect ?

Mamarok wrote:Are you sure you have bluetooth enabled on your PC?
In other words: do you have bluetooth enabled on both your devices and did you pair them?

Yes, BT is enabled and set to visible on both devices. As i already said, transfer files from/to PC with other tools (dolphin) works fine.

Nothing to see, if i press the Refresh button


And also nothing to see in Android (in german):



The both items smyk@... are my WI-FI connected PC's at home

I don't know about the requirements for the Bluetooth protocol version, but could well be that 4.0 is too old.
Maybe try looking up specifics for the Bluetooth protocol versions, phones nowadays support version 5 as a standard, so yes, 4.0 looks quite outdated to me. Even 4.1 on my laptop is rather old, as this laptop is not the newest model either.
Not my speciality, fact is this is the wrong thread for this kind of problems, as it is in no way related to what KDE Connect offers, and I am not even sure this is in any ways Plasma or KDE related, but a hardware issue.

I found out that the bluetooth link provider is optional and must be enabled (BLUETOOTH_ENABLED) when compiling KDE Connect.
How can i check, which flags/options were used on building KDE Connect for Neon ? Is this stored somewhere in .deb packages ?

Or in other words, is someone here, that successfully paired Android with KDE Connect on Neon (using packages from repo)?

Please make a new post in KDE Neon, this does definitely not belong in Brainstorm

I missed we are here in brainstorm. Sorry

The backend for Bluetooth is buggy in both KDE server and the Android software. However, you don't need it in anyway to use Bluetooth as the network layer to connect with KDE connect.
The process to connect over bluetooth is described here.
Mainly, you'll use the built-in BlueZ functionality to accept LAN over BT, and the fact that any android handset supports sharing its network connection over bluetooth. Once it's set up, it works beautifully without the battery monster of the WIFI consumption.

I just stumbled over this thread wondering for a long time why KDEConnect does not finally offer the long discussed connection via bluetooth.
Only to find out that it actually does, only that no one knows about that!

As Mamarok said: works out of the box. Impressive.
And yes, a connection via bluetooth _does_ make a lot of sense as an alternative. I have all my mobile devices using a wireguard based VPN tunnel and never managed to get a network based KDEConnect connection to work with that. Yes, I do understand that bluetooth is slower and probably less secure. But it works. And does not restrict me by network topology details.

arkascha wrote:...
As Lydia said: works out of the box....

my name is not Lydia