Registry Entries for Voice Command v1.6.

saridnour · #1 (**permalink**) 02-04-2007, 04:48 AM

Well these should be them. The Reg entries for VC 1.6 when adding it into your own rom. I have this working in mine and should have all that are required in the two files in the zip. Add your VC bits to the windows dir and add a shortcut to the startup folder in the windows dir and you should be good to go. I mapped VC to Button #5 push and hold as it defaults to a press with this button.

Let me know if there are any issues as I believe I have all the entries here, but am working from my master reg entires and could have not copied one of the tokens. I am just trying to keep it as clean as I can but will add them in if anyones having issues.

THE VC1.6 Bits are not in the attachment as these are not freeware! -Don't ask me for them!

-saridnour

finster869 · #2 (**permalink**) 02-04-2007, 08:38 AM

Thanks for the registries. I downloaded them, but before trying to import them I decided to try installing differently and seems to have worked.

If you are having trouble getting VC1.6 to work with a kitchen cooked rom, try this and let me know if it works:

1. Put phone in flight mode.
2. Install VC1.6 cab file from storage card rather than via active sync.
3. Turn blue tooth on and off several times (should work)
4. Soft reset
5. This is where it used to hang: try turning bluetooth on and off via comm manager several times (MINE IS CURRENTLY WORKING).

If it stops working, then I will try importing saridnour's registry files, but right now installing with the phone in flight mode via cab file on storage card rather than via activesync seems to have made a difference.

UPDATE: After 3rd soft reset, it conked out again.....This is weird, though. Putting phone in flight mode, then restarting (with phone in flight mode) seems to restore it to working status again. I'm going to play a little, and if I can't get it to work I will try this registry file.

UPDATE 2: Using these registries made no difference for me. I still had it conk out. HOWEVER, SOFT RESETTING IN FLIGHT MODE SEEMS TO BRING BACK FUNCTIONALITY FOR ME. A less than perfect resolution, but at least it is usable without having to constantly hard reset.

**schettj** · #3 (**permalink**) 02-04-2007, 09:49 AM

What is your radio firmware version (and carrier)? The radio firmware also has the low-level BT radio code in it. It's possible this is the reason this is working for some people and not for others.

finster869 · #4 (**permalink**) 02-04-2007, 10:11 AM

Sprint Radio version 1.27.00, PRI 1.19_003

haus · #5 (**permalink**) 02-04-2007, 01:10 PM

I'm on verizon, radio 1.10 IIRC, same problem. Finster869, I applaud your work on this so far; sounds like you are making progress.

finster869 · #6 (**permalink**) 02-04-2007, 01:14 PM

Quote:

Originally Posted by haus

I'm on verizon, radio 1.10 IIRC, same problem. Finster869, I applaud your work on this so far; sounds like you are making progress.

Thanks. Haus, have you tried soft resetting in flight mode in order to restore funcionality? I am interested to seeing whether this works for anyone else. As noted in another thread, I am sometimes having problems usb syncing (won't aquire lan ip address). Flight mode followed by a soft reset and active syncing while in flight mode resolves that issue, which is what gave me the idea to try it with the bluetooth problem.

saridnour · #7 (**permalink**) 02-04-2007, 02:06 PM

I am not using the kitchen to build my roms. I am also using a sprint ohone. I have had no issues with vc.

Another thing you could try is to take the VC16 cab and edit the package. Remove all the files except setup.dll and reset the install path to \windows. If you do this you can add the bits to your build in the kitchen or whatever and then, after booting, run the cab. This should only add the reg data and run the setup.dll thus setting the phone to whatever state or services state needed at install. I used this method until I could find the issue in my initial installs until I tracked down all of the keys.

-saridnour

finster869 · #8 (**permalink**) 02-04-2007, 02:09 PM

Thanks Saridnour. The Bluetooth/VC problem is Kitchen related, which explains why you aren't having a problem. I might try your suggestion, though, of building voice command into my rom, even though my soft reset in flight mode solution seems to be working.

**ImCoKeMaN** · #9 (**permalink**) 02-04-2007, 02:24 PM

I'm beginning to think this might be related in some way to the USB issue i'm having with 3.5 now that you mention syncing issues. If there is a conflict in some of the drivers in the OS it can cause weird issues. I did witness the bluetooth/ VC problem on 3.5. Now, i hope to get the USB driver issue fixed and test this again. Perhaps in finding the problem with 3.5 the same change could be applied to the 3.3 kitchen to fix VC there. Although if the USB is fixed in 3.5 i don't see much of a reason to stick to 3.3

With all the great minds in this community i'm sure it will be worked out soon enough!

**mikee4fun** · #10 (**permalink**) 02-04-2007, 03:05 PM

I fixed this issue I believe, the problem is that the bluetooth stack kept turning off when the phone went into suspend and would not wake back up until I did a soft reset which sucked big time. Add the following setting and then soft boot using psshutxp. If you use the soft reset hole for some reason the registry will not remained changed. After the soft reset walaa the bluetooth doesn't turn off anymore. My only issue is with VC 1.6 and when I get a incoming call while I am in a call it broadcasts the caller name over my earpiece which is annoying. I changed the settings and it still does it. I am running a Verizon vx6700 with colonel 3.3 rom and using radio ver 1.10

HKLM\System\CurrentControlSet\Control\Power\State\ Suspend, add a new DWORD called btl1: (make sure the colon is there), with a DWORD value of 2

The value is dec

Cheers,

Michael