I have Verizon's Touch Pro 2 and it appears to have the Widcomm bluetooth stack. I have had a really terrible time using the phone with my bluetooth enabled car stereo (6.1 and 6.5 stock ROMs). From a ton of reading, I think it may be related to the Widcomm bluetooth stack. My questions are:
1. How can I verify which bluetooth stack I actually have?
2. Is it possible to replace it with Microsoft's?
3. If so, where can I get it from?
I'm sure this information is out there somewhere, but it's just so scattered, I can't really find any solid answers. Thanks.
There is not a way to replace the stack yet and none of the others are compatible with the hardware in these devices. Rhodium devices run Widcomm stacks, which are not that good (even on PC...). The new (leaked) T-Mobile rom leak is supposed to have fixes for some of the problems we currently have with this stack. Hopefully, that's true.
Related
Ok so this is not the only phone that I can see that is wireless everything but does not support A2DP so you can listen to the mp3 player wirelessly??? I have seen that some have updated other units (MDAIII) to use a BT stack from broadcom and I was wondering if it is possible to do it on the sp5? I am guessing that using the broadcom stack does not require BT 1.2 but I am not sure what stack the sp5 is using and where I would get the updates. I am also reading that most that have done an update have mention static if they move around?? Why then would you need BT if you cannot move?? Is this then the V1.1 causing the problem and why it should be on 1.2?? :?
more info
Ok so I have asked the question about the sp5 & sp5m about A2DP so you can use stereo bluetooth headphones that include player controls and I found some answers.
A2DP only fully works on Bluetooth V1.2 and these units only V1.1. I have seen that some people have installed some third party BT stacks on there BT V1.1 units to get high quality stereo profiles but they do not have player control. Also it may not even be A2DP it may just be a facsimile but more interesting it may be A2DP. When looking at the specs of phones it says Bluetooth V1.1 but does not say which silicon (Chip) is in the unit which is very important because the chips are backwards compatible. Meaning it may be V1.1 but the chip maybe able to run V1.2 because the manufacture just put in V1.1 stack and rom. So we should all be not asking about new stacks and upgrades but first ask which chip is in the units and if it is a V1.2 compatible, then we should start demanding rom and stack upgrades now. As for the chips the V1.2 and more chips have been out for at least 2 years so the manufactures cannot say the release of them postdated their own development date unless they have been hand building the units for the last year and that gave them one year to test.
Well can someone please tell me which or who’s BT chip is in the sp5 and sp5m
I've heard about a bunch of new roms (the BLACK and LVSW) that have somehow cleared up that nasty A2DP bug in the Microsoft BT stack that caused certain headsets to buzz and hiss with certain frequencies.
I'm wondering if anyone here knows how that works, what has changed in these new Roms? Are they updated bluetooth drivers from MS?
I'm wondering if we can't put together a new a2dp patch for other devices so that additional phones can benefit as well, without getting a whole new rom (similar to the way the initial Tornado A2DP patch was circulated around).
Anyone have any info?
Can anyone even verify that this is true? (I don't have a hermes, but I do have an i.tech R35 headset with horrible distortion from any windows Mobile device playing music... I'm just assuming what I've heard is true about new roms fixing it...)
The only change is to some registry entries, the HTCustom tool should work on most any phone. Black's config tool should work but sometimes crashes on other roms when you try to save.
I have got the same problem with my iTech. I think it is something related to the design of the bluetooth headset. Is anyone experiencing the same problem with a solution?
nope maybe your release is a bad bath?
My Hermes with the Black ROM works fine with my Jabra BT620s. Hands-free mode works flawlessly too.
porkchop83 said:
nope maybe your release is a bad bath?
Click to expand...
Click to collapse
No no no, this is KNOWN issue with the MS stack and certain Bluetooth headsets, including the R35.
Its not the headset.
Proof is that when paired with another device, IE a nokia, or PC running bluesoleil, it works just fine- no hissing, very good audio quality.
Also, tested on a Wizard using the Widcomm stack instead of the MS stack, and sure enough it works GREAT!
So, its clearly a problem with the MS Windows Mobile stack, and in fact it has been discussed in various forums here.
Shadowmite, are you sure its just registry changes?
Is there any way to find out what they are?
Dishe said:
No no no, this is KNOWN issue with the MS stack and certain Bluetooth headsets, including the R35.
Its not the headset.
Click to expand...
Click to collapse
Correct. I had that problem with my Vodafone V1640 (HTC Universal). Kind of solved that problem using the Widcomm stack patch uploaded by someone here. Go search for it.
richardlai said:
Correct. I had that problem with my Vodafone V1640 (HTC Universal). Kind of solved that problem using the Widcomm stack patch uploaded by someone here. Go search for it.
Click to expand...
Click to collapse
Yes, I mentioned that I had it working with the Widcomm stack on a Wizard, but I'd rather have a working MS stack for various reasons including the Widcomm stack's instability on certain devices, and more importantly, its not available on the Tornado and Vox (or any smartphone), which is my device of choice at the moment!
So, once again, does anyone know what these new roms do to "fix" the problem?
Its gotta be something I can re-create...
Dishe said:
Yes, I mentioned that I had it working with the Widcomm stack on a Wizard
Click to expand...
Click to collapse
Sorry, I missed that part.
I didn't notice that Bluetooth performs differently in custom ROMs on the same hardware. If it is true, the ROM creators would know what they have done. Try contacting them directly if no one else here knows.
I've searched around for this and can't find anything, so maybe someone can help to point me in the right direction or let me know that at least the problem is known but not fixed yet.
I can't get Wifi and Bluetooth to work on my 8525 with WM6, currently using Schap's 3.54c rom and radio version 1.48.
I have motorola s805 stereo bluetooth headphones and would like to stream radio over my work's wifi and hear it on my headphones.
The problem is Neither wifi or bluetooth work reliably when used at the same time, (no problems individually). I have even tried reducing the bit pool, but can't take it below 24 because it sounds to bad then, but it still doesn't work.
Anyone have any ideas or can at least verify you have the same problem?
I have the same issue when trying to play internet radio over wifi with my ht820 a2dp linked to the jasjam (Sleuths v2 rom). The only time i ever got a2dp and wifi streaming to work was with the widcomm bt driver that is now extinct.
Thus i have come to the conclusion that the problem is not with the hw but has more to do with the standard ms bt stack.
If anyone has found a workaround please do share
Thats a start
Thanks, that is helpful.
I remember seeing a widcomm stack thread....
http://wiki.xda-developers.com/index.php?pagename=Hermes_Widcomm_stack
I'm going to check that out, also if there is a specific rom that comes with the widcomm stack I'd be interested to know.
I find that with bluetooth turned on I can associate to my Cisco AP at all. As soon as I turn Bluetooth off it works fine.
I had hoped my issue was due to the way the particular WM6 was put together but now Im using offical Dopod and it is the same.
Widcomm stack
Well I found this
http://www.htc-devs.com/uploads/Univ...m_bt_stack.CAB
at the end of the Widcomm stack for Hermes development thread.
I'm not sure where it came from, but I installed it and so far I can use IE while connected to my home wireless network, and listen to music on my headphones.
The com manager will not show bluetooth as being on, but go to settings-bluetooth and you can re-pair.
Currently I'm getting some hiccups, but its working at least. I'll keep you updated and I would still like to see a rom that incorporates this stack so that the com manager works right.
It also changes the headset icon on the top bar.
Streaming!
I'm streaming SomaFM with no problems!
AVRCP problems
I didn't notice this at first, but after the widcomm stack has been installed the AVRCP functions don't work... so Im going back.
AVRCP
It works in WMP, just not audiomanager anymore.
Bricking Blog
Pretty much what this thread has turned into.
If you install that cab above, don't uninstall it, you'll get bricked.
helpful reading
Hello all chefs, I'm having a pain with the BT interface to my car kit and headset on the current ROM, on other ROM's its been ok, is there any way to create a CAB with only the bluetooth components and their dependancies in? If so can we populate this thread with ones from your ROM's
BT
How I would appreciate this...
Off-topic a bit maybe, but I have been trying for long without luck to backup pairing (registry) of GPS and car BT devices and then reinstall them (either after flashing same ROM or different one).
BT
The problem seems to be that BT connectivity works with some WM6 ROMs (original HTC and some of Schaps for example) but not with all.
I use Pays ROMs which are quite excellent but BT is not working with my Audi MMI. It worked with HTC Original.
Same problem over here
Same problem over here, Original HTC WM6 Rom and Schaps work ok. Others keep conecting and disconecting win an Audi handsfree Bluetooh radio.
so maybe SCHAPs will let us know what he has done differently, I have found the same occurs for me, I had an older SCHAPs rom installed, I decided to move over to a clean more up to date rom which has poor BT quality and performance for some bizarre reason..
Bluetooth
Which of Schaps WM6 ROM versions are working with Audi MMI?
I think people's best bet (and I promise this isn't the same glib answer people give a lot around here) but your best bet is to run a search.
There are quite a few versions of Bluetooth 'software' around - and I don't mean the external programs but the whole internal software 'mechanism' of bluetooth in windows devices. The 'stack' that largely controls bluetooth has a number of different versions and I'm 90% convinced that I've seen OEMs floating about for it.
Rather than the XDA search (which has had problems lately), try using google and search for the terms you want with site:forum.xda-developers.com after. Thus (DON'T include the inverted commas) you'd maybe put:
"bluetooth stack site:forum.xda-developers.com"
into Google and it will prob find your info. Sorry I'm not being more specific.
My last phone was the AT&T 8525 also known as the Hermes. It had the MS BT stack built in and all the BT talk in the forum was about how bad the MS BT stack was and that it was the source of all the MS Voice Command problems and could someone figure out a way to cook in the Widcomm stack instead.
Fast forward a couple of years and I come here with my brand new US TMo TP2 and guess what I start reading? That MS Voice Command doesn't work properly and it is the fault of the Widcomm BT stack. Can't someone figure out how to get rid of it and cook in the MS one instead?
Huh? What gives?
S
I hear ya. Also, i am experiencing significant "lag" with my verizon touch pro 2 when connected to a bluetooth carkit. Some say it is because of the widcomm stack and that the MS stack would be better. Is it a big deal to install a different BT stack? or do they have to be cooked into a ROM?
Yes please
I would support this. This stack is driving me mad.