Hey all,
Got a query on the bluetooth side of things, I seem to have bluetooth connections dropped/interrupted when a new device/connection is made.
For example, set a constant l2ping to the phone on one bluetooth device (a computer).
Then send a file to another computer via bluetooth. The first l2ping drops pings immediately, you have to restart the ping to resume it, as the phone has dropped the connection (I'm assuming as it negotiates the file transfer).
I've tweaked the registry to try and fix this setting:
HKEY_LOCAL_MACHINE > Comm > BTPAN1 > Parms > MaxConnections = 16 (decimal)
But this doesn't seem to solve the problem. Can anyone suggest why this is?? (Is it just a poor bluetooth stack?)
Thanks in advance folks.
Related
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.
any idea's anyone?
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.
jakubd is right it is limitation in MS BT Stack
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.
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!
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.
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.
bigmike said:
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.
Click to expand...
Click to collapse
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.
bigmike said:
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.
Click to expand...
Click to collapse
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...
sassa said:
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.
Click to expand...
Click to collapse
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.
jakubd said:
If this works with one set and doesn't work with another, it might be connected to list of profiles supported by the headset
Click to expand...
Click to collapse
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...
bigmike said:
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).
Click to expand...
Click to collapse
No I have not, bigmike, just the opposite. I was delighted that somebody confirmed my point.
bigmike said:
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.
Click to expand...
Click to collapse
Couldn't agree more. And I think it's worth trying to resolve it.
Multiple BT connections - solution?
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.
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.
"Hi guys. Can anybody tell me how do I connect to a bluetooth headest manually through WM 6.0?
I understand that WM6.0 is supposed to do it automatically, but it doesnt . There has GOT to be a way for me to sync the TyTnII with my bluetooth headset manually.
My headset is Jabra320s (piece of crap), and it does not allow me to connect to the TyTnII manually through the headest because there is no menu LCD on the headset. Therefore, in order to connect my TyTnII and my Jabra manually, this must be done though the phone."
--------------------------------------------------------------------------
"hm...its pair'd....here is the situation
even though it is pair'd, when i goto the bluetooth connects scree (device tab) there are no options to connect. the only options that come up are "edit, delete, set as hands-free, set as wireless stereo". theres no connect option. so i cannot tell it to connect....
sometime sit connects automatically, sometimes it simply doesnt, no matter how many times i restart it or the headset. sometimes even when i RE-PAIR it, it still does not connect."
I'm trying to connect my phone (ATT HTC Tilt) with a stereo bluetooth headset or trying to send files and everytime I scan for new devices it gives me an error stating "PROBLEM WITH BLUETOOTH HARDWARE"
Additionally, the "Turn on Bluetooth" option always turns off automatically....
What is going on? Can anyone help?
Please...
Anyone who experienced this or can give me a hand? Thanks!!
I had this same problem all of a a sudden on my Kaiser. But after doing a hard reset this got resolved.
And now i just flashed Dutty's 6.1 ROM. Its amazing update..
Cheers
Thanks Arun...
Tried the hard reset NO LUCK! Problem persists, and bluetooth keeps turning off. I go back to the wireless manager and check both boxes and they come back off in 30 seconds!!
When searching for devices it says (ERROR: PROBLEM WITH BLUETOOTH HARDWARE)
Not able to beam or receive files at all.
Any help? Thanks so much!!
Same Problem
Running into same problem here. I haven't even updated the ROM from stock yet, although I have done the JumpSPL step (cuz I received the white screen). My Radio is 1.27.14.09.
Any help is appreciated.
I would think that if you have done a hard reset and you don't install anything and you still have a problem then you **** is borked. time to do a warranty exchange.
has your bluetooth ever worked, with the rom that is currently on your phone?
Problem with Bluetooth Hardware!!!!
I am having the same problem. I have the stock AT&T ROM. Here is exactly what is happening:
The bluetooth is not working on my Tilt at all. It has lost connections with devices that it was already paired with (a Motorola Q Global and a headset). All attemps to pair the devices again lead to the following: "Error: Problem with Bluetooth Hardware".
When I go to Bluetooth Settings through the Comm Manager, then Mode and check "Turn on Bluetooth" and "Make this device visible to other devices", it unchecks as soon as I exit the settings menu. The Comm Manager constantly shows the bluetooth being off and when I tap the icon, the phone "thinks" for awhile and then it greys out again.
The only change that I have made from the time that it was working is to install the iphone package, and a today plugin (which I have since uninstalled) found here.
I recently changed my Kaiser Tweak bluetooth settings: I changed the BitPool from 'medium' to 'very high', but my headset was still working after that. The other settings are:
Sample Rate - 48000 (Advised)
Use Joint Stereo - Enabled (Default)
Receive Files - Enabled
Any ideas/suggestions?
Forced to do a hard reset
kcrumbley said:
I am having the same problem. I have the stock AT&T ROM. Here is exactly what is happening:
The bluetooth is not working on my Tilt at all. It has lost connections with devices that it was already paired with (a Motorola Q Global and a headset). All attemps to pair the devices again lead to the following: "Error: Problem with Bluetooth Hardware".
When I go to Bluetooth Settings through the Comm Manager, then Mode and check "Turn on Bluetooth" and "Make this device visible to other devices", it unchecks as soon as I exit the settings menu. The Comm Manager constantly shows the bluetooth being off and when I tap the icon, the phone "thinks" for awhile and then it greys out again.
The only change that I have made from the time that it was working is to install the iphone package, and a today plugin (which I have since uninstalled) found here.
I recently changed my Kaiser Tweak bluetooth settings: I changed the BitPool from 'medium' to 'very high', but my headset was still working after that. The other settings are:
Sample Rate - 48000 (Advised)
Use Joint Stereo - Enabled (Default)
Receive Files - Enabled
Any ideas/suggestions?
Click to expand...
Click to collapse
They only way to fix the problem was for me to do a hard reset.
Hi all.
I have Darkyy's v8 installed, (very nice btw ) but I have noticed a problem that I think is not related to the v8, but to the Galxay S itself.
I have a Kenwood head unit in my car, the phone pairs fine, and auto connects every time, but it seems to disconnect its self.
On checking the phone, it lists my car kit as paired but not connected, if I click and select CONNECT, then it connects just fine. The problem is, the point of having the BT car system is to make and received calls without the distraction of haldling the handset.
Any ideas whats going on, or a possible fix? I have seen a lot of people with this problem but no solutions.
regards
I have the same problem - I'm trying different roms still the same issue. have you found anything to sort this?
I dont know if this is the case: http://www.howardforums.com/showthread.php/1666363-Galaxy-S-Bluetooth-Car-Connection-Keeps-Dropping - gonna try it today!
UPDATE: Actually I did this (below) instead of the above suggestion.
"Set source to Standby
- Goto Menu > SPCL DVC Select
- Press and hold the right knob for 1 second to select SPCL DVC Select
- Navigate to option "Disable automatic sync"
- Press the right knob
- It will say "Completed"
- Turn radio off, wait for it to shutdown completely and phone to no longer act like it's connected via bluetooth
- Turn radio back on and voila, no more download!"
From: http://androidforums.com/evo-4g-tips-tricks/210381-how-turn-off-phonebook-sync-w-blue-tooth.html
So I've been trying to set tasker to turn on my Bluetooth when I get out of range from my homes WiFi signal.
Problem is I have no idea how to set tasked to do that.
Has anyone done this and possibly shoot me some info.
Sent from my XT1060 using xda app-developers app
I would do something like this:
Profile: BT Off at Home
Context: Wifi Connected [SSID:<YourSSID>]
Enter:
Bluetooth Off
Exit:
Bluetooth On
The exit task isn't really necessary if the Bluetooth was on before you connected to your home Wifi, but it ensures that you get the results you're looking for regardless of the Bluetooth state before the profile activates.
UncleMike said:
I would do something like this:
Profile: BT Off at Home
Context: Wifi Connected [SSID:<YourSSID>]
Enter:
Bluetooth Off
Exit:
Bluetooth On
The exit task isn't really necessary if the Bluetooth was on before you connected to your home Wifi, but it ensures that you get the results you're looking for regardless of the Bluetooth state before the profile activates.
Click to expand...
Click to collapse
I have a similar tasker situation setup on mine where if I'm not on WiFi my phone turned BT on and enables BT tethering. It is a bit more complicated than that though. Let me know if you'd like me to post it.
titanshadow said:
I have a similar tasker situation setup on mine where if I'm not on WiFi my phone turned BT on and enables BT tethering. It is a bit more complicated than that though. Let me know if you'd like me to post it.
Click to expand...
Click to collapse
I would definitely appreciate if you posted it
Sent from my iPad using Tapatalk
I use 2 profiles.
Enable BT Tether 1 is triggered when not connected to WiFi and executes "Enable Bluetooth Tethering" on entry and "Disable Bluetooth Tethering" on exit.
Enable BT Tether 2 is triggered when BT is turned when Bluetooth is on and does the same as above.
I use 2 profiles so that if Bluetooth is turned off when WiFi is also off, tethering enables itself again once BT comes back on. This also requites the use of an app called "Secure Settings" which can turn tethering on and off. When you turn tethering on if you're running a stock OS for your device it will check with your carrier (the OS does it, not Secure Settings) to see if you have that feature. This does not work if you use a 3rd party app to do tethering outside of the native OS method. If you are on CyanogenMod it does not check.
Enable Bluetooth Tether:
Code:
Profile Status BT Tether 1 ON
Profile Status BT Tether 2 ON
Secure Settings BT Tether Enabled if %WIFII !~ *CONNECTION*
Disable Bluetooth Tether:
Code:
Profile Status BT Tether 2 OFF
Secure Settings BT Tether Disabled
Now, I also have a much more complicated tasker series set up on my tablet to make sure my tablet always connects when wifi fails, but it took a lot more work to not waste battery power.
Auto Tether is triggered when not connected to WiFi and executes "Tether to Phone" on entry and "Disconnect from Phone" on exit.
Please note that where it says "Secure Settings Connect to Phone" the Secure Settings action used is "BT Connection" and you select your already paired device from the dropdown list. You can also set Secure Settings to toggle Bluetooth to ON if it is off, I don't have it say that way but it could be handy. I also found myself getting a lot of errors popping up as Toast notifications, but they were meaningless as the connection was established. Thus, I didn't worry about them and ended up disabling all notifications from Secure Settings.
Tether to Phone:
Code:
If %PhoneConnected = 0
Profile Status Monitoring Phone Connection ON
Secure Settings Connect to Phone
Profile Status Tether Search ON
Else
Profile Status Tether Search OFF
End If
Monitoring Phone Connection is triggered when the phone is connected via Bluetooth and executes "Phone Connected" on entry and "Phone Disconnected" on Exit.
Phone Connected:
Code:
Wait 1 Second
HTTP Get www.google.com:80
If %HTTPR=200
Variable Set %PhoneFailed to 0
Variable Set %PhoneConnected to 1
Profile Tether Search OFF
Else
Variable Set %PhoneFailed to 1
Variable Set %PhoneConnected to 0
End If
PhoneDisconnected:
Code:
Variable Set %PhoneConnected to 0
If %WIFII !~ *connection*
Profile Status Tether Search ON
Perform Task Tether to Phone if %PhoneFailed=0
End If
Tether Search is triggered every 5 minutes and executes Tether to Phone and has no exit.
I basically had to set it up this way because there is no way to have the tablet aware that it is connected to the phone at any given time, it'll execute an event but unlike WiFi there is no tasker variable for what devices are connected via Bluetooth using %PhoneConnected to manage this works very well. Using %PhoneFailed allows the script to be able to tell that a connection was attempted but unsuccessful, without this the tablet gets stuck in a loop always trying to reconnect once the phone goes out of range. I found this happening a lot when I would go to the grocery store and leave the tablet in the car after school. The battery drain wasn't extreme but it was there.
It is a little complicated, which kind of annoys me. One of these days I may get into Android programming and just make an app. But for now, this works. If the phone or tablet disconnect and are out of range, every 5 minutes a connection is attempted. If the connection drops, it does try once right away to reconnect, but then trips the Failed variable which prevents the tablet from going hardcore at trying to reconnect.