So I was at my parents house this weekend and I noticed his Netgear WG602 was not providing a very happy wireless environment. I went round and round with Netgear's firmware and settings available on the stock firmwares and was never able to even get my laptop to provide a consistent speed, nor get much over 40K when downloading files, let alone a stable UMA connection.

So I converted them over to dd-wrt which instantly brought my download speeds to the 400-500K range as well as a rock solid UMA connection.

Point of all of this is that I noticed a new option inside the latest version I loaded on his router I hadn't seen on my Linksys 300N, it was called "Bluetooth coexistence mode".

I did some research on the feature and came up with this PDF that was put out by NXP:
http://www.nxp.com/acrobat_download/...7/75015951.pdf

Turns out that white paper shows the basic idea behind what Bluetooth coexistence mode is and what it helps with. After reading it, I thought that this might just help my use of UMA with a bluetooth headset. Every time I had tried to make a call over UMA with my bluetooth headset it wouldn't even make the call, instead it would drop back to EDGE, I wouldn't even hear a ring, and the call would drop.

After I got home I grabbed the latest release candidate from dd-wrt's download page ( Downloads ) and loaded it onto my 300N and enabled the Bluetooth coexistence mode. And it worked! I can now make a phone call while using my bluetooth headset while on UMA.

I will be doing some more testing, but if you already have loaded dd-wrt on your wireless access point / router then I would suggest you goto their download page and grab the latest release candidate and give it a go.

Post your results in here and lets see if this is a solution to this PITA problem!

I heard about this the other day but it sounded like this was something that had to be supported on both the router and the device. Is this not the case?

Edit- Found this toward the end of the article:

It appears it's more of an algorithm change in how the wifi and bluetooth handshakes are done to keep them from stepping on each other's toes.

Because all of the handshaking protocols are stored within the firmware, these things can be changed and tweaked in software.

Seems the client establishes it's settings based on what it receives from the AP, or at least the AP is controlling enough of it to allow a bluetooth connection to be maintained.

Edited my post with a quote from the article.

Thanks, I will give it a try.

The quote at the end of the article states that the software must run on both the WLAN station (BB device) and the WLAN 802.11b/g WLAN chip (router/AP)

Yes it does, however, after I upgraded to the newest version and then set the bluetooth coexistence mode to enable, I was able to make calls over UMA with my bluetooth headset enabled.

I even tested just before I upgraded to the latest version and with a reboot on the old FW, both tries dropped the call and kicked over to EDGE.

I did an update without resetting back to factory defaults, but did make a backup of my settings just in case, and after the FW update and config change to the coexistence setting, I could make UMA calls with my bluetooth headset.

So even if it's listed that way in the white paper, remember the makers of dd-wrt added what ever adaptation they could or knew how to. The paper didn't cover the specifics of how to code it and such.

Well, that's interesting. The only reason I installed v23 was it was the latest it said was stable. Maybe I'll try the v24. I really don't use bluetooth that much but mostly because I knew it has issues with UMA.

What routers does this work with???

thanks..... And also did my research here goes nothing... I just dont which one to download??

Good luck!

Yea it said download failed.... I just have to wait til tomorrow to do more reading......

tdawg, what router do you have? I can point you to the right file and procedure if it needs some special instructions for your model.

I have the Linksys WRT54G-TM from tmobile. I think someone got it to work but it looks like they had to go through a lot to get it to work. I am not even sure what all they had to do. Are you familiar with it?

I have the same problem with a Jabra BT8010. RIM sent me their branded Plantronics 655 Discovery bluetooth headset and it works perfectly with UMA (they must know something). But If I try the stereo Jabra BT8010 it becomes a mess. Basically I have to disable WiFI in connection settings and go move onto Edge to make it work.

Linksys WRT54G-TM from tmobile.... Thanks for the help

Looks like right now they don't have a version that can be flashed from the webgui on the WRT54G-TM. The only way you can get the firmware onto it would be to open the router up and solder on a jtag connector.

Probably not the route you want to take and I'd wait until a version becomes available that will update through the built in web interface.

Okay, who has what headsets working? I am trying to get my Jabra BT8010 working and so far it is a nogo!! I have upgraded both of my routers to the latest suggested (there is one newer as it cam out on 1/7/08, but others have said to use a certain ECKO build as it is the best so far) and still not good on my end. I want BT and UMA, so what headsets actually work (we have one vote above for the 655, does the Plantronics work the same as the RIM branded as in the past this wasn't necessarily the case)?

I've been using the B&O bt headset for the past couple of months along with the Airport express that Apple makes, which I use for traveling. The headset and UMA have been working great except for a brief period last month when the UMA stopped working a few times.

A good tip is to enable the WMM settings, use the default values. Also, set the beacon interval to 50 or so, this seems to help out many people. I was able to get the curve working over here, better call quality for sure...

Those settings can/may help some with maintaing UMA connectivity but will in no way affect the interaction of the Bluetooth functions of the phone and the UMA (namely using a BT headset and the UMA function at the same time), which is what this thread is about because the problem lies in the fact that the frequencies of the two overlap and cause interference when trying to be used concurrently.

The jawbone is what I am using and it is working fine for me since going back to the default SSID and updating the router to the latest firmware which is .38 I think. Best wishes...

Your profile indicates you have an 8230. Is this really an 8320?

I have a Dlink DIR-655. Anyone get it working with UMA and Bluetooth yet?

All,

I have a Linksys WRT54G v5 running DD-WRT v24 RC6.

UMA and BlueTooth work properly.

Now if I could get my incoming calls to not go to voicemail.....

Thanks to the thread starter- You saved me a bunch of time searching for BT / UMA solution!

-Bill

Okay, so this topic has been dead for a while as there hasn't been any progress in this category for my BT stereo headset and using it with UMA. That is, until I loaded 4.5.0.42 and decided to give it another go. The first time it worked! Fantastic! Before I couldn't even complete a connection before I'd get the cannot connect message and it'd drop to EDGE.

Now I did find a way to mess it up, but it deals with the problem much better then it used to before. If I use my stereo headset to listen to music or I've noticed it if I start a movie, then when I goto make a call on UMA, it breaks up badly and the incoming audio is distorted. On the other end my voice is garbled as well and this continues on for about 10-15 seconds before it kicks over to EDGE and then the call instantly clears up. No drops when this happens though, that's fantastic. It seems to be related to the media player because if I open it up to play a video, the audio still comes through the handset, but after stopping and closing the media player if I goto make a call on UMA I will receive the garbled audio. Odd part about the messed up audio is that it sounds fine for the first few seconds and then starts studdering and echoing.

Well to get around that I've come up with these few steps to clear it up. Close the media player, shutdown the headset, then goto connection manager and shut off Wi-Fi and bluetooth, wait for them to power down completely and give it a few seconds, turn bluetooth on first, then turn the headset on, after those two are connected and the BB shows it's hooked up to it go ahead and turn the Wi-Fi back on. After it gets it's UMA connection, I've got 100% success with it not garbling and holding the connection.

I've updated my Linksys 300N to the final release of dd-wrt v24 and set my bluetooth coexistence mode to "Preemption". Didn't try it with any others as this seems to work fine for me.

So rest assured that when the later versions of this OS hit the carriers, it looks like our bluetooth problem is getting some long needed attention! I think there's something goofy with the media player still and that's why using it seems to mess up the bluetooth stack, but I'm alright with that as I rarely use the media player. If I am using it, I'm on a plane and can't use the phone to begin with! Still wish they could get the audio out the bluetooth connection when watching a video though......

If others are testing out 4.5.0.42 please report back here if it helped you at all.

And for those looking, please do not bombard me with PM's for it. It's out there and available and if you're persistent enough, you'll find it.

I didn't try 4.5.0.42; I jumped straight to 4.5.0.44. My UMA/bluetooth problems (complete disaster with Jabra BT8040) disappeared completely!

I am using DD-WRT also. I tried it both with and without bluetooth coexistence mode on, and it worked equally well both ways. I have left it turned off and have had a few 1+ hour conversations and many shorter ones using my BT8040 and UMA with no problems.

Great to hear! .44 has been working well for me, .46 UMA and bluetooth still worked but I had radio weirdness with it so I went back to .44.

Hopefully RIM finally squashed this problem..

All that and .44 works with the WRT300N and WRT350N (these are all the routers that I have tried so far).

Friends,

I have had nothing but trouble since September of 07 with UMA and dropped calls. I am willing to try the dd-wrt route as a last ditch effort to get this thing working as intended.

I will accept PM's and emails if anyone is willing to help. I am using the WRTU54G-TM

Tks

Help is generally given here in the public forums so that all can benefit from the solutions given. That's the intent of a forum.

That being said, you've included no information on which to begin to help you. Dropped calls can be caused by your ISP, your router (type,) etc. Loading DD-WRT won't likely help with this problem. We need a lot more info. What type of router? What kind of ISP?

Hey John!

I am using the new WRTU%$G-TM router. My ISP is Comcast, and I have plenty of bandwidth. The Cable Modem is an Arris

I have been working on this problem since I first got the service, and it has not been fixed by newer OS's (for me)

I have switched handsets 4 times, and switched SIM card as well. I do a battery pull on a daily basis.

Then it's obviously something in the router/ISP. Do you have e911 info entered in MyTmobile.com?

yes

Does it work ok at a Starbucks (TMobile Hotspots?)

never been there. I have gone through 2 Netgear Routers, the TMO (branded) WRT54G-TM and now the WRTU54G-TM. I have changed handsets 4 times, Sim cards, and I get dropped calls with and without the Jabra BT200v.

If it works at a TMobile Hotspot (like Starbucks) then that narrows it down to your router/ISP. Since you've used the TMo router I'd say it could be an issue with your ISP.

Go try it at Starbucks.