View Single Post
  #38 (permalink)  
Old 11-16-2009, 11:08 PM
dodgeboy's Avatar
dodgeboy
PPCGeeks Regular
Offline
Location: Berkley, MI
 
Join Date: Dec 2006
Posts: 155
Reputation: 80
dodgeboy is becoming a great contributor
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Re: Bounty for working MS Bluetooth stack on TP2

I'm in for $20 if someone can either fix it or port the MS stack and solve the issues.

My main issues:

When connecting to Chrysler U-Connect in my '09 Dodge Ram, I had a lot of trouble pairing the phone. It took 8-10 attempts (my TP1 and Touch both paired without a problem). When I finally got it paired, instead of answering the call, it would sometimes just start ringing through the car speakers. And of course, I cannot hang-up, like just about everyone else in this thread.

If this wasn't so damn frustrating, it would almost be comical that something as common and basic as Bluetooth would get implemented so poorly in a device today. This is like buying a printer that only prints 6 of the 26 letters of the alphabet. How does it get through quality control? I thought Bluetooth was pretty well standardized at this point. It has been years (4+) since I've had a significant problem with BT functionality with any phone or headset. And I've been through many phones, headsets and car BT setups in those 4 years. I remember being annoyed when the battery and signal strength icons didn't show up on my radio when using my old Treo 650, back in the day! I can only dream of having such petty BT problems with this phone.

Dave
Reply With Quote