| 1 |
On Mon, Sep 21, 2020 at 05:27:58PM +0100, Peter Humphrey wrote: |
| 2 |
> > I'm sure you've already seen this, but you might derive value from the |
| 3 |
> > "Device Pairing" section of the Bluetooth Gentoo Wiki page with |
| 4 |
> > `bluetoothctl` [4]. |
| 5 |
> |
| 6 |
> I have, yes. I followed that method to get the devices paired. |
| 7 |
> |
| 8 |
> I was hoping to integrate the phone with my desktop. I had a vague idea of |
| 9 |
> using the multimedia somehow. (I did say it was vague.) KDE Connect sounded |
| 10 |
> like the bee's knees, but as Andrew said, it operates over WiFi, which is a |
| 11 |
> problem for me. |
| 12 |
|
| 13 |
KDE Connect does look fantastic, although I'm not sure the client application |
| 14 |
could work with my Nokia 6310i. Texting is terribly tedious using the in-built |
| 15 |
keyboard; Gnokii works well over Bluetooth, though. ;-) |
| 16 |
|
| 17 |
As for a Bluetooth back-end for KDE Connect, it _does_ seem like there's been |
| 18 |
some work done towards such a goal, although it also seems to be abandoned and |
| 19 |
opaque. There's an unanswered comment on a blog post which goes into some detail |
| 20 |
[1], and then there's a package entry in the Arch User repository (AUR) called |
| 21 |
`kdeconnect-bluetooth` [2]. |
| 22 |
|
| 23 |
Cloning the AUR git repository, it seems like the build script (`PKGBUILD`) just |
| 24 |
downloads KDE Connect and passes a flag to the configure script: |
| 25 |
|
| 26 |
build() { |
| 27 |
cd build |
| 28 |
cmake ../$_name-kde-$pkgver \ |
| 29 |
-DBUILD_TESTING=OFF \ |
| 30 |
-DCMAKE_INSTALL_LIBEXECDIR=lib\ |
| 31 |
-DBLUETOOTH_ENABLED=ON |
| 32 |
make |
| 33 |
} |
| 34 |
|
| 35 |
Gentoo does something similar [3]: |
| 36 |
|
| 37 |
src_configure() { |
| 38 |
local mycmakeargs=( |
| 39 |
-DBLUETOOTH_ENABLED=$(usex bluetooth) |
| 40 |
$(cmake_use_find_package pulseaudio KF5PulseAudioQt) |
| 41 |
$(cmake_use_find_package wayland KF5Wayland) |
| 42 |
$(cmake_use_find_package X LibFakeKey) |
| 43 |
) |
| 44 |
|
| 45 |
ecm_src_configure |
| 46 |
} |
| 47 |
|
| 48 |
Unfortunately, getting the Android APK companion application to use Bluetooth as |
| 49 |
a back-end is slightly more difficult. More information, if you really want to |
| 50 |
use KDE Connect: [4], [5], [6], [7], [8]. The developers made it painfully clear |
| 51 |
that this is not on their immediate TODO list, as neither of the two primary |
| 52 |
developers are Bluetooth users [9], so I wouldn't expect anything marvellous. |
| 53 |
|
| 54 |
Keep us updated, |
| 55 |
Ashley. |
| 56 |
|
| 57 |
[1] https://albertvaka.wordpress.com/2019/09/29/kde-connect-sprint-2019/#comment-21243 |
| 58 |
[2] https://aur.archlinux.org/packages/kdeconnect-bluetooth/ |
| 59 |
[3] https://gitweb.gentoo.org/repo/gentoo.git/tree/kde-misc/kdeconnect/kdeconnect-20.08.1.ebuild#n67 |
| 60 |
[4] https://bugs.kde.org/show_bug.cgi?id=330536 |
| 61 |
[5] https://www.reddit.com/r/linux/comments/6ggb36/ |
| 62 |
[6] https://phabricator.kde.org/T7447 |
| 63 |
[7] https://nicolasfella.wordpress.com/2018/07/31/kde-connect-new-stuff-ii/ |
| 64 |
[8] https://www.omgubuntu.co.uk/2017/06/kde-connect-bluetooth-backend-development |
| 65 |
[9] https://bugs.kde.org/show_bug.cgi?id=330536#c8 |
| 66 |
|
| 67 |
-- |
| 68 |
|
| 69 |
Ashley Dixon |
| 70 |
suugaku.co.uk |
| 71 |
|
| 72 |
2A9A 4117 |
| 73 |
DA96 D18A |
| 74 |
8A7B B0D2 |
| 75 |
A30E BF25 |
| 76 |
F290 A8AA |
Archives