Request for Chefs: Do NOT use Widcomm bluetooth stack from shipped ROMs

[Boo Boo]

i wish the bt stack would play ringtones and hangup calls when you hit the end button on the headset. at least the tp worked.

disapointed withthe inability to get a work around taken care of

[sammy12oz]

I have the Jawbone 2 and this is an issue for me as well. I cannot use the buttons on the headset to activate MSVC, end a call or redial.
This headset worked flawlessly with my touch pro.
It's extremely dissapointing to not have these features as I use them all day at work, or I did. Also I am in CT and even though I don't see it enforced it is ilegal to use a cell phone without a hands free device.
I really hope that this is addressed by HTC, the carriers or someone in the community.

[dodgeboy]

Originally Posted by raidzero

I have been working on removing the widcomm stack and am cooking again without it. I am no master at this by any means and my methods are pretty much brute force. I removed everything from oemdrivers that had a bt in the front (file name) except for the few modules, they stayed as they were in the TP oemdrivers. I then removed the widcomm registry entries from the rgu in oemdrivers. I very much doubt this will work. I am only doing it so toggleBTh.exe will work as it does not with the new stack. I have not tested with my car yet as I just got bluetooth working at all today. It did work fine with my cheapo earpiece. It is cooking now and I will report how it goes... it seems to me that what I did should work in theory, as all that is needed for MS BT to work are those SYS packages, which are included in this build. right? wrong?

edit: no luck.. no more widcomm in registry and no widcomm files = no bluetooth lol

Is the MS BT Stack available anywhere to try to install in its place? I really appreciate your work on this! I would definitely be willing to donate to whomever cooks a clean rom with the MS BT Stack.

[helix139]

Originally Posted by raidzero

I have been working on removing the widcomm stack and am cooking again without it. I am no master at this by any means and my methods are pretty much brute force. I removed everything from oemdrivers that had a bt in the front (file name) except for the few modules, they stayed as they were in the TP oemdrivers. I then removed the widcomm registry entries from the rgu in oemdrivers. I very much doubt this will work. I am only doing it so toggleBTh.exe will work as it does not with the new stack. I have not tested with my car yet as I just got bluetooth working at all today. It did work fine with my cheapo earpiece. It is cooking now and I will report how it goes... it seems to me that what I did should work in theory, as all that is needed for MS BT to work are those SYS packages, which are included in this build. right? wrong?

edit: no luck.. no more widcomm in registry and no widcomm files = no bluetooth lol

Try asking Juicy or MightyMike or Scrosler or one of the other chefs. Juicy said in another thread that the MS stack files just aren't present in our ROMs, but I believe he knows what they are and probably where you can get them. My guess is the MS stack can be pulled from one of the TP1 ROMs. Getting rid of the Widcomm stack is half the battle though. Outstanding work!

[the3rd]

more than happy to donate to the chef who gets the ms stack as well.

[ftc_osiris]

I will as well

[amw1972]

reading thru all the posts...its clear to anyone that pays attention that MOST of the notable cooks are not going to go back to the MS Stack anytime soon. Even members of the elite team represented early in the thread.

I think this is going to be fixed if we voice own complaints to HTC. Some of us paid top dollar for our bluetooth device...NOT to mention vehicles...and for all to play nice...seems the Widcomm stack is it...but MS needs to playball and allow the Widcomm stack play well with its software (MSVC to be exact.)

HTC needs to come up with a fix so we can hang up calls from out headsets...or else why bother with a headset!


so if I was using the headset...VC doesn't work...and I reach down to dial...get a ticket...can I sue HTC/M$ for the fine that i paid...would that be a class action suit if enough of us are affected??

[mikee4fun]

Only issue I have seen with the new widcomm stack is it has issues hanging up when the phone is off. I am sure we will find a way to fix this issue. On a positive spin the new bluetooth stack turns off the bluetooth audio gateway when you disconnect your headset so you battery life is much better. You can with the Microsoft stack with a registry change but it has issues reconnecting.

Yes the widcomm stack is the best ever, that I have used. This is going all the back to the xda II

[grv]

I'd donate to someone who can cook up a clean stable ROM with the MS stack too. No way to get AVRCP to work with anything but HTC Medai Player, WMP or Pocket Player on the TP2 with the Widcomm stack, which just about has me on the point of sending the TP2 back.

If anybody ever figures it out, it would be awesome. I really like the TP2 otherwise, but BT is a dealbreaker for me.

[helix139]

It appears the hanging up issue is related to the data connection. When the connection is on or dormant, the BT headset will not hang up. When it is completely disconnected, the headset hangs up no problem. Perhaps someone can figure out a fix?