5 replies to this topic

[hendersj]

Hi,

I've been building my own CM 7.2 RC1 roms for a few weeks now for my HTC Incredible, and overall am really happy with it.

One thing that has been an issue, though, is that people whom I call tell me they can't hear me when I'm using my bluetooth headset.  If I use the regular headset or speaker, they can hear me fine.

I'm updating with the latest files from the repo, but wonder if anyone else has seen this with the RC1 builds and if there's a known issue (or a fix)?

Thanks

ETA:  I tested this with the build I compiled on April 3, and I find that if I hold the headset directly in front of my mouth, I can be heard, but when it's on my ear, the amplification is still insufficient to be heard.

Edited by hendersj, 05 April 2012 - 06:27 PM.

[hendersj]

Seems that this is still a problem - I've tried making a few changes to the audio.conf file for this and the other issue I posted about here - is anyone else seeing this behaviour?

[PolynesianMedic]

I have not seen or heard this before.  Are you sure that it isn't your bluetooth device itself causing the issue?

[hendersj]

Pretty sure, it works fine on my laptop and on HTC's stock ROM (as well as CM 7.1) on this device.  Just seems to be a problem with 7.2 RC1.

[hendersj]

I've just installed 7.1 on my wife's Incredible and her headset (same make/model phone and headset for both devices) works just fine.  It's definitely something in the 7.2 RC1 release that's not right....

[hendersj]

I just compared the logcat output from both phones/headsets, and noticed that on CM 7.1 I see:

I/BluetoothDeviceProfileState(  177): Entering ACL Connected state with: 102
D/AudioFlinger(  129): setParameters(): io 0, keyvalue bt_headset_name=Motorola H17;bt_headset_nrec=on, tid 226, calling tid 281
D/AudioHardwareQSD(  129): Using default acoustic parameters (Motorola H17 not in acoustic database)
I/AudioHardwareQSD(  129): Routing audio to No microphone Wired Headset (0,8)
D/AudioFlinger(  129): setParameters(): io 0, keyvalue bt_headset_nrec=off, tid 1787, calling tid 281
D/AudioHardwareQSD(  129): Turning noise reduction and echo cancellation off for BT headset
I/BluetoothDeviceProfileState(  177): A2dp:Connect Other Profiles
D/BluetoothA2dpService(  177): connectSink(00:24:1C:6E:1D:F5)
W/BT HSHFP(  281): RFCOMM poll() returned  success (1), but with an unexpected revents bitmask: 0x18
I/Bluetooth HeadsetBase(  281): headset read error 5
D/BT HSHFP(  281): Device: 00:24:1C:6E:1D:F5 Headset  state2 -> 0, result = 0
E/BluetoothEventLoop.cpp(  177): event_filter: Received signal org.bluez.Device:PropertyChanged from /org/bluez/2333/hci0/dev_00_24_1C_6E_1D_F5
D/BluetoothService(  177): setRemoteDeviceProperty addr = 00:24:1C:6E:1D:F5 name = Connected value = false
V/BluetoothEventRedirector( 2214): Received android.bluetooth.headset.action.STATE_CHANGED
D/CachedBluetoothDevice( 2214): onProfileStateChanged: profile HEADSET newProfileState 0
I/BluetoothDeviceProfileState(  177): Entering IncomingHandsfree state with: 6
E/BluetoothDeviceProfileState(  177): Processing command:6
I/BluetoothDeviceProfileState(  177): Entering ACL Connected state with: 102

But on CM 7.2 RC1, I see:

I/BluetoothDeviceProfileState(  184): Entering ACL Connected state with: 102
D/BT HSHFP(  515): Saved priority 00:24:1C:6E:29:46 = 1000
D/AudioFlinger(  131): setParameters(): io 0, keyvalue bt_headset_name=Motorola H17;bt_headset_nrec=on, tid 177, calling tid 515
D/AudioHardwareQSD(  131): Using default acoustic parameters (Motorola H17 not in acoustic database)
I/AudioHardwareQSD(  131): Routing audio to Speakerphone
D/AudioFlinger(  131): setParameters(): io 0, keyvalue bt_headset_nrec=off, tid 440, calling tid 515
D/AudioHardwareQSD(  131): Turning noise reduction and echo cancellation off for BT headset
I/BluetoothDeviceProfileState(  184): A2dp:Connect Other Profiles
D/BluetoothA2dpService(  184): connectSink(00:24:1C:6E:29:46)
W/BT HSHFP(  515): RFCOMM poll() returned  success (1), but with an unexpected revents bitmask: 0x18
I/Bluetooth HeadsetBase(  515): headset read error 5
D/BT HSHFP(  515): Device: 00:24:1C:6E:29:46 Headset  state2 -> 0, result = 0
V/BluetoothEventRedirector( 5498): Received android.bluetooth.headset.action.STATE_CHANGED
D/CachedBluetoothDevice( 5498): onProfileStateChanged: profile HEADSET newProfileState 0
I/BluetoothDeviceProfileState(  184): Entering IncomingHandsfree state with: 6
E/BluetoothDeviceProfileState(  184): Processing command:6
I/BluetoothDeviceProfileState(  184): Entering ACL Connected state with: 102

I find the difference in the bolded lines from each log to be interesting....Can anyone tell me if that is expected?