|
||||
Re: BT Headset Not Connecting to Incoming Calls
Bluetooth is notoriously buggy on the TP2.
Supposedly, the newest VZW ROM fixes a lot of the issues, but I don't know that anyone has parsed those changes out yet; would love to see this get some attention. In the mean time, try these reg edits, as they work for a lot of people: 1. Modify the HandsFree plug-in: HKLM\Software\WIDCOMM\Plugin\HandsFree i. Change SupportedFeatures to 45 (default varies; make a note of it, just in case) ii. OPTIONAL Add value HFBDA binary, set to same value as LastConnectedBda iii. Add value HFDeviceType decimal 2 2. Modify the WIDCOMM bluetooth general settings: HKLM\Software\WIDCOMM\BtConfig\General i. OPTIONAL Change bdaddr to (no value) ii. Change/Add (some phones do not have this key) DisableReopenAudio to decimal 0 (default is 1) |
|
||||
Re: BT Headset Not Connecting to Incoming Calls
Okay, this worked a bit. If I answer a call by hitting the button on my headset, audio comes through the BT. However, if I answer with the phone itself, audio comes through the phone, even if the BT is connected. So not perfect, but better than before.
As for the edits, I didn't do the optional ones since they were, well, optional. I did the non-optionals first to see how they'd turn out. Also, I'm not a whiz at this editing thing (just figured out the basics a few weeks ago) so I assumed that the values I had to add were supposed to be something called "DWORD". I use PHM editor, and when adding values I get the options of DWORD, bianry, and string. I've only seen DWORD referenced in various posts, so that's why I figured that was the correct value. Quote:
|
|
||||
Re: BT Headset Not Connecting to Incoming Calls
I identified the above as "optional" because they tend to reset themselves. They just list a mac address of the last connected devices; doesn't seem to do much more than that.
Two others I forgot to include:
And yes, dword is correct; it can be either decimal or hexadecimal. |
|
|
|