I have an HTC Touch Pro2 and an AVIC F7010BT (both unmodified, no hacks). I can place outgoing calls, but whenever I receiver an incoming call, I get the on-screen message with the answer, hang-up and volume buttons, but after one ring, it goes away. I can't answer the call, and my phone freezes for about a minute. I then get the "missed call" notice on the phone, which again causes he phone to freeze for about a minute. I've tried both version of the BT firmware on the AVIC with the same results. I've also tried various setting for the BT interface and auto-answer on both the phone and the AVIC with the same results. I even removed MS Voice Command from the phone in case it was an issue with it trying to announce the call. Does anyone have any helpful ideas?

Having the same problem as you. Are you using a stock rom or a custom rom? Hoping to find an answer soon because the freezing is really annoying. The phone works fine with my other headsets, it's just the headunit that is not working correctly. But from what I know, it might be because of the BT stack on the phone and not the unit.

I am running pure stock rom on both the phone and the AVIC.

I am also having this same issue.

It's just frustrating that I don't even use BT in the car. UGH!

I am using a custom ROM.

Well, I may have this working. I have been able to use it two days in a row now. I'm not sure what was the fix, but here's what I have done:

1. AVIC had BT ver 3.3, downgraded to 2.9 - No change.

2.Removed Microsoft Voice Command (ver 1.60.4633.0) from the phone to eliminate that as a problem - No Change

3. Upgraded AVIC back to BT ver 3.3 - No change

4. Noticed that MS Voice Command had not totally uninstalled (still had option in Settings), reinstalled Voice Command ver 1.60.4633.0. Changed Voice command notification setting to "Announce Notifications through device speaker or wired headset only". - Working for now!

So, I don't know if it was a bad install of Voice Command, the settings for it, or maybe just switching back and forth between the AVIC BT versions that did it, but it's working so far.

Are you able to receive calls smoothly with no freezing? That was my biggest problem so it would be great if we can receive calls and not have the phone freeze. I don't think it's because of going to 2.9 and back to 3.3 because I tried that before and it didn't work. Must be something wrong with the voice command and reinstalling it might have fixed the problem. If you can, please post the files you used so we can test it with the same versions. Thanks.

I don't think it has anything to do with Microsoft Voice command as I don't even see that on my phone...

What is that?

I am going to try and revert back to 2.9 and see if that helps...

Voice command is used to access features on the phone through voice recognition. It's in all settings under personal.

I see.

I found it and unchecked the "Enable" box.

I'll report back tomorrow or so to see if that helps out at all or not.

None of these fixes should make a difference. I think they're all placebo. The problem is that the bluetooth stack on the phone is NOT the same MS stack that was on the TP1 and Mogul, etc. It has a LARGE number of incompatibilities with various other bluetooth devices. http://forum.ppcgeeks.com/forumdisplay.php?f=97 has more info. There's not much you can do other than hope one of the custom ROM chefs manages to put the MS stack back on. I hate using the bluetooth on my TP2 with my F90BT for this very reason.... bleh.

Yes nothing works.

Ugh.

I hate getting missed calls on it when I have it connected to the car.

Hope someone comes out with a fix.

Well, it worked fine this morning when m daughter called me on my way to work, but then when my wife called on the way home, it locked up. And it locked-up the AVIC, too! I had to reboot it by pressing the reset button.

I'll join this discussion by saying that I just got the TP2 and have these EXACT same problems. Only 1 ring, no call dialog box, and I have to modify my contacts to get the entire name on the "first name" line... so that I don't have to say the last name first to have VR recognize who I want to call. This sucks!! My old Samsung Instinct worked fine...

Yep very annoying, hopefully someone cooks in MS BT stack so we can have a working unit again. For now, I just ignore all incoming calls and call them back after it's not frozen anymore.

I've found it is much more reliable if I have already gone into map mode on the AVIC and pressed OK to the obligatory warning message. It's not 100% perfect, but this at least gives me about twice the reliability I had before.

I'm having the same problem with my Touch Pro 2 w/windows 6.5

I did the hack to skip most of the navi warnings but I'm still getting trouble with the bluetooth.

I have a similar problem with the HTC HD2. I have previously used the Touch HD and TyTn II with no problems. It seems to be a problem with the Bluetooth stack in the phone. It will eventually be possible to change the stack, using a "cooked ROM" (see http://forum.xda-developers.com/), but we'll have to wait until someone comes up with one featuring a new bluetooth stack.

It may be worth trying out Jetware Mobile's bluetooth app (http://www.jetwaremobile.com/), but if the phone uses a non-standard MS stack, it probably will not install.

+1. same scenario for me, F900BT with Verizon Touch Pro 2.

So I just flashed to MightyMike's 1/4/10 ROM from PPCGeeks (http://forum.ppcgeeks.com/showthread.php?t=79579) and it works much better sofar with my F90BT. Apparently the newly released 6.5 USC (another carrier) ROM had an updated BT stack that seems to alleviate many issues. Here's to hoping it works for you too.

Are you able to answer calls and the phone not freezing? I'm pretty sure most of the ROMs use the same stack by now but I'm still getting freezes whenever I get an incoming call. Will check out the MM ROM when I have time. Thanks for the heads up.

Ditto for me. I have Verizon's Touch Pro2 and the F900BT. I saw one poster mentioned Windows Mobile 6.5, but is that a cooked ROM or is that the AT&T version of the Touch Pro2? Better asked, is there anyone that is having this problem with the AT&T Touch Pro2 (all stock, nothing cooked or hacked)? Thanks.

Add me in with the same problem, 1 ring and the phone freezes. Outgoing calls work fine but the Voice Recognition is not as reliable as it used to be.

F700BT w/ Pioneer v3 (legal) update w/ 3.3 BT Stack

Verizon Touch Pro2 Stock ROM (Win 6.1)

My old AT&T Tilt worked perfectly

So I got this straight from the horse's mouth: MM uses an updated BT driver (not a new stack, just an updated driver, which seems to fix most of the issues) from the USC 6.5 ROM Update that was released. It works. I can answer calls. Hang up calls. Make calls... and all the while, my phone is just as fast(or maybe 90%) as it is normally. It doesn't slow down to a "FFUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUU" state anymore. I do have a small problem with answering, in that I have to answer with the headunit OR the hardware phone button, because about 1/4 of the time using the "slide-to-answer" mechanism doesn't work. But yeah, HUGE improvement.

So I got this straight from the horse's mouth: MM uses an updated BT driver (not a new stack, just an updated driver, which seems to fix most of the issues) from the USC 6.5 ROM Update that was released. It works. I can answer calls. Hang up calls. Make calls... and all the while, my phone is just as fast(or maybe 90%) as it is normally. It doesn't slow down to a "FFUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUU" state anymore. I do have a small problem with answering, in that I have to answer with the headunit OR the hardware phone button, because about 1/4 of the time using the "slide-to-answer" mechanism doesn't work. But yeah, HUGE improvement.

Great info. Do you know if it required a ROM to be flashed to the phone or was it just installing a cab or was it just replacing a couple of dll's or what? Thanks.