I'm a MightyROM junkie too and am also finding the 1/4/10 release to be much better performing, on the phone itself as well as BT.

Do you know which one of MM ROMS have it? He has quite a few releases out right now. Hopefully there will be a CAB to install it because I'm running Juicy's ROM right now.

Edit, NVM. It's his 1/4 release. Thanks.

Do you know which one of MM ROMS have it? He has quite a few releases out right now. Hopefully there will be a CAB to install it because I'm running Juicy's ROM right now.

 

Edit, NVM. It's his 1/4 release. Thanks.

Oh, that's what you meant by MM. My bad .

Juicy may have incorporated it into his most recent rom. If not, ask him to talk to MM. I know they've chatted in the past.

I've been experiencing a similar issue with my HTC TP (not TP2) using Win mobile 6.1.. I upgraded the ROM to Win6.5 and still have the same issue. I even tried it with a friends Sprint phone (non windows mobile) and a Nokia AT&T phone (Non win mobile). Every time it connects to the F500BT via BT, it reboots.

I was having trouble with my 900BT... I thought it was due to changing (upgrading) my Custom Rom from CFay to 1.3 so I downgraded to 1.1 w/no change...

Problem was no answer, end call or volume box on screen.

So, I copied "My Flash Disk" from my second unit (second unit worked w/phone) & replaced it... now I have the phone UI box & it works perfect again. (no mods to unit before issues started)

BUT, I can't hangup or adjust volume if I dial from phone book or dial pad on screen on either unit or from the phone itself??? (no phone UI box) drivin' me nuts!!!

My phone has never froze/hung at anytime with standard or custom ROM's w/either avic900Bt's... (phone always works no matter what the avic does)

I use to run a TREO 650 w/no problems with either AVIC... but the phone would freeze/hang from time to time.

oh, I'm running (hacked) V3.01 on both AVIC's... and CFay's 1.3 rom is based on "US Cellular's" 6.5 rom.

Raymond

Edit: Oh, I'm on Sprint...

Been reading around and it seems like for right now, only MM has the new bluetooth stack in his ROM. I'm waiting for Juicy to release his R8 and hopefully it will be included. But luckily, there seems to be an official VZW ROM out that upgrades to 6.5 with the new stack. Try flashing to either of those and BT on our F series should be working properly again.

For those Verizon Touch Pro2 owners who aren't really into the cooked ROM scene, it looks like they've finally make a Windows Mobile 6.5 update available. I'm downloading it now and will give it a look and update everyone. Enjoy.

slow..but stable for sure. They beat Sprint, which is a surprise

Tested...and all I have to say is everyone that is having trouble with their bluetooth needs to get this update ASAP. Everything works great. I can answer from the Avic, using the hard button on the phone, and the slider. And best of all, virtually no slow down, lag, or freezing at all. Can't wait til Juicy puts out a ROM with this included.

Edit - I grabbed some BT files from the MM 1/9/10 release when I finished testing it and put it on Juciy R7 and everything still works great. Seems like you can just copy and paste the files into your Windows folder if you don't want to flash any ROMS.

Tested...and all I have to say is everyone that is having trouble with their bluetooth needs to get this update ASAP. Everything works great. I can answer from the Avic, using the hard button on the phone, and the slider. And best of all, virtually no slow down, lag, or freezing at all. Can't wait til Juicy puts out a ROM with this included.

 

Edit - I grabbed some BT files from the MM 1/9/10 release when I finished testing it and put it on Juciy R7 and everything still works great. Seems like you can just copy and paste the files into your Windows folder if you don't want to flash any ROMS.

can you provide a list of those files you've replaced?

I grabbed all the files in the windows folder that starts with "BT" or "Bluetooth". But I'm pretty sure it would work with just the DLLs, you probably won't need all the BT files since they should be the same, like the PNG images. I didn't copy those over.

I grabbed all the files in the windows folder that starts with "BT" or "Bluetooth". But I'm pretty sure it would work with just the DLLs, you probably won't need all the BT files since they should be the same, like the PNG images. I didn't copy those over.

Do updated BT friles make Touch Pro2 announce incoming calls through the Bluetooth headset (not necessarily AVIC) instead of the device speaker?

I grabbed all the files in the windows folder that starts with "BT" or "Bluetooth". But I'm pretty sure it would work with just the DLLs, you probably won't need all the BT files since they should be the same, like the PNG images. I didn't copy those over.

 

Do updated BT friles make Touch Pro2 announce incoming calls through the Bluetooth headset (not necessarily AVIC) instead of the device speaker?

Announce as in Voice Command announcing it, or just the BT ringing? Right now I have VC turned off but the unit still rings to let me know there's an incoming call. I haven't tried VC on yet though.

For those Verizon Touch Pro2 owners who aren't really into the cooked ROM scene, it looks like they've finally make a Windows Mobile 6.5 update available. I'm downloading it now and will give it a look and update everyone. Enjoy.

So I just got around to syncing my phone with my F900BT a few minutes ago. At first glance, I can actually hang up from the radio now, but every time I have a call come in, it hangs up on the caller after 1 ring. I'll play with it more later, but this still is sucking . Anyone else have any different results? Thanks.

I just updated my phone with the Verizon MR1 update from the link on dougthug's post. Incoming calls now work! The phone had no problem syncing with my F700BT and the volume control stays up and allows me to accept and hang up calls. Now I just have to get my contacts into the unit, I got a "no number found" error when I tried. I'll have to look that up next.

Verzion Touch Pro2 w/ MR1 update (Windows Mobile 6.5)

Pioneer F700BT w/ valid 3.0 update/Bluetooth v3.3

I just updated my phone with the Verizon MR1 update from the link on dougthug's post. Incoming calls now work! The phone had no problem syncing with my F700BT and the volume control stays up and allows me to accept and hang up calls. Now I just have to get my contacts into the unit, I got a "no number found" error when I tried. I'll have to look that up next.

 

Verzion Touch Pro2 w/ MR1 update (Windows Mobile 6.5)

Pioneer F700BT w/ valid 3.0 update/Bluetooth v3.3

Good deal, I'm glad you're up and running. It may be a reach, but there are two things I'm going to try when I have time and it's not 18 degrees outside). First, I'm going to try disabling the HTC dialer so that it just uses the default Windows Phone one. For the curious ones, you need some registry editing software (Schap's Registry Editor is great) and you have to simply change a 1 to a 0 on one specific registry key (HKEY_LOCAL_MACHINE\Security\Phone\Skin\Enabled). If that doesn't work, I'm going to try removing BTTray from the Windows\StartUp folder on my phone. I have no idea what it does or what it's for, but Bluetooth seems to work fine if it isn't there. Thanks.

I just updated my phone with the Verizon MR1 update from the link on dougthug's post. Incoming calls now work! The phone had no problem syncing with my F700BT and the volume control stays up and allows me to accept and hang up calls. Now I just have to get my contacts into the unit, I got a "no number found" error when I tried. I'll have to look that up next.

 

Verzion Touch Pro2 w/ MR1 update (Windows Mobile 6.5)

Pioneer F700BT w/ valid 3.0 update/Bluetooth v3.3

Make sure you check the prompt that comes up after you sync the unit with your phone. It asks for permission to access the phonebook. I usually check the box that allows it every time when that comes up so the next time I need to sync, I won't have to allow it manually.

Good deal, I'm glad you're up and running. It may be a reach, but there are two things I'm going to try when I have time and it's not 18 degrees outside). First, I'm going to try disabling the HTC dialer so that it just uses the default Windows Phone one. For the curious ones, you need some registry editing software (Schap's Registry Editor is great) and you have to simply change a 1 to a 0 on one specific registry key (HKEY_LOCAL_MACHINE\Security\Phone\Skin\Enabled). If that doesn't work, I'm going to try removing BTTray from the Windows\StartUp folder on my phone. I have no idea what it does or what it's for, but Bluetooth seems to work fine if it isn't there. Thanks.

I just checked it, it is build 500. I'll update everyone once I have a chance to check it out again.

Announce as in Voice Command announcing it, or just the BT ringing? Right now I have VC turned off but the unit still rings to let me know there's an incoming call. I haven't tried VC on yet though.

Voice command... Does not seem to work for me with Jabra 3030, which is a pain...

jk47 wrote:

I just updated my phone with the Verizon MR1 update from the link on dougthug's post. Incoming calls now work! The phone had no problem syncing with my F700BT and the volume control stays up and allows me to accept and hang up calls. Now I just have to get my contacts into the unit, I got a "no number found" error when I tried. I'll have to look that up next.

It looks like I spoke too soon. I'm still having the same problems. My initial test worked but I just got a call in and the volume control disappeared and I couldn't answer it. I guess I still have some work to do...Also, my BT verson is 500 with the new Verizon 6.5 update.

Verzion Touch Pro2 w/ MR1 update (Windows Mobile 6.5)

Pioneer F700BT w/ valid 3.0 update/Bluetooth v3.3

It looks like I spoke too soon. I'm still having the same problems. My initial test worked but I just got a call in and the volume control disappeared and I couldn't answer it. I guess I still have some work to do...Also, my BT verson is 500 with the new Verizon 6.5 update.

 

Verzion Touch Pro2 w/ MR1 update (Windows Mobile 6.5)

Pioneer F700BT w/ valid 3.0 update/Bluetooth v3.3

I've had issues with the volume control not being there for the longest, same thing still. Sometimes it will be there, sometimes not. With my old XV6800 or my Touch Pro, it was the same thing.

It turns out that I also have problems when I try to voice dial. Dialing out from the phone or from the contacts menu works fine. Answering and dialing from voice commands are my only two problems. I still haven't gotten around to trying any of the things I was gonna do to troubleshoot the issue. Has anyone else had any progress? Thanks.

I GOT IT!!!

I finally got around to trying some of the troubleshooting things I was talking about doing. I removed all the extra things from the \Windows\StartUp\ folder that I didn't recognize seeing from my other Windows Mobile phones in the past. There were three files that stood out. BTTrayCE, HTCStartUp, and PKG. After removing all three of those and restarting my phone, everything worked as expected on my F900BT! I can now place calls using the voice dialing and I can actually answer phone calls! I still don't always get the hang up/volume up/volume down dialog on the F900BT, but it doesn't matter what phone I use, I don't ever get that consistently. Not even my wife's F900BT with her Motorola RAZR or her newer Motorola phone. When I have a few more seconds, I'll try and see specifically which file is causing the problem of those three. Obviously, I would figure it to be BTTrayCE based on the name, but you never can tell. As far as what has changed with those three files being absent from the StartUp, beats the hell out of me. I don't notice anything different with my phone now at all (not even memory usage), but I also don't use TouchFlo 3D anymore, so maybe it would be more evident if I did. I'm just stoked that I can use my phone in my car again . Let me know if this does or does not work for anyone else. Thanks.

It might not be the BTTrayCE because I have it on my phone running EnergyROM Leo and my BT still seems to work fine. The only thing I notice is that every time the unit turns on and the phone connects, the first call is laggy and sometimes won't pick up. But after that, all calls seem to work fine. Does that happen to you too?