Related
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
Hello all,
I've had my TP for over a month now, and globally I'm pretty much happy with it. Of course there are some glitches here and there, but no doubt a firmware upgrade will fix those bugs soon.
That said, there's an annoying issue with the way bluetooth headsets work with the phone part. Let me try to explain :
- When an incoming call occurs and I answer using the "take call" button on my headset (which is a Plantronics Pulsar 590), sounds is transferred to the headset and everything works fine.
- When an incoming call occurs and I answer using the "answer" button on the mobile, the sound stays on the TP even if the headset is switched on and connected to the TP.
When the latter happens, I can't get the sound back to the headset. When I select "transfer to hands-free" from the phone menu, the transfer works erratically.
Is there a fix available somewhere to make sure that, when the headset is on and connected, the sound of an incoming call always goes to the headset?
Thanks a lot in advance for any help you may bring on solving this issue!
Are you using AEBPlus?
No (and honestly, I don't see how that relates to the problem)
Hi Guys,
I also have this issue.
But if I press the 'answer call' on the mobile the sound stays with the Touch Pro but if, once I realise what I've done, I press the 'answer call' on the headset then audio is transferred to the headset again.
Does that happen for you? I'm using an SBTHS-3500 BT headset.
Cheers,
D.
clandestino_usr said:
No (and honestly, I don't see how that relates to the problem)
Click to expand...
Click to collapse
Sorry, I had multiple tabs open for responses.
Copy'n'Paste error.
P.S. I had this issue on my TP and Diamond as well. I have since installed a 2.03-based ROM which fixes the issue (since you can no longer press the phone button to answer, but rather have to use a slider).
I am having multiple issues with Bluetooth on TouchPro2:
Issue # 1 with no solution
When trying to end calls using the end button of Jawbone Prime, it does not work, you must end call using the handset.
Issue # 2 (New)
When ending calls with any Bluetooth device (in my case built in Bluetooth in Nissan Altima) the calls will not terminate, have to press end button many time before calls ends
Are there any Bluetooth registry hacks that may solve either one of these issue?
golfman32 said:
I am having multiple issues with Bluetooth on TouchPro2:
Issue # 1 with no solution
When trying to end calls using the end button of Jawbone Prime, it does not work, you must end call using the handset.
Issue # 2 (New)
When ending calls with any Bluetooth device (in my case built in Bluetooth in Nissan Altima) the calls will not terminate, have to press end button many time before calls ends
Are there any Bluetooth registry hacks that may solve either one of these issue?
Click to expand...
Click to collapse
I see the same issue. Sorry no solution.
I confirm same end issue ....although until reading above i didnt know it stemed outside of the plagued nissan vehicles with navigation.
I have a lot of confidence that this will be fixed sooner rather than later since it is now affecting everyday bt headsets vs. one isolated group of nissan / infinity vehciles.
For those who own this phone and a nissan / infinity. we will take this partial victory as it has been a long two years since the last known phone from htc that worked correctly with our cars was a mogul with WM5 / before that the apache.
Its nice to have a working touchpro 2 and nissan ...even if its not 110% with the disconnect issue.
I have an 08 Nissan with the Bose/Communications/convenience package, and my bluetooth worked fine with my i760, xv6800, and Touch Pro. But I experience the disconnect issue as well now with my TP2. Must be the new HTC drivers.
We'll standby for a patch. But I'm pretty sure even though the time keeps running on the radio, that the call still disconnects. In any case, it isn't right, and I doubt we'll see it when we get patched to 6.5.
FYI, from my research this is the widcom stack on the TP2. I thought i read that in the tmobile TP2 forum.
That would explain why it works because microsoft rarely fixes things on windows mobile.
If so it only more confirms ms at fault and not nissan.
The nav radio was always different than the non nav bose radio in the nissans. Different BT modules i believe.
That would explain why you didnt have the problems that so many others did.
I might be wrong on the widcom stack but I woudl think the tmobile and cdma variety are using same chipsets and drivers. for the BT radio
BMW bluetooth
Same issues on BMW bluetooth
Having simmular problems with an JVC BT1 specielly if i use AD2P at the same time.. phone can lag for like 10-20-30 sec someethimes even more....
Getting VERY tired of this!
several BT issues
I seem to be having the same issue as most of the post on this thread ...my headset, and my Infiniti will not end my call , but has anyone else had a problem just trying to get the bluetooth to open from comm manager or settings ? When I try to turn on Bluetooth through my comm manager it says cant turn on bluetooth , and when I try trough settings it says cannot start the Blutooth stack ???? If i do a soft reset BT will work but if i disabale and try to connect again im having the same issue ....some one help me out
TP2 sprint
have exact same issue with my parrot MK6100
have to press end call many time on the remote to end the call sucessfully
Me too, also using Parrot 6100
The bluetooth is a nightmare. I have a Pioneer AVIC-F90BT with v3 software and I can't even answer the phone when it rings. I even sent to phone to automatically answer after 1 ring and when BT is connected it just freezes the dialer. Then when I hang up a call the phone freezes for about 20 seconds. It sucks so bad.
verizon tp2, jawbone prime.
from prime: I can initiate voicecalling. I can answer a call. I just cannot end a call from the headset.
I think the blue tooth issues are due to the locking of the fm raido they reside on the same chip they talk about this on ppcgeeks
I have issues with my Ford Sync as well. If bluetooth is on and I want to use the Sync system I have to turn off bluetooth then turn it back on to get it to work. Quite annoying. I never had any issues with my XV6800 so it must be the bluetooth radio in the phone. Hopefully they come out with an update or when 6.5 is out it gets fixed.
WITHOUT DOUBT THE BLUETOOTH on the TP2. I have the same issue with Parrot 3200. It may be that different drivers would help.
Anyone been brave enough to try anything else?
Ditto here, but I'll take it a step farther:
I'm using a Jawbone Prime with my Verizon Touch Pro2 and it's not only unable to end calls from the headset, but it will disconnect the headset at random in the middle of calls. The only way I figure it out is to pick up the phone when I can't hear anything, only to find the "headset disconnected, place the handset to your ear" message.
Annoying.
arche3 said:
verizon tp2, jawbone prime.
from prime: I can initiate voicecalling. I can answer a call. I just cannot end a call from the headset.
Click to expand...
Click to collapse
Same setup and results here, and additionally the redial last number feature is spotty at best.
When HardSPL comes out, I'm going to offer a bounty for $50 for whoever can get the MS stack working correctly on our devices with all profiles. Anyone else in with me?
Ohiowa said:
Ditto here, but I'll take it a step farther:
I'm using a Jawbone Prime with my Verizon Touch Pro2 and it's not only unable to end calls from the headset, but it will disconnect the headset at random in the middle of calls. The only way I figure it out is to pick up the phone when I can't hear anything, only to find the "headset disconnected, place the handset to your ear" message.
Annoying.
Click to expand...
Click to collapse
Seeing exact same random disconnect issue with my jawbone prime and my sprint touch pro 2. It happened twice today. One time I was speaking and didn't even realize it had happened for several minutes! Any fix for this?
I contacted HTC over this. The more people that complain about it to HTC, the quicker they will release a fix.
MS BT Stack on TP2
helix139 said:
Same setup and results here, and additionally the redial last number feature is spotty at best.
When HardSPL comes out, I'm going to offer a bounty for $50 for whoever can get the MS stack working correctly on our devices with all profiles. Anyone else in with me?
Click to expand...
Click to collapse
I am in. I need the MS stack for my wireless keyboard and mouse.
Hi all
I have a fully unlocked (from purchase) P5100 tablet which has been rooted for openvpn support. I set up a bluetooth headest with it and everything was ok.
After a few days mobile originiated GSM voice is no longer working properly although mobile terminating seems to work fine .
GSM Speakerphone calls ring once on the tablet then go silent. and this is total "audio shut down" silent, no hiss no nothing, the call proceeds but when the call is picked up at the remote (B party) end , there is no voice path either way but DTMF tones can be inserted to line from the keypad.
GSM tablet originated calls made with a stereo headphone (i.e. expecting to listen to the call on headphone using the tablets internal microphone) give the same result as GSM speakerphone
GSM inbound calls to headphones work as expected
VOIP calls route as expected
tried turning off BT and WIFI , rebooting , unpairing the BT headset ...no restoration of audio !!
Well....i'm stumped !!! anyone got any clues ???
regards
CQU
for the record - I have checked the obvious like the "in call" volume was set to maximum not set to "0"
try Reset factory setting
Factory reset hasnt fixed it, going back to supplier as 'not fit for purpose" under the sale of goods act
Specifically wanted a 5100 for gsm voice calling
Regards
CQU
same problem...
Hi, I've got the same issue...
Even after flashing several custom roms I can make between 0 and 2 succesful outgoing gsm phone calls after a reboot.
Maybe anyone knows a radio rom that works properly in the netherlands? I'm hoping that that might solve the issue. Unfortunately, samsung hasn't released a new version for the netherlands yet as far as I know...
So I have a Vodafone s8+ that I got just a month ago. I just downloaded an update that they sent out a night or 2 ago (Android 8.0.0, Samsung Experience 9.0, build # R16NW.G955FXXu1CRB7) and since then I have been having periodic problems with the microphone:
Google Assistant does not hear me (acts as if I am constantly talking loudly but no discernible words)
Samsung voice recorder records loud static with no actual input from the mic
Trying to use the voice keyboard fails, not recognizing any speech
phone calls (normal; I'm not talking about speakerphone) work without difficulty (making a phone call actually "resets" the microphone so other problems disappear for 60-90 seconds whereupon the former problems reassert themselves) (the phone call doesn't have to actually go through - I can make the call and immediately hang up before talking and the "reset" still happens)
using a wired headset works without any difficulty
Rebooting causes the mic to work normally for 60-90 seconds
Rebooting in safe mode causes the mic to work until I leave safe mode
Using a BT headset works fine and has the same "reset" effect where the phone mic continues to work after I disconnect BT for about 60-90 seconds before the same mic problems reassert themselves
I am not 100% certain that the update is the cause. I had a malfunctioning BT headset at about the same time - obviously I am no longer using the headset and it is not connected (it is *off* and out of range) when the problems are occurring