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.
Related
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.
This problem I am having seemed to start with WM5 AKU 2.3 and is still happening to me in WM6. If someone calls me, and I push the button on my bluetooth headset to answer, my ringtone plays for about a half a second to the person calling me. They usually complain about a loud noise when I answer the phone. I have discovered if I push the answer soft key on my phone instead, it doesn't play the ringtone, but it takes a little longer for my headset to pick up. This happened with my old headset (Plantronics Discovery 640) and my current headset (Jawbone). Has anyone else experienced this problem? If there was some way to adjust the delay for when the headset picks up, I think it would fix this problem because when pressing the key on the phone to answer there is a delay, but when pressing the button on the headset, there isn't.
Thanks...Brian
Hi Guys,
Does anyone have a solution for the problem that the call button on bluetooth headsets won't work anymore with the TP2?
I use it in combination with Voice Command which worked flawlessly with the Touch Diamond, it's also been set to the same (and only) hardware key as the diamond but it won't work on the headset!?
It works fine when you press and hold the call button on the phone though...?
thanks!
jan
redsunpost said:
Hi Guys,
[...]
It works fine when you press and hold the call button though...?
[...]
Click to expand...
Click to collapse
When you say it works fine, do you mean through the BT headset, or just through the speakerphone?
P.S. I had an opportunity to talk with someone at Microsoft, and the response I received was "it's a known problem" and "wait for the next update or next version".
Alas...
i've edited it..
Strange problem cause the diamond had the same windows mobile version?
redsunpost said:
i've edited it..
Strange problem cause the diamond had the same windows mobile version?
Click to expand...
Click to collapse
It's nothing to do with the WinMo version, it's a different BT Stack.
I have been playing with it today and will post an update in the tweaks thread once I have it patched.
Cheers,
Beasty
Its not the BT Connection with a headset in general. That function works fine. I've tested it with my bt headset. Pressing the button I can accept the call and/or redial.
The problem lies within Voice Command itself. Once installed it gets assigned to the one and only hardware button configurable (hold call button for 3 seconds). The problem with that is when I do that with my BT headsets (normal and motorcycle one). They get powered off by pressing them for 3 seconds (same button). xD
I disabled Voice Command though due to the ringtone volume bug. Every 2 seconds the ringtone gets low for an announcement that you don't hear. Still waiting for a proper fix without all the work of replacing files.
I was looking for the original voice dialing function. But it really isn't there on the TP2. Voice Command is much better though. But damn that bug.
ChriX84 said:
Its not the BT Connection with a headset in general. That function works fine. I've tested it with my bt headset. Pressing the button I can accept the call and/or redial.
The problem lies within Voice Command itself. Once installed it gets assigned to the one and only hardware button configurable (hold call button for 3 seconds). The problem with that is when I do that with my BT headsets (normal and motorcycle one). They get powered off by pressing them for 3 seconds (same button). xD
I disabled Voice Command though due to the ringtone volume bug. Every 2 seconds the ringtone gets low for an announcement that you don't hear. Still waiting for a proper fix without all the work of replacing files.
I was looking for the original voice dialing function. But it really isn't there on the TP2. Voice Command is much better though. But damn that bug.
Click to expand...
Click to collapse
Sorry to disappoint you chrix, but the same hardware button (also hold) is used with the Touch Diamond.
Like I said they both look the same but with the TP2 it doesn't work, i'll be looking out for your patch beasty!
Another suffering TP2 user!
Hi guys,
I am also suffering with this issue as well. I did try and see if an old registry hack worked (changing HKLM\Software\OEM\VoiceCommand path=\Program Files\Voice Command\VoiceCmd.exe) but it didn't unfortunately. As previously pointed out in this forum, I think that this issue is more down to the fact that HTC seemed to have replaced the Bluetooth stack with their own proprietary version which isn't bad by all accounts, but does seem to lack this functionality. I might try and contact them to see if there's an update to resolve this but if someone does manage to create a patch for it, I'm sure there's a number of us who would be interested!
Cheers,
Barry
I installed voice command as well.
I'd already used the send button to put my lock on so it gave me another button (see attached).
Any body Know where the button is.
On my TP2, if a call is coming in and I have the bluetooth headset turned on, the headset will pick up the call only if I answer by pressing the headset answer button. If I answer by sliding the on-screen bar over the green "answer" button, the speaker in the phone itself comes on instead.
Is there a way to change this behavior such that the sound always comes through the headset if it is connected to the device, even if I answer on the phone itself?
I would be interested in this too, as I have a bluetooth car kit, if I accept the call from the car screen it is ok, if I accept it on the phone it routes through the phone.
I'm having a similar issue, but a little more complex it sounds like... When the phone rings and using my bluetooth headset (Jawbone2), I have to:
Press the answer button on the Jawbone2
Ringtone sound now comes through the headset
Remove phone from pocket and Slide2Answer with S2U2
Call is now connected through bluetooth
With my Kaiser, all I had to do was press the bluetooth answer button and the call would automatically pick up. No removing the phone, no pressing buttons or sliding to answer!
If I Slide2Answer on the phone when ringing without "transferring the call to bluetooth" first, the handset picks up the call. Useful in many cases, especially if I can't find the bluetooth after putting it down or in my jacket pocket for the time being. If I use the phone to make a call from the handset with bluetooth connected, it always transfers the sound directly to bluetooth. The problem lies with answering the phone with a bluetooth headset - the 4 steps above need to be completed instead of just #1 like it should be!
if you don't want it to go to the phone you need to answer with the device you want to talk with. thats how bluetooth on phones work, tp and tp2
You stole Boo Boo's Name said:
if you don't want it to go to the phone you need to answer with the device you want to talk with. thats how bluetooth on phones work, tp and tp2
Click to expand...
Click to collapse
I get that, If I try to answer the phone on the headset though, just the sound of the ringtone comes through the headset - the phone is still not answered, and is still ringing, just now in my ear! I STILL have to actually answer it via the phone's controls, which is pretty hard to do if you have your hands full........
For the OP Boo boo is correct. Answer the call on the device you want to use.
For Garcia25 the problem is S2U2. I ended up removing it and going back to the built in lock + LockDevice + built-in slide-to-answer.
S
Hi, I have a Bluetooth speaker on my visor, I pair it with my Z. When I am driving & select & dial a contact it goes via the Bluetooth speaker & I can hear them & I can talk to them. However when someone calls me when my Bluetooth is connected I can answer it via the phone or the Bluetooth Speaker but I then have to manually press the "speaker" icon (to the bottom right of the contact picture) & select the bluetooth device so people can hear me. Is there a way of defaulting the phone to "BT Speaker" (or any Bluetooth device) when the Bluetooth is connected? Thank you, I've searched but didn't come up with anything! http://forum.xda-developers.com/search.php?searchid=57383234
Not sure this helps
When I pair it with my bluetooth headset, I have to press the answer button on my bluetooth to hear sound or anything on my bluetooth headset
If I press the answer key on my phone, it would just work normal like it didn't connect to bluetooth( using the speaker on the phone)
So I guess if your bluetooth speaker has some kind of answer key, you would have to press it for it to using it by default
Sent from my HTC Vision using XDA App
Ah yeah, I wondered that too as it was one of the first things I had a look for but it still comes through the phone until I manually "change" the speaker, it must be my bluetooth speaker that's causing it if what I'm trying to achieve works on yours. Thanks for your reply!