Oh no... After turning of the keyboard, bluetoothd start to consume 100% CPU...
I have to run systemctl restart bluetooth after unconnecting my device. Come on... On 02/18/14 17:49, Ralf wrote: > I got it working! > > But I can't reproduce what i did.. > > I played around with "bluetoothctl" which seems to be a interactive > replacement for simple-agent. > After powering my bluetooth device on and off, trusting and untrusting, > pairing and unpairing for several times it now *seems* to work. > It even connects automatically after turning it on :-) > > Bluetooth stuff is really weird.... > > Thanks! > > On 02/18/14 17:20, Canek Peláez Valdés wrote: >> On Tue, Feb 18, 2014 at 10:14 AM, Ralf >> <ralf+gen...@ramses-pyramidenbau.de> wrote: >>> On 02/18/14 17:10, Canek Peláez Valdés wrote: >>> >>> systemctl status bluetooth.service >>> >>> >>> Yes, sure, as I wrote above. >>> >>> Active: active (running) since Tue 2014-02-18 16:57:05 CET; 15min ago >>> >>> ps auxw|grep bluetoot >>> root 3571 27.6 0.0 21200 2112 ? Rs 16:57 4:29 >>> /usr/libexec/bluetooth/bluetoothd >>> >>> As you see everything is actually running fine... I even tried to restart it >>> several times >> OK, sorry, I hadn't read carefully your first post. blueman-applet >> fails because it uses the 4.x dbus API from bluez. gnome-bluetooth >> uses the 5.x dbus API, and AFAIK, right now it's the only tool using >> it. >> >> So, with gnome-bluetooth you can detect your keyboard but the pairing >> fails? You say you paired the keyboard correctly with your android >> phone; you don't need to do something in the keyboard to pair it to a >> different hosts? Something like keep pressing the power button? >> >> Regards. >
