Ok, what is up with this POS phone. I love the phone, but jesus the bluetooth is a piece or garbage. I have a Plantronics 645 or 655 . It's only a yr old. It pairs up fine with my 8100 pearl. It took no time to pair up. It was easy as pie. Nope, the Curve won't pair no matter how many time I keep entering the correct bluetooth key. It sees it but wont take it. I saw a thread before and a few people complained about the same exact issue. I bought a new bluetooth headset today. The blueant Z9. Same crap. After a reboot and constant trying it finally paired. But it keeps dropping off and on randomly. At one time, I got the plantronics to work once in the past. And when it did connect it did the same crap. Constant dropping for no reason. You people with the TMO curves are you having any bluetooth issues or is everything working flawlessly. Zero drops? Was pairing simple that took only one minute? If so, what brand headset are you running? I have the newest .180 os loaded. I had this issue with the original TMO os then the next upgrade and now the .180. I am so mad. I spent $80 for a headset that is doing the same crap. I guess my next option is to call TMO for a new phone. That cant be it since other user reported the same crap.

When I say dropping I don't mean while making a call. Just the bluetooth headset not seeing the phone and connecting and reconnecting.

Ditto here! I have paired about 8 different headsets to compare sound quality and comfort. Never had an issue pairing any Plantronics headset...no headset for that matter. Are you on UMA or EDGE when the calls drop.

Your problem is not with your headsets or your bluetooth on the phone itself. You said the key, UMA. There are serious threads on the UMA not being compatible with bluetooth devices and mode/ Dp a search and yoy will see. Even T-mobiles UMA group is aware of the major problem

I had the same problem and had to disable UMA to use my bluetooth devices

Didnt work. I had wifi off and I even turned off the mobile network. Nothing works. It keep connecting and dropping just sitting there. I erased the pair and tried it again. It sees the BT but it wont accept the freakin 0000 passkey. This is ridiculous. What a POS. I guess time to call tmo and ask for a new one. This sucks. It did this from day one when I first bought it over a month ago.

Definitely not a general BT problem with Curves. I have an 8300, and the BT is probably the best I've had out of several BT phones. I've used it with a couple of Moto HS850's, a Cardo Scala 500 and Jawbone -- all with excellent results. I personally find the Jawbone uncomfortable and floppy on the ear, but the BT connection between it and the Curve is spectacular - volume, clarity, noise suppression and voice recognition. Definitely not a general Curve BT issue. Like the others here, I suspect it's a problem with UMA/WiFi conflicting with BT, or a problem unique to your device. Definitely follow up with T-Mo.

Ditto. My husband and I each have a Moto H700 and they both work on our Curves without issues. We don't use UMA for phone calls - manage connections is set to "mobile network only" and no dropped calls on T-Mo network.

Ditto. My husband and I each have a Moto H700 and they both work on our Curves without issues. We don't use UMA for phone calls - manage connections is set to "mobile network only" and no dropped calls on T-Mo network.

The problem is with UMA and bluetooth!! I have a thread talking about how I can't use bluetooth with UMA. The problem got worse with the .180 software.

I already tried it with the WIFI off. Doesn't work. I can see UMA interfering if I was on a call or trying to make one. This piece of junk won't even pair with the 0000 passcode. 2 diff BT headsets due the same thing. It sees the headset asks for the code and when I put it in, it comes back asking me to enter it again over and over again. I did search and I remembered reading someone else had the same pairing issue.

Wi-Fi B/G and BT all run on the same 2.4GHz, the reason for the interference (possibly since channels could also provide minimal isolation or difference); only Wi-Fi A runs on 5GHz (less saturated frequency)

DeanQ, to further isolate your issue, since i'm sure you've tried turning off the Wi-Fi on the Curve, why don't you try to turn off your Wi-Fi router or try turning off your 2.4GHz landline phones, as well and let us know what happens; worst-case, try to reinstall your OS (wipe first) and make sure you don't touch the Curve at all when it's talking to your PC/Mac; all else, then that's the time we press TMo to post a fix on this Wi-Fi/BT issue..

if i can do battery pulls all day, i would; thankfully, my Curve works 110%! ?

OK this may or may not be relevent, but I have an 8300 and use a bluetooth GPS puck, however when I run an app, usually Telenav just to get info without my GPS turned on the device searches and searches for it. When this happens my headset goes crazy connecting and disconnecting, until I close the app that is searching for my GPS device. Then my headset connection goes back to normal.
Also no problems with both headset and GPS running, its only when something is searching for my GPS device.

Last edited by pegb856 : 11-17-2007 at 10:46 AM.
Reason: Also have you made sure you are in NUM mode before entering the pass key?

I've got both a Plantronics 655 and a Jawbone. Both pair perfectly with Tmo 8320, works flawlessly....

...that is, unless, I try to use UMA at the same time. Then it's drop city. But as long as I leave Wifi/UMA off, it works perfectly with both headsets. I prefer the Jawbone to the Plantronics...the 655 just sounds awful with noise reduction. The Jawbone sounds great.