![]() |
Bounty for working MS Bluetooth stack on TP2
I'm sick of this bluetooth stack and its neverending issues so I'm offering a $50 bounty for whoever can get the MS bluetooth stack working fully on an otherwise stock TP2 ROM for both Verizon and Sprint with the standard set of profiles (Headset/handsfree, PAN, OBEX, DUN, Stereo, File Transfer, Activesync, Print, etc. basically everything available on the TP1) and can explain how they did it. Any and all methods are acceptable, including an installable .cab or cooking it into the stock ROM.
If the Widcomm stack works fine for you, then great and this topic does not concern you. This thread is not to debate which stack is better or for people to share their experiences on what works. It is for donating to the bounty for a working MS stack ONLY. As I've never setup a bounty before, if someone could PM me the easiest way to do this I would be very grateful. Anyone else who wishes to contribute, please post your amount below and PM me. will keep track of the total amount so far at the bottom of this post. Current Total Bounty: $145 (11/17 8:44 AM) |
Re: Bounty for working MS Bluetooth stack on TP2
$10 right here! (Yea, I'm cheap, but I just dropped $350 on this phone haha)
As long is it permanent fix. Thanks to all! |
Re: Bounty for working MS Bluetooth stack on TP2
I dont get what is wrong, I think it works fine. I've not had one issue with BT at all.
|
Re: Bounty for working MS Bluetooth stack on TP2
Quote:
If Widcomm works for you, then fine. No need for you to post in this thread. Not to be a jerk, but this thread is for contributions to the bounty for those who want the option of using the MS stack only. |
Re: Bounty for working MS Bluetooth stack on TP2
Quote:
|
Re: Bounty for working MS Bluetooth stack on TP2
Quote:
|
Re: Bounty for working MS Bluetooth stack on TP2
I think you should set up a PayPal account to get people to donate to if your serious. I've seen too many times were people said they would contribute, just to disappear when it was time to pay up.
So set up a donation account on paypal and post a link here. Then keep updating the available balance in the account on this thread. However, I have no problem with the widcomm bluetooth stack except that my bluetooth headset sometimes needs two clicks to hang up and that my car bluetooth takes forever to hang up. Otherwise everything else works fine. |
Re: Bounty for working MS Bluetooth stack on TP2
I'm sorry to disappoint any of you, but you're gonna be hard pressed to find an installable solution for this. Until the Hard SPL is released to allow custom ROMs, you're gonna have to either cope with what we've got. I'm not saying it won't happen at all ever, but it's not just as simple as a reg hack or a couple files.
Maybe this is HTC's way of agreeing with me that bluetooth headsets should be banned, lol... |
Re: Bounty for working MS Bluetooth stack on TP2
Quote:
NM...They're pretty gay but I have to wear it in my car, or I have to answer to my commander of the Air Force Base. You just have to find the least gayest one. |
Re: Bounty for working MS Bluetooth stack on TP2
I use it at church just in-case i get an important call. ;)
|
Re: Bounty for working MS Bluetooth stack on TP2
Quote:
For some of us, not using a headset is not an option. I drive a stick so I'm one of those people, and trying to dig my phone out and get it out of its case to hang it up when you hit someone's voicemail while shifting, steering, and trying not to hit the person in front of you defeats the whole purpose of using a headset. |
Re: Bounty for working MS Bluetooth stack on TP2
Quote:
|
Re: Bounty for working MS Bluetooth stack on TP2
Works fine for me, but the MS stack is better so I will donate $5 for a working MS BT Stack.
|
Re: Bounty for working MS Bluetooth stack on TP2
Oh don't get me wrong... I understand all the reasons for using them, lol... it was a joke really. :)
And I think you're going to get plenty of ROM chefs who agree with putting the MS stack in their kitchens rather than WIDCOMM, but I've also seen a few that have already posted that they view the WIDCOMM to be superior and they won't go back. In any case, I think you'll not have a problem finding ones that do choose to use it. |
Re: Bounty for working MS Bluetooth stack on TP2
$30 from me!
|
Re: Bounty for working MS Bluetooth stack on TP2
All bt headsets are gay, everytime i see a person that talks on one while looking straight at me makes me very violent, but i do agree its very usefull in the car or when you need both hands for washing your dog, just please dont wear it while walking down the street. I have a premier business paypal account with excellent feedback of about 8 years, if i can help(i dont have the problem with bt set though) let me know
|
Re: Bounty for working MS Bluetooth stack on TP2
Quote:
~John |
Re: Bounty for working MS Bluetooth stack on TP2
Quote:
There are a lot of smart people around here whose talents could probably be put to use in solving the issue. We're just trying to get some help with that. Not trying to bait anyone or get myself flamed, it just seems like this particular problem is being discounted by most people, either because they don't have the problem, or because they wouldn't be caught dead wearing a BT headset in the first place. |
Re: Bounty for working MS Bluetooth stack on TP2
I gave up on BT headset for any windows phone. I have a Blueant BT speaker in my car that's really of no use along with a Plantronic, and jawbone 1. Luckily the speaker on the TP2 is great so I just leave it on the dash board in speaker mode when on a call. No complaints on the other end compared to when I'm using any type of BT device.
|
Re: Bounty for working MS Bluetooth stack on TP2
Quote:
I propose we boycott drive-thru restaurants as well. Maybe even start a petition to ban radios from cars. Way to much stuff that could possibly distract a driver now a days. At least if we had a working hands-free device for our phones we could use both hands to drive. I've never seen anybody eat McDonalds hands free. Just my $ 0.02 |
Wirelessly posted (VZW TP2: XV6875 Opera/9.50 (Windows NT 5.1; U; en))
i for 1 would like PAN option. sucks that my old apache 6700 could do this but a new $350 tp2 doesnt work for this. carrying around the usb cord incase i need to tether sucks cause sire enough when ineed to tether it wil prob b when i dont have the usb cord with me. Count on $20 from me. |
Re: Bounty for working MS Bluetooth stack on TP2
Quote:
I thought I would chime in and at least help on the widcomm end call issue. I found a real working solution for headsets not hanging up. You have to disable internet being always on. You can use hd or diamond tweak to do this. I would not use advanced config as it causes a lag in answering the phone. I have cooked quite a few roms and can confirm this does work. I stumbled across this fix when I went to hang up the phone, quite a few times I would get a could not connect #777. So if you set your connection to disconnect after 10 minutes and then soft reset the phone. You will no longer have end call lag. Another post by apristel's Avatar apristel http://forum.ppcgeeks.com/showpost.p...73&postcount=1 is to go into this registry key and change it. I have had it at 0 and at 1000 and see no difference. But I thought I would add this to my post. Registry Edit: [HKEY_LOCAL_MACHINE\Software\HTC\PHONE\PhoneExtendS etting] "EndCallTime"=dword:1000 1000 = 1 second If this helps your end call lag, which it will, please give me a thanks. Cheers, Mikee |
Re: Bounty for working MS Bluetooth stack on TP2
Mike- interesting find... so basically, the delay has something to do with the data connection? Your solution may not be acceptable for those of us who rely on the data always being on for things like push mail, etc.
I don't have a TP2 myself (yet) so I can't test anything, but it sounds to me like the stack is simply telling the radio to terminate a session, assuming that session "x" is a voice call. Does the GSM version of the Rhodium have this problem as well? Maybe someone with some radio protocol knowledge and a CDMA TP2 can look into this, but this is what I imagine is happening: If you initiate a connection (be it voice 1x or data EVDO), it may dynamically name the session (lets call it session X). If a data call was initiated first, and then put on hold for another session (a voice call), perhaps it is given another name to reference the connection (lets call it Y). So, when the Widcomm stack sends the terminate connection command, it *may* be trying to end session "X", and not getting any response since the call is on hold. If no data call was initiated first, and the voice call ends up being "X", than it works fine. This would also explain why a GSM version possibly does not have this problem (again, I don't know, I'm just assuming since I haven't heard of this problem before now)- the GSM radio does not put calls on "hold", since voice & data can be operated simultaneously. By the way, most people consider the Widcomm stack to be far superior than the MS one in many ways (I was following and even contributed to some of the initial efforts to port it to HTC devices in the days of the Wizard and Tornado because of MS stack quality issues). As far as I know, this marks the first CDMA device to use the stack, and therefore it is very possible that they were unaware of this potential problem. If this is really the only problem you are having, I think you'd all be better off fixing it than ditching the entire stack for the MS one. The Widcomm stack is more efficient on CPU time as well as battery (look at the side by side tests done at pocketpcmag), not to mention dramatic sound quality improvement with things like A2DP stereo. Hope this helps... |
Re: Bounty for working MS Bluetooth stack on TP2
Quote:
|
Re: Bounty for working MS Bluetooth stack on TP2
Quote:
Whatever the case, I'd at least like the option to use the MS stack and see for myself if the tradeoffs are worth it to me. |
Re: Bounty for working MS Bluetooth stack on TP2
Agreed having the choice is always prefer...
|
Re: Bounty for working MS Bluetooth stack on TP2
Choices are great, but I think Widcomm was chosen because of the new chipset. I'm not sure drivers exist for this chipset and MS Stack.
|
Re: Bounty for working MS Bluetooth stack on TP2
Can we please get this thread back on the track that the OP started.
This is not a BT stack discussion. This is a bounty. I am in for $50 as well. |
Re: Bounty for working MS Bluetooth stack on TP2
wonder if htc will fix it and collect the pot.
or use it to pay for the class action on defective units :) |
Re: Bounty for working MS Bluetooth stack on TP2
Quote:
|
Re: Bounty for working MS Bluetooth stack on TP2
Hold on- before we go all gaga about this... are there any other problems you guys are having with the stack? Or is it just the hangup problem?
If HTC releases an update that fixes this one issue (which is entirely likely since it sounds like a simple bug), are you guys OK with the stack otherwise? As someone who helped identify and fix a BT error on the Titan, I can tell you its more likely easier to fix the problem than port the entire stack... EDIT: As for the PAN issue, there are workarounds to connect over BT I believe. Its funny, because originally when PAN came out, folks who were used to Dial Up Networking profile hated it because it was different. Now if we lose that, people are angry again. Funny, is all. |
Re: Bounty for working MS Bluetooth stack on TP2
bump to the hangup issue...
I hope if HTC does update and fixes the BT issue...they would include the following: quicker and more accurate response to MSVC |
Re: Bounty for working MS Bluetooth stack on TP2
Quote:
|
Re: Bounty for working MS Bluetooth stack on TP2
Yeah, I'll admit that I tried that this morning (finally got my own TP2), and noticed MSVC problems. But, to be fair, I found it didn't work well directly into the phone either. MSVC problems?
|
Re: Bounty for working MS Bluetooth stack on TP2
Quote:
|
Re: Bounty for working MS Bluetooth stack on TP2
Quote:
The Widcomm stack used to be considered better, although I'm starting to see some of the things you guys are describing. I won't where it went wrong... |
Re: Bounty for working MS Bluetooth stack on TP2
Count me in for $50 for the bounty.
|
Re: Bounty for working MS Bluetooth stack on TP2
I'm in for $20 if someone can either fix it or port the MS stack and solve the issues.
My main issues: When connecting to Chrysler U-Connect in my '09 Dodge Ram, I had a lot of trouble pairing the phone. It took 8-10 attempts (my TP1 and Touch both paired without a problem). When I finally got it paired, instead of answering the call, it would sometimes just start ringing through the car speakers. And of course, I cannot hang-up, like just about everyone else in this thread. If this wasn't so damn frustrating, it would almost be comical that something as common and basic as Bluetooth would get implemented so poorly in a device today. This is like buying a printer that only prints 6 of the 26 letters of the alphabet. How does it get through quality control? I thought Bluetooth was pretty well standardized at this point. It has been years (4+) since I've had a significant problem with BT functionality with any phone or headset. And I've been through many phones, headsets and car BT setups in those 4 years. I remember being annoyed when the battery and signal strength icons didn't show up on my radio when using my old Treo 650, back in the day! I can only dream of having such petty BT problems with this phone. Dave |
Re: Bounty for working MS Bluetooth stack on TP2
Quote:
|
Re: Bounty for working MS Bluetooth stack on TP2
I miss the BT Pan. USB cord ICS works but rather have the BT Pan. Was considering using WMWifiRouter as a possible fix but been hearing some say there device is getting hot.
|
All times are GMT -4. The time now is 06:14 AM. |
Powered by vBulletin® ©2000 - 2025, Jelsoft Enterprises Ltd.
©2012 - PPCGeeks.com