Ive been having a problem when I am on a call using my bluetooth headset.
If I get a call waiting coming in, it will take me call off of bluetooth and suddenly audio switches to the handset.
The headset icon on the dialer is still lit as if its connected, but the audio is not through the headset.
I then need to uncheck the headset icon and then reclick it, which gets the bluetooth audo working again.
Obviously not ideal, especially when Im driving.
Any ideas? Thanks.
lirong said:
Ive been having a problem when I am on a call using my bluetooth headset.
If I get a call waiting coming in, it will take me call off of bluetooth and suddenly audio switches to the handset.
The headset icon on the dialer is still lit as if its connected, but the audio is not through the headset.
I then need to uncheck the headset icon and then reclick it, which gets the bluetooth audo working again.
Obviously not ideal, especially when Im driving.
Any ideas? Thanks.
Click to expand...
Click to collapse
Which ROM and kernel are you using?
Sorry should have posted that. All stock.
MrKhozam said:
Which ROM and kernel are you using?
Click to expand...
Click to collapse
any thoughts?
lirong said:
any thoughts?
Click to expand...
Click to collapse
Oh, all stock, hmm... Did it ever work as expected before this happened?
MrKhozam said:
Oh, all stock, hmm... Did it ever work as expected before this happened?
Click to expand...
Click to collapse
Yes. It used to work fine.
Then a couple of months ago this started...I will be speaking with bluetooth headset not problem, a second call will come in and the call waiting will automatically disconnect the bluetooth.
Interestingly, the headset button on the dialer is still lighted, but no audio through the headset. I then need to click the button off and on again, and it resumes.
lirong said:
Yes. It used to work fine.
Then a couple of months ago this started...I will be speaking with bluetooth headset not problem, a second call will come in and the call waiting will automatically disconnect the bluetooth.
Interestingly, the headset button on the dialer is still lighted, but no audio through the headset. I then need to click the button off and on again, and it resumes.
Click to expand...
Click to collapse
One thing you could try is unpair and re-pair the headset in bluetooth settings. And if this still occurs, you can always do a factory reset (painful though).
Did you ever solve this problem? I have a T-Mobile Samsung Galaxy S4 that has a rooted stock ROM and started experiencing the exact same problem this week. I use my bluetooth headset several times per day and before this week that problem never occurred. Now call waiting beep causes the bluetooth to disconnect even though the headset soft button is still illuminated to show that bluetooth is still active.
Related
I have a Cingular 8125 paired with a Plantronics 320. When I answer an incoming call with my bluetooth headset, the other party hears static while the headset establishes a connection. Once the connection is ready, the static disappears. It only lasts for a second or so, but is highly annoying to the other party. Has anyone else experienced this or have a solution? This also happens with my old Tekkeon BT headset, so I know it is a phone issue. Thanks!
Are you using both ring and vibrate at the same time? Perhaps a custom ringtone?
If so, I have had the same situation. Unfortunately, the only solution at the moment that I know of is to turn off the vibrate, or don't use Bluetooth.
I submitted this to HTC a while back after experiencing it on my 8125, and an 8125 I had to replace it.
EDIT: I've only tested it with two 8125's, and a Samsung WEP150 and Motorola H810 (I think) headsets..
Also, as an experiment, try calling yourself from another phone, and answer with the headset. What you'll likely notice is that the static goes away as soon as the vibrating stops.
sk0t. Thanks for the reply and info. It sucks that we have to disable vibrate. I'll give it a shot and see if I don't blow out my friends' eardrums.
*UPDATE*
That did the trick. Thanks.
psychotron said:
*UPDATE*
That did the trick. Thanks.
Click to expand...
Click to collapse
Suspected it might. It certainly does suck that we have to disable vibrate when using a BT headset. Drives me nuts actually.
When I went through and discovered this (haven't seen reference to the issue anywhere in my searches), I had tested with something like 3 different headsets and two 8125's.. Was able to duplicate it every time once I figured out what the cause was.. Very very strange..
I just hope that HTC can do something with this issue on these phones..
Wish I had found this thread a couple of weeks ago. I went through 3 Plantronics 510 headsets and two Cingular 8125 before making the discovery that the problem was tied to the vibrate ringer setting.
One thing I've done--since I'd still like the vibrate feature--is you can set the ringer to "vibrate then ring". I just have to make sure I don't pick up while the handset is vibrating--which isn't too hard since that usually is just the first caller's ring.
Another think I found when troubleshooting: if I put my handset in another room and pick up incoming calls everything is fine. Seems like the vibration needs to be in proximity to the headset for this problem to occur.
hmm i just got my bt headset and was told of the static...
thanks for the info guys will deff turn of the vibration to see if that prevents the static when answering a call
Using my 8525 for a bit over a month now, and I love the phone. Plenty of hacks/tweaks/edits and the phone is just how I like it right now.
Driving a 2005 Acura TL with the built in HandsFree Link and the phone paired seamlessly.
Recently, I notice that while on a call, sometimes the BT Link will drop and automatically transfer the call to the handset. This only happens here & there, not every call. Once call so far after I hung up in the car, the phone was still on and I ended up leaving someone a 6 minute voicemail of me driving, listening to music.....that can be dangerous!!!
Any help or suggestions?
Thanks,
John
i HAD SOME DISCONNECTS WHEN I RECEIVING MESSAGES..IS THAT IT?
No, it will just drop the bluetooth signal mid-call, then to get the car to recognize the phone again, I have to turn off the car and turn it back on to reset connection.....
johnny--2k said:
Recently, I notice that while on a call, sometimes the BT Link will drop and automatically transfer the call to the handset. This only happens here & there, not every call. Once call so far after I hung up in the car, the phone was still on and I ended up leaving someone a 6 minute voicemail of me driving, listening to music.....that can be dangerous!!!
Click to expand...
Click to collapse
I've had the same problem, only once or twice in about a week, using my Jawbone bth headset. Very disconcerting, but survivable. I can see where losing the car pairing might be a bit more problematic.
I wonder if this is because of the /weak/ Bth stack on the TyTN???
-Humbert
Possibly. I thought I saw some upgrades for the BT Stack on here somewhere but now I cant seem to track them down.
Something about the BT Radio shutting down or going into sleep mode after a while and a registry edit to keep it on at the sacrifice of minimal battery life which is fine by me...
Didn't read you mentioning it, but does bluetooth power off during the breaking of the link? If it does, read on and try the following..
not sure if this will help, but try to disable your auto power off options, uncheck the on battery power and on external power..
I had this solved some bluetooth problems especially using the Hermes Widcomm hack and MSI Blueplayer..
Yes, the BT does turn off, but then on again automatically as soon as the call is ended.
Where are you talking about? Is this in the registry or the BT Settings? I was not sure if the WidComm stack is fully functional as of yet, if so, is it in the Wiki?
Thanks again,
John
The WidComm stack is definitely NOT fully functional yet. One of the problems I have with this stack is that, the bluetooth will power off when my wizard turns off or goes into standby, which is not normal!
Not it is not a registry setting, but it is just how it behaves on my system. Sorry for not being a help... I know how the MS Stack pisses people off..
Best regards,
Eugene
Hey, every little bit of info I can get helps....
Thanks for the info on the WidComm Stack....I might just wait and deal with the MS untill the WC is fully functional and possibly in CAB format....just to make life all the easier!
OK, So today my phone would not drop the BT signal from my car.....after being home for 4 hours, it was still trying to use the HandsFree when recieving or making calls....took me a minute to figure out because the dialer skin I have is black at the top, so I could not see the headset icon at the top and was wondering why I could not hear anyone or use speakerphone.
Hopefully it was just a freak accident and wont happen again, but just incase, any suggestions?
I'm running DCD 3.0.0 rom and I found that everytime I turn off my bluetooth headset and bluetooth on my phone that when I go to make a call I cant hear anything from my phone, I've tried turning on the speakerphone too but nothing, I don't know if the other end can hear me but the only way I can fix it is by soft-reseting...
is this a known problem? is there a simple fix? or am i doing something wrong here?
t0mmyr said:
I'm running DCD 3.0.0 rom and I found that everytime I turn off my bluetooth headset and bluetooth on my phone that when I go to make a call I cant hear anything from my phone, I've tried turning on the speakerphone too but nothing, I don't know if the other end can hear me but the only way I can fix it is by soft-reseting...
is this a known problem? is there a simple fix? or am i doing something wrong here?
Click to expand...
Click to collapse
Hmmm... is the volume turned all the way up in the system settings along with the volume for calls?
I have this same problem. I think it is related to Voice command. Do you have VC?
This happens to me 1 or 2 calls after turning off my headset. When I turn the headset back on, the audio works again. I tried turning BT off but that didn't do it along. The fix (so far, I think) is to activate VC (push the right mapped button), and say "cancel". This may need to be done in conjunction with turning BT off. That may reset the audio and ensure it is mapped through the phone speaker, rather than the headset.
I am not 100% sure on this fix yet, as I just figured it out this morning. I think it is related to VC because VC obviously has other problems related to BT.
-BD
I've had this problem sporadically with Plantronics 855. I found that turning off BT before the headset seems to cause my problem. When the problem occurs, a soft reset is the only thing that gets audio back. In general, stock 2.17 worked better with the 855 than 3.35 (I'm now using DCD 3.0.1). The headset will occasionally redirect to the handset unexpectedly and will not resume playing audio after a call. None of this is a deal breaker, just minor annoyances.
bump for a fix please
Hey folks,
I've been struggling with this issue for months now and couldn't find a solution yet. Had the same problem with my Polaris before.
When using BT Handsfree profile, either with my Jabra 250 headset or with my built in car handsfree (Parrot) I get a more or less big delay after accepting a call until the audio stream is transferred from my phone to the BT device.
Meaning, accepting the call in the car results in like 5 seconds delay until I can actually hear what the person on the other end is saying. Until then the voice is still routed via the phones builtin speaker, as if no BT device would be connected.
Same happens with my Jabra headset, though the delay is less there. Maybe 2-3 seconds sometimes.
I tried playing around with Shaps Advanced Config or HD Tweak Bluetooth settings, but no luck so far :-(
Could anyone who is using BT handsfree devices, especially car kits, tell me if you get your audio on your BT device right away, without delay on your BT device? If yes, please tell me exactly what settings you are using for your BT on the phone, e.g. Bitpool min/max, Audio Gateway on/off, Joint Stereo Yes/No etc.
Please let me know if ya using S2U2 as well, I think this could add up to the problem, though for me I still have the issues when I disable S2U2
thanks,
boba
i am using a Bury comfort BT and it rings 2-3 seconds b e f o r e my phone rings! i did not tweaked any settings in my HD. i am not using s2u2.
I also have a Parrot in car hands-free system. Have to say, whilst there are and have been some 'issues' (from time to time) a long delay when an incoming call is accepted isn't one I get.
I don't have the 2 programs you mentioned, as I'd not heard of them before - so I'm running my HD (as far as BT goes at least) in stock trim - FYI I have the auto-answer selected (in 'Settings>Phone>More') set to talk after 4 rings, as a personal pref.
I do have issues with the BT on these phones - I think it's a WinMo thing though, as it's been the same on all the WinMo phones I've had - the BT is pretty retarded unfortunately and it's the one major gripe I have with it and ultimately 'put up with' (very begrudgingly, as it's a feature I use a lot)
Issues are;
Occasionally the phone will answer instead of the car kit (if it's in my pocket - although I may have solved that by having pocketshield 'slide to answer' on there now)
It will NOT auto-answer at all on my BT stereo headphones NOR [more annoyingly] my Scala-Rider motorcycle helmet kit (where every other 'normal' phone I have had has done so with no issues at all)
Every now and again it will freeze the car-kit by showing that there is an active call, when there isn't - and the only way out of it is a soft reset of the HD itself
I only wish there was a fix/tweak for the BT in WinMo - but it seems that most programmers don't see this as a priority area and as such it's not been resolved - maybe 6.5 will address it...but I'm not holding my breath!
Hello, same problem with my Motorola bt350, with and without s2u2.
Same with stock ROM or with dutty's ROM and other.
Its a known win 6.1 BT stack issue.
Regards
T
@ boba23
If you find a fix for that issue please tell me!!! its so annoying
T
Same issues here. Anyone find a fix.
thought it was mine in car blue tooth that has this problem...good (or bad?) to know that it's not an isolated incident.
same issue...
I have parrot MK9000 and HTC BH S100 (stereo). The delay is the same. I do not think there is going to be a solution.
Ι have the transfer delay BT issue here too.... the others person voice is going out from the phone for 2-5 sec and suddenly its transferred to BT heasedet.
Preety annoying, it happens to all my ΒΤ headssets (Jabra , Samsung) the dead seconds just varies.
Plz guys anyone who has solved this let me know
boba23 said:
Bumping this thread up again, since I am still facing the delay issue. I am pretty sure it's not ROM related, since I had this issue with all 6.1 roms I tried. Right now using Topix 2.7.
Played around with Advanced Config BT settings again, but I still have that incoming call delay with my Jabbra BT250. Mostly takes 3-4 seconds, after accepting an incoming call till I hear sound on my headset. I really can't believe that this is an issue that only a few ppl are facing. I have nothing spectacular installed, even disabled S2U2 to see if that helps, but nothing :-(
boba
Click to expand...
Click to collapse
I think this has to do with a combination hands-free / rom version. I have a built in car kit and if I accept the call with phone answer I get the voice right away on the car kit. If I accept it on the radio, it will take 2-4 seconds before sound is transferred to car kit.
I've made another test on a parrot car kit, with same ROM version as before, and it behavior was diferent. If I accept the call on the car kit button, the sound is transferred immediately to the car, if I accept the call on phone button, I get instant sound, but on the phone - private mode....
I made also this test with a plantronics headset, and the sound is transferred right away to the headset either I accept the call on the headset or the phone
so
I am using topix 2.9.4 6.1 rom version - but already tested with several 6.1 roms and 6.5 - behavior is more or less the same
boba23 said:
Bumping this thread up again, since I am still facing the delay issue. I am pretty sure it's not ROM related, since I had this issue with all 6.1 roms I tried. Right now using Topix 2.7.
Played around with Advanced Config BT settings again, but I still have that incoming call delay with my Jabbra BT250. Mostly takes 3-4 seconds, after accepting an incoming call till I hear sound on my headset. I really can't believe that this is an issue that only a few ppl are facing. I have nothing spectacular installed, even disabled S2U2 to see if that helps, but nothing :-(
boba
Click to expand...
Click to collapse
Hi Boba, you're not alone I use BT sometimes as a backup.. and I too have an annoying delay of several seconds... at that very moment I think "hey where's the incoming call", I then hear the sound from the normal phone speaker, and when I switch to the normal phone again the sound is passed to BT ....
Bluetooth Incoming Call Delay
Has anyone come across a solution for this yet?
I have always had a 1-2 second delay in being able to hear the caller using my BT250 headset but, after installing the Orange update ROM, the delay seems to have increased to 3-4 seconds. The caller can hear straight away though.
I have just purchased a BT2020 headset and the delay is still 3-4 seconds.
I am not confident in installing different ROMs (because of my limited knowledge) but would install any that will eradicte this really annoying delay. Any suggestions?
alanu said:
Has anyone come across a solution for this yet?
I have always had a 1-2 second delay in being able to hear the caller using my BT250 headset but, after installing the Orange update ROM, the delay seems to have increased to 3-4 seconds. The caller can hear straight away though.
I have just purchased a BT2020 headset and the delay is still 3-4 seconds.
I am not confident in installing different ROMs (because of my limited knowledge) but would install any that will eradicte this really annoying delay. Any suggestions?
Click to expand...
Click to collapse
Just spoke with Orange Technical Helpdesk and they are sending me a new handset.......will publish result.
Hi all
My Sennheiser VMX-100 headset worked fine on my HTC Rose (WM6) but isn't playing ball reliably on my new Nexus One. Here's a list of symptoms i've noticed:
- Place a call. Screen goes blue. No audio. Call connects. No audio. Press answer button on headset, get audio. (If you press answer before the call connects it drops the call though).
- Place a call. Screen goes blue. No audio. Call connects. No audio. Press answer button on headset, get no audio.
- Call received. Answer with headset. Audio, but no mic, other party cannot hear. (also does this sometimes with placing a call)
So pretty much all call/failure scenarios are observed with this pairing. Has anyone else seen this, or perhaps are interested in debugging?
Thanks
nb: Phone not rooted, running the recent OTA software.
Anyone?
I've got a vmx-100 that I haven't used on the N1, I'll give it a go and report my findings. Charging it now.
Update: 3 calls in/out worked fine, no audio issues.
I tried my VMX-100 today, as my main headset went dead. Guess what? It wouldn't work. I answered the call, but there was no audio.
rotohammer said:
I tried my VMX-100 today, as my main headset went dead. Guess what? It wouldn't work. I answered the call, but there was no audio.
Click to expand...
Click to collapse
Aha! At least one of my issues has been reproduced by someone else!
I'm not really sure how I could get these issues properly addressed. I doubt Sennheiser would be interested and no idea how to trace/track the problem on Android?