Bounty for working MS Bluetooth stack on TP2

[helix139]

I'm sick of this bluetooth stack and its neverending issues so I'm offering a $50 bounty for whoever can get the MS bluetooth stack working fully on an otherwise stock TP2 ROM for both Verizon and Sprint with the standard set of profiles (Headset/handsfree, PAN, OBEX, DUN, Stereo, File Transfer, Activesync, Print, etc. basically everything available on the TP1) and can explain how they did it. Any and all methods are acceptable, including an installable .cab or cooking it into the stock ROM.

If the Widcomm stack works fine for you, then great and this topic does not concern you. This thread is not to debate which stack is better or for people to share their experiences on what works. It is for donating to the bounty for a working MS stack ONLY.

As I've never setup a bounty before, if someone could PM me the easiest way to do this I would be very grateful.

Anyone else who wishes to contribute, please post your amount below and PM me. will keep track of the total amount so far at the bottom of this post.

Current Total Bounty: $145 (11/17 8:44 AM)

[dbldwn02]

$10 right here! (Yea, I'm cheap, but I just dropped $350 on this phone haha)

As long is it permanent fix. Thanks to all!

[appzattak]

I dont get what is wrong, I think it works fine. I've not had one issue with BT at all.

[helix139]

Originally Posted by appzattak

I dont get what is wrong, I think it works fine. I've not had one issue with BT at all.

Headsets aren't hanging up, Voice command is having all kinds of problems, redialing isn't working, etc. There are numerous threads on this and if the Widcomm stack works fine for you, then great, but there are a great many of us who are VERY dissatisfied with it.

If Widcomm works for you, then fine. No need for you to post in this thread. Not to be a jerk, but this thread is for contributions to the bounty for those who want the option of using the MS stack only.

[appzattak]

Originally Posted by helix139

Headsets aren't hanging up, Voice command is having all kinds of problems, redialing isn't working, etc. There are numerous threads on this and if the Widcomm stack works fine for you, then great, but there are a great many of us who are VERY dissatisfied with it.

If Widcomm works for you, then fine. No need for you to post in this thread. Not to be a jerk, but this thread is for contributions to the bounty for those who want the option of using the MS stack only.

wow, I honestly do not have any of those issues and use them all. Could it be the headsets or devices? I use a q1 blueant and the thing is awesome, answering, hanging up....but yeah, good luck

[helix139]

Originally Posted by appzattak

wow, I honestly do not have any of those issues and use them all. Could it be the headsets or devices? I use a q1 blueant and the thing is awesome, answering, hanging up....but yeah, good luck

It's happening with multiple headsets and handsfree devices, including popular ones like the entire Jawbone series (which works perfectly on the MS stack) and is consistent from device to device, so no, that isn't the problem. As far as I know, only Nissans with factory nav had problems with the MS stack, so now instead of a small subset of users with no functionality, we have a very large subset of users with significant loss of functionality. It's not a hands free device if i have to dig my phone out of my center console every time I want to end a call.

[mikee4fun]

Originally Posted by helix139

Headsets aren't hanging up, Voice command is having all kinds of problems, redialing isn't working, etc. There are numerous threads on this and if the Widcomm stack works fine for you, then great, but there are a great many of us who are VERY dissatisfied with it.

If Widcomm works for you, then fine. No need for you to post in this thread. Not to be a jerk, but this thread is for contributions to the bounty for those who want the option of using the MS stack only.

I thought I would chime in and at least help on the widcomm end call issue. I found a real working solution for headsets not hanging up. You have to disable internet being always on. You can use hd or diamond tweak to do this. I would not use advanced config as it causes a lag in answering the phone. I have cooked quite a few roms and can confirm this does work. I stumbled across this fix when I went to hang up the phone, quite a few times I would get a could not connect #777. So if you set your connection to disconnect after 10 minutes and then soft reset the phone. You will no longer have end call lag.

Another post by apristel's Avatar
apristel http://forum.ppcgeeks.com/showpost.p...73&postcount=1 is to go into this registry key and change it. I have had it at 0 and at 1000 and see no difference. But I thought I would add this to my post.

Registry Edit:

[HKEY_LOCAL_MACHINE\Software\HTC\PHONE\PhoneExtendS etting]
"EndCallTime"=dword:1000

1000 = 1 second

If this helps your end call lag, which it will, please give me a thanks.

Cheers,

Mikee

[helix139]

Originally Posted by mikee4fun

I thought I would chime in and at least help on the widcomm end call issue. I found a real working solution for headsets not hanging up. You have to disable internet being always on. You can use hd or diamond tweak to do this. I would not use advanced config as it causes a lag in answering the phone. I have cooked quite a few roms and can confirm this does work. I stumbled across this fix when I went to hang up the phone, quite a few times I would get a could not connect #777. So if you set your connection to disconnect after 10 minutes and then soft reset the phone. You will no longer have end call lag.

Another post by apristel's Avatar
apristel http://forum.ppcgeeks.com/showpost.p...73&postcount=1 is to go into this registry key and change it. I have had it at 0 and at 1000 and see no difference. But I thought I would add this to my post.

Registry Edit:

[HKEY_LOCAL_MACHINE\Software\HTC\PHONE\PhoneExtendS etting]
"EndCallTime"=dword:1000

1000 = 1 second

If this helps your end call lag, which it will, please give me a thanks.

Cheers,

Mikee

The problem with the data issue is if you use push email it is not workable. This stack is just plain bad.

[isdnmatt]

I think you should set up a PayPal account to get people to donate to if your serious. I've seen too many times were people said they would contribute, just to disappear when it was time to pay up.

So set up a donation account on paypal and post a link here. Then keep updating the available balance in the account on this thread. However, I have no problem with the widcomm bluetooth stack except that my bluetooth headset sometimes needs two clicks to hang up and that my car bluetooth takes forever to hang up. Otherwise everything else works fine.

[helix139]

Originally Posted by isdnmatt

I think you should set up a PayPal account to get people to donate to if your serious. I've seen too many times were people said they would contribute, just to disappear when it was time to pay up.

So set up a donation account on paypal and post a link here. Then keep updating the available balance in the account on this thread. However, I have no problem with the widcomm bluetooth stack except that my bluetooth headset sometimes needs two clicks to hang up and that my car bluetooth takes forever to hang up. Otherwise everything else works fine.

I have a personal paypal account, but I've never set one up to accept donations before. Perhaps you could direct me as to how this can be done?