[Bug 416056] Re: Automatic rfcomm binding at startup doesn't work in Karmic
fabio.ornellas at gmail.com
Sat Nov 14 14:16:21 GMT 2009
That's a device binding issue then, Please check the channel. My Nokia E71
chooses an arbitrary bluetooth channel for DUN at startup. Usually it ticks
with channel 4, but it changes sometimes. rfcomm needs to be informed of the
correct channel at rfcomm.conf, it isn't able to find the channel by itself.
This issue however, is not related with this Ubuntu bug in question.
Fabio Pugliese Ornellas
E-Mail: fabio.ornellas at gmail.com
gTalk: fabio.ornellas at gmail.com
MSN: neo_fpo at ig.com.br
On Sat, Nov 14, 2009 at 10:43, mantakbilug <mantakbilug at gmail.com> wrote:
> No, bluetooth is turned on.
> I also redid the pairing and restarted the phone
> I do not understand ...
> Automatic rfcomm binding at startup doesn't work in Karmic
> You received this bug notification because you are a direct subscriber
> of the bug.
Automatic rfcomm binding at startup doesn't work in Karmic
You received this bug notification because you are a member of
Bluetooth, which is subscribed to bluez in ubuntu.
More information about the Ubuntu-bluetooth