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

It has become abundantly clear that the Widcomm bluetooth stack included in the shipped ROM doesn't play nice with a variety of software, including visual voicemail and voice command. Thus, I would like to request that all custom ROMs and kitchens will include the more standard MS bluetooth stack rather than the $hitcomm stack if at all possible. Thanks in advance!

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

It actually has been an improvement with the connection in my car, so I don't think this sweeping generalization is the perfect answer ... I do admit 2.1 is supposed to be backward compatible and isn't working with some software, but some software is being updated to accommodate the updated stack. There's got to be a better answer than just not using the newer stack.

Also, wasn't the stack in the TP1 2.0 a Widcomm stack as well? Maybe I am confused.

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

It's not the BT version that is the problem. It's the fact that the stack is a Non-MS stack. The MS Stack works perfectly fine and is the generally accepted WinMo standard (and thus the most widely developed for) and there really was no reason to switch to something else. The TP1 has an MS stack. The last HTC to have a Widcomm stack was the XV6600/PPC6600 IIRC. When the stack works properly, it's great, but that seems to be the exception rather than the rule. It's having a ton of problems across the board with software, such as MSVC, VVM, etc., not to mention the nerfed PAN profile leaving ICS with no bluetooth option. Perhaps in the kitchens it could be made into a selectable option, but I for one hate the thing. Give me a 2.1 MS stack or even the 2.0 MS stack.

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

AFAIK they can't put the MS stack in because they would need a driver for it, and the driver doesn't exist, or something like that, so I think you're SOL.

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

I wonder if this stack is meant to interface with WM6.5 more then WM6.1, and they accepted a few inherent problems in order to get the phone out the door.

In other words, could there be some new bluetooth API or driver included in WM6.5 that isn't included in WM6.1, that will make everything fine once we have the WM6.5 ROM's???

I could be WAY off, but that's something I thought of.

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

From what I have seen on PCs, the stacks are compatible with certain chips, the driver is kind of a part of them. Like with dongles, you could download a different stack, ironically to not use the MS one since its profile support was horrible, and the common one to use was Widcomm.

Is the bluetooth built into the main Qualcomm chip? If so, I would think that should be compatible.

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

I don't think that is the case. I remember many people were switching to the MS bluetooth stack from Widcomm on the Blue Angel, but that was WM2003. Even if that is the case, I wouldn't doubt that the driver from HTC phones with similar chipsets would be compatible, such as the driver from the TP1.

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

I think the bluetooth chip is separate, since I found the MSM7600 datasheet (looking into the FM radio, which is located on the bluetooth chip) and it makes no reference to the bluetooth chip, leading me to believe it's separate.

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

Having tried a few different 6.5 ROMS on the 6800 with the MS stack, the bluetooth performance was better (in my car at least) than any 6.0 or 6.1 ROM which I've used, including the TP2, so I wouldn't worry about getting rid of Widcomm. On the other hand, the Samsung 760i which I had for a short time had Widcomm, and was universally panned for it lousy bluetooth performance. I would second the OP on this.

Please be sure...
 

Neither the Titan's nor the Raphael's shipped bluetooth works with Nissans (or Infinitis) that have navigation. Many have tried to fix it with no luck.

The Rhodium's is the first shipped bluetooth to work on a Sprint/Verizon HTC device in a long time.

History of the struggle here

I don't know enough about the specifics here to comment constructively, but I thought it was relevant.

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

Generally widcomm is a much much better stack that MS gives

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

I had the i760 too, until it was discontinued due to Bluetooth performance bugs. Maybe it was BECAUSE of this, but equally likely this is just coincidence.

Re: Please be sure...
 

The VZW Raphael worked fine in my 08 Altima, right from the get-go.

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

Just throwing my hat in the ring.

Takign apart many Rhodium and Whitestone ROMs show that the following packages are missing from every SYS;

Bluetooth
Bluetooth_Lang_0409

IMO, the newer stack works better for me, and won't be using the MS default. But maybe another chef... or maybe even you can create such a ROM.

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

The bluetooth stack that came on my TP2 works much better with BMW Bluetooth/iDrive...

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

Vote me out too.


For the first time in 2 years, I have an HTC pda that works with my Nissan Altima 08 with Factory Nav / BT

~ Widdie ~Wiiddie Widdie ~ Widcomm Wins~

Re: Please be sure...
 

Your Altima doesn't have factory GPS navigation. With/without gps makes a difference here.

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

This bluetooth stack kicks ***. sorry to hear that you don't like it.

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

I've never had any problems with the MS stack whatsoever on either the 6700, 6800, or TP1. I've had 2 devices with Widcomm stacks (XV6600 and TP2) and both have been subpar. The Widcomm stack lacks the PAN profile, has major issues with voice command, won't hang up, ignore, or redial when you hit the appropriate buttons on your headset, and does not work at all with visual voicemail. It will connect and function fine during calls, but that is about it. I know that these problems have been well documented in the main forum.

At least if the chefs don't want to replace it, perhaps they can give us the option to do so ourselves, like many have done with the sys files on the TP1 ROMs. I'd be willing to donate to have that ability. I'd make a ROM myself but I have neither the time to do it, the knowledge to do it, or the time to learn how.

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

Are those the MS Bluetooth packages? Perhaps you can detail them for me a little better and how they function. Is switching the stack as easy as swapping the packages out in the SYS? Also, would it be possible to create a standalone MS BT stack installer or create an option to install the MS stack within a kitchen?

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

It is going to be messy.

You will need to add

Bluetooth
Bluetooth_Lang_0409

into your ROM... as well as remove the Widcomm stack, which is scrambled up in the OEMDrivers folder. Again - MESSY.

Maybe once an unlocker is done some people can do trial and error to confirm what needs to be removed to wipe out the Widcomm stack.

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

Thanks for the response. Would be nice if the Widcomm stacks displayed all of their files in the Bluetooth settings like the old 6600 stacks. Perhaps I'll offer a bounty for the first person who can successfully get a fully functioning MS stack after the HardSPL comes out. I'd learn how to do it myself but like I said earlier I just don't have the time.

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

I would also love to see the bluetooth stack replaced with the MS stack. This stack is completely unusable with my Dodge U-Connect system. My TP1 (MS BT Stack) worked flawlessly.

Dave

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

Great!!!!
Glad to hear you are keeping it.

I myself love the new bluetooth software with the Sprint TP2's

It works great w/ all the bluetooth devices i have...

I just need to find a A2DP app that will work with it and everything would be great!!

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

Question for everyone:

How many of you can actually get your headset to end a call when you hit the end call button, and what type of headset are you using?

Nothing like driving in your car with your phone put away in your center console and leaving someone a voicemail only to realize your phone didn't hang up and having to fumble around while driving for your phone so you can end the call, all while trying not to swear up a storm due to your frustration into your buddy's voicemail.

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

I can't get my headset (Moto HX1) to end a call 90% of the time. I've even noticed that if I've been on the headset for a call, if I press the end button on the phone it still takes 2-3 seconds for the phone to hang up.

Beyond that, the A2DP is acting goofy for me. For example, if I connect up my Jaybird stereo earbuds and then press play on PocketPlayer, the phone loses the A2DP connection. I have to start PocketPlayer playing, THEN establish the A2DP connection. I'm having other odd issues with A2DP not wanting to connect with my Parrot car kit. This is Bluetooth 101 in my book, and it isn't working. I have 3 devices from 3 different manufacturers, and none of them work as they should with this phone, while all 3 worked perfectly with my TP1.

Perhaps this Widcomm stack is better, but if this is better, I want the one that's worse. I feel like I'm back in 2003 trying to get basic Bluetooth functions to work.

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

Not I (U-Connect). I think the only time mine has hung up when pressing the button is when the other end hangs up and the call just ends. I don't believe I've ever successfully ended a call with the handsfree button.

I have since turned off bluetooth all together, because it's just too frustrating to use in its current state.

Dave

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

I've noticed this as well. I'll push the end button on my headset and 75% of the time it WON't end, but then out of nowhere it will? This is on a Motorola H700

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

Same issues with the hangup button using the Plantronics Voyager Pro.

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

Same here....Motorola H710. I've now got into the habit of taking my phone out of it's case when I'm in the car and leaving it within arms reach so I can end calls....or at least make sure they've really ended when I think they have!

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