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

helix139 · #1 (**permalink**) 09-17-2009, 10:10 PM

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!

**meatgel** · #2 (**permalink**) 09-17-2009, 10:20 PM

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.

helix139 · #3 (**permalink**) 09-18-2009, 09:51 AM

Quote:

Originally Posted by meatgel

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.

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.

iamrobk · #4 (**permalink**) 09-18-2009, 12:20 PM

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.

zim2323 · #5 (**permalink**) 09-18-2009, 01:47 PM

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.

Kamokazi · #6 (**permalink**) 09-18-2009, 01:53 PM

Quote:

Originally Posted by iamrobk

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.

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.

helix139 · #7 (**permalink**) 09-18-2009, 02:20 PM

Quote:

Originally Posted by iamrobk

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.

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.

iamrobk · #8 (**permalink**) 09-18-2009, 02:25 PM

Quote:

Originally Posted by Kamokazi

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.

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.

ebb · #9 (**permalink**) 09-18-2009, 04:20 PM

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.

FZ1 · #10 (**permalink**) 09-18-2009, 09:31 PM

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.