Re: 3.19-rc1 refuse connection from bluetooth headset

[Pali RohÃr]

On Wednesday 24 December 2014 18:36:52 Johan Hedberg wrote:
> Hi Pali,
> 
> On Wed, Dec 24, 2014, Pali RohÃr wrote:
> > now I installed 3.19-rc1 kernel and my bluetooth headset was
> > refused to connect automatically. I need to start
> > connection manually from laptop (and then it working).
> > Before when I started bluetooth headset it automatically
> > connected and I did not have to do anything. Now with
> > 3.19-rc1 kernel I need to do connection manually and I see
> > error
> > 
> > messages in hcidump:
> >  $ sudo hcidump
> >  HCI sniffer - Bluetooth packet analyzer ver 2.2
> >  device: hci0 snap_len: 1028 filter: 0xffffffffffffffff
> >  
> >  > HCI Event: Connect Request (0x04) plen 10
> >  > 
> >      bdaddr <HEADSET_ADDRESS> class 0x240404 type ACL
> >  
> >  < HCI Command: Reject Connection Request (0x01|0x000a) plen
> >  7
> >  
> >      bdaddr <HEADSET_ADDRESS> reason 0x0f
> >      Reason: Connection Rejected due to Unacceptable BD_ADDR
> >  > 
> >  > HCI Event: Command Status (0x0f) plen 4
> >  > 
> >      Reject Connection Request (0x01|0x000a) status 0x00
> >      ncmd 1
> >  > 
> >  > HCI Event: Connect Complete (0x03) plen 11
> >  > 
> >      status 0x0f handle 34 bdaddr <HEADSET_ADDRESS> type ACL
> >      encrypt 0x00 Error: Connection Rejected due to
> >      Unacceptable BD_ADDR
> >  > 
> >  > HCI Event: Connect Request (0x04) plen 10
> >  > 
> >      bdaddr <HEADSET_ADDRESS> class 0x240404 type ACL
> >  
> >  < HCI Command: Reject Connection Request (0x01|0x000a) plen
> >  7
> >  
> >      bdaddr <HEADSET_ADDRESS> reason 0x0f
> >      Reason: Connection Rejected due to Unacceptable BD_ADDR
> >  > 
> >  > HCI Event: Command Status (0x0f) plen 4
> >  > 
> >      Reject Connection Request (0x01|0x000a) status 0x00
> >      ncmd 1
> >  > 
> >  > HCI Event: Connect Complete (0x03) plen 11
> >  > 
> >     status 0x0f handle 35 bdaddr <HEADSET_ADDRESS> type ACL
> >     encrypt 0x00 Error: Connection Rejected due to
> >     Unacceptable BD_ADDR
> > 
> > (real address of my bluetooth headset was replaced by
> > <HEADSET_ADDRESS>)
> > 
> > Can you inspect why new kernel refuse connection from my
> > bluetooth headset?
> > 
> > I'm still using bluez 4.98 (which is in Ubuntu 12.04), I did
> > not do any update.
> 
> Could you try the attached patch? I think the reason might be
> the dependence on the HCI_CONNECTABLE flag that's only set if
> the page scan was enabled through mgmt (which wouldn't be the
> case with BlueZ 4.98).
> 
> Johan

Hi Johan! Thanks for quick reply. Your patch fixes my problem and 
auto-connection of my bluetooth headset is working again. Will 
you forward patch to mainline kernel?

-- 
Pali RohÃr
pali.rohar@xxxxxxxxx

Attachment: signature.asc
Description: This is a digitally signed message part.