fonix problems - General Topics

i have installed fonix voice dialer from the o2 upgrades and i cant get it to work.it loads but wont complete.
any known bugs .
cheeers
rob

Related

Thinking of upgrading to TT5 on an XDA2i? Then Think again..

I am close to seeing if my XDA2i and TT5.10 can swim better than it navigate without locking up . . .
I installed the corporate version when hard reset, and performed a clean install of version 5.10 as requested by the tom tom support team.
TT5.10 works like a dream . . .. if you dont get a phone call (locks up) or dont get a text message (locks up) dont want a traffic update (locks up) - in fact it probably works best if you do not switch it on . . .
After 10 updates to my online question, because getting to play a round of golf with the President is easier than speaking with anyone at tomtom, they replied . . .
"Thanks for the feedback. The issues that you mention should have been resolved with the update to version 5.10. I'll contact our technical team about this, and will get back to you." (yeah, right)
Thanks for the feed back? THANKS?? Maybe it should be us XDA2i users thanking TT for wasting our time getting lost because their update is more premature than me sharing a bed with a supermodel.
I contacted O2, because when someone calls me on my trusty XDA2i (locking up TT) the phone line is totally dead when I answer.
O2 said . . .
"The XDA2i has an upgrade due for release very shortly. We haven’t been given a set date yet, but I would suggest checking the website each day for the update - www.my-xda.com
Hopefully their new ROM will sort this issue . . . TomTom clearly not tested TT5 on an allegedly supported device . . .
Incidently when I ask TT to unlock my old TT3 code (because TT3 actually worked and I want to re-install it) they said . . .
"Unfortunately we can't unblock your Product Code for Navigator 3 at the moment, as this was code was blocked when you ordered the Upgrade"
If any one has any solutions, or a sledge hammer, I be very grateful
Hi there, im currently using TT5 with hardly any problems(im using i-mate ROM) but there are a few that may cause it.
Firstly the SD card has caused alot of problems for people, i use a 1gig card and it is the cause of most of my problems.
However i think the root of the many problems the 2i has is ... The ROM.
As O2 say they are releasing a new ROM soon and i can bet this will sort alot of the problems your having right now.
in the mean time you should think about installing the i-mate ROM which has made my XDA2i more stable.
I have an XDA 2i & can use Tom Tom 5 wiithout a problem, bearing in mind it is version 5.0. I haven't experiencd these problems you have mentioned.
My first XDA2i did play up (freezing up at random times!), after a quick call to O2, they replaced the unit & so far I haven't had the same problems. I just put it down to a glitch in the system.
I am however interested in upgrading the ROM as my version is the same as yours & from what I have read on this website, it seems that people find it worthwhile upgrading their ROMs to iron out the glitches. But is it safe to use upgrades meant for other devices?
I'm also using TTN5 without a problem, version 5.0 with the patch I posted here, before applying that patch it would crash fairly regularily, now however it's fine.
I have had problems when using a 1gig card on my XDA2i. It seems that any gsm/gprs activity causes the SD card to disconnect, thus freezing/locking up the phone, especially in TOMTOM. If I switch cards to a 512mb or 256mb the card does not disconnect and everything is fine. I had problems with the phone locking up whilst navigating and a call coming in, whis was with tomtom 3.07. Moving to tomtom5 cured all of this. I'd definately say it's a ROM problem with the XDA2i as my 1gb card will without fail disconnect when I switch on GPRS.
roll on ROM update....
I am running the i-mate 1.11 ROM and I have hardly any problems compared to when I was running the O2 1.10 ROM.
Rarely the phone will lock up when I hang up a call, and sometimes GPRS will fail to reconnect after a call, but in general it is *very* stable compared to 1.10.
WM2005 on the XDA2 has been perfectly stable for me, but alas, I sold it last week, and am now stuck with a more buggy device/os.
I upgraded to the imate 1.11 rom and now my bluetooth head set disconnects when the unit powers off. A call will come in and i have no headset icon. This worked fine under the O2 UK rom
Any ideas ????????? :? :?
yeah i tried the i-mate rom as well and was no good on my xda2i kept freezing the pda after i exited tomtom
i don't think it is the sd cards either that is causeing this as i have been though 3 cards already and there was never any difference allways locked up ..BUT the best i ever got was a clean install then using tomtoom updated traffiffic fine and the whole i did it about 10 times but as soon as it hit the gps cable thats when it all froze on me
I haven't experienced either of those problems with the 1.11 rom, and I use TomTom 5 (well, 5.10 now) and a Jabra BT800 headset all the time.
So many of the issues really are random.

voice command 1.6

hi hope someone can help ive installed the new rom on my xda JASJAR_WWE_20200_20305_11300 ubt voice command does not work for calling out incoming calls and reading tex mes.ive played round with the settigs but still can't get it to work. thanks in advance
voice command
Hi I also had the same problems.
I ended up flashing back to Midgets v1 vanilla to solve the problem.
I like the voice command function its quite a nice feature on crossbow,
I have just flashed upto darkforces 2.10.02wwe radio 1.15 its fantasticly fast
but sadly no VC.
I have tried putting on CyberonVoiceCommand and MSVoiceCommand as
cab's but to no joy they still wont work.
Does anyone have a cab file that works on Darkforces 2.10.02 with 1.15
radio.?? or can point me in the right direction.
Thanks gingerchristopher
voice command .cab
Ok after a bit of hunting around this weekend I found this CAB.
it is 1.6 ms voice command. I have popped it in om uni's sd card and loaded it up to the device and not the sd card. All is working fine it reads texts and transmits to my bluetooth headset ok. hope this is of help.
gingerchristopher
Edit: I can't attatch the cab file. pm me if you would like it. or [email protected]

WM6.1 and MS Voice Command

Did anyone get it to work on wm6.1? i install it and it installs, but when i try to go to settings it will not go any farther. I like to have in say whos calling. Its a feature i can't live without! any help would be appreciated!
wolfskin
I think this is a problem when using the "official" 6.1 base. When I load it, it freezes after the install (like when it tries to load the "Help" file) and I must SR the phone. The next boot will be fine until it seems to start the Voice Command program, at which point will freeze the device. I had to hard reset to recover.
Others have reported Dutty's and other 6.1 releases not based on the "official" ROMs work with Voice Command.
i have it installed, haven't noticed any problems or than it needs to be tweaked to anounce calls. all other features, buttons, menus work.
i cant resist this one
READ THE FORUMS
http://forum.xda-developers.com/showthread.php?t=365118&page=6
1.6.1722 works out of the box for me, even launches from the headset. HOWEVER, it totally doesn't recognize ANYTHING I say! Totally the opposite of my normal experience. Normally I have to install ZaJules BTCommand, enable, reset, disable, reset to get the headset launch to work.
Hmm, I'll have to try another version.
***Update***
after radio update it is working PERFECTLY! Also it does seem to make a big difference which minor version of MSVC you're using - 1.6.17913 is what I have, my manager has 1.6.4xxx and his won't work from the headset after trying all my common tricks (although he's on Dutty v4, not 6.1)
Mine works with Schaps...
I am the same way, i must have MSVC for my blutooth carkit...Schaps is the only one i could get it to work well on; however, I din't try it on Dutty's
Just Tested on Alex's WM6.1 Home BETA 2
Works Great.
No problems...works on WM6.1
OK Guys... Do this test... Press and say "play music", it will ask you by saying "what do you want to play?", say "Anything" ( one of the choices), and let me know if it works.
I have dutty V3 and it works fine. On any wm6.1 rom, it will freeze. That is what I am experiencing with VC.
Same Here, no issues (Except the caller id anouncement)
Works fine for wm6.1 and its fine with my parrot carkit actually bluetooth audio much much better now
WM6.1 VoiceCommand 1.6 US
Works fine here - in fact BETTER than with original TYTN release where it would often hang just after hoing the lookup till you hit the Red Phone Key.
Now that it sounds like BT volume is better with 6.1, has anyone taken the time to compare registry settings between WM6 and WM6.1 to see what the differences are?
asking it to play music, and than anything works for me, no issues.
Laubscherc said:
Same Here, no issues (Except the caller id anouncement)
Click to expand...
Click to collapse
Did you go into Settings-Personal-VC and check "announce incoming callers"?
Mine is working completely without any hacks.
In the official 3.03 used in Alex's 6.1 Beta 1, MSVC didn't work for me, crashed the settings.
Now with Alex's Beta 2 he used official 3.02 and MSVC works perfectly.
asfoor said:
OK Guys... Do this test... Press and say "play music", it will ask you by saying "what do you want to play?", say "Anything" ( one of the choices), and let me know if it works.
I have dutty V3 and it works fine. On any wm6.1 rom, it will freeze. That is what I am experiencing with VC.
Click to expand...
Click to collapse
I am experencing the same issue,
I have dutty V4 and it works fine. On any wm6.1 rom, I get the Voice Command.asx error message (The file Voice Command cannot be open. Either it is not signed with a trusuted cerification, or one of it components cannot be. found. If problem persists, try reinstalling orrestoring this file). Ireinstalled several this and soft reset also, but the issue still remain.
Help!
MELPHBOY said:
I am experencing the same issue,
I have dutty V4 and it works fine. On any wm6.1 rom, I get the Voice Command.asx error message (The file Voice Command cannot be open. Either it is not signed with a trusuted cerification, or one of it components cannot be. found. If problem persists, try reinstalling orrestoring this file). Ireinstalled several this and soft reset also, but the issue still remain.
Help!
Click to expand...
Click to collapse
Use Kaiser Tweak in disable the trusted certification.
alltheway said:
Use Kaiser Tweak in disable the trusted certification.
Click to expand...
Click to collapse
Not true....
The Voice Command.asx is NOT part of Kaiser Tweak Menu. There are only two certificates to disable or enable. Even if you were to disable both the WiFi certificate announcement or the BT Certificate announcement, the VC.asx certificate right violation still shows when you request or command the VC, and will not respond to the command.
Did you locate the certificate disable/enable on your phone Kaiser Tweak before you decided to post your response?
Unless you can prove me wrong, I AM WAITING.........
pkley said:
1.6.1722 works out of the box for me, even launches from the headset. HOWEVER, it totally doesn't recognize ANYTHING I say! Totally the opposite of my normal experience. Normally I have to install ZaJules BTCommand, enable, reset, disable, reset to get the headset launch to work.
Hmm, I'll have to try another version.
***Update***
after radio update it is working PERFECTLY! Also it does seem to make a big difference which minor version of MSVC you're using - 1.6.17913 is what I have, my manager has 1.6.4xxx and his won't work from the headset after trying all my common tricks (although he's on Dutty v4, not 6.1)
Click to expand...
Click to collapse
What radio did you upgrade to ? just tried all 3 and still doesnt work for me

Voice Cmmmand for tornado?

hi i recently "aquired" MS Voice Command 1.5 for smarphone, but it keeps comming up with an error message:Voice Command has encouterd a problem. restart Voice Comman and try again, i have done so ..but the still the same error mesage comes up, i have tryed with diffrent roms(orange) and cooked roms (WM 6.1 5.2.20282(Bulid 19597.1.1.8) Made by Karas. and some other tornado "cooked" roms, my question is it possible to get this working or is 1.5 only supported with WM 5.0, dunno some registy tweak maby??
i have a orange spv c600 btw dunno if that makes a diffrence but the insides the same as all the others except the wifi part
Hypola
much appricated
Have you tried Nitrogen's ROM?
[UPDATED to SP1] WM6 Platinum Edition 5.2.1711.18165.0.5.0 SP1 by NiTroGen
Voice dialing works fine with his ROM.
that was the fiest rom i tryed MS Voice Command still no luck, im not relly looking for voice dialing, just when i press a button and say windows media player its starts the appropriate program or when i say start bubble breaker and it does so ... cause im getting real pissed off with that joystick thing not working when i press down. just some easy way to get around ..and plus it looks cool inforn of other ppl lol - when i had my spv E650 i had voice command in the roms its a nice feature to have i guess

[Q] Voice actions doesn't work on branded Xperia

I have an xperia s on 3 contract and preinstalled Google voice actions will only work perfectly on 'listen to'.... plays any track of the 1800 on my phone and gets it right every single time... woooooooo hoo !!
'Call' doesn't interpret my voice properly and whatever it does interpret it tries to search the net... it doesn't search my contacts....
'Text' puts recipients name (mispelled) in the message text and leaves who it's meant to be sent to empty
None of the other voice market apps work properly either... I've tried them all... Jeannie starts out ok but then goes nuts with weird **** and you just want her to go away !!!
I've uninstalled/reinstalled the 2.3.7 with latest .73 update... but no joy.
I checked other 3 branded xperia's and same problem... also tried T-mobile and same story.
So I went and found someone with an unbranded xperia s and discovered it works perfectly !!!!
Does anyone know if there's a branded software clash causing this issue...?
My smartphone... which I actually got to use the voice actions for handsfree in-car convenience..... just ain't smart afterall.
Appreciate some help....... or should I ditch the branded and splash out on an unbranded...?
Bump,... Anyone.,. Someone
????

Categories

Resources