Will try this soon. Thanks for keeping us updated.

Did a little driving and testing yesterday. All is still good. The only thing worth noting is that one time when a call was coming in, it took a couple (2 or 3) rings before the answer call/ignore call buttons would show up on the screen. They did show up, which is most important, but that one time it did take a second. i can live with that, especially compared to what the phone was like before. I'm officially giving this my "IT WORKS!!!". Please, everyone who tries this, continue to update and let everyone know if it does or does not work for you. Once we get enough consensus that it does work, we need to update the subject to "Solved". Thanks.

Can you please check your phone and check what version of the BT stack you are using. Thanks.

1.9.2 build 500 here. Verizon is my carrier and I'm currently on stock 6.5 ROM, moving to MightyROM later today.

Still working solid here as well.

I'm using the stock Windows Phone (Windows Mobile 6.5) ROM from Verizon with version 1.9.2 build 500. Thanks.

I will try this solution in the next few days. My only concern is that I'm using AT&T Tilt 2 BT Version 1.9.0 Build 4800. I hope the BT version doesn't hamper the fix. Will update thread later this week with results. Thanks for all of the great info!

The attached file can be installed on your Touch Pro 2 to (hopefully) solve the problems with Bluetooth documented in this thread.

Before installing this, make sure you're experiencing the problem described and have the right hardware.

I have tested this file on my Touch Pro 2, using the stock Verizon WinMo 6.5 ROM as well as MightyROM 1.20.10.

To keep modifications to a minimum, the fix assumes that you do NOT have any Bluetooth devices paired. Therefore, you should delete the connection for your phone on your AVIC, and re-pair following installation of the fix. Alternatively, hard reset the Touch Pro 2.

The file makes the following modifications to the registry, and will take effect after a soft reset:

REGEDIT4

[HKEY_LOCAL_MACHINE\SOFTWARE\WIDCOMM\Plugin\HandsFree]
"HFDeviceType"=dword:00000002
"SupportedFeatures"=dword:0000002D

[HKEY_LOCAL_MACHINE\SOFTWARE\WIDCOMM\BTConfig\General]
"DisableReopenAudio"=dword:00000000

PioneerAVIC_WIDCOMMBT_Hotfix.zip

Wow, cab worked great. Thanks a lot. I get my ringtone in the car now when I get a call. That never happened before. This sure is a much better fix than the one I posted, which didn't seem to work for anyone else but me.

The attached file can be installed on your Touch Pro 2 to (hopefully) solve the problems with Bluetooth documented in this thread.

 

Before installing this, make sure you're experiencing the problem described and have the right hardware.

 

I have tested this file on my Touch Pro 2, using the stock Verizon WinMo 6.5 ROM as well as MightyROM 1.20.10.

 

To keep modifications to a minimum, the fix assumes that you do NOT have any Bluetooth devices paired. Therefore, you should delete the connection for your phone on your AVIC, and re-pair following installation of the fix. Alternatively, hard reset the Touch Pro 2.

 

The file makes the following modifications to the registry, and will take effect after a soft reset:

 

REGEDIT4

[HKEY_LOCAL_MACHINE\SOFTWARE\WIDCOMM\Plugin\HandsFree]
"HFDeviceType"=dword:00000002
"SupportedFeatures"=dword:0000002D

[HKEY_LOCAL_MACHINE\SOFTWARE\WIDCOMM\BTConfig\General]
"DisableReopenAudio"=dword:00000000

So you didn't do any of the other registry changes that the post I linked to mentioned? If so, do you know what those are for exactly. Thanks.

So you didn't do any of the other registry changes that the post I linked to mentioned? If so, do you know what those are for exactly. Thanks.

Trial and error was essentially how I arrived at what I posted. The other changes essentially null the phone's Bluetooth MAC as well as the last connected device's Bluetooth MAC..which seemed redundant.

The way I look at it..I want to modify as little as possible.

Happy to do another .cab that does the full meal deal, but if this works for folks I'd rather leave it alone.

Again, much appreciated for tracking the solution down, this is a life saver.

So you didn't do any of the other registry changes that the post I linked to mentioned? If so, do you know what those are for exactly. Thanks.

 

Trial and error was essentially how I arrived at what I posted. The other changes essentially null the phone's Bluetooth MAC as well as the last connected device's Bluetooth MAC..which seemed redundant.

 

The way I look at it..I want to modify as little as possible.

 

Happy to do another .cab that does the full meal deal, but if this works for folks I'd rather leave it alone.

 

Again, much appreciated for tracking the solution down, this is a life saver.

I wasn't suggesting that. I was mostly just curious how you came to that .

I agree with modifying it as little as possible. This works great so far. The only problem I had was once when I was testing it out. I rejected a call and it sent the call back to the phone and froze the unit for a while and the next call came through the phone and not the unit. But it was fine after a while and rejecting calls ended the call instead of sending it back to the phone. So I'll take it as a fluke.

I just put the registry changes on my phone. I'll test it out tomorrow and post my results.

The HFDeviceType, SupportedFeatures and DisableReopenAudio regchanges fixed it for me. Great job figuring this out guys!

Followed it and all my TP2 problems are gone. Works like a charm!!

Thanks for the great help!

So far so good with registry changes. I can't believe the fix is that easy. Thanks Dougthug for tracking it down.

Interestingly enough, after applying these registry changes, TP2 finally started making voice announcements of caller's name through the BT headset (either my Jabra or AVIC) as well. Neat!

Is this fix only for the Verizon TP2s or also for the HTC phones (european)

Well, I only have experience with my Verizon Touch Pro2, but I would think you should be fine trying this on any phone. I can't think of anything it would hurt to do this on a European model, but I can't say for sure. If I was you, and I was having the same problems that all of us have reported, I would try it, but first document the registry settings before they are chnaged and be prepared to do a hard reset on the phone as a worse case scenario. Good luck.

I did the upgrades and tried it this morning and it looks like it works great. Can now receive on other screens than the GPS/map. My Avic receives my incoming call sound and I can hang up without any problem and my music returns. GREAT. I will test this further.

Works great after some more testing. If my phone rings and I'm in the AV screens, I can't receive but if i turn to the map screen during the call, I can answer it. This is OK for me.

Finally got around to testing the cab on my AT&T Tilt 2 BT version 1.9.0 Build 4800. Works great! Solved all of my problems... Thanks!!!

Works great after some more testing. If my phone rings and I'm in the AV screens, I can't receive but if i turn to the map screen during the call, I can answer it. This is OK for me.

That's weird. It should switch you to the map screen and then popup the box with the Call, Reject, and Volume Keys.

Works great after some more testing. If my phone rings and I'm in the AV screens, I can't receive but if i turn to the map screen during the call, I can answer it. This is OK for me.

That's weird. It should switch you to the map screen and then popup the box with the Call, Reject, and Volume Keys.

I wonder, what firmware version the AVIC unit is running?

HI.

My unit was bought 4-5 months ago, so I have the v3.