dougthug

I was going to suggest trying JETware, but it's even better that you got it to work without. Thanks.

Good luck with the man bag .

If you're talking about something other than a Windows Mobile phone, I would go with an Android phone. The Droid is kind of an ugly phone, but it's a beast from what I've been told. Again, if it was me, that's what I'd probably do.

Good to hear you're making progress. It's some weird stuff, but progress none the less. I wonder if there are more things you can do to the Bluetooth settings to "trim down" what's going on? More things you can disable and try. Keep us updated.

I'm still thinking phone. Are you a Verizon customer? If so, you know that you can buy any phone and return it with-in 30 days and get a complete refund (even get your calling plan reverted if you had changed it). You can't do that and exchange it for another phone for free, but if you just return it, it would be like you never bought it. If you're in the market, I would consider buying another phone. I love my Touch Pro2 now that it has Windows Phone (Windows Mobile 6.5) and I have it working so great with my AVIC unit. Not saying I won't continue to try and help you resolve your issue,

Agreed

4 - 5 seconds!?!? That's not normal. You should be able to adjust that setting. I thought my old Touch Pro has the ability to do something like never, 1 minute, 1 hour, always. Check the Bluetooth settings.

Don't do it simultaneously. Put the phone in discovery mode and wait about 10 seconds before you have the AVIC unit search for it.

With the other phones you've tried in the past, did you have the same symptom where they couldn't be searched for from the AVIC unit? Also, do you make your phone discoverable before you try to search from the AVIC? Thanks.

I think slvrdrgn123 is correct about the stacks. These hacks probably won't help you at all. I'm very curious about how you're pairing the devices. I have had different results depending on how I did the initial pairing. Sometimes, if I had the AVIC unit do the searching for the phone, it would work differently than if I have the phone search for the AVIC unit. How are you getting yours paired up? Thanks.

So every single one of those phones, after you setup the relationship between the phone and the AVIC unit, for there on out, once they try to pair, the AVIC unit reboots? Or is it when you try to setup the relationship the first time that it takes place? Thanks.

Um, wow. Seeing as how you've had two different AVIC units and identical results when pairing (if I read your post correctly), I would say that it's definitely your phone. If it was me, I'd delete the profiles for each device from each of the other devices, do a hard reset on the phone, then apply the registry changes and try it all again. If that still fails, I cannot hurt to try the zip file cause you can always do another hard reset on the phone to restore it back. To be honest, my best guess is there is something seriously up with your phone and it may be time for an upgrade. Hope thi

Is it time to mark this thread solved?

When you first got it, did you have the Touch Pro2 or did you have another phone that you had paired up to it? If so, did the AVIC do the same thing with that other phone? Thanks.

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?

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.

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 .

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.

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

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 d

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 t

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.

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

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.

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.