Related
Hi
I use a Nokia HDW-3 headset with the latest BT ver " 1.0.0 Build 3900 ". They are able to connect to eachother easily . There is no crackle in voice also.
But the problem starts when the phone switches off " stand by mode " , I hear two beeps in the BT Headset and then it disconnects .
If I get a call within this period the PDA rings and I see a headset with "?" in the middle and then after 5-7 seconds the headset wakes up.
This is nt a problem with HS as I have checked on a Nokia Phone..
Anyone else facing this issue....any possible solution.
Regards
Dhruv
Yes,It's driving me crazy too!
Bought an o2 headset for xda2i,and it just won't send voice to phone or receive.Have paired ok,and its on headset mode.Pressing headset opens phone application and closes it. You can play windows media player and hear sound,not that I want to. Using Broadcom 3900 with bt update.Have returned headset as faulty,so am having a rest from it,but I don't think it is.
Anyone had the same problems?
BTTrayCE problem???
From time to time, I experienced this problem...........
Anyone has a solution other than soft reset?????
i get the same issue too.. just soft reset for me.. im not too irritated by this...
:lol: :lol:
Same here. Yes to all the above. Soft reset for me also. I have an unproven theory that this happens when bluetooth, is switched on and off with profile changes etc. I i keep BT on all the time, it seems to reduce the times I get the memory error..
dhruvkataria said:
Hi
I use a Nokia HDW-3 headset with the latest BT ver " 1.0.0 Build 3900 ". They are able to connect to eachother easily . There is no crackle in voice also.
But the problem starts when the phone switches off " stand by mode " , I hear two beeps in the BT Headset and then it disconnects .
If I get a call within this period the PDA rings and I see a headset with "?" in the middle and then after 5-7 seconds the headset wakes up.
This is nt a problem with HS as I have checked on a Nokia Phone..
Anyone else facing this issue....any possible solution.
Regards
Dhruv
Click to expand...
Click to collapse
This happens to me too frecuently... If anyone finds a fix, please let us know.
try disabling all your today plugins, restart. and see if you can turn on and off the bluetooth w/o having to resort for a second restart[/b]
I think I found a workaround to prevent BT to go on sleep mode and consequently disconnects the BT headset.
Click on the BT icon located at the bottom right of the today screen. Select BT Manager. Then, DON'T click on the X (Close) button of the BT Manager. Just click on the Start > Today icon. This will hide the BT Manager, but it will leave it running on the background (so this way it does not go in sleep mode). I tried this morning and my headset haven't disconnected in all day.
Hope it helps...
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.
Hello,
I searched a program for my Kaiser that disconnects a BT device, such as carkit or headset, when a call is finished.
With disconnecting I mean that the device is not connected anymore at that moment.
So when I have an incoming phonecall, I have to push to connect my BT device to my phone. Then I can pick up the phone with my device.
Who knows were I can find this?
Thanks,
Temba
Hmm, I don't see the point.
When an incoming call is received, before it starts ringing the Kaiser will look for a known paired BT device, if it is on but not connected it will connect it automatically. If it's not on at that moment you're out of luck for that call.
Just leave your device connected... you should already have to push on your device to take the call, no?
Kilrah,
The point is that when I end a call, I want that my BT device disconnects from my phone. Reason is that when I walk to my car, I want to use my BT carkit and not my headset.
Maybe I had to ask how I can unpair a BT device from my phone after a call. But 'unpairing' is for me that I have to enter a pincode every time I want to connect.
Any ideas?
Temba
Hi,
This is an issue between HTC Windows Mobilie devices and carkits equiped with a parrot chip.
As far as I've understood all Windows Mobile 6.1 devices are affected.
I myself have a Kenwood DNX 8220 BT Double DIN Head Unit in the car but there are more Head Units and carkits that make use of the Parrot chip CK5050 if I'm not mistaken.
Does anyone have a tweak or a registry setting that is able to fix this?
I've allready tried to change the COD registry value to: 52020C which is suggested as a solution in a parrot forum topic:
http://www.parrot.com/forums/english/viewtopic.php?id=5620
It didn't solve the issue
tembares said:
Kilrah,
The point is that when I end a call, I want that my BT device disconnects from my phone. Reason is that when I walk to my car, I want to use my BT carkit and not my headset.
Click to expand...
Click to collapse
Oops, had missed this reply back then. I know it's way old, but as someone brought this thread up again, never know if you might read it...
AFAIK this isn't possible. If you have 2 BT devices, paired and powered on but not connected, when a call is received / placed form the phone it will use the last one that has been either connected or selected and "Set as hands free" in the BT settings. If you want to make sure the phone connects to one of them without you going in the BT settings and set it as hands free, you need to turn the other one off.
Hello!
I bought an SBH20, paired with my XZ via NFC, listened to music, then disconnected the headset, using the NFC.
After a while, i tred to connect again via NFC but all i get is a 'connecting' message, BT turning on -white BT icon- but no real connection, therefore the BT turns off.
After several tries it finally connects, but it's not reliable this way.
I noticed, if i enter to settings(not turning anytihng on/off) and trying to connect (still using NFC), everything works fine: connects, disconnects perfectly, and handles the BT as it should.
I've reseted the headset, tried single and multi point modes aswell. Deleted the BT devices, then repaired, still got the problem.
Am i doing sth wrong? I want to connect and disconnect the headset with a simple touch, and not toggling the BT manually (NFC yeah...) Is this something, SBH20 is not compatible with?
(btw sony support says: "For subsequent connections between devices that have already been paired once, make sure that Bluetooth™ is turned on so that the devices can connect automatically." If it's a "must" , then what is the [email protected] use of the NFC??? Just to pair once???)
Please share your experiences! Any advice would be greatly appreciated!
Thanks for reading ( and sorry for my english)
I actually have the same problem using the SBH50. For me sometimes it connects perfectly fine, other times it doesn't and I have to go into bluetooth settings after which it seems to connect properly.
I have noticed that it also depends on how I disconnect it; if I remember to touch the headset to disconnect then next time when I try to connect I have more chance of it being successful. Also, when I try to connect I hold the headset aganist the phone even after the ‘connecting’ popup until I get the 'connected' popup.
These are just work-arounds which aren’t always 100% successful though so would be good to find out what the proper method is.
fl4r3 said:
I actually have the same problem using the SBH50. For me sometimes it connects perfectly fine, other times it doesn't and I have to go into bluetooth settings after which it seems to connect properly.
I have noticed that it also depends on how I disconnect it; if I remember to touch the headset to disconnect then next time when I try to connect I have more chance of it being successful. Also, when I try to connect I hold the headset aganist the phone even after the ‘connecting’ popup until I get the 'connected' popup.
These are just work-arounds which aren’t always 100% successful though so would be good to find out what the proper method is.
Click to expand...
Click to collapse
It is a real shame... In my case it's the opposite, if i touch the headset to disconnect, the next nfc-connect tends to be less successful.
(and i noticed that it also matters if i turn off the headset after disconnected, or not)
And what is really odd, that i don't have to do anything in the settings menu ( or bluetooth settings) just open it, and everything works like a charm...( all connect or disconnect tries are succesfull, no exception, even if i push the headset repeatedly to the pohone's back)
I'm not affraid to mod some system files, apps, maybe build.prop tweaks, but i don't know where to start. In bulild.prop there are only a few nfc related lines (tried to enable/disble those)
So i'm not alone...maybe even more people are in the same boat, trying to solve this.
Again; any related info is welcome
I also have a sbh50 but i normally disconnect by turning off the headset. I have set it in smartconnect to turn off bluetooth automatically when the connection shuts off but it doesnt always do that.
It reconnects with no issues when bluetooth is on and i turn the headset on again. I use the nfc tap only for the initial pairing.
The only issues I have is the google music skipping issue that i posted the other day and the gmail smart connect not working on the sbh50
swtam said:
I also have a sbh50 but i normally disconnect by turning off the headset. I have set it in smartconnect to turn off bluetooth automatically when the connection shuts off but it doesnt always do that.
It reconnects with no issues when bluetooth is on and i turn the headset on again. I use the nfc tap only for the initial pairing.
The only issues I have is the google music skipping issue that i posted the other day and the gmail smart connect not working on the sbh50
Click to expand...
Click to collapse
Well, then we don't have the same issue. I tought i could use the nfc for connect/disconnect (i actually still think it is capable of that, just sony messed up sth)
Could you try to connect/disconnect and connect again with your devices, please :angel:
I'm really curious about this whole nfc story ( why does the headset have the chip/tag if it only works for initial pairing -its not a big deal to pair manually, especially that it has to be done just once-, and on the other hand: if i put nfc in the device, why not put in this functoin too- not a big deal: a proper working BT toggle, but it brings a tad more functionality-
I am rooted but still using the stock ROM. I have two Bluetooth-enabled Pioneer head units and a Bluetooth adapter for my home stereo system with this issue, so I know it's not the other Bluetooth device that's the problem.
When I pair the other Bluetooth device, everything works fine until the Bluetooth device disconnects. I either leave the area with my One, or turn the car off. When I come back home or turn the car on, the One will not reconnect unless I manually turn Bluetooth off and turn it back on again. I don't have to redo the pairing, just cycle Bluetooth off and on. This gets really, really annoying with the car stereos because I have to do it every time I make a stop.
The weird thing is, I had the problem before and it went away when the KitKat update was released. Unfortunately it only worked for a few weeks because I sent my One in for the pink camera issue. I did a hard reset before sending it off and rooted it got back, and now the Bluetooth problem has returned even though it's still on 4.4.2.
Anyone know how to make this go away?
No one is having a similar problem or knows how to fix this?