Database Info

MS Voice Command not working..for many of us..

I'm having this problem and have seen several others with same. When trying to use VC, get the "..have encountered a problem, try restarting" error. I fixed this problem with registry corrections before but the required Keys are not setup when installing under WM5 or lower. Just having this problem with WM6 (reloaded 1.7.1). Any ideas?

Atra said:
I'm having this problem and have seen several others with same. When trying to use VC, get the "..have encountered a problem, try restarting" error. I fixed this problem with registry corrections before but the required Keys are not setup when installing under WM5 or lower. Just having this problem with WM6 (reloaded 1.7.1). Any ideas?
Click to expand...
Click to collapse
What else do you have loaded on your phone(s) that have this issue. I use VC on all WM6 and WM5 roms that I've run (and ones I've cooked, like the Crossbow Reloaded ones you mentioned) and have never had this error and I've never tweaked around registry settings. I just install the cab and it works...
Are you installing VC 1.6 US?

With all the WM6 roms i've used (not as many as some but i'm new here) I haven't had an issue with VC 1.6 US either.

don't think it's a definite answer, but i did have this problem in the past when i installed voice command on my memory card rather than on phone memory. sometimes during loadup after a soft reset i would get that error...think it's because it takes longer to load from the card and voice command is setup to run right away (always in the background)...
if it's installed on the phone memory...dunno...sorry

I run VC 1.6 US and have never had a problem with it. I always install it in main memory.

I give..
Going back to WM5 Molski. To answer some of the post..
It's VC 1.6
No other software loaded..Fresh flash.
Installed to device, not storage *only option offered for install location*.
Get a message during device install: (...recommend installing to main memory. Do you still want to install to "."...) I answer Yes because it just aborts install to say No.
Thanks for the replies guys..

<--[Totally Screwed]
OK, now I have no sound from the speakers and Mic not working. While in Phone mode, the speaker button stays in the On position and won't turn off. Got the old Voice Command registry settings in place but it seems the new problem is the culprit. Going to start a new thread with new problem unless someone has any ideas..

Closing out
Back up and functioning on Molski 3.3 Crossbow. From what I can tell, during the WM 6 load, the speaker phone option became stuck in the On position but the speakers and Mic were not functioning. Voice Command seemed to know there was a problem and gave the "..restart VC.." message. After re-flashing Molski (a few times, still no joy), I flashed with the wired earbud/Mic connected. After flash and phone restart, I removed the headset while in phone mode. Speaker button reset to normal, phone speakers/mic started working again. Reloaded Voice Command and all worked.
aaahh the joys of PDAdome.. Where else can you get the thrill of accomplishment by getting back to the same friggin place
Thanks again for the replies all..

I have actually had this error a LOT with various ROMS, all were based on the Faria real thing base I believe. I'm not sure if that's relevant or not. At first it would just pop up randomly. Sometimes I could restart it and it would be fine, others it would never restart until I soft reset. The errors tended to get more and more frequent until it finally stopped working completely. Even on a reset it would come up right away. I hard reset that particular rom and it was fine for awhile but the issue returned and much more quickly. I never really installed any software onto the phone that ran in the background so I'm really at a loss as to what causes it. The last couple of ROMs I used didn't have VC and I never bothered to reinstall it because it kept having errors anyways. I am about to reflash yet again so I guess I'll put it in if it's not already there and see how it goes.

Give Molski a try..
Avatar28 said:
I have actually had this error a LOT with various ROMS, all were based on the Faria real thing base I believe. I'm not sure if that's relevant or not. At first it would just pop up randomly. Sometimes I could restart it and it would be fine, others it would never restart until I soft reset. The errors tended to get more and more frequent until it finally stopped working completely. Even on a reset it would come up right away. I hard reset that particular rom and it was fine for awhile but the issue returned and much more quickly. I never really installed any software onto the phone that ran in the background so I'm really at a loss as to what causes it. The last couple of ROMs I used didn't have VC and I never bothered to reinstall it because it kept having errors anyways. I am about to reflash yet again so I guess I'll put it in if it's not already there and see how it goes.
Click to expand...
Click to collapse
I didn't have any problems with his roms (..and went back to it with no probs). Only started having problems after I tried the Faria WM6. If the Molski works for you let me know. We'll give Faria a nudge.. Good Luck!

VC issues I've run across
I've tried pretty much every WM6 rom out there.... and cooked some of my own using the Pandora Kitchen.... and it seems that VC 1.6 decides to ignore my bluetooth activation button on some roms... all incoming calls and texts and reminders get announced as expected and the handsfree works great, but I can't push the headset button and get VC to wakeup.... Tried disabling VC and then re-enabling it, repairing the bluetooth, removing and then readding VC... nothing would fix it.... reflash with a different rom and presto! VC works!
At one point I had a strange issue with the bluetooth microphone.... VC would work fine (I'd ask "what time is it" and it would tell me the time) but when I was in a call, no one could here me.... I ended up enabling and then disabling auto gain control... wallah, mic works again.... weirdness.... (don't think this was rom related)
Anyway... the roms that I've had this problem with was XDA Mobile 6 (release 1... relase 2 is kicking a$$) and I think NBD 7.1... never had a problem with a ny Pandora cooked roms.....
Anyway... my $.02... (I'll probably get change)
kudo's to the rom wizards that be...

never had a problem. Installed in a few different roms. works fine
installed to main memory.

wolverine9827 said:
I've tried pretty much every WM6 rom out there.... and cooked some of my own using the Pandora Kitchen.... and it seems that VC 1.6 decides to ignore my bluetooth activation button on some roms... all incoming calls and texts and reminders get announced as expected and the handsfree works great, but I can't push the headset button and get VC to wakeup.... Tried disabling VC and then re-enabling it, repairing the bluetooth, removing and then readding VC... nothing would fix it.... reflash with a different rom and presto! VC works!
Click to expand...
Click to collapse
Voice Command Bluetooth Fix
View attachment 43147
I can't take credit for this and I can't give credit but Thank you...!
I've used this and has worked when VC w/n initiate via earpiece.
There's several threads on the specifics of this cab.

The Official WM6/TomTom Thread

Has anyone managed to get tomtom working on wm6?
I cannot for the life of me work out how to stop it crashing after about 20 seconds of it running. Ive tried 5.2.

Well, TomTom 5.2 runs smoothly on my Tornado, using the Fortuna Clip-On Bluetooth GPS receiver. No crashes at all!!!

A latest PPC version of TomTom 6 Navigator (V6.201.7160) works perfect on my SP5 w/ WM6 or WM5.0 before, but the virtual mouse SW i.e. FakeCursor should be used with occasional conditions.
Its really stronger than TT5.
Heres the original package of TT6 (delete the .cfg file unless u like the chinese interface)
and the crack
Enjoy!
Admint edit: Links have been removed warez is not allowed!

How does Fakecursor work?
Everytime i tried to use it, i got problems with the backlight of display.

i cant thank you enough.. thanks for posting this!
what maps work with this? i need a great britian map.
also its very slow, the black screen and red hands splash screen stay on for a good 30 seconds.

i spoke too soon.
it hangs on the screen with the arrow after the hands. like its crashed.
i think i have a memory problem.
i'll try overclocking.

overclocking works. ive managed to get to the screen where you pick your langauge but there is no cursor to select anything!
ive pressed every button and moved my joystick in every angle and i can only change the volume and not pick a language therefor not go on to set up the rest of tomtom.
this is driving me mad

Same problem here. I've managed (after about 30' of waiting, screen after screen) to reached the Time Format selection. Couldn't go further!
Lanny, are you sure that this version runs perfectly?

i cannot get fakecursor working

Guys u should create a shortcut of FakeCursor as long_camera.lnk (or any other button u like) in windows root w/ FakeCursor.exe, NOT in storage card.
Otherwise u cant do anything after TT's logo screen.
This version i posted runs pretty good on my SP5 w/ North American map v.665.1294 for 4 days after i installed the WM6 OS from jm012a9749.
Anyway,its a PPC version,so u must use FakeCursor to change lang., maps and edit the address when u input the wrong one.
You can press hold the camera key to call out the FakeCursor anytime when u use the TT. If u wanna stop it, u can press the home key to go back to the homescreen and press the back arrow to go back to the TT's screen, then the FakeCursor will be cancelled automatically.

create shortcut
Guys u should create a shortcut of FakeCursor as long_camera.lnk (or any other button u like) in windows root w/ FakeCursor.exe, NOT in storage card.
Otherwise u cant do anything after TT's logo screen.
This version i posted runs pretty good on my SP5 w/ North American map v.665.1294 for 4 days after i installed the WM6 OS from jm012a9749.
Anyway,its a PPC version,so u must use FakeCursor to change lang., maps and edit the address when u input the wrong one.
You can press hold the camera key to call out the FakeCursor anytime when u use the TT. If u wanna stop it, u can press the home key to go back to the homescreen and press the back arrow to go back to the TT's screen, then the FakeCursor will be cancelled automatically.

FakeCursor for Smartphone
This is the FakeCursor w/ shortcut i used on my SP5, try it.

thanks i got another cursor thing working called sphelper. when ive passed all the settings i cannot get bluetooth talking to tomtom with my gps reciver.
'no gps signal'

aha, u should add a new device in phone's bluetooth setting first and create a new outgoing com port for your GPS reciever. After this step, a new com port, usually com6 will be added in TT's bluetooth setting screen. Well, choose it and enjoy!

thanks a lot
i wonder if tomtom will release a smartphone version of tomtom 6 in the not so distant future.. or is it pda only from now on.

I think its no chance to get a separate smartphone version even was told it surport PPC and smartphone platforms with one software when the TT6 was unveiled last year.
I hope the all new TT7 can surport smartphone exactly.

Tomtom 5.20
I had the same problem (Not function TOMTOM 5.20) and I have it solved. Only problem was missing file "CurrentMap.dat" in folder "\\\WinCE Device\My Documents\TomTom\".

TomTom 6 with WM5 & WM6
I read throughout all the postings to find a solution. I installed TomTom 6 v 6.010 (and had it running fine) on my original Tornado (SPV C600 running WM5) using the method described in earlier posts (copy the files manually to the device) I was able to plan routes. No issues here. However, after installing the WM6 rom (and following the same process to install TomTom) the following happens:
- TomTom starts with the black splash screen/red hands
- I get the green warning page where you need to click "Agree" and immediately, the program quits (no time to press the Agree button) and a message pops: "Your device is incompatible with TomTom NAVIGATOR"
Now what is interesting is the following:
- If I revert to WM5 (original Orange ROM) and do the same steps for TomTom, I get the exact same behavior (same message:Your device is incompatible with TomTom NAVIGATOR). BUT if I apply the patch send by Orange Security Unlock (Cab sent by orange for my IMEI), it works fine.
- So, I reinstalled WM6 and tried to apply the same patch, it will not apply and comes up with an error: "You cannot use this CAB file with this device". I thought the reason was maybe because the operator was not showing. So I used TyphoonNBFTools to put back the original operator and reflashed. Same error when applying the patch
_ So next step was to use the change in registry found on spv-developers. That change does an application unlock but still does not allow Tomtom to run. There might be other registry settings that prevents this.
Has anyone found a solution?
Thank you

I have the same problem when i installed TomTom6 in my new WM6 OS first time.
But, after i changed following registry values, everything was fixed. Try it!
[HKEY_LOCAL_MACHINE\Security\Policies\Policies]
"0000101a"=dword:00000001
"0000101b"=dword:00000001
"00001001"=dword:00000001
"00001005"=dword:00000028 (or40)
By the way, i used the V6.010 at first, now the latest version V6.201 works smoothly on my SP5 w/ WM6 OS.

lanny said:
I have the same problem when i installed TomTom6 in my new WM6 OS first time.
But, after i changed following registry values, everything was fixed. Try it!
[HKEY_LOCAL_MACHINE\Security\Policies\Policies]
"0000101a"=dword:00000001
"0000101b"=dword:00000001
"00001001"=dword:00000001
"00001005"=dword:00000028 (or40)
By the way, i used the V6.010 at first, now the latest version V6.201 works smoothly on my SP5 w/ WM6 OS.
Click to expand...
Click to collapse
Thanks for the info. I wished I waited a bit longer. I ust bricked my phone following instructions at http://www.spv-developers.com/forum/showthread.php?t=7484
Thanks again

Missing Voicemail icon in WM6

I've loaded WM6 (AT&T) ROM, cleaned out all the crap from the ExtROM and now have a sweetly running phone that seems to be pretty much stable. It's had a few issues when bluetooth connected to my car kit, freezing when a 'reminder' popped up during a call. Call continued ok, but the screen and buttons all froze. Soft reset sorted it out - but it also did this in WM5.
Anyway, the biggest pain I've found with the WM6 ROM is that the voicemail icon does not appear, and I'm having to manually check 3 times a day just in case I've got messages. Does anyone out there know how to resolve this problem?

I have the same concern with an o2 xda orbit2 out of the box. I think this is a setting that o2 use, as i had the same concern with my jam which was rectified by changing network to orange! If anybody could help it would be much appreciated.

sleep of death

any one else getting it? unit goes in to standby and then wont wake up you have to soft reset.
ive been getting it frequently very anoying im using the big storage rom i dont rember who made it i can find out of some one wants to know
but is any one else having problems like me?

No problems here. I'm using the clean 1978 ROM...

I had it happen yesterday, running the stock AT&T ROM.

Hi
No problems here either.
It's worth remembering the phone wakes itself up about once an hour, although the display is dark so you will not see this happening.
If you have installed some software that doesn't handle this switching on very well and it crashes the phone, it will look the phone has died in standby, but it probably hasn't, it just looks that way.
I would advise a clean reset and not to install any programs, and see if it happens again. If it does your phone may be faulty, for example a memory problem that surfaces when the phone goes into a low power state.
Regards
Phil

Mine SOD'ed last night. I was using the phone, turned the screen off using the power button, then plugged it into my computer USB to charge. I was trying to do it one-handed and as you could imagine I was fiddling with the cable/phone for 30 seconds before I got the mini-usb plug into the phone. I watched to see the charging light come on but it didn't. I then tried to turn on the phone and realized I was SOD'ed. It only happens to me once every 1-2 weeks. My phone runs the stock Tilt ROM, but with lots of custom cabs installed, ie:
HTC Home 6 button
HTC Taskmanager 2.0 30995
Skype
Color Dot battery indicator
Schaps 10 Button Comm manager
PocketCM
Funambol 6.5.4
I push my phone all day long, surfing, ssh'ing into servers with putty, imap email, playing music etc, and I think if there was a bad memory issue Id see something other than an SOD. IMHO,theres a bug in the power management software.

SOD happened on my Tilt too. Im runnig the ATT rom. I had the same problem with the 8525 with the earlier ROM. The problem is IMAP email push. IF you use IMAP there is a chance you will get SOD once in a while. I changed all my emails to POP3 never had SOD since then.

I think you guys have to run the kaiser tweek to turn off the sleep mode in the registry. I had the SOD once....forgot to modify the registry via the kaisertweak app. 1st 2 options i think is what you have to modify.....that should fix you guys up.

Happened With Me too !!!
Now after using my at&t tilt flashed with HTC stock rom for 5 days, suddenly today my device suffered from a SOD.... had to soft-reset.... tried to figure out what went wrong but without any luck..... do any of u guys figured out the cause.... Kaiser Tweak only allows us to disable the sleep mode during call.....

kaiser falling sleep happens to me so frequently that I read all the posts with the key words KAISER FREEZE on xda-developers.
The only solution seems to power off and on again.
On modaco.com somebody posted a small applet which does automatically the power on-off for you.
Of course this does not remove the problem, just hide it...
Additionally I have tried 4 different WWE ROMS! from Att to HTC original ROMS to cooked Helmi aka 0.7.0 etc... No way to solve.
Please if modifying the registry can solve, can somebody post the link for kaiser tweaks and possibly the application?
Thanks
Saulo866

I think it might have something to do with Windows Live Maps program. This happend to me everytime I was using the program in the background. I upgraded the version and it stopped the problem I was having.

hollywood said:
I think it might have something to do with Windows Live Maps program. This happend to me everytime I was using the program in the background. I upgraded the version and it stopped the problem I was having.
Click to expand...
Click to collapse
Same here... I upgraded to helmi_c's Tilt ROM and haven't had the problem since. Pretty much guarantted though, if you leave Live Search running in the background and your phone goes to sleep... it will not wake up with the stock ATT ROM (at least with the current version of Live Search).
Cheers!!

SOD has typical been associated with running programs off of a Storage card. I had tons of SOD problems with the early WM6 Hermes ROMs. So far I have only had SOD a few times on my Tilt (running austinsync's BigStorage ROM). I installed Google maps to my microSD and within 20 minutes had 3 SODs. I uninstalled it and they stoppped immediately (Live Search is way better anyway).
I would recommend installing any programs that you use heavily or leave running onto the main memory. Also, saving attachments to a storage card has been a known cause as well.
I think SOD issues will get better as more ROMs start coming out for the Kaiser (and the chefs keep cooking).

OK, this keeps happening to me with the AT&T ROM....today it happened with no programs running in the background, anybody figure out a solution yet?

Me too
well I've had this problem also while running my own cooked rom, however to be fair i had this problem in the early days of the hermes. I thought however that the hermes problem was related to activesync's push email and the data connection (i.e. switching between 3G and 2G alot making activesync trip out) That all said maybe I'm barking up the wrong tree?!
Oh just in case anyone as the time to investgate this problem, I do know the Toshiba G900 had alot of problems with SOD inwhich tosh releases a fix for...... maybe if someone was to look at what that fixed it could help us here? have a read here > www.my900.com

Kaiser won't power back up
My unit after reset won't either power up or down with the power button. Everything still functions.
I found that if I have the power charger connected it works fine, so I thought I had a weak battery. Got a new battery and same thing.
Don't know what's going on, but if you do a soft reset with the charger plugged in, it will reset fine.
Hope someone figures this out!

Be careful overconfiguring...
PhilipL said:
Hi
No problems here either.
It's worth remembering the phone wakes itself up about once an hour, although the display is dark so you will not see this happening.
If you have installed some software that doesn't handle this switching on very well and it crashes the phone, it will look the phone has died in standby, but it probably hasn't, it just looks that way.
I would advise a clean reset and not to install any programs, and see if it happens again. If it does your phone may be faulty, for example a memory problem that surfaces when the phone goes into a low power state.
Regards
Phil
Click to expand...
Click to collapse
This might be the case, but I tried calling my phone when it SOD'd and didn't get a ring (it rang on the phone I was calling from.) I bet the problem is installed programs conflicting somehow, maybe kaisertweak will fix it in the future.
I can't guess what causes it tho...
For now, I'm running Kyphur's XDA Live and it has yet to happen.

PocketCM
rotohammer said:
Mine SOD'ed last night. I was using the phone, turned the screen off using the power button, then plugged it into my computer USB to charge. I was trying to do it one-handed and as you could imagine I was fiddling with the cable/phone for 30 seconds before I got the mini-usb plug into the phone. I watched to see the charging light come on but it didn't. I then tried to turn on the phone and realized I was SOD'ed. It only happens to me once every 1-2 weeks. My phone runs the stock Tilt ROM, but with lots of custom cabs installed, ie:
HTC Home 6 button
HTC Taskmanager 2.0 30995
Skype
Color Dot battery indicator
Schaps 10 Button Comm manager
PocketCM
Funambol 6.5.4
Click to expand...
Click to collapse
I was running Kypher's Tilt XDA-Live v 1.0 (AWSOME) with several custom cabs including PocketCM and was getting the SOD every time. I wiped the phone and started adding all of my cabs one at a time and all of them are loaded back in except PocketCM and since then i have not seen a single SOD.
Tim

I've noticed that I get the SOD a LOT more when I have bluetooth active. Not sure if that's just coincidental but literally the only time I've noticed the SOD has been when I've had BT enabled.

Happens to me a few times a week very annoying.

Well, I don't do emails, use Windows live, have pocketCM, used my bluetooth, tried Google maps, or have any programs on my sd card (basically whatever you all mentioned above, I don't have or do!), and still get SOD. So I guess I start backtracking. Sigh...
tilt with xda Live

TomTom And Diamond2

a support me because suddenly goes into pending the pda while running tomtom, I have done all combinations of energy but still the same!

I use "ttn7.916.9189_qvga_black" on my Topaz together with Dutty`s HG1 rom and it`s works like a charm.

patensas said:
I use "ttn7.916.9189_qvga_black" on my Topaz together with Dutty`s HG1 rom and it`s works like a charm.
Click to expand...
Click to collapse
same here with tess 3.9 rom. In fact, since using 6.5 rom, the problem with voice clipping off before the end of the message (usually skipping all distances information) is gone, without even using the workaround that was needed with 6.1 ( silent wav/mp3 looping in background). Very happy about the 6.5 upgrade regarding TomTom (i do not know if the official 6.5 solves the issue, but I guess so)

I know exactly what TS means; I had the same on my Topaz. It is even been send back to Brussels (repair center Europe) and it came back OK. After a week or so, while driving with tomtom: screen blanks. I posted several threads about this on XDA, no solutions however. The screen went blank/phone suspend mode, no matter what settings I used in Energy settings. Even unchecking the boxes (so the phone should stay on, no matter what) didn't help: suspend mode after 30 seconds. After 30 minutes on external power.
After I upgraded to WM6.5, the problem is over.