On Sunday 02 Mar 2014 07:21:18 cov...@ccs.covici.com wrote: > Hi. I am getting more troubles with bluetooth 5.14 -- 4 worked fine, 5 > seems to have a lot of quirks.
I occasionally tether my phone to my laptop using bluetooth and have found that establishing a connection can be quite temperamental. Rebooting the phone or disabling/enabling its bluetooth service usually helps get a response from it. > I get the following lines from a program I am running called brltty: > >Mar 1 15:25:35 ccs bluetoothd[2684]: No agent available for request > >type 0 This is typically obtained when the device is not set to be discoverable. Check that they both are. If you have restarted/reset either you may need to set them back to discoverable. > >Mar 1 15:25:35 ccs bluetoothd[2684]: device_request_pin: Operation not > >permitted > >Mar 1 15:25:35 ccs brltty[16004]: RFCOMM connect error 111: Connection > >refused. Have you set up the correct device MAC address in /etc/bluetooth/rfcomm.conf and restarted it? If yes then this may be a matter of misstyping the pin? > HOw can I fix this? There is a new program under bluetooth 5 called > bluetoothctl, and I paired, trusted and connected, and still no joy. I don't have bluetoothctl here to know what it does, but I use l2ping, hciconfig and sdptool first to make sure that I can see and read the device I am trying to pair with. If you have indeed managed to pair the two devices you would not be getting the above connection errors, unless the radio signal broke down after pairing, due to e.g. weak signal or electromagnetic interference from some external source. -- Regards, Mick
signature.asc
Description: This is a digitally signed message part.
