Bounty for working MS Bluetooth stack on TP2

[jp2307]

disabling the DATA might work...but i want to listen to music with NanoGroove , SPB Radio and SPB TV..disabling the data is not an option!!! LOL

JP

[dishe]

Not that I want to defend the widcomm stack anymore, but I've noticed one great feature: A2DP starts up / turns off when it is supposed to, even during a stream.

The MS stack had a problem with 3rd party applications that send audio out to the speaker. For example- If an A2DP stereo headset was connected before I started CorePlayer, it would stream to the headset. However, if I started CorePlayer, and audio is coming out of the device, then I start the headset, it will continue playing out of the device. I have to shut down coreplayer and open it again to make it start using the headset.

This bug has plagued me for years, especially since I have A2DP stereo receivers in both my cars. When I turn off the car, the audio is STILL trying to send out to the BT stack, even though the connection to the device is gone. And if I was listening to wired headphones before I get into the car, I can't just switch to the car speakers over BT without closing the app. A real PITA.

Its something I learned to just deal with until the Widcomm stack- wow, now even in the middle of a song I can turn on my BT stereo and have it stream. Turn it off, it goes back to the handset. Perfect! At least they did SOMETHING right! People on XDA have been trying to fix that part of the MS stack for a long time, but there was a problem with the way streams are handled that prevented it from working.

I'm not saying I wouldn't like the option of an MS stack, but it might be more possible to fix the little bugs in widcomm- these seem like bugs that can totally be patched.

[mdphoenix]

Originally Posted by Cobaltikus

Does M$ Voice Command announce incoming calls?
Does MobileSrc MobileRemote work now?

Some things may be fixed, but not all. It still has a Widcomm BT stack.
I do believe we still would prefer a M$ BT stack.

I cannot answer the question about Voice Command. I have a Motorola T505 which has it's own incoming call announcement which overrides Voice Command's.

As for the new ROM from VZW, I can tell you that it's still WidComm so the fantastic interface is still there. I can also tell you that I've been using this ROM since last week and it's been FLAWLESS with handsfree. A call hangs up immediately every time now. No more delays. No issues pairing or re-establishing connections, either.

[jp2307]

Originally Posted by mdphoenix

I cannot answer the question about Voice Command. I have a Motorola T505 which has it's own incoming call announcement which overrides Voice Command's.

As for the new ROM from VZW, I can tell you that it's still WidComm so the fantastic interface is still there. I can also tell you that I've been using this ROM since last week and it's been FLAWLESS with handsfree. A call hangs up immediately every time now. No more delays. No issues pairing or re-establishing connections, either.

But have you tried Other Profiles besides HFP (Hands-Free Profile).... Like A2DP (Advanced Audi Distribution Profile), AVRCP (Audio/Video Remote Control Profile).... there seems to be an issue with these...not with HFP..

Is there versions of A2DP (like 1.0 and 2.0)?? i have only seen A2DP ...not A2DP 1.0 and 2.0.....if there was...then it might me incompatibility versions...but if there isn't ...then HTC or Widcomm has to find an issue and needs to solve it!!!

thanks


JP

[Cobaltikus]

Originally Posted by mdphoenix

I cannot answer the question about Voice Command. I have a Motorola T505 which has it's own incoming call announcement which overrides Voice Command's.

As for the new ROM from VZW, I can tell you that it's still WidComm so the fantastic interface is still there. I can also tell you that I've been using this ROM since last week and it's been FLAWLESS with handsfree. A call hangs up immediately every time now. No more delays. No issues pairing or re-establishing connections, either.

Since you already have the "fixed" widcomm stack, can you see if this program works?

http://www.mobilesrc.com/mobileremote.aspx

I LOVED this program on my Touch Pro, but it doesn't work at all with the Widcomm stack on my Touch Pro 2.

It allows you to use your phone's keyboard as a BT Keyboard for a PC or a PS3, and the Touch Screen or G-Sensor as a BT mouse pad also for PS3 or PC

The program runs, but fails to connect to anything.

[stifiling]

these reg keys posted by 'djqwikcut' in post # 46 is working for me to get MSVC bluetooth announcements.

1. Modify the HandsFree plug-in:
HKLM\Software\WIDCOMM\Plugin\HandsFree
i. Change SupportedFeatures to 45 (default is 1135)
ii. Add value HFBDA binary, set to same value as LastConnectedBda
iii. Add value HFDeviceType decimal 2

2. Modify the WIDCOMM bluetooth general settings:
HKLM\Software\WIDCOMM\BtConfig\General
i. Change bdaddr to (no value)
ii. Change DisableReopenAudio to 0 (default is 1)

[ravic]

I applied this registry fix and it adressed my main issue with not being able to answer any incoming calls via bluetooth in my car. This was with the Verizon Stock 6.5 ROM.

Originally Posted by djqwikcut

Here are some REG fixes to get the bluetooth working better.. this worked for me 95% ... BUT there is now a phone lag after being connected to the bluetooth device.. disconnecting the bluetooth speeds up the phone. If someone can figure out what is causing this I would love to know...

1. Modify the HandsFree plug-in:
HKLM\Software\WIDCOMM\Plugin\HandsFree
i. Change SupportedFeatures to 45 (default is 1135)
ii. Add value HFBDA binary, set to same value as LastConnectedBda
iii. Add value HFDeviceType decimal 2

2. Modify the WIDCOMM bluetooth general settings:
HKLM\Software\WIDCOMM\BtConfig\General
i. Change bdaddr to (no value)
ii. Change DisableReopenAudio to 0 (default is 1)

[avoider03]

Originally Posted by mdphoenix

Dunno if ya'll are aware, but the new Verizon ROM fixes the Bluetooth issue. The problem is that now I'm stuck with a stock ROM again until someone incorporates this fixed stack into their ROM.

I tried flashing to RUU_Rhodium_W_WM65_VERIZON_WWE_3.04.605.3_RS_2.23. 00WV_NV_VZW_1.94_1111_PRL58005_Ship.exe

I went straight out to the car, paired and tried to make a call. It rang once then dropped the signal.

I don't think the new Verizon ROM is the whole solution.

[avoider03]

Originally Posted by jp2307

disabling the DATA might work...but i want to listen to music with NanoGroove , SPB Radio and SPB TV..disabling the data is not an option!!! LOL

JP

I agree that disabling the data is not a very good option. Even with the data disabled, my phone typically connects automatically only to hands-free. Then I have to go in and connect the stereo.

I'll also put in $10 if someone can come up with a solution to the problem in calling out or receiving a call -- even if the data is enabled. I would also like to have the phone reconnect to the car bluetooth automatically!

[batpot]

Originally Posted by avoider03

I tried flashing to RUU_Rhodium_W_WM65_VERIZON_WWE_3.04.605.3_RS_2.23. 00WV_NV_VZW_1.94_1111_PRL58005_Ship.exe

I went straight out to the car, paired and tried to make a call. It rang once then dropped the signal.

I don't think the new Verizon ROM is the whole solution.

bummer.