nueROM 2.2 Bleeding Edge General Discussion Thread

[zadok]

Originally Posted by flyers2114

Any word on the registry changes not working? I am going to try the basekit and see what happens....thanks..

I've been using the basekit.

Are you trying the same registry change as me?

Current : HKLM\SOFTWARE\OEM\VoiceCommand\Path \Windows\sddialer.exe

Desired : HKLM\SOFTWARE\OEM\VoiceCommand\Path \Program Files\Voice Command\voicecmd.exe

Update:

I uninstalled Voice Command, soft reset, then tried to delete the "Current" key that has sddialer.exe in it. Won't delete!

I used the PC to install a licensed copy of MSVC via ActiveSync connection -- I didn't cook it in the ROM.

STRANGE

[flyers2114]

Originally Posted by zadok

I've been using the basekit.

Are you trying the same registry change as me?

Current : HKLM\SOFTWARE\OEM\VoiceCommand\Path \Windows\sddialer.exe

Desired : HKLM\SOFTWARE\OEM\VoiceCommand\Path \Program Files\Voice Command\voicecmd.exe

Update:

I uninstalled Voice Command, soft reset, then tried to delete the "Current" key that has sddialer.exe in it. Won't delete!

I used the PC to install a licensed copy of MSVC via ActiveSync connection -- I didn't cook it in the ROM.

STRANGE

I am using the rom only.....I am changing the HKLM-Software-Microsoft-Bluetooth-Audiogateway-----BTAGExtModule from OEMAGW.dll to \Windows\vcbthag.dll


Edit: Is this just isolated to MSVC or have others made any changes to the reg?

Edit: Just tried another reg change......same thing wont stick....

[EtherealRemnant]

So no2chem, last night I changed the pagepool to 12MB and set the phone kernel to low memory... when I soft reset, it completely wiped out the flash and acted like I had just flashed the phone for the first time. Basically, it hard reset itself.

I can't really think of anything else but the kernel mods that caused this.

[zadok]

Originally Posted by flyers2114

I am using the rom only.....I am changing the HKLM-Software-Microsoft-Bluetooth-Audiogateway-----BTAGExtModule from OEMAGW.dll to \Windows\vcbthag.dll


Edit: Is this just isolated to MSVC or have others made any changes to the reg?

I reflashed from the kitchen... Did NOT install Voice Command

In the same HKLM\SOFTWARE\OEM\VoiceCommand\

I changed VoiceCmdDuration to 20 from 10 -- it stuck

And VoiceCmdEnable to 1 from 0

Interesting...

Since you're finding this registry entry in the "nueROM3Titan 3pre3," while I'm finding it in "nueROM3TitanKitchen 3pre3," then it might be cooked in the original in a way that write protects it.

I'm going to check my OEM folder in the kitchen to make sure that I didn't somehow create that entry. Don't think that I did, tho.

MSVC UPDATE -- 18Sep08 18:48 EDT


OK. 1) I removed the User_OEM folder in the kitchen.
2) Carefully reflashed.
3) Pulled the battery once the it loaded to the "tap with the stylus."
4) Hard reset at the "tap with the stylus."
5) Installed Resco Registry edit.
6) Went to the HKLM\SOFTWARE\OEM\VoiceCommand\Path "\Windows\sddialer.exe" and tried to change entry to to "\Program Files\Voice Command\voicecmd.exe"
7) The entry will not modify! It is as though it is bullet proof or something.

Is this a standard reg entry in all ROMs?

If so, why could I edit it in other builds and not this?

Or is it just me?

Anyone?

[no2chem]

Originally Posted by EtherealRemnant

So no2chem, last night I changed the pagepool to 12MB and set the phone kernel to low memory... when I soft reset, it completely wiped out the flash and acted like I had just flashed the phone for the first time. Basically, it hard reset itself.

I can't really think of anything else but the kernel mods that caused this.

interesting, i'll take a look at this..

[zadok]

Originally Posted by no2chem

interesting, i'll take a look at this..

Would you please look into my suspicion that the MSVC registry entries and OEMAGW.DLL are cooked into the ROM.

We can't change them.

Here's the directions we are following:

http://forum.xda-developers.com/showthread.php?t=391262

Thanks!

Z

[MrHappy]

just to confirm. BT works for calls but something is not right with MSVC. The same cab I have been using for quite some tome no longer responds to hitting the button on the headset...

[R.J.B]

Originally Posted by zadok

Would you please look into my suspicion that the MSVC registry entries and OEMAGW.DLL are cooked into the ROM.

We can't change them.

Here's the directions we are following:

http://forum.xda-developers.com/showthread.php?t=391262

Thanks!

Z

I seached in the basekit and found the OEMAGW.DLL, removed it, re-cooked, then added teh MSVC reg key and my bt voice command is back...

[Zenoran]

for you people with bluetooth problems -- are you cooking a rom? -- did you include the ppckitchen kitchen in yer cookin or did you use the useroem folder? im thinking the similar drivers/packages could be conflicting if you include the whole ppckitchen.rar?

I copied all the oems i wanted into useroem and built with no problems. easier to manage too, including the whole ppckitchen.rar in the build process is so cluttered and messy!

[zadok]

Originally Posted by Zenoran

for you people with bluetooth problems -- are you cooking a rom? -- did you include the ppckitchen kitchen in yer cookin or did you use the useroem folder? im thinking the similar drivers/packages could be conflicting if you include the whole ppckitchen.rar?

I copied all the oems i wanted into useroem and built with no problems. easier to manage too, including the whole ppckitchen.rar in the build process is so cluttered and messy!

I used only what was in the basekit -- no additional apps.

The MSVC / BT problem has to do with inability to edit registry entries in order to allow the headset/earpiece to initate commands.

I can use the assigned button on the device.