Hi people,
I just bought myself a Prophet so now I'm putting it through the paces configuring it the way I want it.
Everything is dandy on the new ROM I flashed (Prophet ROM CE OS 5.2.20721) but I am having trouble getting MS Voice Command to activate via Bluetooth.
I did a search in the forums but could not find anything on it, my question is does anyone here use BT with MSVC and can they activate MSVC with their bluetooth? If so, what ROM are you using, and what Radio Version? I'd like to get this to work as it is the most important app for me in a phone.
Thanks
Try read this topic:
http://forum.xda-developers.com/archive/index.php/t-256855.html
Thanks, that trick never worked for me over 5 different devices, but anyway the good news is, for some reason, it suddenly worked.
I currently have Vincent's Speedy Diamond ROM (Build 20273.1.3.3) with radio 2.69. I installed Voice Command 1.6.19209, and it did not work. Then I uninstalled it, reinstalled VC 1.6.19213, still no dice, then I uninstalled that then reinstalled VC 1.6.19209, then it *still* didn't work.
Then I did a soft reset and all of a sudden it works. =_= The world is a mysterious place.
did you check this?
This cab is good for me, but to make it work with the button on your bluetooth headset
you also need to do the following changes in the registry:
HKLM\SOFTWARE\Microsoft\Bluetooth\AudioGateway\BTA GExtModule\"Windows\OEMAGW.dll"
My headset only make the "input speech name" after this change.
regards
Thanks. I prefer MS Voice Command but I'll use that if ever the miracle that happened screws up later. For now it somehow worked so I'll just hope it stays fixed!
Related
1. A2DP icon missing
I want to re-direct skype audio to my bluetooth earphone. How can I do that?
2. I can not login MSN/windows alive though skype can login without any problem via WIFI. Seems MSN try to get online through different connection setting? how/where can I define the connection setting for MSN?
3. Phone module die without any sign. All incoming call is diverted to voice mail automatically until soft reset. As if the phone is switched off.
(I am not sure whether this is WM6 related)
this means you might miss important call without any sign!
Does anybody have same experience?
1) I dont think that was ever a default thing? Did you install something and forget? have a cooked rom? There are A2DP solutions in this forum, "Use the Search luke."
2) No, its shagged. I installed the windowslive50.cab file I had on universal, it works now.
3) No idea, mine works fine. Hard reset? Check your sim?
I can get online with my WLM but it does sometimes take a resync of the whole account to do it.
Skype did say (unless changed recently) that they were still working on transferring calls to bt headsets. Which means, currently, that it does not work through anything other than headphones and the mic on the phone.
Comm Manager
Hello,
It is possible to change the green color from the Comm Manager ?
Thanks
French Keyboard
I have upgraded my french Advantage and all is OK apart for keyboard layout. On my old Universal (also french keyboard) I had changes the registry for hklm/software/oem/qwerty layout to 1040C (hex) and it had worked.
On the advantage this does not seem to change anything, any ideas?
Also has anyone got integrated VoIP working? I have used a CAB file from Universal to activate it and SIP Config Tool to do the set up but it does not allow me to select VoIP from today menu.
Anyone got this set up and working? Integrated VoIP is the reason I upgraded to WM6!
Messenger Etc....
Live Messenger stops working correctly after a soft reset. Initially it works fine. Contacts show as offline, although they are still able to contact me and vice-versa.
As far as I can ascertain push email still functions correctly.
I cannot confirm whether this is related to MS's side (rather than the program) as I haven't had chance to check if anyone else experiences the same problems.
Have tried installing the separate CAB file but I am subsequently told that I do not have the necessary permissions (or something like that).
This comes from tests on a T-Mobile branded Ameo (not the brand new one I'm selling, if anyone decides to cross-check!)
I haven't come across any other problems. Seems a bit less laggy than the original T-Mobile ROM, loads up web pages slightly faster too it seems.
No other issues as yet.
Ive had no probs at all since installing the messenger cab.
Still using it now.
Do we know what version of WLM is on this new ROM?
I've pulled \windows\wlmmessenger.exe to desktop and looked at the Version tab...10.6.28.2700 is what comes out.
Pyrofer - can you do the same on your cabbed version and let me know what the version number says? Not always an accurate guide but worth a shot. Also the digital signature is 3rd May 07.
Cheers
Ant
EDIT - never mind, just seen ur post in general Athena tab...10.6.0026.1400
I wonder what is different? If anything? I also wonder whether this is actually a final release of the ROM that's just been leaked early, as WLM is a pretty central component to web using Athena owners (myself very much included) and for it not to work after a soft reset...hmm.
Hi royalmail,
I've got exactly the same problem you mention about the phone.
I was unable to answer calls.
So I belive you've use the second file to upgrade to WM6 (HTC001 ... with ipl...).
You have to go back to WM5 WWE using the last ROM posted in the Athena upload folder in the XDA FTP. After flashing your Athena to WM5, Use the first ROM posted (the one with a readme file included).
And voila! No problem at all since I've done it this morning, everything works fine!
Hope this helps!
Hi Thibale,
I flashed with the t-mobile version. the phone dead only once so far, though i am not sure it's caused by WM6. Anyway, thx for sharing your info.
royalmail said:
1. A2DP icon missing
I want to re-direct skype audio to my bluetooth earphone. How can I do that?
2. I can not login MSN/windows alive though skype can login without any problem via WIFI. Seems MSN try to get online through different connection setting? how/where can I define the connection setting for MSN?
3. Phone module die without any sign. All incoming call is diverted to voice mail automatically until soft reset. As if the phone is switched off.
(I am not sure whether this is WM6 related)
this means you might miss important call without any sign!
Does anybody have same experience?
Click to expand...
Click to collapse
See if this helps
http://www.silentservices.de/btIO.html
Also, read through the forum regarding some of your other issues.
Try to disable your GPRS and see if your calls start coming through.
Pyrofer said:
Ive had no probs at all since installing the messenger cab.
Still using it now.
Click to expand...
Click to collapse
Thanks for all the input.
@Pyrofer, could u upload yr WLM5.cab here? thanks in advance.
After flashing the phone to schaps 4.22 hermes rom the voice dial button (button 5) does absolutely nothing. Schaps has written that it is mapped to advanced task manager but this does not start either. Nor can button 5 be mapped to anything else.
Is is a bug or a classic user error?
yes, I have noticed the same problem with my phone too.
MMM, you might need the PPT fix if your using PTT.
If your trying to use Voice dial, Its not in the rom
If you read through the thread where the Rom is located, there are actually two different fixes for it... Both are supposed to do the same, but only one works without any additional side effects... They are the Sleuth's PTTFix cabs... As I said, there are links to two different ones in the thread, I don't feel like looking for them now, but they are both there... the second one doesn't give any errors upon soft reset and works fine...
Happy Hunting...
With this new rom I can now enable conformation when using MS voice command 1.6. Before i would have to disable conformation in order to use bluetooth with MS voice command, this is no longer a problem; can any one else confirm this?
Wow, I so have to check this out.
No lie! ha ha ha it works! saweet!
well, now caller id and messages arent sent through
there is a reg tweak which will let the caller id come through the bt headset,
sorry but not sure where it is.
Notification
I set the notification options to "Announce notifications using bluetooth hands free if available" and it works. When the phone rings I hear the ringing and the announcement through the headset. I did not do any registry changes as I used to do before this ROM. I am using a Jabra 8010.
I'm more excited about the confirmations working on 3.16 than even GPS and EVDO-A. I don't keep my headset in my ear very much, so I haven't even checked to see if notifications work through the headset.
JimSmith94 said:
I'm more excited about the confirmations working on 3.16 than even GPS and EVDO-A. I don't keep my headset in my ear very much, so I haven't even checked to see if notifications work through the headset.
Click to expand...
Click to collapse
I can also confirm that this problem is fixed. I took the plunge with the pre-release ROM and it's been working like a charm. I have not had to modify the registry to get notifications to work, either. I just went to Settings->Voice Command and setup my preferences.
I also have to agree that the Bluetooth fix is more exciting to me than the GPS stuff since I use this feature way more than I use GPS.
where can I get this fix?
HTC TOUCH
VOICE COMMAND 1.6
NO CONFIRMATIONS THOUGH BLUETOOTH
Where can I get this fix?
mtnTOUCH said:
HTC TOUCH
VOICE COMMAND 1.6
NO CONFIRMATIONS THOUGH BLUETOOTH
Where can I get this fix?
Click to expand...
Click to collapse
touch forum? lol. we have a newer radio rom and bt drivers witch fixed the issue, so wait for someone to port them over. Sorry man.
Question: bluetooth definitely seems to be working 100% better (no longer disconnecting randomly, I can shift all sound to it now if I want, etc), but the button on my bluetooth earpiece no longer brings up the voice command prompt. When I run the bluetooth voicecommand proggy thingy it works, but I can't do it from the earpiece.
Am I missing something ridiculous? I've done some searching on the forums, but haven't found anything. ('course, I might just be pathetic and searching)
taxilian said:
Question: bluetooth definitely seems to be working 100% better (no longer disconnecting randomly, I can shift all sound to it now if I want, etc), but the button on my bluetooth earpiece no longer brings up the voice command prompt. When I run the bluetooth voicecommand proggy thingy it works, but I can't do it from the earpiece.
Am I missing something ridiculous? I've done some searching on the forums, but haven't found anything. ('course, I might just be pathetic and searching)
Click to expand...
Click to collapse
Did you assign Voice Command to Button 5? (Start > Settings > Buttons). I have Button 5 set to Voice Command, and Button 5 (Press & Hold) set to Record.
mtnTOUCH said:
HTC TOUCH
VOICE COMMAND 1.6
NO CONFIRMATIONS THOUGH BLUETOOTH
Where can I get this fix?
Click to expand...
Click to collapse
This worked for me on my wizard and Hermes
taxilian said:
Question: bluetooth definitely seems to be working 100% better (no longer disconnecting randomly, I can shift all sound to it now if I want, etc), but the button on my bluetooth earpiece no longer brings up the voice command prompt. When I run the bluetooth voicecommand proggy thingy it works, but I can't do it from the earpiece.
Am I missing something ridiculous? I've done some searching on the forums, but haven't found anything. ('course, I might just be pathetic and searching)
Click to expand...
Click to collapse
i have the same problem. after a hard reset and then installing ONLY voice command, it works PERFECTLY - announcements, confirmations, everything. after a soft reset something gets changed in the registry and it no longer is activated from the headset.
is there a program that can tell you what has been changed in a registry?
its frustrating that is working PERFECTLY and only upon a soft reset does it not work anymore...
ok... still trying to isolate what the problem is.
here are the symptoms. as before, everything works GREAT until i soft reset.
then, rather than the headset triggering the voice command, it opens the dialer app and hangs open. i have to uncheck the object in bluetooth settings, save, then recheck to reset headset.
i am trying some more stuff...
i found a PITA fix. apparently whatever happens after a soft reset messes up the bluetooth files. so i uninstall, soft reset, then reinstall.
sad thing is - i'd rather do this than keep trying to figure out what is causing this conflict...
1.6 Voice Command; announcements not coming over incoming calls
I have a ppc-6800 sprint mogul.
I have WM6 Professional
CE OS 5.2.1238 (Build 17745.0.2.3)
My issue is that when I installed VC 1.6, everything works fine, except I don't get the incoming call or calendar announcements. I have checked the appropriate boxes in the VC options settings to no avail.
I am certainly no xda-developer, and can become easily confused when talking about registry edits and .dll files. If anyone can provide explicit directions on how to fix, I would truly appreciate.
JFA
Sorry. I can't find an answer to this. I have found several possibilities, but none work.
I have the XV6800 with DCD's 3.2.6 ROM installed and Voice Command 1.6 (I purchased it myself)
I can't get the bluetooth button to work with VC. I tried installed Cody's "Fix" for this but afterwards, my phone reboots everytime I go into "Settings" from the main menu.
Has anyone else gotten this to work with DCD's 3.2.6?
Please help!
Thanks in advance!
You need to have these two registry entries for VC to work over bluetooth.
[HKEY_LOCAL_MACHINE\Software\Microsoft\Bluetooth\AudioGateway]
"BTAGExtModule"="vcbthag.dll"
[HKEY_LOCAL_MACHINE\Software\OEM\VoiceCommand]
"Path"="\\Windows\\VoiceCMD.exe"
Also, if you use a wired headset, place a copy of voicecmd.exe and call it sddialer.exe in the \windows\ folder. This will allow you to use your headset's talk button to call voice command.
findthisfunny said:
You need to have these two registry entries for VC to work over bluetooth.
[HKEY_LOCAL_MACHINE\Software\Microsoft\Bluetooth\AudioGateway]
"BTAGExtModule"="vcbthag.dll"
[HKEY_LOCAL_MACHINE\Software\OEM\VoiceCommand]
"Path"="\\Windows\\VoiceCMD.exe"
Also, if you use a wired headset, place a copy of voicecmd.exe and call it sddialer.exe in the \windows\ folder. This will allow you to use your headset's talk button to call voice command.
Click to expand...
Click to collapse
Are there supposed to be 2 "\\" in front of "Windows" as well as 2 "\\" in front of "VoiceCMD.exe"?
The other registry key was already there.
?
It didn't work. Is there something I'm missing?
Sorry, that's all I have. I don't know why it's not working for you. As far as the registry entries go, you only need one '\' when you're entering it in manually.
I have the puchased version of VC as well and once I enter these registry keys and reboot, it works perfectly for me.
Hi all,
In my Renault BT Car Kit (originally designed by Parrot) it seems to be impossible to access my phone's contacts. I have had it working with one of the earliest Tom Codon ROMs by changing a setting in the advanced settings, bet ever after I have not been able to get it working again.
I have searched the forum several times, but it seems that I am not looking good enough.
The problem is not in my car, since I never changed it's ROM, and my wife's phone (Elf) is working great.
My phone is working great otherwise.
Tanks,
TC.
When you paired the phone with the "car" did you answered Yes to the question where you are asked to allow access to the phone contacts?
Thanks! That would be something hard to overlook , but sadly, there is no such question. Neither from the phone, nor fron the 'car'. The 'car' gives <empty> when accessing names. I have tried copying contacts to the SIM, but that also has the same result.
I have tried many (many! also the original from the provider) different ROMS the past year or so, and all of them have the same 'problem'.
When my wife purchased the Elf, the 'car' allowed it immediately, just as her previous phone (some samsung thing). It is just with the Nike that it has trouble with.
Also the Diamond of my collegue that drives the car every now and then, communicates without hassle.
The stupid this is that it has worked with a previous ROM, and I cannot find (in my memory or the internet) how to activate it again. It's more an annoyment than really really a nessesity (is that a proper word ?). I have also been looking into the advanced configuration of both the Elf and the Nike to spot a difference, but nothing seems available.
I am thinking of calling the 'car' "Christine", and just stop trying, but as a technician, I want to have this working, because it has worked before.
thanks,
T.
I assume that your wife's name is not Christine!
Did you try with WM 6.1 and 6.5, including the original ROM? Did you tried to upgrade the carkit firmware? I am using a Parrot CK-3100LCD carkit but I have no problems with my Niki since the first time I was using it.
The pairing process was started from both sides or only from one side?
No, my wife is not Christine... but Stephen King wrote a book once...
The pairing always starts from both ways, I cannot find 'Christine' from any phone without starting the pairing from both sides.
All different WM versions available for Nike have the same problem. (I have had about 30 different ROMs on my phone, just for the fun of it, only 1 has worked properly after changing 'something' in the advanced settings)
I really have no idea what kind of parrot it is, because it has been re-branded by Renault while integrating it into my Clio. I have for that same reason not tried to upgrade the ROM in 'Christine'.
Strange, very strange what's happening. Did you tried some other radio ROMs?
strange... I know...
I have been on the road for a couple of days, have installed a new ROM prior to leaving, but still the same problem occurs: I can call whomever I like, via the phone itself, and I can answer the phone normally by using the the car's controls.
In the Netherlands it is not allowed to use the phone other then via a carkit, so dialing a number is not really an option here.
I have tried several person's ROMs, also radios (although I have not been able to find a link to the recently used 1.71 version, anyone a link?), and all have the same, except for that once...
thanks!
Did you tried with another Nike (from a friend or coworker) to see what's happens? Do you see (on the car screen) the digits or the name of the callers? Did you tried pairing only from one side? Did you contact Renault for a firmware upgrade of the bluetooth carkit?
A coworker has the same problem with the original ROM in a different car (Volkswagen),
I see only <empty> when accessing the name area from the car,
I have tried pairing on different ways, all with the same result
I have not contacted Renault or Parrot , since ny coworker has the same problem AND it has worked (once) before.
It is just a strange, not really big issue, but I would like to have it out of the way.