Database Info

Bluetooth headsets - sequence of operation

I decided to open a new thread although there were several threads on the use of bluetooth headsets. My intent is to explore whether there is a particular sequence that we need to follow when operating the XDAII and BT headset. I am using a Ericsson HBH-65.
First observation:
I notice that I need to end all calls via the bluetooth headset rather than from the XDAII. If I end a call using the XDAII (ie depressing the red button), for subsequent calls whether incoming or outcoming, I cannot use the headset. There is no connection between the 2. I seem to be able to simulate this almost 99% of the time.
Second observation:
I normally switch off my BT headset overnight for charging purposes etc. At the same time I deactivate the BT settings on my XDAII.
The next morning, I would activate the BT settings, BT profiles and then switch on my headset.
I notice that for the first call I made/receive the next day, I will have problems using the headset. I am not quite sure whether it is the case that I need to switch on my BT headset first and then the XDAII BT settings and BT profiles. I say this as to resolve the problem, I seemingly need to deactivate/activate the BT profile settings before it works and then for subsequent calls I would have no problems using the headset. This needs further testing to test my hypothesis.
Anyone notice anything different on their part.
regards

Same issues
I have had the HBH-65 and have noticed the same issues. I have also had an Logitech and did not have any problems with that.. I am guessing the issue is with the firmware on the HBH-65.

I use Bluetake GII with my xda2. No sequence, no problems. I never even think about switching it on or off. Works in any sequence. Nice looking too! :wink:

I have a Jabra 250, and I do not have to follow any ritual to have it to work fine

I have a Logitech Bluetooth headset with my Qtek 2020 (rom 1.60.21), and it works like crap.
First of all, the headset wont turn on/off sometimes.
Second - if its turned on, and the qtek has been turned off, i need to reconnect it, to switch automatticly when recieving a call.
Thirdly - both speak and hear is very poor quality/fare away (very silent) even though ive turned the volume to maxx.

BT Headset - Works Flawlessly
I have a Sony Ericsson HBH-30 headset and I never give the slightest thought to sequences or procedures. I can turn the headset on and off, the profile on and off, even the BT stack on and off - without ever having to re-bond or anything else.
Now if I could just voice-dial a call with the bloody thing I would be truly happy indeed.

Same problems but getting it figured out
I have the HBH-65 and it seems to work fine now that I've hopefully figured it out. I do a few things. First, I leave the Bluetooth on, on my i-Mate. Second, once it's in range I've noticed it takes about a minute for it to link up. When it links it either makes a single beep (if I just turned on the Headset) or a quiet click if it was already on. I doesn't work ALL of the time, but the more I use it the better it gets. I really expected it to be a little easier.

I have the HBH-200 with call display...which the salesman assured me that it would work with my XDA 2! Call display does not work, and if I end a call on the O2 the headset will hang. Other than that it's great!

I Have a XDAII and a HBH-35
They key to it seems to be not to turn anything off ! it's really frustrating when you think it's all linked up and then get in the car only to recieve a call and not be able to answer it with the headset.
If I have turned the headset off it's a right pain to bond again, red, green lights, funny beeps it's very confusing !
Once it's bonded it's great ! I am amazed with the call quality.

I have an Sony Ericsson HBH 35, I have no problem w3ith the bluetooth pick up call are end calls.
I can even transfer call from my bluetooth to the handaset and by reverse pick up call on my handset and then transfer the call back to the headset all I have to do his to hold the button on the headset fro a few second and the call transfer from the handaset to the bluetooth headset no problem.
Great piece of headset I would really reccomended it to anyone.
The rom on my XDA II is still the version 1.05
Regards
Gigino

Cheers Gigino
Do you ever turn your headset off or disable bluetooth?
I don't have any problems when it's bonded. Just problems if I turn the headset off to save battery

I only turn the headset off at night when I charge it. I use to swwitch off the headset but not anymore becauswe if it is on it use very very little power so it last all day with no problem.
The bluetooth on the XDA II I have never turn it off since I bought it 5 month ago the bluetooth headset on the XdA II is always on.
I've try it switch it of and then on the bletooth and the bluetooh heaset on the XDA II but when I turn it on and turn the headset on it all works fine.
They is no issue on the headset I've tryed every diffrent combinetion the is and the headset works fine.
I have never needed to rebond the headset with the XDA II.
The only thing I have not try is if I can receive a second caller.
Mean trying to switch between 2 caller when I have the chance I will try it.
Regards
Gigino

cheers

Problems with Plantronics M3000 and QTEK 2020

I have bought a Plantronics M3000 bluetooth headset for my QTEK 2020. I have no problems pairing, calling and answering. However the headset just shuts off after a few minutes of conversation. It doesn't just cut the conversation but shuts off. I can make multiple short calls but nothing longer than 3/4 minutes. It works, however, without problems on my wife's Ericsson T68. Anyone can help ? Thanks.
Marek

Hello,
I have the MDA2 (same as QTek2020) and a Plantronics M3000 and It's been working just fine.
The problem you describe it's very weird since you mentioned that the headset works fine with your wife's mobile, and that makes me think that your QTek has some sort of problem with the Bluetooth stack or hardware.
It may be well worth to try (if possible) another headset just to make sure that is not the M3000 fault.
Do you see any type of error or message on the screen at the time of disconnection?
Does it always cut the conversation at the exact same moment?
Does the problem match the time the QTek takes to power save?
Any other clues?

Thanks.
I did not have the occasion to test another BT headset on the Qtek. When it shuts down there isn't any message displayed.
I have no problems with the BT stack (with the Pocket Bluetooth Tools patch) when using it with a BT GPS (Emtac) receiver, it works for hours.
However, your suggestion that it might happen when the Qtek goes in energy saving mode is interesting. I will check that tomorrow.
I'll post the result.

Hi
I seem to have a similar poblem after installing pocket bluetooth tools!.
I use a Jabra BT 250..and I noticed that the headset just mutes during the call..
I am generally used to switching off the display of the XDA after placing the call to power save ...
So I discovered that the headset would mute whenever i switch off the xda after making the call (which it never did prior to installing PBT)!
any thoughts on that?
maybe it has to do with the auto switch off plugin?

Actually I just experienced that too...
If I place (or answer a call) the next time I try to use the phone via the BT headset I notice the BT headset was turned off... Yeah, it could be related to the Powersave feature on the today plugin that PBT installs as a plugin... :roll:
Need to investigate...
Best regards,
Rayan

Both my bt headsets have stopped working since installing pocket bluetooth tools latest version, I have reverted back to version 1005 and everything is fine. I have a sony-ericsson EBH-65 and a skypower clip on headset.

my platronics does the same also its annoying you cant even transfer the call back to the device you have to hand up turn off bt and then turn it abck on and headset mode back on it also does the same on my pc
when im on msn using it as a headset it just d/c and i have to turn it off and turn it back on again
dont see what the problem is
btw the range on the xda2 and platronics is amazing i had it on my bedrooms desk and i went outside it passed through the living room wall and the patio window and i was stood 5m down my garden im sure it would of been over 10m and it was still working if i kept still when i moved it went crackly but ah well lol
just hope someone sorts the prob out

Hi,
I was having the same problem with the M3000. I just had confirmation from Plantronics that this problem is a bug in the product that occurs with the XDA II. I am currently in the process of returning the product.
Regards...Mike

Same problem M3000 doesn't work. Give up now before too much frustration makes you feel ill.
Try the Hello 2 headset. Work with my Aussie XDA2 and is very small and lightweight. Even had a neck chain to carry it around like a USB drive.

Bluetooth Disconnects

Hi,
I'm having a problem with intermittent Bluetooth disconnects between my new Touch Pro and my In Car hands free kit, it's a Factory fitted Vauxhall option with the car.
I can pair everything up, and it all works fine, contacts get pushed, recent calls display etc..
Except that after a random period of time, can be 5 mins or an hour, the display on the dashboard in my car changes from showing 'vodafone UK' to the Phone name, and then disconnects.
Looking on the HTC in Bluetooth settings, it shows that Bluetooth has been turned off!
I have tried various things suggested from all sorts of other forum sites, but nothing has worked.
I hope someone can help me here, as I love the phone.
Thanks.

Enable SMS over Bluetooth?

I have the Kenwood DNX8120 and it works fine with my Fuze (did have disconnect issues but just updated the Kenwood firmware which should take care of that) but the SMS feature on the radio doesn't work. I know only certain phones are compatible with this feature but on the Kenwood compatibility list there are several HTC devices that work. In any case, does anyone know how to enable SMS over bluetooth on the Fuze?
Thanks

I have the Kenwood DNX8120 in my car and have had no luck getting the Fuze to work correctly. It constantly drops connection. I updated the Bluetooth firmware and that only seemed to make matters worse. It will pair with the Kenwood, but either won't make a phone call or will take up to 60 seconds (or not at all) for the Fuze to recognize I it the call button on the radio. SMS, sent and received call history also do not work.
Have you had similar issues?

I can not get sms working. The only other issue I have is that after a call, it drops the connection. If I get another incoming call, it will reconnect and the radio will ring and handle the call. But, if I want to place a call, I have to either select "set as hands free" of something similar, in the bluetooth settings on teh phone and it reconnects and I can dial. I just upgraded to elite rc3 and the problem is still there. I havn't messed with it enough yet to know if it dials ok without having to bring the phone out of standby yet. I too have updated the bluetooth drivers from Kenwood and that didn't help. I also tried the jetware handfree extension and didn't see any improvement.

I called HTC about this, and they told me it only "officially" supports a hand full of car units. Mostly in the Audi and BMW. They don't "officially" support anything from Kenwood so they were absolutely no help on this. I've also noticed this phone drops all connections except cell and data when it sleeps. Wifi, GPS and Bluetooh all seem to go to sleep with the phone. This seems to make bluetooth pretty useless if the connection drops every time the phone sleeps and needs to be manually reconnected.

I haven't seen it drop the bluetooth connection during sleep. I see that the Kenwood supports some HTC devices but not this one specifically. The other wierd thing is that the first time it pairs it shows the battery indicator but after the next connect it doesn't show it. It shows the battery icon but shows it empty. The jetware extension however does fix that. I will play some more with it and report here.

After resetting my phone to AT&T's original setup, I am experiencing the exact same functionality as you. It now sync's my call history and phone book. No voice dial support or SMS yet. (These have never worked with any of my phones) It will disconnect after a couple phone calls and I have to set as hands free to reconnect. Also, mine still looses the connection to the unit when it goes to sleep. I'm keeping it on a car charger for now and turning off any sleep function when charging. That at least keeps it connected until I make a call. It's almost still not worth using with having to reconnect hands free. Maybe if a hands free quick connect shortcut could be created?
This is all really ridiculous that a phone with this kind of tech can't auto pair and be ready for a call. My LG Chocolate had absolutely no problems with the Kenwood. As soon as the Kenwood finished booting the LG would auto connect and be ready for a call.

I thought I found a workaround at
http://forum.xda-developers.com/sho...ghlight=bluetooth+connection+drops+phone+call
But, once installed an trying to run BT Restart I get an error saying that I need .net compact framework (version 1 or 2) installed. Not sure what to do now, cant seem to find a cab for this.

I've used this package from another post on the forum. It has many useful apps including the latest version of .net compact framework.
http://www.tyguy.net/_xchg/PPC/@essentials.rar
Let me know how it turns out!

I will take a look but I have 3.5 already installed. I guess that app needs the older version. Not sure I want to mess with downgrading it.

Not Kenwood
Hey Guys,
I drive a Jag XK8 and it has the same issues you are mentioning with your Kenwood, but its an Alpine unit, it drops calls, and after the first call connects the second call rings on the stereo but you can only answer on the handset.
I also recently had a new Jag XF for a week. It had a full integration to the phone. It also only showed the battery status when the phone first connected then the battery showed empty. It would drop bluetooth connections constantly on some days (every 90secs) and then somedays it would keep the bluetooth connected without issue. Very unreliable.
The reason I bring this up, is just to let you know these issues are not limited to the Kenwood.
Dave

Just an FYI. I have found it easier to just go into setup in the Kenwood and reconnect the bluetooth from there when the phone disconnects. It's under Setup/Bluetooth/Set, then just click on the device and hit connect. It seems easier than fiddling with the phone while your driving.

Bluetooth issue in car: Stock ROM vs non-stock ROM

Hi all,
I have a 2008 vehicle in which Bluetooth seems to be a problem depending on which ROM I have installed on the device.
I'm currently on Android 9 OB 7 and Bluetooth connects and stays connected through incoming and outgoing calls. Works flawlessly.
However, with for example Lineage (among others), the Bluetooth pairs, but connection drops soon after or drops after the first call with the car stereo showing "Net Search", meaning the car BT lost service but the phone Bluetooth is still connected. I've tried restarting and resetting network settings but no luck at all. Changing dev options doesn't work either.
I'm thinking it could be a Bluetooth stack difference?
Is there a way to replace the lineage Bluetooth with OOS?
There is no bluetooth.default.so file that I could find
Any help or direction is appreciated.

nickelnine said:
Hi all,
I have a 2008 vehicle in which Bluetooth seems to be a problem depending on which ROM I have installed on the device.
I'm currently on Android 9 OB 7 and Bluetooth connects and stays connected through incoming and outgoing calls. Works flawlessly.
However, with for example Lineage (among others), the Bluetooth pairs, but connection drops soon after or drops after the first call with the car stereo showing "Net Search", meaning the car BT lost service but the phone Bluetooth is still connected. I've tried restarting and resetting network settings but no luck at all. Changing dev options doesn't work either.
I'm thinking it could be a Bluetooth stack difference?
Is there a way to replace the lineage Bluetooth with OOS?
There is no bluetooth.default.so file that I could find
Any help or direction is appreciated.
Click to expand...
Click to collapse
I am having the same issue with 9.0.2 OOS. So not sure if this us a compatibility issue with more than 1-2 years old vehicles or something else? Glad to hear that OB7 is working fine for you. Hope fix is coming soon. It's simply annoying.

I am having car connection issues as well. I have a 2010 Ford Edge. Just moved from Sony Xperia XA1 Ultra on Orea to my first OP device - OP6 Pie 9.0.2 - I can connect to my car initially but once I turn off my car, I have to go through a series of reconnect steps. I called tech support and we spent about 45 min troubleshooting - of course I was told I was the only one who had complained of this issue - anyway no resolution. The only way I can "reconnect" is to go into my car's system settings and select "connect to BT device" then toggle bluetooth off and on in the phone - sometimes this works with the first go, other times I have to repeat this cycle 5 or 6 times. Simply selecting "previously paired devices" in the phone app doesn't work either.
Really a pain in the tush, because I am usually in a hurry and don't have time to go through all this scenario to get a connection.
On the other hand, I have a bluetooth ear piece (made by Samsung that is like 5 or 6 years old) that reconnects every time I turn it on, no problems.

Car connections too but was not present in omni

I found for stock, performing a network reset (mobile, wifi Bluetooth) then restarting the device fixed the Bluetooth connection issue.
For custom non-stock ROMs, for my issue at least, I found its not a Bluetooth issue at all but rather the mobile network drops and the car Bluetooth cannot reconnect. The same network reset as above does not work but what does work is toggle off the "automatically select network" and manually select the mobile network from the menu that pops up. This keeps the mobile network intact (until the next device reboot, at which point repeat the steps) with the car and all is good.
I only figured it out by accident; hope this helps others.