Voice Command OEM package for kitchen

[lightsail]

First, in the Kitchen OEM version of the Voice Command, edit the .RGU file to make it empty. The registry is not working.
Second, as mentined by someone here, create an empty cab installer (with files removed, default install dir to Windows).

Then after hardreset, install the dummy VC cab image. Then softreset.

[finster869]

Originally Posted by nickfuzz

My solution has worked perfectly, though not "completely" ideal.

I tried so many versions of the placing the registry in the kitchen, and it still wouldn't work perfectly. I edited many times, but the program still wouldn't work well. Instead of wasting more time, I simply used 2 steps (these steps were outlined elsewhere, so I can't take credit for them). I used win ce cab manager. First I opened the Voice Command cab, then extracted all the files to my desktop. Then I placed the files into a newly created kitchen OEM. Next, in win CE cab manager, I deleted all the files (ignored the warning), changed the default install folder to \\windows (which you can change under cab properties option in the drop down menu of the program). I saved the cab and moved it to my device. The new cab was 87kb and has the setup.dll and the registry files.

Hope that helps.

Ok, now I see. Actually, you could probably put the stripped down cab file that you create in the extrom so it loads automatically on a hardreset.

[imkk]

FYI. Still does not work for me even with the dummy cab file. VC starts, but does not recognize any commands. Also, does not stop until I soft reset.

[finster869]

Originally Posted by imkk

FYI. Still does not work for me even with the dummy cab file. VC starts, but does not recognize any commands. Also, does not stop until I soft reset.

Agreed, I couldn't get it to work either.

[JBabey]

After about a few DOZEN flashes I have lost all hope of getting this to work properly integrated into a ROM image via OEM.

I have tried about 8 different reg files, ive tried 4 or so different ways with the empty cab and just file placement.... all to no avail... the program installs... it launches.... and my voice commands nothing...

/sigh

on the bright side, with all the free storage i have now from my ROM.... having it and the prl20226 & phonealarm are now the only programs that install out of the extended rom.... and if i cared, i would just manually install those INTO the extended rom.

I will watch this thread as it progresses, and if anyone wants me to try something or has an idea that inspires me ill pick back up the torch and run with it... until then, this application has sucked my soul.

Shout out to colonel for keeping tabs on us and giving me a starting place with the OEM he put up, and to everyone else who works tirelessly to see this through.

[luv2chill]

You don't ever need to reinstall a PRL... that's stored in the nvm of your phone so it will survive all manner of resets - soft, hard, master (yikes that sounds wrong).

[Alwaysbelieve1]

LOl! Luv u have something on the brain.

[ImCoKeMaN]

Unless of course you have prl 20224 in your extrom still, then the prl doesn't surive a hard reset unless you do an additional soft reset before customization.

Sorry not really sure why i felt the need to post this useless bit of info, but if you for some reason go back to a stock sprint rom you could downgrade the prl

[luv2chill]

Well that is true. I figured though that anyone who's gotten into OEMs and building their own ROM would have removed that file from their extrom long ago.

And he is welcome to have PRL 20226 in his extrom if he wants--I was just pointing out that it doesn't need to be run after every hard reset like the other ones he mentioned.

[colonel]

Has anyone tried the VC OEM that I put on the ftp? I use it to build my rom and it always works. Once the rom is flashed, all I have to do is install the VoiceCmd.exe in the Windows dir.

Sorry that I am just now getting to this thread. I will go back and read through the whole thing to see what the actual problems are.