Re: Headset not working, 2.6.24.x style

jayjwa <[email protected]>
Newsgroups gmane.linux.bluez.user
Message-ID <[email protected]>
On Thu, 6 Mar 2008, Guillaume Bedot wrote:

-> I guess you have a bluetooth =< 1.2 headset. It's a known issue,
-> unfortunaletly it is not fixed yet.
-> 
-> You can try this kernel patch and report if this works for you (for me
-> it does) :
-> http://lkml.org/lkml/diff/2008/2/25/530/1


Thanks. I was just looking into this further and found this link which looks 
like the trouble I'm having:

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/39414

specifically:

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/39414/comments/47


I have the same message flood. My guess was the dongle supports esco, while 
the headset doesn't (because it's not in the feature set). Is this not 
the same issue? Here, the headset:

Requesting information ...
         BD Address:  00:1A:45:01:F9:42
         Device Name: Jabra BT135
         LMP Version: 2.0 (0x3) LMP Subversion: 0xbfa
         Manufacturer: Cambridge Silicon Radio (10)
         Features: 0xfc 0xfe 0x0b 0x00 0x08 0x08 0x00 0x00
                 <encryption> <slot offset> <timing accuracy> <role switch>
                 <hold mode> <sniff mode> <RSSI> <channel quality> <SCO link>
                 <HV2 packets> <HV3 packets> <u-law log> <A-law log> <CVSD>
                 <paging scheme> <transparent SCO> <AFH cap. slave>
                 <AFH cap. master>


I have to leave for the day in about 60 minutes. I'll give the patch a try but 
it might be tonight before I report back (depending on how fast I can build 
kernels). Last night I went with 2.6.23.17 instead of 2.6.24.3, 
but I'd really like to see my headset working under 2.6.24.x kernels.




-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.