No, that's not what has been going on with me. When I first got the phone, it came from Verizon with Windows Mobile 6.1 on it. When it was paired up to my F900BT, I couldn't answer incoming phone calls at all. Not from the headunit or the phone. I could dial out OK, and I think that even using the voice dialing (from the F900BT, not phone voice commands) worked fine. After Verizon released the update for Windows Phone (Windows Mobile 6.5), I had the same thing going on but the voice dialing wouldn't work either. So really, the only thing I could do successfully at that point was place a call by initiating it from the phone or using the Contacts menu on the headunit. After I removed all three of those files I previously mentioned from the \Windows\StartUp\ folder, I can now do everything that I used to be able to do. The first call is just as good as any other for me now. The unit was always a bit funky when it came to using the phone. I think it may have a something to do with the fact that it still uses Bluetooth specification 1.2 where as the phones and most everything else make after 2005 uses 2.x, but I don't know that for fact and 2.x is supposed to be completely backwards compatible. Thanks.

Well, it turns out I may have spoken too soon. Last night, everything was working great. I hop in the car to run an errand, and it's all the same again. Can't answer the phone still. Back to the drawling board .

I find things seem to work more consistently if you uncheck the option to play system sounds over bluetooth. Or if it fails, maybe try flashing a custom ROM?

Well, I take back part of what I said. Right now the only thing I can't do seems to be answering, which is huge. At least it seems that my problems are down to just one thing though. Although, I did also disable the HTC dialer and am using the Windows Phone default one.

From everything I've read, it seems to me that it all about the bluetooth stack. I'm not finding anything out there about replacing the stack either. I'm not sure where to go from here...

With my last phones - 8525, Tilt, and Fuze - I used Jetware Mobile and everything worked perfectly with both of my cars. My AT&T Tilt 2 works great with my other car but has lots of problems with the F90BT. The first thing I noticed is that the radio isn't muted when I place a call. I can control the volume while a call is in progress but with past phones, the radio always muted. The bigger issue is receiving incoming calls. Even though my address book transferred over perfectly, no caller ID is displayed when a call is received. I can answer the call but then when the conversation is over, the F90BT freezes and is in need of a reset (after every call!). The Tilt 2 hangs for about 20 seconds and then returns to normal use. I tried Jetware Mobile on the Tilt 2 with WM 6.5. It installed fine but I couldn't load the Bluetooth extension. It gave me an error and said this version of WM was incompatible. I contacted Jetware before the holidays and I received an email a few weeks later that my request was being escalated to their level 2 technicians but that was three weeks ago. I notice that the Jetware Mobile site hasn't been updated in a long time so I'm wondering if they are even bothering with a version for 6.5. I love the phone but the Bluetooth stack is killing me!

With my last phones - 8525, Tilt, and Fuze - I used Jetware Mobile and everything worked perfectly with both of my cars. My AT&T Tilt 2 works great with my other car but has lots of problems with the F90BT. The first thing I noticed is that the radio isn't muted when I place a call. I can control the volume while a call is in progress but with past phones, the radio always muted. The bigger issue is receiving incoming calls. Even though my address book transferred over perfectly, no caller ID is displayed when a call is received. I can answer the call but then when the conversation is over, the F90BT freezes and is in need of a reset (after every call!). The Tilt 2 hangs for about 20 seconds and then returns to normal use. I tried Jetware Mobile on the Tilt 2 with WM 6.5. It installed fine but I couldn't load the Bluetooth extension. It gave me an error and said this version of WM was incompatible. I contacted Jetware before the holidays and I received an email a few weeks later that my request was being escalated to their level 2 technicians but that was three weeks ago. I notice that the Jetware Mobile site hasn't been updated in a long time so I'm wondering if they are even bothering with a version for 6.5. I love the phone but the Bluetooth stack is killing me!

It looks like Jetware was released into open source, there's something going one at Sourceforge with it, but they always were supporting Microsoft's Bluetooth stack, rather than Widcomm in Touch Pro2/Tilt2...

With my last phones - 8525, Tilt, and Fuze - I used Jetware Mobile and everything worked perfectly with both of my cars. My AT&T Tilt 2 works great with my other car but has lots of problems with the F90BT. The first thing I noticed is that the radio isn't muted when I place a call. I can control the volume while a call is in progress but with past phones, the radio always muted. The bigger issue is receiving incoming calls. Even though my address book transferred over perfectly, no caller ID is displayed when a call is received. I can answer the call but then when the conversation is over, the F90BT freezes and is in need of a reset (after every call!). The Tilt 2 hangs for about 20 seconds and then returns to normal use. I tried Jetware Mobile on the Tilt 2 with WM 6.5. It installed fine but I couldn't load the Bluetooth extension. It gave me an error and said this version of WM was incompatible. I contacted Jetware before the holidays and I received an email a few weeks later that my request was being escalated to their level 2 technicians but that was three weeks ago. I notice that the Jetware Mobile site hasn't been updated in a long time so I'm wondering if they are even bothering with a version for 6.5. I love the phone but the Bluetooth stack is killing me!

 

It looks like Jetware was released into open source, there's something going one at Sourceforge with it, but they always were supporting Microsoft's Bluetooth stack, rather than Widcomm in Touch Pro2/Tilt2...

What's the name of the project in SourceForge? I just checked there for Jetware and they have nothing coming up. Thanks.

What's the name of the project in SourceForge? I just checked there for Jetware and they have nothing coming up. Thanks.

Codeplex, actually:

http://bthfx.codeplex.com/

yeah..well, this is unfortunately becoming a showstopper. I really like the TP2. I've tried disabling all voice command and system sounds via bluetooth, I've blown away the F900BT as well as the TP2, tried custom roms on the TP2. I got nothin'.

Can't answer a call on the F900BT or on a Jawbone headset. The caller gets sent straight to voicemail, the phone hangs for ~20 seconds, and the F900BT (usually) requires a power cycle.

I can, however, make calls, but in the F900BT's case, the phone UI does not show up. The audio is muted but the unit otherwise acts like no call is in progress.

My Touch Pro and Mogul were both fine and worked perfectly; I tried a Droid Eris and that was fine, as well. Unfortunate that HTC has decided to integrate the Widcomm software instead of the Microsoft BT stack.

Does the Motorola DROID work okay?

Not sure why you guys are still having problems, even after custom ROMs. Mine has been working pretty smoothly lately. I just flashed the latest Energy ROM, will test it out later.

You guys might want to try Mighty Mikes 1/9/10 ROM, it worked for me perfectly. I would have stuck with it, but I prefer Sense 2.5. I did try, his newer releases, but there were problems, so try the 1/9/10 ROM first. I will also upload the BT files I grabbed from that ROM for you guys to try out. I've replaced files on different ROMs, with them and the BT worked, so maybe it will for you guys too.

Not sure why you guys are still having problems, even after custom ROMs. Mine has been working pretty smoothly lately. I just flashed the latest Energy ROM, will test it out later.

 

You guys might want to try Mighty Mikes 1/9/10 ROM, it worked for me perfectly. I would have stuck with it, but I prefer Sense 2.5. I did try, his newer releases, but there were problems, so try the 1/9/10 ROM first. I will also upload the BT files I grabbed from that ROM for you guys to try out. I've replaced files on different ROMs, with them and the BT worked, so maybe it will for you guys too.

I'd like to know more about what files you've replaced exactly. On another note, I just submitted an email to HTC's support. It may be a waist of time, but like mom always said, it never hurts to ask . Thanks.

I would too. I've called Verizon about the same problem several times, and it seems I hit some sort of threshold: the last 2 times, I got a replacement device (which, of course, changed nothing). This time, they said they'd "escalate to HTC".

Probably not too much different from dougthug emailing HTC support, but, well, it's something I suppose.

I was offered a 4th replacement, which was entertaining. I declined.

They are just the files that started with BT in the WINDOWS folders. I'm pretty sure the only ones really needed were the driver files. But I grabbed everything just in case. When you replace it, it seems to update the BT stack to the 500 build. The only weird thing is that on MM newer roms with the 500 build, BT wasn't working. But it works when I replace the files. Not sure why that happened.

They are just the files that started with BT in the WINDOWS folders. I'm pretty sure the only ones really needed were the driver files. But I grabbed everything just in case. When you replace it, it seems to update the BT stack to the 500 build. The only weird thing is that on MM newer roms with the 500 build, BT wasn't working. But it works when I replace the files. Not sure why that happened.

So it's still the same stack that that you're working with, just updated? The Verizon update build 500 as well. Thanks.

They are just the files that started with BT in the WINDOWS folders. I'm pretty sure the only ones really needed were the driver files. But I grabbed everything just in case. When you replace it, it seems to update the BT stack to the 500 build. The only weird thing is that on MM newer roms with the 500 build, BT wasn't working. But it works when I replace the files. Not sure why that happened.

 

So it's still the same stack that that you're working with, just updated? The Verizon update build 500 as well. Thanks.

Yea, still the stack I mentioned before. Seems to be the only one that's working for me.

Edit - Here are the BT files I use. Download, unzip, copy into the Windows folder, soft reset and hopefully it works.

http://www.sendspace.com/file/i4p2si

Edit - Here are the BT files I use. Download, unzip, copy into the Windows folder, soft reset and hopefully it works.

 

http://www.sendspace.com/file/i4p2si

For me (Verizon WM6.5) this simply killed any and all Bluetooth operation on the phone

Sorry about that.

It worked for me when I tried it with Juicy ROMS, and now NRGZ ROMS.

Sorry about that.

 

It worked for me when I tried it with Juicy ROMS, and now NRGZ ROMS.

does noyt work for me on Dutch M-rom...

Maybe you guys can try flashing to a ROM that I used where it worked to test it out. If it works on one of those ROMs then it might just be something wrong with a ROM you are using.

Try Juicy R7-R8, NRGZ Leo 1/14 and 1/20, MightyROM 1/9 all worked for me. If using NRG or Juicy, replace with the BT files I posted above. MightyROM should work after flash. Good luck guys.

FYI, I just tried this. I don't know if anyone else has tried it yet or not, please let me know if you have. I'll give it a try when I leave the office today and see how it does on the ride home and let everyone know. Thanks.

I don't want to jump the gun and shout "I GOT IT!!!" prematurely like I did before (see this post if you don't know what I'm talking about), but I think I got it. I did everything in this post from PPCGeeks (except I didn't download the registry editor he linked to) and it all looks to be working better than before, even better than with my old Touch Pro. I'm gonna give it a couple of days before the "I GOT IT" comes out, but I think it's good. I did exactly what he had in his instructions. There was even one entry he said to edit that I didn't even have, so I added it and set it like he told to. A couple of observations. First, every single time I was testing it, the buttons appeared on the screen to hang-up and volume up and down (sweet!). Second, hanging up my phone was quicker. It seemed before that when I would hang up the phone, it would take a few seconds before the phone actually showed the call ended. Third, if I didn't make the call from the contacts screen, the caller ID only showed the number, not the name. If I dialed from the contacts dialog, I got the name, but even when I voice dialed or had an incoming call that is in my contacts, I just got the number. Lastly, when a call is coming in, for the first second, I get the normal ring that the F900BT always, but only for a second. After that, I hear my phones ring tone through the radio. Doesn't really bother me, but it is something different for me.

I tried everything on my way home from work a couple of times and it was all good. Then, a little while ago, I went out the garage and was just testing. Turning both the car and the phone off and back on and calling into the car and calling out from the car over and over again. I never once had a problem. Let's hope this sticks. Please, let me know if it works for anyone else that tries it. Thanks.

giving this a try. THANKS for keeping us posted.

Initial result is huge success..

Previous behavior was:

-Incoming calls ring for ~1 second and get rejected to voicemail

-Outgoing calls work from the phone only, and do not display the Phone UI on the AVIC device

Now:

-Incoming calls ring with the "Pioneer" ring for a short moment, then switches to the phone's ringtone

-Incoming calls working fine, UI displayed, caller ID looks good

-Outgoing calls work from the phone or from the AVIC UI

I had not paired my AVIC to the phone, and in fact had just hard reset. So I was missing some of the settings called out in the PPCGeeks post.

I changed:

HKLM\Software\WIDCOMM\Plugin\HandsFree

SupportedFeatures to 45

Add value HFDeviceType decimal 2

HKLM\Software\WIDCOMM\BtConfig\General

Change bdaddr to (no value)

Add value DisableReopenAudio dword 0

Following a soft reset, I paired the AVIC and was astounded that it worked.

I will too give this a couple of days, reflash, reverify, and create a CAB for you guys.

Just documenting while I try to understand what these settings actually mean.

Following reboot and re-pair:

HKLM\Software\WIDCOMM\Plugin\HandsFree

SupportedFeatures to 45 - stayed the same

Add value HFDeviceType decimal 2 - stayed the same

* LastConnectedBda was created and was set to the AVIC's BT MAC

HKLM\Software\WIDCOMM\BtConfig\General

Change bdaddr to (no value) - reset itself to the BT hardware's MAC

Add value DisableReopenAudio dword 0 - stayed the same

Heavy use of the phone last night (on-call for work)..

Got in the car today, got 2 calls while on the road, placed 1 from the AVIC dial pad.

No problems, looking real positive here.