Just got the TouchPro 2 Saturday and love it so far, but can't pair it with the OEM Uconnect bluetooth in my car; the car does not see the phone. Phone and local VZW tech support couldn't get it to work either. It will pair up with another phone or a PC but only if it initiates the pairing. If another phone tries to pair with the TP2, the TP2 never sees it, even though it saw the other device when it initiated the pairing.
The car successfully pairs with every other phone we've tried, including the HTC Touch.
All devices, including the car, were verified visible. Is anyone else having this problem? I do like the phone and have been waiting for it for months, but if I can't use it in the car it may be a dealbreaker. Thanks for any help you can provide.
My guess is theres a problem with the bluetooth stack (basically, the bluetooth software/driver). Most (almost all other) WinMo phones use the Microsoft BT stack, but for the TP2 HTC decided to use one by Widcomm. So in short, theres probably nothing you can do about it unless someone manages to hack the MS stack onto the TP2.
Thanks for the prompt response, but wish it was better news!
Since I don't understand the details, it obviously won't be me hacking it. I would think though that a lot of people would be having similar problems, maybe that'll spur a change...guess I have 20+ days to decide how big an issue it is.
HOLY CRAP!! The TP2 uses the Widcomm stack?!? OMG I got to order mine now... I HATE the MS stack. I have used the Microsoft and Widcomm stacks on both Win32 and WinCE platforms, and Widcomm by far blows everything out of the park when it comes to reliability and usability.
Hopefully the TP2 has the full Widcomm stack and not a bastardized version of something to pass off as it. I would be royalled pissed then.
Maybe Widcomm is superior, I honestly don't know. But from my perspective the TP2 is a bluetooth brick. It doesn't play well with others, and either doesn't communicate at all, or only communicates one-way, with every bluetooth device I own and those at work.
Providing a bluetooth device that doesn't communicate seems just a bit counter to the whole purpose of bluetooth.
Speaking of bluetooth connections i have not been able to get my bluetooth dun to work properly. I had the xv6900 before this and i remember i had to dial a number and edit the settings but i have been searching online and can't find the number... Anyone familar with this?
YES!!! I figured it out
Dial ##778
Click Edit
Unlock Code is 000000
Click View Info
Scroll Down to M.IP Default Profile
3rd row down is DUN NAI
Click DUN NAI and then click Menu
Then Edit
Change the Value to (yournumber)@vzw3g.com
example 7777777777@vzw3g.com
Click ok
Click Menu , OK
Should Soft reset and then you are good to go!
In fact I am typing this on my laptop which is bluetooth tethered to my TP2 right now!
Thanks for the info. I tried it, and the only change was to remove 'dun.' in the edit, is this correct? It already showed my phone number, but the address was given as @dun.vzw3g.com
haven't been able to try it in my car yet, but a co-worker's phone still couldn't get a response form my TP2 to a connection request.
I forgot how to put my Jawbone in pairing mode yesterday. That was frustrating until I googled it...
I also paired it with my HP laptop, which allowed me to play music and use the laptop speakers/ mic for phone calls. That last part was overkill. I used the speakerphone today for a conference call and it was awesome.
Only real gripe so far is that we didn't get the backlit keyboard. There are worse things that could have been wrong for sure.
At the time I typed that I didn't see any way to backlight it. Then last night in the dark it did by itself. Very cool. Now I don't have any gripes about the phone. I love this thing.
TP2 Pairing Problems
Reply With Quote
Originally Posted by iamrobk
Bookmarks