Bluez 5
Does anyone have a Bluez 5 (currently at 5.24) Slackware package or SlackBuild?
I'd attempt to make one myself, but first I want to make sure I'm not reinventing the wheel. |
A quick search shows the one below, which has 5.24 as the version number.
https://github.com/PhantomX/slackbui...uez.SlackBuild |
There are other changes that you might need. I wonder about a slackbuild that doesn't have "--disable-systemd" as a configuration option, myself.
If you want gatttool, you'll have to patch Makefile.tools.... Code:
--- Makefile.tools 2014-06-20 13:33:13.000000000 -0500 As an aside: I was looking for decent BLE support for my heart rate monitor. Bluez doesn't provide that. bstack did, but I cannot recommend it for a bluez replacement. (bstack isn't designed to be a bluez replacement.) |
If you (or anyone else) gets a working bluez5 stack going in such a way that bluez4 is not missed, please include us in the loop. Last I looked (granted, this was long ago - just after bluez5's early releases), it was not in a usable state.
|
What I ended up with appeared to be usable, but I don't use Bluetooth for anything other than my BLE heart monitor. (My complaint was that there is no dbus interface for heart rate notifications; in fact, the dbus support for BLE was in flux the last time I looked [bluez-5.22].) The configuration's changed between 4.x and 5.x; I didn't spend a lot of effort trying to untangle it.
Most of the effort appears to be on the Android side. |
I have built BlueZ-5.25 and it is working, but without an applet (blueman, bluedevil or so) for managing this is not usable by end-users. I'm trying to build blueman-1.99 (which is alpha), but it does not works for me. Here is output from blueman-applet when it's launched in command line:
Code:
$ blueman-applet Code:
python-2.7.5-x86_64-1 rebuilt |
My guess is that it needs a different version of PyGobject. The latest version is 3.10.2, and there might have been changes between 3.0 and 3.10.
|
Quote:
|
Blueman is under development by new folks here: https://github.com/blueman-project/blueman
bluez-5 support is in progress but not yet there. If you know python and gtk, please take a look at some of the Issues and see if you can address them - I'm trying to do my part (what little I can). |
Well that wasn't bad. I cloned PhantomX's SlackBuild repository, edited the Bluez SlackBuild to build Bluez without systemd support (--disable-systemd), launched the Bluetooth daemon (/usr/libexec/bluetooth/bluetoothd), then went through the Gentoo wiki's Bluez-5 quickstart.
http://wiki.gentoo.org/wiki/Bluetooth#BlueZ_5 Before long I had my Dualshock 4 controller paired, and I could see its input in the /dev/input/js0 device node. I'm fine with doing stuff from a bluetoothctl shell instead of a GUI. Also, my desktop is OpenBox+Tint2, not having desktop integration isn't an issue for me. |
BLFS is using BlueZ-5.28 without systemd here:
http://linuxfromscratch.org/blfs/vie...ral/bluez.html Maybe this can be of some insight? |
Something I hit with this upgrade, and you'll likely hit as well... they changed the 'trusted' devices bit in bluez... so while a device will pair and work, it won't pair again automatically as other bits need upgraded as well for this to work..
Eventually i got into a scenario of upgrading too much and backed out to the -current bluez. Just a heads up. |
How long ago was that? This blog entry from 2013, combined with the Gentoo wiki, are implying to me that that was fixed:
http://patkoscsaba.blogspot.ca/2013/...bluetooth.html I haven't yet tested it myself. |
couple of months ago... it isn't a bug, but rather the newer bluez 5 needs an updated d-bus as the trusted device has changed in the newer kernels and bluez has updated to reflect this.
Looks like from my notes it was kernel 3.17 and forward, bluez 5.24 and forward. I didn't work out the d-bus completely as i ran out of time. The devices paired fine, but wouldn't reconnect as a trusted device should. |
Thanks. I didn't know about that. Could you please post a link or two for me to read?
Anyway, it looks like it reconnecting my Dualshock 4 consisted just holding down the PS button. I had bluetoothctl running at the time. The light on the controller flashed for about a second, and then I saw the "connected" message in bluetoothctl.. That's fine, but I'm still interested in learning more about what you found out about the DBUS issues. The machine I'm tested on is using kernel 3.10. |
All times are GMT -5. The time now is 10:26 PM. |