Is anyone here experiencing a lag of 2-5 secs when making or answering a call with a Jabra BT800 & XDA IIs ?
I can't speak for that exact combination, but if I'm using my headset (a Logitech one) with either my XDA IIs or C500, there are noticable delays between the call registering as incoming on the handsets, and the initiation of the bluetooth "intercept" of that call. I guess it's down to the BT stack of the handset needing to
a) Recognise that there's a call coming in
b) Check that there's a BT headset paired and active
c) Send an incoming call signal to the headset
d) Wait for the headset to respond
e) Pair securely on an uncluttered frequency with the headset
In an ideal world, all of this would be instantaneous
There's also a pause of about 1 second between the time I press the 'answer' button on my headset and when I can talk. Even though I can hear the call in the earpiece, I have to wait for a second before I can say "hello"
In short; I'd say a two second overall delay is probably the time taken for the bluetooth headset initiation to complete, but longer than this might indicate some problems with signal strength etc.
Related
Can the XDA2s phone be configured to produce loud audio so it can be used as a handsfree speakerphone? The audio from Fonix Voice Dialler is loud but as soon as a call connects it drops to telephone levels.
crocodile said:
Can the XDA2s phone be configured to produce loud audio so it can be used as a handsfree speakerphone? The audio from Fonix Voice Dialler is loud but as soon as a call connects it drops to telephone levels.
Click to expand...
Click to collapse
Yes, during the call, press and hold the green phone key for 2 secs.
I tend to dial the no, soon as it rings, press & hold green key for 2-3 secs till i can hear the ringing. Not bad too.
Thanks.
...
R O F L, so I have had my MDA3 for almost a year now and ALL THIS TIME I was thinking why in the world would MDA3 not have a speakerphone since my last H6315 (hp) had a neat little icon for speakerphone right by the "talk" button.
Thanks for posting this!!!!
This can also be achieved programatically
Here is an article:
http://www.teksoftco.com/forum/viewtopic.php?t=80
as far as I know all MS smartphones and pdaphones have all had this same functionality since the release of WM 2002
Actually the speakerphone is very device dependent. So we should be more concerned on the features HTC has to offer then Microsoft.
Still speakerphone is a must, so i doubt that it wouldnt be included on a phone-capable device.
I have the O2 xdaIIi and was advised to purchase the Jabra BT250v headset to use with my pda/phone and the fonix voice dial function. The headset connects easily and will let me receive calls by pressing button on headset. I can make calls using the phone pad on the pda.
I can not initiate the fonix voice dialling software by pressing the button on the headset as described. I have to press the button on the headset first to establish connection between the two and then press the voice dialling button on pda, clearly this is not right........anyone help?
I am not sure if it will work as the Imate phones don't have profiles for voice recognition. I maybe wrong though...
1. Is it possible to have the BT headset announce incoming calls but still have the phone ring with Voice Command 1.6?
Seems like it's an all or nothing deal so far... either ring and announce through the BT headset (by selecting "Announce Incoming Calls") or ring and announce through handset... Notifications work fine though. The handset would play the alert then the BT headset will announce the reminder. (See here for more details.
2. My BT headset and handset don't automatically re-pair after returning in range or resetting the handset. Anyone else experiencing this?
Everytime I walk out of range or reset my phone, I would have to turn off my headset then turn it back on for the two to pair back up. I sometimes forget and when I hear the handset ring, I pick up w/ the headset only to find that they're no longer paired. Is there a way to have the two automatically pair back up? I never had this problem when I was using AKU3 roms and the stock Cingular 2.25 ROM.
Hi everyone and good year!
I bought the lc1 by Lubix bluetooth headset, good sound quality, immediate piring, buti have a BIG problem:
calling, i have to wait 1 ring, then the call is in my headset. Answering instead needs me to wait a pair of seconds and the conversation starts on the phone and LATER goes to the headset. I hope only a small configuration adjustment is needed......
Having this problem on 2 stock Tilt2s:
My Plantronics Discovery 925 headset doesn't properly answer incoming calls when I press the button on it that's supposed to (and that has worked with all other phones I've used). It's weird: when I press the button, the beep in the headset that's supposed to notify you of an incoming call changes to a different style of ring, but the call is not answered. Pressing it again does nothing.
I tried my wife's Discovery 925 and I'm getting the same issue.
I'd say it's a problem with these headsets in particular, but as I said, I haven't had any issues using them with other phones. Also:
My car bluetooth (2009 Audi A4) also has problems answering calls with the Tilt2.
If I answer the call on the phone itself, everything works fine.
I've heard that the Tilt2 uses a different bluetooth stack than usual, and perhaps this is to blame. Any way to fix this?
Here are some other threads reporting bluetooth problems:
http://forum.xda-developers.com/showthread.php?t=561292
http://forum.xda-developers.com/showthread.php?t=541498
Same exact problem with a Plantronics Discovery 975.
Wow, OK, figured out the problem:
The Widcomm bluetooth stack, in its infinite wisdom, interprets the pressing of a bluetooth headset answer button as equivalent to a press of the Green Button / Answer button on the phone (as opposed to treating it as the standard bluetooth command to answer the call). I had the Green Button remapped to iContact using aebuttonplus, which caused the problem. Incidentally, using "Green Button" to remap the green button doesn't result in this problem.
So I guess we can close the file on this one. Love these conversations with myself.