Multiple bluetooth connections?

[shanks916]

I wonder if anybody knows if it is possible to have two (or more) divices connected at onceon a Blue Angel?
eg. Tom Tom 6 plus a hands free connection.
I have tried every configuration I can think of, different ports ect, but to now avail.
With the gps connection up and running, as soon as you turn on the hands free , the gps connection link is lost, turn off hands free and it will resume connection.
I am using BA WM5 AKU3.5 R4 - xplode's excellent rom
In GPS settings
Program is using COM 5
Hardware is using COM 0
Manage GPS settings set to Auto

In Device settings,
BTGPS unit is on COM 0 (Serial box ticked)
Hands free is unassigned

Any help will be much appreciated.:confused:

[shanks916]

any idea's anyone?

[jakubd]

On Last Baniaczek's ROM I made an experiment just a moment ago: BlueAngel, Navigation system (Polish one, Automapa), plus GPS on Bluetooth and A2DP headset - first connected headphones, then added GPS (using automatic GPS connection - it's M$ Stack) - Everything seems to be working fine. I thought it was a bit unstable at first, but AD2P stops sending data, when there is no sound from the device.
GPS Settings are default: COM6 for applications and GPS has COM7 assigned on Hardware tab and in Bluetooth outgoing port. Quite seamless.
then I made the 2nd one: same headset connected in Handsfree mode: indeed turning on navigation made it connect and disconnect every few seconds.
For me it seems to be fault of M$ BT stack: it cannot hold 2 similar streams on BT (COM and Handsfree/Headset are both typical serial connections of highest priority in BT stream). At the same time it can cope easily with two different streams (A2DP is lower priority, high-bandwidth BT connection).
I'm not sure, but I think when I used old Helmi 1.3.2 with Widcomm stack it could cope with GPS and Handsfree at the same time, but it needs more testing.

[xplode]

jakubd is right it is limitation in MS BT Stack

[sassa]

Don't give up and it should start to work. I have similar problem with BT GPS and BT headset. GPS goes on and off while headset is on. And than I try to switch headset off and on, BT off and on, GPS off and on and after some time it start to work together with no problem. It takes first 10-15 minutes of my voyage but then it works for the remaining few hours.
Sorry, but I still didn't find out what combination make it work. If I do, I will post it here as workaround.

And I'm almost sure that I had no such problem with Helmi 1.4 ROM.

[shanks916]

Thanks guys,
have tried every configuration I can think of, but its always the GPS connection that is dropped, not the hands free, this would not be a problem if it was just when you are answering a call.The GPS reconnects only when you disconnect the hands free connection. ?
Has anyone Successfully used the Widcomm stack with this type of setup?
I am sure alot of members would find this usefull if it can be made to work!

[bigmike]

This is my experience:


ROM : Helmi_BA_WM2k5_AKU3.5_v1.4.CF2.R2 (baniaczek)
Tom Tom 6
GPS : Bluetooth
Headset : Nokia BH-300


When the headset is on and connected, the GPS doesn't work (TT say no GPS found). When I turn off the headset, the GPS is working.

With ActiveSync I have the same problem: when the headset is turned on, I can't establish a connection with the PC via bluetooth.


BUT!


If I use a different headset, a Logitech HS03, all is working fine. I can leave the headset on and the GPS is working. I can receive incoming calls with no problem (using the headset) while I'm driving without loosing GPS signal.
With ActiveSync is the same: I can connect my PC with the headset on.


:confused: I have no idea why there is this difference with these two headsets, but one is working and the other no. I don't know if the problem is the MS BT stack, but my test demonstrates that under some circumstances this stack could manage more than one connection at time.

[sassa]

I don't know if the problem is the MS BT stack, but my test demonstrates that under some circumstances this stack could manage more than one connection at time.

Bigmike, my point exactly. As I wrote in my post I keep turning on and off until finally it works. So there are some circumstances under coexistence is possible.

It seems that devices try to use same port which means that first device does not reserve port for itself. I am not an expert but it seems if we could somehow force devices to use different ports problem would be gone.

[jakubd]

If I use a different headset, a Logitech HS03, all is working fine. I can leave the headset on and the GPS is working. I can receive incoming calls with no problem (using the headset) while I'm driving without loosing GPS signal.
If this works with one set and doesn't work with another, it might be connected to list of profiles supported by the headset:
1. Headset - HSP - more common, typical profile for use with cell phones (supports AT commands)
2. Handsfree - HFP - audio-centric, used mostly in cars, less common
http://en.wikipedia.org/wiki/Bluetooth_profile
My SonyEricsson HBH-600 has both profiles (checked with services list on SonyEricsson phone), but I don't know how to select which profile is used by headset.
Just a thought...

[bigmike]

Bigmike, my point exactly. As I wrote in my post I keep turning on and off until finally it works. So there are some circumstances under coexistence is possible.

I hope you haven't misunderstand my previous post. I haven't in mind to minimize the value of your post (very useful is someone will try to investigate about this problem).


I was thinking that somebody, reading your contribute, could wrongly think: “you're are a lucky guy and turning on-off the headset repeatedly you crash some library and the two devices are working together”.


My intention was to remark the fact that under some circumstances the headset and the gps can connect together every time and always at first try: it's not lucky, crash or random events.


If this works with one set and doesn't work with another, it might be connected to list of profiles supported by the headset


I have a similar thought.

It seems to me that some times ago I have read that it should be possible to change some profile's parameters “playing” with the registry.... but I could be wrong...

[sassa]

I hope you haven't misunderstand my previous post. I haven't in mind to minimize the value of your post (very useful is someone will try to investigate about this problem).


No I have not, bigmike, just the opposite. I was delighted that somebody confirmed my point.


My intention was to remark the fact that under some circumstances the headset and the gps can connect together every time and always at first try: it's not lucky, crash or random events.


Couldn't agree more. And I think it's worth trying to resolve it.

[sassa]

I think I find a solution for this, or maybe we can call it workaround. At least it works for me.

As I wrote in my previous posts, I could make it work every time just didn't know how. Now I established repetable procedure which worked every time for reasonable number of experiments.

Secret was to turn on BT headset (in my case Plantronics) and BT GPS device (Haicom 406-BT) and GPS program (iGo) first, and then go to Comm Manager and turn bluetooth on.

So my procedure is:

1. make sure that BT is off in Comm Manager
2. turn on BT headset
3. turn on GPS device
4. open iGo program
5. minimize iGo
6. turn on BT in Comm manager
7. open iGo and make sure it's connected
8. go to phone and call myself just to make sure it works
9. back to iGO and make sure it works

If 8 or 9 fails for the first time, just turn BT off and on again in Comm manager and check it again. I never need to do this more than twice.

Try this, guys, and good luck.

P.S. I don't know if it matters, but make sure that in Settings/Connections/GPS "GPS program port" and "GPS hardware port" is set to (None) and "Manage GPS automatically" unticked.

[bigmike]

Very good! Many thanks Sassa!


I have tried for two times your procedure and both tries worked very well (with TomTom6 and Nokia BH-300)

I use a slightly different procedure:

1. BT off in Comm Manager
2. turn on BT headset
3. turn on GPS device
4. turn on BT in Comm manager
5. open TomTom 6 (wait some seconds and make sure it's connected)
6. go to phone and call myself (on the first call the headset is disconnected)
7. back to TomTom and make sure it works


I have noticed a different behavior of the BT headset having the BT always on (in Comm Manager) and using this procedure... but I need to make some tests before writing more.