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

I know alittle bit about alittle bit about bt stacks, This is where the problem lays ms bt stack cant be the primary stack used by auto manufacs because the car companies dont want to give any money to ms, now the widcomm stack is more universal with foreign markets and is a default stack in many auto navs and radios. But this is where the good stuff ends widcomm stack is more of a highschool grad stack (generic stack)where ms stack is more of graduate school stack(more intuitive). widcomm is made to talk to car navs and radios very easily but just the basic level bt stuff. Now the ms stack is more of a intelligent stack dealing more with more complex (too many acronyms to names) versus the widcomm stack. Now if you dont want to do much other than talk to you car with your phone then yes you will want the widcomm stack but if you use it for more than that then the ms stack is way way better. Now both stacks can do what the other can do but its like asking a person with a high school diploma to take a test and asking a person with a graduate degreee to take a test both parties can take the test but its who gets the most questions right that matters. I urge all of the cookers out there to use the MS stack please. Especially Juicy. I used anologies instead of programming and stack acronym vs stack jargon.

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

I'd be interested to know the programming and stack jargon behind what you're saying.

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

I can only end calls in my car when the Bluetooth Fairy is riding shotgun -- which is very rarely. I contacted HTC through e-mail and said it worked with my Diamond and doesn't work now ... I got a response back that clearly showed my first e-mail wasn't read correctly. This is the second response:

"Hello Tammy,

First and foremost, let me extend my sincerest appologies. I misread your original statement regarding the end call functionality with the Diamond. I accidentally read it as "I had problems disconnecting calls with my Diamond" and missed the 'no' in that sentence. As for how widespread the bluetooth functionality issues are, there are a few customers contacting us. However, it appears that not everyone that is having issues is contacting us. This can make it extremely difficult for us to isolate the cause of the issue and work on a solution if one is possible. That said, we are researching the situation, but do not have any estimate as to when or if a fix will be made available, as Sprint has sole discretion on that matter since it is their branded version of the device. Even with that correction of my understanding of the situation, it does still stand that we do not have a soluntion for the problem at this time, and I apologize for any frustration you may have experienced due to either the issue at hand or my misunderstanding of the information you presented.

You can check for updates for your device on the following page: http://www.htc.com/us/faq_detail.asp...&act=faq&cat=0. When any updates become available, a software download tab will appear with the list of updates to select from. If you have any further questions or concerns, please contact us again or check www.htcwiki.com as well. Also, don't forget 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"

I hope more people who are having problems can start contacting HTC so they can tell it is a widespread problem.

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

At least an acknowledgment that the problem exists and a fix in the works!

http://i262.photobucket.com/albums/i...91-09-49PM.png

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

Sweet victory! I hope the fix is released soon... Thanks for posting that!

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

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

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

Thanks for trying. Widcomm stack is useless to me as well. I need Microsoft BT Stack and would flash just to get it. I hope someone gets it figured out soon

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

I would donate to that!

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

here is the widcomm stack and all its registry entires. this is in EXT format... maybe one of the geniuses can figure some stuff out from it..

I also have issues with my BT stereo in the car.. cannot hang up, same as everyone else.

is all that I noticed but I think that just replaces the bluetooth icon in the control panel.

Wirelessly posted (HTC-P4600/1.2 Opera/9.50 (Windows NT 5.1; U; en))

I love the new bluetooth stack, the sound qualtiy between my phone and my pioneer deck is fantastic. It was pretty awful on my TP. I haven't really tried ending a call cause I always let the other person end the call