Cannot hang up call with Infiniti bluetooth

[madmax2k1]

Ok I took the plunge and implemented the following from the hack above:

Modify the HandsFree plug-in:

HKLM\Software\WIDCOMM\Plugin\HandsFree
i. Change SupportedFeatures to 45 (default is 1135)
ii. Add value HFBDA binary, set to same value as LastConnectedBda
iii. Add value HFDeviceType decimal 2

and it works; I just tested it on my car, and I was able to make a call and hangup without issues.

[p-slim]

Originally Posted by madmax2k1

Ok I took the plunge and implemented the following from the hack above:

Modify the HandsFree plug-in:

HKLM\Software\WIDCOMM\Plugin\HandsFree
i. Change SupportedFeatures to 45 (default is 1135)
ii. Add value HFBDA binary, set to same value as LastConnectedBda
iii. Add value HFDeviceType decimal 2

and it works; I just tested it on my car, and I was able to make a call and hangup without issues.

I won't be able to try for an hour, but if this works you're the man.

[helix139]

Originally Posted by madmax2k1

Ok I took the plunge and implemented the following from the hack above:

Modify the HandsFree plug-in:

HKLM\Software\WIDCOMM\Plugin\HandsFree
i. Change SupportedFeatures to 45 (default is 1135)
ii. Add value HFBDA binary, set to same value as LastConnectedBda
iii. Add value HFDeviceType decimal 2

and it works; I just tested it on my car, and I was able to make a call and hangup without issues.

Problem solved on my Jawbone Prime! Additionally, it gets rid of the lag when confirming the contact you wish to dial when using voice command. This bluetooth stack is almost bearable now. All we need now is the PAN profile.

Anyone want to cab this up?

[Austin808]

Originally Posted by helix139

Problem solved on my Jawbone Prime! Additionally, it gets rid of the lag when confirming the contact you wish to dial when using voice command. This bluetooth stack is almost bearable now. All we need now is the PAN profile.

Anyone want to cab this up?

Where do I find the following value?
Add value HFBDA binary, set to same value as LastConnectedBda

I can't find the LastConnectedBda value.

Edit: Nevermind, I had to pair my bluetooth headset before the value would show up. I quickly tested with my Plantronics Voyager 510 and it appears to fix my hangup issue. Also fixed my issue with answering just sends ringtone to bt headset. I will continue testing this.

After further testing it apears that the hangup issue is not gone. The last time I tried I had to press the button about 5 times before it hung up. Tried a few more times sometimes it works right away and sometimes I need to press the button many times.

[patrickoneal]

Originally Posted by madmax2k1

Ok I took the plunge and implemented the following from the hack above:

Modify the HandsFree plug-in:

HKLM\Software\WIDCOMM\Plugin\HandsFree
i. Change SupportedFeatures to 45 (default is 1135)
ii. Add value HFBDA binary, set to same value as LastConnectedBda
iii. Add value HFDeviceType decimal 2

and it works; I just tested it on my car, and I was able to make a call and hangup without issues.

Thank you! Worked for me. I even clicked the thank you button I've got a motorola IHF1000 installed in my truck, and I haven't really been able to use it since I had my mogul, and even then it may not have worked right. The TP1 didn't work right, and my Sprint TP2 would hang up 10 seconds after pressing the end call button. Only my motorola i355 worked properly. That's unacceptable. I downloaded this registry editor and had to guess on a few things:

http://download.majerus.net/RegEdit/...t.Mrln_ARM.CAB

Supported features was '1383' on my phone, but I went ahead and changed it to what you said. Can you explain exactly what the registry changes do?

[keentech]

Anyone else confirmed this is a fix?

[dbldwn02]

Originally Posted by keentech

Anyone else confirmed this is a fix?

Not sure how many people you want to confirm this, but seeing that no-one has claimed it doesn't work we're sitting at about a 100% success rate.

[Austin808]

Actually if you look a few posts back I said that it worked at first, but then after further testing it started to not hang up again.

[JZ*]

Originally Posted by Siflan

It's been like that with many headsets. I have a Jawbone and it does the exact same thing. Guess we won't know 'til someone figures it out. I need to call HTC.

Don't bother...or maybe you should...what I mean is, I had a long email conversation with them...string attached if you care to read...WARNING, LONG READ!... Start at the bottom and read up (the first question was esentially that BT and Voice Command doesn;t work right)...enjoy!


Seems like a pretty "non-answer" to me...and a little backwards "At this time the testing of bluetooth headsets has not yet been completed, and the information as to which bluetooth devices have been found to be compatible has not yet been made available to us by the development department"...so you release a device, without testing the bluetooth for compatibility...like I originally stated. Thanks for confirming.

I am done with this back & forth email crap...face it, you guys did not thrououghly test this before changing the stack, period.


Hello John,

At this time the testing of bluetooth headsets has not yet been completed, and the information as to which bluetooth devices have been found to be compatible has not yet been made available to us by the development department. We are eagrly awaiting this list so we may better assist customers such as yourself with setting up their devices to best suit their needs. We do appreciate your patience in this situation, but we do not have an estimate as to when exactly the compatibility list will be completed. Please check back about once a week for any updates as to the availablity of the compatibility list.

If you have any further questions or concerns, please contact us again or check www.htcwiki.com as well. We also invite you to participate in our feedback survey at survey.htc.com/worldwide. We enjoy getting feedback from our customers and look forward to hearing from you.

Best regards,

Joseph


Oh I see...so, with this in mind, per your statement, which BT headset did HTC test, that works as intended, with Voice Comand utilizing all features from the Microsoft (the developer of Windows Mobile BTW), that you guys tested? I want this info so I can verify these statements, and have a working phone. Please send the info to me ASAP. Thanks


Hello John,

I am glad to hear that you were able to get your Jawbone headset to work with your original Touch Pro, as this was not always the case for every customer. We do test our devices with popular bluetooth headsets. Issues arise when the manufacturers of those headsets build their devices to be compatible with a different bluetooth stack or impliment features that conflict with the software on our devices ,such as the BlueAnt's built in voice command features that seem to interfere with Microsoft Voice Command. With such devices there is little we can do to improve compatibility without making large changes to our devices that could cause far more serious problems.

If you have any further questions or concerns, please contact us again or check www.htcwiki.com as well. We also invite you to participate in our feedback survey at survey.htc.com/worldwide. We enjoy getting feedback from our customers and look forward to hearing from you.

Best regards,

Joseph


My HTC Touch Pro worked PERFECTLY with my Jawbone...So your resonse is not really reasonable...I am happy you are working out the problems with Voice Command...hopefully this will not take too long to address.

You really should consider better testing with popular headsets as well...


Hello John,

We have actually had some issues with Jawbone brand headsets having connectivity issues with our devices even before we began using the Broadcomm stack, and the issues you are experiencing do appear to be fairly typical of our devices that use the Microsoft stack attempting to interface with a Jawbone headset. We have received some reports of Jawbone devices working with some of our devices, but over all there have been compatibility issues since before the use of the Broadcomm stack.

If you have any further questions or concerns, please contact us again or check www.htcwiki.com as well. We also invite you to participate in our feedback survey at survey.htc.com/worldwide. We enjoy getting feedback from our customers and look forward to hearing from you.

Best regards,

Joseph



First off, I appreciate your quick responses, AND I appreciate that your are looking to fix Voice Command. This is a start.

To answer your question. Yes, I have already done a hard reset...it makes no difference. The Headset I am using is one of the most popular, and reliable out there; Jawbone Prime and Jawbone 2. The headset should disconnect, it does not, and this is not correct and should have been uncovered in testing...which headset actually works with this model, can you give me that answer, I would like to try it and verify myself.

I am pleased that you are addressimg one of these issues...I hope the "Leo" is not plaged with this issue...or I will most likely switch brands, thanks for the response.
Hello John,

I understand that the answer you have received is frustrating, and I understand that the issues you are experiencing have not been resolved at this time, but beyond the basic troubleshooting of the bluetooth connectivity and attempting a factory reset of the device to help rule out any software glitches there is little else we can do without Sprint requesting a ROM update to be created for the device. We are aware of an issue with Voice Command not correctly announcing incoming calls, and are currently working for a solution on that issue at the behest of Sprint. Please understand that a change to the device as large as changing the bluetooth stack is not something that can be done through a simple hotfix like the Voice Command situation may be addressable, because there are numerous changes that have to be made to a number of device systems. Additionally, we can not guarantee that even after such an update is applied to the device that there will be increased compatibility with your particular bluetooth accessory. This is because each manufacturer builds their bluetooth devices differently, and there are multiple bluetooth stacks that they try to be compatibile with. Because of differences between these bluetooth stacks, there are some devices that simply will not work properly with some stacks if they work at all.

If you would like to perform a factory reset to try and resolve these bluetooth issues you are experiencing, please understand that such a reset will remove all data from the device and reset it to the settings it had when it was removed from the box. To perform a factory reset, conduct the following steps:

1. With the device powered off, press and hold the Talk/Send, End, and Power buttons.
2. Continue to hold these three keys until a prompt appears on the screen that talks about deleteing all personal data.
3. Release the three buttons and press Volume Up as indicated by the prompt.
4. Allow the device a few minutes to reinstall all neccessary software, and be sure to conduct any set up steps the device advised to conduct.

I can not guarantee that this will have any affect on the issues you are experiencing, through you may be able to resolve the issue with the bluetooth headset entirely by trying a different bluetooth headset.

If you have any further questions or concerns, please contact us again or check www.htcwiki.com as well. We also invite you to participate in our feedback survey at survey.htc.com/worldwide. We enjoy getting feedback from our customers and look forward to hearing from you.

Best regards,

Joseph


No, the issue is NOT resolved. The Broadcomm Bluetooth stack was a big mistake to use vs. the established Microsoft stack you had been using. To simply state that there is no fixes for these issues is NOT acceptable. Your phones/PDAs cost much more that your competitors, and I can appreciate the build quality of your devices…but to suddenly switch to a different stack, and not do proper testing (which if properly done BTW this problem would have surfaced immediately on your new devices) I don’t understand.

In addition to the hangup issue, VoiceCommand doesn't work correctly anymore.

HTC has a responsibility to fix this issue, not pass it off on Sprint or Verizon or whomever! Seems to me you should dump the Broadcomm stack and go back to what works…You need to rebuild your ROM without Broadcomm and get this to your consumer base

Please fix YOUR Touch Pro 2…


Hello John,

I understand how frustrating it can be when a device does not function as expected. In order to increase the Touch Pro 2's compatibility with other bluetooth devices, we began using the Broadcomm bluetooth stack. This has caused some compatibility issues with devices that were 100% compatible with some of our previous devices. At this time there are no fixes for these compatibility issues. Our development department must work with Sprint to determine when and if an update will be released for their version of the device. The same is true with Verizon and their version of the device, and T-Mobile and their version of the device as well. As for attempting to correct the issue, you can try unpairing, then re-pairing the devices to see if this increases performance of the headset.

If you have any further questions or concerns, please contact us again or check www.htcwiki.com as well. We also invite you to participate in our feedback survey at survey.htc.com/worldwide. We enjoy getting feedback from our customers and look forward to hearing from you.

Best regards,

Joseph

[TheMostToys]

I made these two changes and it works better (not 100% of the time but much better than never.)
ii. Add value HFBDA binary, set to same value as LastConnectedBda
iii. Add value HFDeviceType decimal 2