1 |
I got it working! |
2 |
|
3 |
But I can't reproduce what i did.. |
4 |
|
5 |
I played around with "bluetoothctl" which seems to be a interactive |
6 |
replacement for simple-agent. |
7 |
After powering my bluetooth device on and off, trusting and untrusting, |
8 |
pairing and unpairing for several times it now *seems* to work. |
9 |
It even connects automatically after turning it on :-) |
10 |
|
11 |
Bluetooth stuff is really weird.... |
12 |
|
13 |
Thanks! |
14 |
|
15 |
On 02/18/14 17:20, Canek Peláez Valdés wrote: |
16 |
> On Tue, Feb 18, 2014 at 10:14 AM, Ralf |
17 |
> <ralf+gentoo@×××××××××××××××××××.de> wrote: |
18 |
>> On 02/18/14 17:10, Canek Peláez Valdés wrote: |
19 |
>> |
20 |
>> systemctl status bluetooth.service |
21 |
>> |
22 |
>> |
23 |
>> Yes, sure, as I wrote above. |
24 |
>> |
25 |
>> Active: active (running) since Tue 2014-02-18 16:57:05 CET; 15min ago |
26 |
>> |
27 |
>> ps auxw|grep bluetoot |
28 |
>> root 3571 27.6 0.0 21200 2112 ? Rs 16:57 4:29 |
29 |
>> /usr/libexec/bluetooth/bluetoothd |
30 |
>> |
31 |
>> As you see everything is actually running fine... I even tried to restart it |
32 |
>> several times |
33 |
> OK, sorry, I hadn't read carefully your first post. blueman-applet |
34 |
> fails because it uses the 4.x dbus API from bluez. gnome-bluetooth |
35 |
> uses the 5.x dbus API, and AFAIK, right now it's the only tool using |
36 |
> it. |
37 |
> |
38 |
> So, with gnome-bluetooth you can detect your keyboard but the pairing |
39 |
> fails? You say you paired the keyboard correctly with your android |
40 |
> phone; you don't need to do something in the keyboard to pair it to a |
41 |
> different hosts? Something like keep pressing the power button? |
42 |
> |
43 |
> Regards. |