Develop Bugs

Incoming calls not transfered to PAMA BT headset

Hi,
It seems that my PAMA Plug N Go4 headset just works in one direction: when I make a call it is transfered to the headset, but I can't disconnect using the headset buttons. Incoming calls can only be answered when I press my XDA green button, and they are not transfered to the headset (though the headset does give a ringing tone). Anyone has any idea why this is happening ? Pairing was ok, and done via the setup directions in the manual.

simple tweak
by my experince, the following tweak may help u solve this problem.
1. make sure u must see the "headphone" symbol after turnon the bluetooth function, that's mean ur bt device is well connected with your xda;
2. keep the "bluetooth manager" still running in background or in front.
hope this can help u solve ur rpoblem :wink:

Bi-directional OK now, but Bluetooth Tools 1.1 cause problem
If I wait long enough before picking up the call, it seems to transfer.
But now I have another problem: I've installed Bluetooth tools 1.1.0 and when I try to bond, after entering the passcode and hit next , it returns always back to the passcode screen. No way to bond :-(
somtimes when I try to bond, XDA gives me a message that the PAMA wants to bond, which I accept and enter the passcode. Everyhting seems ok, but it does not pass the call to the headset. Anyone any clue ?

Bluetooth headset button solution?

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.

Hearing sound on Bluetooth headset when answering on device?

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

Incoming Call = Have To Select Speaker When Bluetooth Is On?

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!

[Q] Rogers firmware, bluetooth voice dialing

Bluetooth voice dialing was working on the AT&T firmware, but it seems that since updating to the Rogers firmware it doesn't - pressing the call button (1 second press on my Jabra Extreme 2 headset) does nothing at all. Redial (double-tap on the headset) works as you would expect.
Some searching found this thread: http://forum.xda-developers.com/showthread.php?t=1558776
But this doesn't seem to help in my case - I've installed Bluetooth Launch, but the call button still does nothing. Even more strange, if I run "adb logcat" then nothing is logged when I press the call button (I expected to see something from the bluetooth subsystem at least saying it had been pushed, even if it couldn't launch an application to deal with it).
Voice search is installed, and works as you would expect when manually launched.
Any pointers would be appreciated - thanks.

FireFury said:
Bluetooth voice dialing was working on the AT&T firmware, but it seems that since updating to the Rogers firmware it doesn't - pressing the call button (1 second press on my Jabra Extreme 2 headset) does nothing at all. Redial (double-tap on the headset) works as you would expect.
Some searching found this thread: http://forum.xda-developers.com/showthread.php?t=1558776
But this doesn't seem to help in my case - I've installed Bluetooth Launch, but the call button still does nothing. Even more strange, if I run "adb logcat" then nothing is logged when I press the call button (I expected to see something from the bluetooth subsystem at least saying it had been pushed, even if it couldn't launch an application to deal with it).
Voice search is installed, and works as you would expect when manually launched.
Any pointers would be appreciated - thanks.
Click to expand...
Click to collapse
From the previous thread did you disable any security lock on the phone ?
As that was the clincher for me, once disabled security code to unlock/wake up phone the BT button then actually does something when pressed.
Edit: Actually I supposed if the BT button doesn't do anything while the phone is already awake then its something else.