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.
Related
Does anyone else have this problem...?
I've just got an HBH-662 for the Universal and it pairs fine and can make calls, but answering calls it doesn't work properly.
The headset recognises incoming calls and rings okay, but when you press the button to answer the call, it doesn't put the sound through the headset, only through the phone.
Maybe it's a setting I'm missing, but it's a tad annoying!
F.
I'm not sure I can help much, but I have no problems with my HBH-662 and my Jasjar.
Brett
I too have no problems with the HBH-662 and answering calls.
Will give it loads of testing later and see if i can get it to act the same as yours
I have been using HBH-662 with JJ for few weeks and in general I have no problem. I just wish that the Caller ID issue (the ability for the JJ to send contact name to the BT headset instead of number only) is resolved very soon.
I've not had any problem answering calls. The only problem I've experienced with this headset is an apparent clash with programs like GSPPocketMagic, MagicButton and HandyMenu. With either of the three apps running, my headset drops the connection after 20-30 seconds and I have to press the button on the headset to pick up the call again, which it drops 20-30 seconds later, etc. The moment I uninstall these apps it works fine again.
How strange. It seems to have sorted itself out!
I paired my old BT330 to compare it, it worked fine, so I removed the Akono and re-paired it and it seems to be working.
Thanks for the comments folks, it's useful even though you didn't get the same probs!
Now the next issue is how to reconcile the fact that SE say this thing provides "Caller ID", which I took to mean the NAME of the person, with the fact that it doesn't do anything of the sort... only the number.
And who really remembers the numbers of their friends these days?!
F.
fergusstrachan said:
Now the next issue is how to reconcile the fact that SE say this thing provides "Caller ID", which I took to mean the NAME of the person, with the fact that it doesn't do anything of the sort... only the number.
Click to expand...
Click to collapse
It does provide CallerID name... but only with certain phones WM phones being among those that don't provide name information. It's my understanding that the problem lies in the bluetooth stack on the phone and not with the headset. I did see a post a short while back that suggested the issue was being worked on and would be resolved in a ROM update, so I have hope... but I'm not holding my breath.
Brett
Hehehehehehehe.
Microsoft 'working on' the bluetooth stack...
hehehehehehehehe. Sorry. I just find that really funny. The idea that MS are actually working on anything to do with the BT stack on WM!
I don;t really understand why it takes so long to program a bit of BT to provide something like that (or, say A2DP!). I mean, how hard can it be?
Well I'm not a programmer so I won't moan.
F.
Splatt! said:
I've not had any problem answering calls. The only problem I've experienced with this headset is an apparent clash with programs like GSPPocketMagic, MagicButton and HandyMenu. With either of the three apps running, my headset drops the connection after 20-30 seconds and I have to press the button on the headset to pick up the call again, which it drops 20-30 seconds later, etc. The moment I uninstall these apps it works fine again.
Click to expand...
Click to collapse
Any more comments if Sony Erickson Akono BT headset HBH662 really clashes with magic button and handy menu?
Hiya, I got a BT800 for Christmas from my lovely wife and am having a hell of a time getting it to activate voice dialling!
Having paired it and chosen to use it as the hands free device, I can use it for phone calls that I start from the phone, but the Exec doesn't do anything when I 'tap' the answer button (one beep) or squeeze it(beep, pause, beep).
I've even just restored the original rom (hard-reset, basic install) and it still doesn't do anything...
Did anyone else have this problem? Is there a stage I'm missing out?
Hope someone can help, I've a nasty feeling it's too late to return it to Amazon...
Might be a daft question, but have you added your voice tags (or re-added after hard reset)?
Thanks for the reply, I was never intending to use voice speed dial (preferring voice command by miles) and so didn't record any tags. Even without any, you should still get the app launching and a message that there aren't any tags recorded. My problem was that I wasn't even getting that.
I can't claim to have solved the problem, but at least I no longer have it! I reinstalled the original O2 ext_rom and did a nice clean "Basic" install then put my customised ext_rom back and reset again. Having paired the headset I was able to launch voice speed dial from it, so went ahead and installed voice command, made the registry change to launch VC from the headset and am laughing.
I wish I knew what had caused the problem so I could avoid doing it again! I suspect that it was an attempt to restore my bluetooth registry settings on a rebuild that was the cause... Certainly I didn't try to set it up automatically the second time round and it *did* work, but there are too many variables to be sure.
HTH someone!
The Universal has no NATIVE support for Voice Dial using Voice Command. You have to do the following so it will work via VOICE COMMAND as it has to bypass the Installed Vocie software:
Install Voice Command to the default location.
Fire up a registry editor
Go to: HKEY_LOCAL_MACHINE\SOFTWARE\OEM\VoiceCommand
Modify the string marked "path" from the default \Windows\SDDialer.exe to \Program Files\Voice Command\VoiceCMD.exe
This should now launch Voice Command
Maybe you made a mistake like missing a letter?
If you have done the above and it still doesnt work, then i'm just as lost as you are
sorry, browser problem, message was posted twice
I'm using the BT800 with my Qtek 9000 (Original ROM) and don't have any problems with voice dialing. After pressing the button on the Jabra within a second or 2 the voice dialing application is started, I hear a start sound, speak the name and it automatically starts dialing.
I have installed the latest BT800 firmware (becaus of the international dialing bug) and had not tested this functionality with the original firmware. Which firmware are you using?
MvanIperen said:
I'm using the BT800 with my Qtek 9000 (Original ROM) and don't have any problems with voice dialing. After pressing the button on the Jabra within a second or 2 the voice dialing application is started, I hear a start sound, speak the name and it automatically starts dialing.
I have installed the latest BT800 firmware (becaus of the international dialing bug) and had not tested this functionality with the original firmware. Which firmware are you using?
Click to expand...
Click to collapse
Which button do you have to press to activate the voice dial? The left or the right button under the LCD? Is it Tap or Hold, the button i mean?
@jorgee: 1st post - thanks, that's what I meant earlier when I said I'd done the reg fix and it all worked
2nd post - to activate voice dialling on a UK O2 Exec, you press the 2nd button from the left on the front of the device - next to the camera button.
@ MvanIperen, I'm using the latest BT800 firmware too, when I did a couple of rebuilds, the problem went away and it now behaves as you describe.
@ all, thanks for the replies! It was just me after all! Mental note: Mess with the registry at your peril!
[quote="this_mike
2nd post - to activate voice dialling on a UK O2 Exec, you press the 2nd button from the left on the front of the device - next to the camera button.
[/quote]
I meant is there anyway to activate voice dial from the headset? Can i only activate it by pressing the voice command button? I mean lets say my phone's in my drawer and i have the BT800, do i have to pull out the phone to be able to use the voice dial?
Jorgee said:
I meant is there anyway to activate voice dial from the headset? Can i only activate it by pressing the voice command button? I mean lets say my phone's in my drawer and i have the BT800, do i have to pull out the phone to be able to use the voice dial?
Click to expand...
Click to collapse
Maybe I misunderstand what you're asking.
You posted the registry change to make this work higher up the page.
Pressing the answer button on the headset does fire up Voice Command but only if the display is open or in portrait mode. If it's closed in your pocket protecting the screen then it won't work
I've never installed voice command, i was talking about the built in voice dial application. If the QTEK is in my pocket, and i want to call someone, which button on the headset/BT800 do i press to activate voice dial? And is it push or push and hold? Do i ghet any kind of audible warning telling me i can start speaking the voice tag?
I hope this time i am a bit clearer, sorry for the previous confusing post.
Jorgee said:
I've never installed voice command, i was talking about the built in voice dial application. If the QTEK is in my pocket, and i want to call someone, which button on the headset/BT800 do i press to activate voice dial? And is it push or push and hold? Do i ghet any kind of audible warning telling me i can start speaking the voice tag?
I hope this time i am a bit clearer, sorry for the previous confusing post.
Click to expand...
Click to collapse
On the BT800:
- To activate voice dialling (whether using MS Voice Command or the 'standard' voice dialling app) using a BT800 headset, press briefly the button nearest the headset microphone.
- To redial from the headset the last number dialled, press and HOLD the button nearest the headset microphone.
This works for me whatever situation the Exec is in: open, closed, portrait, landscape. I'm using the default voice-dialling software, not the MS one. Hope this helps.
Thanks SiliconS,
That was the answer i was looking for, sorry i had to bother you guys instead of reading the manual as my manual is in Spanish and i am only a beginner-intermediate level reader.
Again THANKS!!!! Very appreciated
Are any of you folks running WM2003SE? See, I was able to make that registry change and do a soft reset and have Voice Command working through the BT headset on my old machine, but it was running WM2003 (not the second edition version). From what I have read, SE doesn't seem to like that registry change, as when you make it, all that will happen is the connection opens when you tap the button on the HS, but the ability to use VC is not there.
I know there must be some way to do this. Any opinions or suggestions would be fab!
Thanks much!
I have a dutch ROM. I cannot find how to record voice dialing commands, moreover, the manual does not mention anyting about it.
What's up??
Voice dialling
There is no voice dialling option on the UK spec version either, I've tried MS Voice Command v1.6 and that doesnt work at all either, anyone got any ideas?
It works. Voice Command gets to the one hardware button assigned that's configurable. Just hold the Call button until u hear a beep.
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.
Another problem is that I use it on my bikehelmet when driving. But on the TP2 you need to hold the call button 3 secs (using Voice Command). That turns my bluetooth communication system off. xD
On my previous phone Xperia X1 I could assign a button without needing to hold it for 3 seconds. That worked for my bikesystem.
Google voice2go
Cyberon Voice speed dial is the best for the job but didnt try it yet. Dunno compatible with broadcom/widcomm stack if using btooth hfree. anybody tried it ?
I try Cyberon Voice speed dial, it seem to work well on mic of phone . but it don't work by BT activate, I think BT stack not support. Any one can solve this?
tornado said:
I try Cyberon Voice speed dial, it seem to work well on mic of phone . but it don't work by BT activate, I think BT stack not support. Any one can solve this?
Click to expand...
Click to collapse
Can you post a download link for this software? Thanks
Pimmr said:
Can you post a download link for this software? Thanks
Click to expand...
Click to collapse
see link in http://forum.xda-developers.com/showthread.php?t=523114
MS Voice Command works gr8 at least when i talk to my phone english
you have to buy the voice command software...
terryd1980 said:
There is no voice dialling option on the UK spec version either, I've tried MS Voice Command v1.6 and that doesnt work at all either, anyone got any ideas?
Click to expand...
Click to collapse
you have to buy the voice command software from Microsoft, its about $39.00. None of the foreign phones came with bluetooth voice command software...
Yes MS voice command works like a charm on TP2
Not through Bluetooth it doesnt, thats the main point of voice dialing, I cant fiddle with my phone whilst driving as thats illegal, voice dialing through bluetooth was a breeze with Voice Command v1.6 on the old Kaiser, I need to find out how to get that functionality again.
The Telus version of the Touch Pro2 comes with Voice Command 1.6.21052 in ROM
terryd1980 said:
Not through Bluetooth it doesnt, thats the main point of voice dialing, I cant fiddle with my phone whilst driving as thats illegal, voice dialing through bluetooth was a breeze with Voice Command v1.6 on the old Kaiser, I need to find out how to get that functionality again.
Click to expand...
Click to collapse
after reading your post sent a question to HTC...cut a long story short they tested MVC on a TP2 and through the BT headset succesfully activated a command... when i first contacted they sent the following cab and suggested i install ... so this may help
CVC-PPC-WWE-711091-hTCPPC (Aus Voice Commander).CAB
did not buy because of this post but according to HTC the profile does work on TP2 so back on final list after my 1st choice the B7610 is pushed back to Oct launch
Due to speaking to HTC support who said they had voice over BT headset working on TP2 brought one and low and behold it does not work ... not happy
Nice to know.
I googled CVC-PPC-WWE-711091-hTCPPC (Aus Voice Commander).CAB got redirected to the HTC site.
http://www.htc.com/au/SupportDownload.aspx?p_id=71&cat=3&dl_id=277
Guess what. Not available for my TP2.
ChriX84 said:
Nice to know.
I googled CVC-PPC-WWE-711091-hTCPPC (Aus Voice Commander).CAB got redirected to the HTC site.
http://www.htc.com/au/SupportDownload.aspx?p_id=71&cat=3&dl_id=277
Guess what. Not available for my TP2.
Click to expand...
Click to collapse
So that's it, there is no voice dialing via bluetooth?
I've got the same issue with this phone, I could not activate voice dialer to listen me by pressing button on handsfree.
Is there anyone who can fix it????
hecksk said:
So that's it, there is no voice dialing via bluetooth?
I've got the same issue with this phone, I could not activate voice dialer to listen me by pressing button on handsfree.
Is there anyone who can fix it????
Click to expand...
Click to collapse
I emailed in detail about this problem. Mentioning that Voice Command only works on the phone itself by holding the call button for 3 secs. When using the bt handsfree set the handsfree set turns off when holding the button for 3 secs on it. While it works perfectly on my old Xperia X1 (wich is made by HTC too). With 3 different bt sets. No holding buttons for 3 sec. But only by shortly pressing the button.
Hopefully they answer with good news.
guys, I have an idea: what if we use AEB button plus to map voice command to one of the vol key-long press or double press for example, and then we see if the BT headset is capable of invoking it using its own volume keys? dunno if it's clear enough...
you might try it, so no long press on power button of the headset or so...
the other problem: even if my strange idea would work, I dunno if then the TP2 / voice command would listen to my commands through the BT headset.. but it might be worth a try
this absence of voice dialing and all this problems are driving me mad
cheers!
Can someone confirm if MS Voice (UK) works on the TP2?
When I installed this on my Diamond, it f***ed up the phone and required a hard reset .... twice! Once I thought it was my fault, but I did it again to make sure, and no it was the phone!
It worked great on my previous phone, but I've just got this one the way I like it, and would not like to have to reset everything
I have the TMoUS TP2 that came with MSVC preinstalled and it works perfectly with my Motorola S9 headset via BT.
Maybe try to get the version in the TMo ROM?
S
Greetings!
I have my Desire running MIui GB and it is fantastic.
I prefer using a bluetooth headset rather than talking to the phone directly.
The problem comes when the headset is inside a pocket ,and its buttons are pressed.
On a single button tap i had voice dial popping on the screen.
There were false matches by the voice dialing app and random calls were made.
This was easily disabled, simply by deleting VoiceDialer.apk from the ROM.
The other problem that i haven't found a solution yet, is when the button of the headset is pressed twice.
When that happens, the phone redials the last number, bypassing any lock screen. It is happening quite often actually.
Anyone knows how can i disable that?
Bluetooth headsets are suppose to go on your head, not in your pocket.... seriously.
Sent from RCMixS
Does your headset have key lock? Or u could buy an extra pocket for the headset.
Meaple said:
Bluetooth headsets are suppose to go on your head, not in your pocket.... seriously.
Sent from RCMixS
Click to expand...
Click to collapse
Meaple in my places they say that " If you don't have something to say, don't speak". Seriously...
mrvanity said:
Greetings!
The other problem that i haven't found a solution yet, is when the button of the headset is pressed twice.
When that happens, the phone redials the last number, bypassing any lock screen. It is happening quite often actually.
Anyone knows how can i disable that?
Click to expand...
Click to collapse
I found a workaround by chance just now. After I installed dialer for JAJAH service that I use I got a dialog asking what program to use after clicking BT button.
As long as i don't select USE BY DEFAULT it stops at that dialog and doesn't dial.
Please all, lets keep it on topic and with respect.
Thanks for your cooperation.
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.