It's incorrectly assigning the bluetooth class to my dongle as well.
My phone defaults to "headset mode" if the last two bytes of the device class
aren't defined, like this:
bren...@ohaithar:~$ hciconfig -a
hci0: Type: BR/EDR Bus: USB
BD Address: 00:15:83:15:A3:90 ACL MTU: 672:4 SCO MTU: 48:1
UP RUNNING PSCAN
RX bytes:716 acl:0 sco:0 events:26 errors:0
TX bytes:109 acl:0 sco:0 commands:26 errors:0
Features: 0xff 0x3e 0x85 0x38 0x18 0x18 0x00 0x00
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: RSWITCH HOLD SNIFF PARK
Link mode: SLAVE ACCEPT
Name: ''
Class: 0x480000
Service Classes: Capturing, Telephony
Device Class: Miscellaneous,
HCI Version: 2.0 (0x3) Revision: 0xc5c
LMP Version: 2.0 (0x3) Subversion: 0xc5c
Manufacturer: Cambridge Silicon Radio (10)
The device class should be 0x480100 or 0x48010C
I've tried changing it in /etc/bluetooth/main.conf but it seems bluez
completely disregards the config files.
The sheer lack of documentation is compounding the problem. It seems with every
release of bluez all of the previous documentation (That was painstakingly
figured out by hand because the bluez developers don't document anything at
all) is completely invalidated.
Setting the class by hand works for a few minutes until bluez sets it back to
an incorrect value again.
If the original/current developers aren't willing to stop breaking backwards
compatibility every time some documentation is made OR document their new
releases with information that will help the end user the code should be forked
or the Ubuntu team should stick with a version so these insane inconsistencies
between releases won't be an issue in the future. </rant>
If anyone has an idea what is causing this nonsense I would be grateful.
--
cellphone recognizes paired Ubuntu computer as headset
https://bugs.launchpad.net/bugs/442424
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
