Bounty for working MS Bluetooth stack on TP2 - Page 4

dishe · #31 (**permalink**) 11-16-2009, 12:53 PM

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.

**amw1972** · #32 (**permalink**) 11-16-2009, 01:03 PM

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

jasoraso · #33 (**permalink**) 11-16-2009, 01:10 PM

Quote:

Originally Posted by amw1972

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

+1 Besides the hang-up issue, my TP1 had MUCH better responsiveness to MSVC. I haven't been able to figure out the timing of confirming with "yes" on my TP2 - it is like the microphone is turning on and off at weird times in an effort to save battery ...

dishe · #34 (**permalink**) 11-16-2009, 01:31 PM

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?

helix139 · #35 (**permalink**) 11-16-2009, 03:01 PM

Quote:

Originally Posted by dishe

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.

hangup, initiating calls, VC responsiveness, and compatibility with other software (such as VZW VVM) are the big issues for me, in that order. The MS stack performed flawlessly for my needs at all of the above and I just don't see why HTC went and changed it.

dishe · #36 (**permalink**) 11-16-2009, 05:25 PM

Quote:

Originally Posted by helix139

hangup, initiating calls, VC responsiveness, and compatibility with other software (such as VZW VVM) are the big issues for me, in that order. The MS stack performed flawlessly for my needs at all of the above and I just don't see why HTC went and changed it.

I don't think its that they "went and changed it" as much as they started using a new chipset for wireless communications on this phone, which may not be compatible with the MS stack at the moment.

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...

davahad · #37 (**permalink**) 11-16-2009, 06:44 PM

Count me in for $50 for the bounty.

dodgeboy · #38 (**permalink**) 11-16-2009, 11:08 PM

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

grv · #39 (**permalink**) 11-17-2009, 01:24 AM

Quote:

Originally Posted by dishe

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?

I would very much like for my BT remote controls to work with something other than HTC Media Player. I know Pocket Player has solved this for their app, but fixing the stack so that any app can make use of the AVRCP feature would be great. There's a cab that makes this work for devices using the MS stack like the original TP.

PPCFreak · #40 (**permalink**) 11-17-2009, 01:33 PM

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.