Xperia X1 with windows mobile voice command 1.6 - XPERIA X1 General

http://www.youtube.com/watch?v=uLAbwT521Fs
Mighty cool

old news!!!

If you find a way to make the VC1.6 incoming calls announcement work on Xperia - that would be big news.
Everything else is working fine. On my old TyTN II those announcements worked too.

Quit using VC since it eats too much battery and screws with Bluetooth headset, i.e. it drops the connection after you've given it a command.

Related

voice dial on XDA II

Can someone please help. I have a new XDA II purchased a couple of weeks ago. I want to add voice dial so that I can record a voice tag to a specific contact, press a button on my bluetooth headset and the XDA II phone will dial that person for me.
Can some kind person please guide me exactly how to go about setting this up?
JSS
You can't record voice tag unfortunatelly... Microsoft sells Microsoft Voice command for
pocket pc for 30$.. you don't need to train it or record voice tag.. it just recognize what
you say. it isn't bad
you can grab it from www.suprnova.com in the App/pocket pc section (you will need a bittorrent client, ABC http://pingpong-abc.sourceforge.net).
You can use Neuvoice: http://www.neuvoice.com/xdasoftware.php
Allows you to record your own commands. I had problems with some English programs to recognize Dutch names in my contacts.
Neuvoice has to be trained, and this takes some time, but works perfect with foreign languages.
i use vito voice dialer
works great you record your voice tags then if you have button plus installed i have mine lined to the contacts button if i hold it down it will say please say name so you say the voicetag and itll begin to dial works very well
I tried MS voicecommand, and i was not impressed. The thing about "not training" is that it will recognise only the obvious. Also, it was very bad, to pathetic, in recognising things with the earphones on. Add to that noise when driving, it was impossible.
I found the fonix voicedial was very good. I downloaded a trial (gave me a few eeeks to use it, now theres a sensible trial period!), and it was very good.
I havent used vito, maybe give it a go.
fonix is very good fun to play with but it likes to call my dad most of the time lol im like mum....
dial dad
does your head in lol
Vito is the best one ive tried
but fonix is very fun to play with lol
I am french and i need to 'train tag'.
I use neu voice navigator.
For 9,99$, the voice recognition works very well, indoor, outdoor with wind and driving in the car.
Voice dial for XDA II
Thanks to all of you so far. I went to the Vito site and read that it does not work for XDA II.
""IMPORTANT! Doesn't work on MDAII/XDAII
VITO VoiceDialer PE is not currently supported by XDAII/MDAII. When recording a voice tag it brings up an error "Cannot process this file" Our development team is working on the solution. We apologize for the inconvenience. ""
Hopefully this can be fixed soon. I will try some other sites
JSS
I've tried Fonix and MS Voice Command on XDAII and in my view MS Voice Command is the best. Contrary to one of the posts above I've found it very accurate especially after learning how to speak to it after the first couple of days. It works well with the wired earpiece but will not work with a bluetooth headset as it takes its input only from the microphone. As such it is a viable hands free solution and you dont need to train it so if you add a new contact then it is automatically recognised. Beware that the current US version doesnt support dialling of UK phone numbers ie you cannot say 'dial 0113 205 3345' as it will only accept 7 and 10 digit numbers that do not begin with a zero.
I tried MS Voice Command and I must concur with others opinions. Because you cannot train it to learn your voice, it means that you must learn to speak the way it wants you to speak. Fair enough, but the 24-hour trial period is too short. After 24 hours, I could not get it to perform to my satisfaction. Perhaps with a longer trial period I might have learned how to use it.
That is why I am not buying it.
I've tried MS Voice command, and found that unless you want to speak with an American accent then don't bother.
I've also just tried Neuvoice, which works with tags that you assign, and that seems to work extremely well. Now if only one of them could work with a Bluetooth headset! But I guess that's a the fault of the XDA's bluetooth implementation, rather than any of the software.
I purchased MS Voice command (use on my XD2) and as everyone has said it is no good unless you use an american accent...only problem is that I keep talking like an American now :roll: LOL
Thanks - Sunny.
""I've also just tried Neuvoice, which works with tags that you assign, and that seems to work extremely well. Now if only one of them could work with a Bluetooth headset! But I guess that's a the fault of the XDA's bluetooth implementation, rather than any of the software.""
Thanks again. Of course, if it does not work with a bluetooth headset, there really is not much point having it until it does, because the whole idea is to make voice dial calls that are completely 'hands fee'.
I spoke with O2 Mobile Internet support team who tell me that the software will soon have an update (bugfix) which will apparently fix this problem and allow the XDA II to work for voice dial. Does anyone know what this is, when is it coming and how will we be able to get it and put it onto our XDA???
JSS
XDA II update
latest information from O2 is quoting Spring 2004.................
.....................so that'll be 2005 then!
ian
I suppose we will have to rely on the brains of the wonderful people on this forum who will surely come up with a way around the problems.
There must be some way through it. All ideas are welcome
JSS
Bougth a second hand P800 this week to compare with the XDA II.
I must say that the P800 is much more advanced on the phone point. It may be not as performant, but the thing works quite nicely. Voice control works perfect, also with BT headset.
And controlling and operating the phone is much easier thanks to the jog dial. I also like the better implemantation of the phone settings and options. Don't understand why this isn't implemented on more devices.
Think MS still has a long way to go with Pocket PC Phone Edition to reach at least the same phone functionality...
@ Jos
do you know why that is?
its because the p800 is a symbian phone with PDA features
the XDA is a PDA with mobile features
theres the difference
and p800 camera is ****e lol
Hi all!
I Just changed from a P800, and fully agree with gazzaman2k and Jos, P800 is a "so-so good" phone, but a very POOR PDA.
XDAII is a fully functional PDA, but the phone parts leaves so much to be desired......
Any way, I still would be using my P800, should I have been able to fix the SYNC problem.... A phone PDA UNABLE to sync with with your PC is a useless combo. Not to mention the full distress recoveries I had to do with my Outlook contact and agenda files.....
I ended up recovering my old T68 phone, (I need it for the BT carkit) I passed my Cassiopeia EM505 to a friend, my wife got my P800 (unable to sell it on e-bay) and I'm so-so satisfied with my XDA.
Until:
1.- it gets the handsfree BT issue solved (car kit usage)
2.- The Voice command functions are fully implemented (BT headset too)
3.- The phone functions are VERY MUCH IMPROVED (one hand use)
I would NOT consider the XDAII a "PHONE-PDA", but a "PDA-phone". (Capitals being removed intentionally)
BTW, most of the "Voice/dial command" programs I tried are useless and/or unreliable.
but also :x
Indeed, I agree the XDA II is a PDA-PHONE and the P800 a PHONE-PDA.
Would be nice to see an OS that would run on the fast hardware of the XDA II with all the plusses of Pocket PC and Symbian...
And the P800 is for my girlfriend. She needed a new phone and I could get this one for a fair price. Plus it gives me the chance to play around with both en see the pros and cons of both.
For performance and Outlook sync, I prefer the XDA II, but for phone funcionality I prefer the P800...
Voice diaing continued...
The XDA II is a quality PDA with phone functions. Since, I understand, other PDA's (even those without built in phones) are able to have voice dial functions for add-on phones, it seems to me that the XDA II could easily also have these functions. I think that it would just mean getting the right software. How and where from I would like to know?
It may be possible to improve the phone functions, but the single one thing that would improve the XDA II for me is the addition of voice dialing via bluetooth - so that you can record a tag to a contact, press a button on the earpiece, say the contact name and then the number is dialed. That handsfree capability would be a very good start - and let's face it, with driving restrictions etc, these days, it really is essential if the XDA II is ever going to be of any value as a mobile phone.
What I need to know for certain is:-
1.Is there a software that will allow me to have this function.
JSS

Microsoft Voice Command 1.6 - ISSUES!

I just got the Microsoft Voice Command 1.6 (refer to as VC from here on) this morning and so far it has been quite disappointing.
I am using it on a Cingular 8525 with a Sony Ericsson HBH-GV435 headset (both are BT 2.0).
Right after the installation I noticed that the talk button on the headset did not trigger the VC so I did a power cycling.
After the power cycling the button will now trigger the VC as if I pushed the VC button on the phone but the problem is that it is not picking up my voice command via the headset but it is still listening from the phone's mic.
Any thoughts on this?
hjkl;' why no delete?
skygear said:
did you try to go under your d\settingd to chsnge the buttons? i think you have to reg edit the files for ear pice mic
Click to expand...
Click to collapse
I didn't know that.....I'm going to try and search for it. Can you maybe post a linky for the info on how to do that?
thx!
Version 1.6 at present time DOES NOT WORK properly with the TyTN. You should go back to V1.5 and wait for a patch...
goestoeleven said:
Version 1.6 at present time DOES NOT WORK properly with the TyTN. You should go back to V1.5 and wait for a patch...
Click to expand...
Click to collapse
I see. Thanks for the info. Hope the patch will be available soon!
What is the probelm with the ver 1.6 and the TyTn? Is it just the TyTN rom or does it not function with the JasJam or the 8525 either?
Dp you guys know this by experience or is it posted somewhere?
PocketPCThoughts list the 8525 as a "compatible device".
The problem will affect all Hermes devices, and it will probably require a patch / a new dll and/or a registry hack to make things work properly. It should work, but it doesn't, and this goes to show you what a poor job of testing was done before product release.
If the single biggest additional feature/function (ie, bluetooth support) doesn't work properly, why was it shipped?
goestoeleven said:
The problem will affect all Hermes devices, and it will probably require a patch / a new dll and/or a registry hack to make things work properly. It should work, but it doesn't, and this goes to show you what a poor job of testing was done before product release.
If the single biggest additional feature/function (ie, bluetooth support) doesn't work properly, why was it shipped?
Click to expand...
Click to collapse
Come on folks... This is MS we are talking about...
If it had been a software package with a little penguin or a devil on it we would be just fine
mrderby said:
Come on folks... This is MS we are talking about...
If it had been a software package with a little penguin or a devil on it we would be just fine
Click to expand...
Click to collapse
Or maybe we should start to look at HTC... Their implementation of the whole bluetooth "feature" is crap too... AD2P anybody? well let's hack the crap out of the register, and than try to be happy with songs that hickup every 30 secs or so... neah great!
First: Hermes generally does not work with BT2.0, I guess, especially my MDAvario2 does not...
I'm using a BT Headset HBH608, which was perfectly working with every phone I've ever tried...
Second: VC1.6 could not be installed on Vario2' and Hermes Devices at all, getting an error message...
VC1.5 (engl.) works, not perfect, but it usually works...
MickKnatterton said:
First: Hermes generally does not work with BT2.0, I guess, especially my MDAvario2 does not...
I'm using a BT Headset HBH608, which was perfectly working with every phone I've ever tried...
Second: VC1.6 could not be installed on Vario2' and Hermes Devices at all, getting an error message...
VC1.5 (engl.) works, not perfect, but it usually works...
Click to expand...
Click to collapse
What do you mean it cant be installed. I have it installed on a TyTn and it works perfectly. I am not using a BT headset, so cant comment on that.
I've got v1.6 on an 8525 and it seems to working fine.
what exactly are the problems others are having with Hermes devices?
@DigitalFX: Hermes does support Bluetooth 2.0, but not Enhanced Data Rate.
@JCrompton: MSVC 1.6 does not route sounds/commands properly through a Bluetooth headset on the Hermes. You may be able to initiate a call with your headset button, but you'll be using the mic/speaker on the Hermes to complete it. Also, sounds/announcements are not working as advertised. HTC and M$ are working on a patch.
VC 1.6 works fine on my MDA with Motorola BT headset.
Mark (NL) said:
Or maybe we should start to look at HTC... Their implementation of the whole bluetooth "feature" is crap too... AD2P anybody? well let's hack the crap out of the register, and than try to be happy with songs that hickup every 30 secs or so... neah great!
Click to expand...
Click to collapse
Seriously, why dind't any OEM use the Widcomm stack instead of the crappy MS one ?!
If only there was a way to hack the Widcomm stack and replace the MS one like they did with the Dell axims..
Adi
goestoeleven said:
@DigitalFX: Hermes does support Bluetooth 2.0, but not Enhanced Data Rate.
@JCrompton: MSVC 1.6 does not route sounds/commands properly through a Bluetooth headset on the Hermes. You may be able to initiate a call with your headset button, but you'll be using the mic/speaker on the Hermes to complete it. Also, sounds/announcements are not working as advertised. HTC and M$ are working on a patch.
Click to expand...
Click to collapse
Has anyone tried this... (look for the cab)
http://forum.xda-developers.com/showthread.php?t=283412&page=5
My 8525 works fine with 1.6 and my SE662 BT headset. Calls can be activated over BT using headset button, and audio routes to my headset throughout my call.
URPREY said:
My 8525 works fine with 1.6 and my SE662 BT headset. Calls can be activated over BT using headset button, and audio routes to my headset throughout my call.
Click to expand...
Click to collapse
Wow! Have you done any registry hacks? I'd love to see what your Voice Command keys look like....
TIA,
Richard
I have an 8525 also, and 1.6 works as MS says it does.
The headset button activates voice command, the Beep occurs on the 8525, and the mike on the 8525 listens for input. If I say, Dial ... or Call... then the call works fine on the BT headset like expected.
I know a patch is in the works to fix this issue, and when they do, 1.6 is superior to 1.5 for voice interpretation.
However, for now, I have 1.5 working perfectly fine. All features work, and all I had to do was enter/change 2 registry keys (only 1 was necessary)
xcsdm said:
I have an 8525 also, and 1.6 works as MS says it does.
The headset button activates voice command, the Beep occurs on the 8525, and the mike on the 8525 listens for input. If I say, Dial ... or Call... then the call works fine on the BT headset like expected.
Click to expand...
Click to collapse
So how loud do you have to shout for the mike on the 8525 to hear you if the phone is in the next room, or in your purse or you're driving? It might be the way MS intended it to work, but I doubt it.
[RANT]
I can't believe that MS wouldn't have caught this problem during beta testing. Speaks volumes (pun intended) for the current state of software development and testing at MS. Anyone know if MS Reader works with WM5 yet? How about full multi-user support for ActiveSync? Win XP has been around for years now with this funtionality. And while I am on my rant, how about SP3 for Win XP? Currently we would have to download and install over 70 (!) critical patches to SP2 just to get our computers to the dynamic state they are at today. Come on MS, enough is enough. Get your s#!* together!!
[/RANT]
John

Voice Command 1.6 UK version BT initiation

Nice to see this new Sable forum and hope it grows with time.
Has anyone achieved VC 1.6 initiation from their Bluetooth earpiece?
I can't. Running WM5 5.1.195 on HP 6915, and guess that is the problem.
No ROM update as far as I'm aware, but please correct me!
Am I flogging a dead horse trying to find a fix?
Alternatively, has anyone got VC 1.5 running properly with the reg hacks? It worked just fine on my old Universal.
$9.99 to downgrade....not such a great deal in my book! Could someone look to see if I have "idiot" written on my forehead?
I have a hw6955 and version voice command 1.6 and I've tried the hack (which starts vc1.6 when the headset button is pushed) that's been used on other wm5 devices and it doesn't work.
Voice command 1.6 is great and I still use it, I've assigned the side button to start vc 1.6.
Trouble is, the device turns off after a few minutes anyways and it seems to lose connection to my BT headset. You have to turn the device on and then press the side button to start vc. If a call comes in, I have to press the button on the headset to reconnect to the device anyways. Not sure if this is normal, because hardly anyone has sables.
Could pressing the button on a headset, turn the device back on and start voice command? That would be awesome. Anyways, the 6955 is a great device, just needs a few more people hacking for it.
1500 and 3000ma batteries for out for it, the 300 gives 4 days of use, which is amazing. The 1500 provides 25% more power then the OEM battery and is the same form factor (and weight).
I don't have the cut-off problem at all.
In the hands-free setting (Bluetooth Manager/Handsfree Connection/HandsFree Settings) I've ticked the box for Standard Audio as well as Telephone Calls - perhaps that makes a difference. Mine (Moto) stays on and I also get all my TomTom instructions through it. Voice recognition through the BT headset is pretty poor though.
Where did you get your batts? I've got the 2500 from eBay - larger size with back cover that is a different colour to the PDA and not a terribly good fit. £15 from Hong Kong - but I can live with that! Found a nice case from US that takes the larger battery.
I have a logitech one, I'm not sure if it's all the great. I may try a moto one. If I turn on both telephone and all sounds in the bluetooth menu, then I find that there is a lot of background static on the headset. People have mentioned that it sounds like I am standing by a jet taking off! Anyways, I think it's the implementation of bluetooth on the hp models and not the headset, but until I try another one, then I don't know.
Have you read the thread here about activating voice dial with the headset button? It's really good.
any more information on this? BTW, all 6940/45/50/55 ipaq users should be using microsoft voice command 1.6. It works amazing for voice dialing. No training, it just works.
If someone could get the bluetooth headset button to initiate the voice command software on the ipaq, that would be ideal.
A lot of smartphone, pda users are attempting to get voice dialing working with bluetooth headsets. There are various posts on here about it.
Obviously, there isn't a huge following for the 6900 series... That is not good.
Battery life would be the most obvious reason!
I have MS Voice Command 1.6 UK Version running fine on my PDA (fair enoughitsan Orbit / Artemis / P3300) but everythingworks fine, announcing calls /messages / BT headset button / voice dailling the lot.

Problem with MS VC 1.6

Hi All
I just installed MS Voice Command 1.6 (US) and so far its been working almost perfect. I say almost perfect because somehow when a call comes in, it announces the name of the caller through the phone speakers even though I specifically tell it to announce only through BT handsfree set. I thought that maybe my headset did not support it but the weird thing is that it would automatically read incoming messages through the BT headset. Is there any tweak that I need to do so that I can hear who is calling through the BT headset?
I am currently using an AKU2.X ROM (Dopod's latest) with a Plantronics 640E BT headset. Any help rendered is much appreciated.
I can at least tell you that a Crossbow ROM won't help...
I still get this irritating issue
Sounds like a MS Bluetooth Stack issue
Funnily this is the symptoms described on Microsoft page :
http://www.microsoft.com/windowsmobile/voicecommand/default.mspx
But for HTC Hermes & Palm Treos
Thanks to a forum member I found my mistake !!
Check this post : http://forum.xda-developers.com/showpost.php?p=1112405&postcount=369
sebbes said:
Funnily this is the symptoms described on Microsoft page :
http://www.microsoft.com/windowsmobile/voicecommand/default.mspx
But for HTC Hermes & Palm Treos
Click to expand...
Click to collapse
I guess my problem is listed as "Older WM5 Devices" where the notifications for calls would be routed to the speakers. No fix there I guess.
With the PDAviet ROM it works ok !
Routed to the headset, and even the incoming calls get notified in the same manner
sebbes said:
With the PDAviet ROM it works ok !
Routed to the headset, and even the incoming calls get notified in the same manner
Click to expand...
Click to collapse
Could you tell me more about this PDAviet that you are talking about?
it's a crossbow ROM (beta of course)
Thanks for the headsup. Unfortunately I need the functions of a proper phone and thus unable to use the ROM. Thanks for the heads up.
I see, in fact this unofficial ROM is pretty ok (just a few times when you'll have to reset before it boot up successfully)
Else the phone part is really nice, with a great smartdial (like you have on smartphones, qtek8310 etc) but you're right, it's for people that are not scared by few minor problems

Getting the Dell BH200 BT to work w/ the Fuze

I just recently acquired a stereo bluetooth headset from dell model number BH200 and so far the stereo music quality is superb, but the moment a call comes in or I pick up a call it immediately disconnects itself. My question would be if any of you guys have any experience with this issue. the Stereo bluetooth and handsfree profile are both set to active. Any suggestions or hints?
I'm going to go on a limb here and assume that you guys haven't had access to the aforementioned bluetooth and i'm short out of luck here... right?
p.s. SAY IT AINT SO!!!!
Hi, I also have the same headphones and the same problem - only on HTC Universal flashed with WM6.
I search a bit on Google and it seems that the problem is with MS Bluetooth stack - it was working correctly for WM5 (but no A2DP), now in WM6 A2DP works, but handsfree does not.
Right now I'm testing alternative BT stacks - started with UniBT (it's Broadcomm stack modified for Universal) - now A2DP works flawlessly (before that, it didn't), but handsfree/headphones mode does not. At least trying to receive the phone call doesn't turn the headphones off.
i tested my fuze with a jabra bt2010 and it works fine. I'd prefer to not carry 2 bluetooth devices so i'm trying to find a way for it to work. I've been suggested to use a widcomm bluetooth stack as well but i dont know how to change my stack. If anyone here does know how to do it, please do enlighten us.
It's been nearly a month so I'm going to bump this thread in hopes of someone might possibly have some insight into this.
Push/bump.
I got the S9 now, it works for both functions but craps out completely when i'm outside, really bad signal reception as well as "muffled sounds" according to my audiophilic and audiophobic friends.
I think it has to be something to do with the actual firmware inside the bh200 that is wreaking some unknown havoc.
Dell bluetooth headset BH200 not working with Sony Xperia X1i
I have a Dell Bluetooth headset model BH200 and in A2DP mode, works flawless but the moment it is used with handsfree mode for call, the connection is broken and the headset switches off itself. This headset works very well with other non WM6.1 devices. Any clues with anony one what should be done in this case, some people have suggested JETware Hands-free Extension , any one tried on this.
I actually gave up on the bh200 and got myself a jabra bt8010. it works like a charm and the sound is just as good as the bh200
Indeed... i used to have a WM device (Mio A501) and I had the WM6.1 Pro..
I bought this BT at that time and it didn't work on WM6.1 (it even didn't asked me the PIN to pair it) but, when I tried with WM5.0, everything worked great, great sound on call's music, etc.. now I have a Sapphire and I'm not able to make calls on it (music works), but since I'm not driving and people used to look like "what a crazy guy speaking in English alone, no cables, it must be a mp3 or something.. hmmm" when I was on a call, it doesn't make a huge difference
i have yet to try this on wm6.5 but I highly doubt there would be a change..i'll give an update when I do charge up the bh200
i charged the bh200 up completely and tested it out.. it was a failure.. looks like 6.5 did not do anything to help...
Maybe windows mobile 7 will work.......... maybe.
You can use BH200 on call by this way only(I tested)
1. Turn on BT
2. Accepted call(However just Turn on your BT after accept call is OK)
3. Turn on BH200
4. Pair ur PDA w/ BH200
5. Done
IS this thead still active? I have a solution
Guys..
Use Reg edit and make the following modifications in your WM device by creating a new DWORD value 0 with the parameter UseESCO. Check out the path
HKLM\SOFTWARE\Microsoft\Bluetooth\AudioGateway\UseESCO = DWORD:0 (Dont use space between UseESCO)
Then restart the phone and delete any previous BT devices on your phone, start up the paining process and get it to work.
worked flawlessly on my Dell BH200
Thanks,
Raj.
seriously????
the fix is in one freaking registry tweak????
I'll have to wait 2 months before i can test this since i left the damn thing to rot in the US while i'm here in thailand..-_-
mputtr said:
seriously????
the fix is in one freaking registry tweak????
I'll have to wait 2 months before i can test this since i left the damn thing to rot in the US while i'm here in thailand..-_-
Click to expand...
Click to collapse
Of course Bro. I waited for 6 months myself too.. and finally found it in a microsoft forum.. well at last got it to work and my 200 sounds better than ever with its new functionality..
All the best
Raj
sweet! thanks a bunch man!
prudviraj said:
Of course Bro. I waited for 6 months myself too.. and finally found it in a microsoft forum.. well at last got it to work and my 200 sounds better than ever with its new functionality..
All the best
Raj
Click to expand...
Click to collapse
Heya, Finally got back ot he US and tested out the BH200 with the fix you mentioned. it works!!!!!
although, i'm wondering if you're having problems with the bh200 not wanting to connect to the phone automatically.
Need help for the same problem in android
I am having similar issues on my Nexus one. Dell BH200 works for music playback but stops functioning when a call is made or received. Even the connection between the phone & BH200 gets lost.
I would be really glad to get some help on this.

Categories

Resources