Database Develop

Setting default input and keeping it.

Ok I have searched and not run across anything without reading every thread in here.
How do I change my default input method from keyboard to letter recognizer and MAKE it stick.
I change it i the input menu and reg edits but every time I soft reset it is back.

...we're on the same boat :?

Join the club!
I'm after the phone pad so I can still use the 8125/Wiz screen as a normal phone keypad at times and not have to whip out the stylus.

whatever you do, dont use registry wizard to set it... I white screened a week ago doing that, hard reset

hope to find a solution

Perhaps this:
HKCU\ControlPanel\SIP
DefaultIM {42429667-.... or one of the others {42429690- {42429691-
Look in the neighborhoud HKCR\CLSID\{424296...... for the others.
Cheers
edit: In case it wasn't clear you need to fill in the whole CLSID in the DefaultIM string value. So {42429667- including the } at the end.
It should work after a soft reset (gone with a hard reset)

Any Solutions to this yet?
Thanks
Jules

I'm joining the club too
I'm on a Charmer, I used to able to change the Letter Reg SIP as default before I upgraded my ROM. I thought I'm the only one.

i'm triing to change the reg value with total commander and with wizard reg but after a restart the phone hang on white screen... someone can help me?
i want to use nullkb as default probably is not possible?

jmel said:
whatever you do, dont use registry wizard to set it... I white screened a week ago doing that, hard reset
Click to expand...
Click to collapse
hrm.....
dromico said:
i'm triing to change the reg value with total commander and with wizard reg but after a restart the phone hang on white screen... someone can help me?
i want to use nullkb as default probably is not possible?
Click to expand...
Click to collapse
cant say i didnt warn you?

jmel said:
cant say i didnt warn you?
Click to expand...
Click to collapse
yes but i make a hard reset after the first try (manually change registry with tcmd) and i try in another way...white screen in every try

lost in translation...
I was saying that if you TRY to use registry wizard to set it, you will get a white screen, and be left having to HARD RESET....

Not the best solution, but perhaps you could use my program SwitchSip to change the SIP on every soft reset. I don't know if it'll stick though, I've never tried...
V
http://forum.xda-developers.com/vie...&postdays=0&postorder=asc&highlight=sipswitch

thanks i try with your program, i never search the forum enough if i don't found your post.
i don't know why there is no possiblity to change default IM in the WM configuration.

Everything is listed here: http://wiki.xda-developers.com/index.php?pagename=WM5_Tweaks_Other "Set default SIP"

tweakradje said:
Everything is listed here: http://wiki.xda-developers.com/index.php?pagename=WM5_Tweaks_Other "Set default SIP"
Click to expand...
Click to collapse
I think we've all tried the method. Read the posts above carefully.

Just as a problem recap: the default SIP reghack no longer works on AKU2 ROMS. The kbd default occurs after a soft reset no matter what you have changed the registry value to.
I'm working on this one too. I coded up a program that quickly set the SIP to block recognizer and exited figuring I could just add it to the startup programs folder to switch over after a soft reset.
However, while this program works just great normally, it doesn't change the SIP when run at startup. I am working on why this is, currently. So far I've determined that my program is able to find the block recognizer SIP so the SIP dll is loaded. Tomorrow I may get a few more minutes to work on it. I'll code my program to check to see if it correctly set the SIP to block recognizer and re-attempt to change until it's successful. I'm guessing that this will have no effect on the issue since my current working theory is that the kbd default is set sometime after the startup programs run.

Guys, I don't know whether my app worked or not, but this post:
http://forum.xda-developers.com/viewtopic.php?p=317635#317635
seems to suggest it did. I don't have a wizard to test it on though
V

@vijay555:
I've got my little app set up on my today screen so I can just tap it quickly after everything's loaded to change my sip but it won't work if I drop it into my startup folder.
Perhaps this is what the poster you refer to is doing? Does your program check the default SIP using SipGetCurrentIM after you switch to see if the operation worked? Or do you just check for an error code after calling SipSetCurrentIM. Me, I'm just checking for an error currently and am not getting one.

Sleuth255: I really can't remember how I did it, I wrote it in c++ before I could program in c++, somehow. I'm on a promise to rewrite it sometime, and turn it into VJSipSwitch, for now it's merely a bastard child.
However, despite this, it's also designed to be configured as a shortcut to be launched from a hardware key or shortcut... if it becomes an issue, I'll look over the code again.
V

Vibrate while dialing a Phone Number

First of all I love my new TyTN II and XDA-Developers!
Question: Anybody know of a hack or a .cab that will make my touch pad numbers vibrate when I dial a number? This way I know when I've pressed a touch button on the display - had it on my MDA Compact II and loved it!
PS: I've attached the two .cab files I use to have, but they don't work on the Kaiser...

frikibabi said:
First of all I love my new TyTN II and XDA-Developers!
Question: Anybody know of a hack or a .cab that will make my touch pad numbers vibrate when I dial a number? This way I know when I've pressed a touch button on the display - had it on my MDA Compact II and loved it!
PS: I've attached the two .cab files I use to have, but they don't work on the Kaiser...
Click to expand...
Click to collapse
it's a bit of a work, but the result is great!
Description Add a small vibration for every key pressed when dialing the phone. Improves tactical feedback.
Type Registry Tweak
Instructions Using a registry editor navigate to the following keys and follow the directions. Do this for each of the listed registy keys
1. Rename Standard DWORD parameter "Sound" to "Sound1"
2. Create new String Parameter "Sound"
3. Assign value *vibrate* to this new parameter.
HKEY_CURRENT_USER\ControlPanel\Sounds\Dtmf#
HKEY_CURRENT_USER\ControlPanel\Sounds\Dtmf*
HKEY_CURRENT_USER\ControlPanel\Sounds\Dtmf0
HKEY_CURRENT_USER\ControlPanel\Sounds\Dtmf1
HKEY_CURRENT_USER\ControlPanel\Sounds\Dtmf2
HKEY_CURRENT_USER\ControlPanel\Sounds\Dtmf3
HKEY_CURRENT_USER\ControlPanel\Sounds\Dtmf4
HKEY_CURRENT_USER\ControlPanel\Sounds\Dtmf5
HKEY_CURRENT_USER\ControlPanel\Sounds\Dtmf6
HKEY_CURRENT_USER\ControlPanel\Sounds\Dtmf7
HKEY_CURRENT_USER\ControlPanel\Sounds\Dtmf8
HKEY_CURRENT_USER\ControlPanel\Sounds\Dtmf9
Notes A softboot is required
to change back to the default function, go back through the list of registry keys, delete the "sound" entry, and rename "sound1" back to "sound"
note: the * needs to be entered in the value for "*vibrate*"
This tweak really makes it easier to know that you have pressed a button when dialing on the touch screen
have fun!

here's the cab.

very good
there is a delay until the vibration begins,
if you are used to tapping the numbers quickly..
otherwise GREAT find
thank you
regards
krassen

To be clear...
There is a delay when you push the first number. After that the vibe is almost instantaneous.
At least on my Tilt.

dgduris said:
To be clear...
There is a delay when you push the first number. After that the vibe is almost instantaneous.
At least on my Tilt.
Click to expand...
Click to collapse
same with me...not even worth installing... i dont dial that slow..

Amazing Tool!
The initial delay doesn't bother me...
Simple to install & simple to use!
Big Thanks!

I installed the program and it works great when you are making the call initially...but call is connected and I tried to key in (like entering numbers on an automatic response system), it doesn't vibrate.
Normal?

when i try to download say " compressed file is invalid or corupted" ....?

bobcho10 said:
when i try to download say " compressed file is invalid or corupted" ....?
Click to expand...
Click to collapse
i receive the same message when trying to unpacking the zip

is there a way to do this on every key press like on the lg viewty this works very well on that handset

bobcho10 said:
when i try to download say " compressed file is invalid or corupted" ....?
Click to expand...
Click to collapse
works fine for me. this is the .cab file. drag it into your phone, and run it from the phone and it should install.
do not unzip the cab prior to install. just dl it, drag to phone, open from phone, and it should install fine.

portos03 said:
i receive the same message when trying to unpacking the zip
Click to expand...
Click to collapse
same thing with me

From a previous thread on this, I thought that the cab version had the delay but the direct reg edit method was virtually instantaneous, but I haven't verifed this.

I installed it, was working about half the time (key presses) , then I deinstalled it. Now the standard "Options" for key tones (short tone, long tone) do not work and the keypad is not very accurate. Is there a way to correct for this?

portos03 said:
i receive the same message when trying to unpacking the zip
Click to expand...
Click to collapse
dont unzip on ur desktop, send it to ur pphone and open it with pocket rar and then install the cab.

rico002 said:
dont unzip on ur desktop, send it to ur pphone and open it with pocket rar and then install the cab.
Click to expand...
Click to collapse
thanks rico, decided not to install it after they fixes the "bugs" with delay...

the delay doesn't bother me too much, seems to be an issue with the first number pressed. I backed up after dialing a number and it had the "delay" when I started the new number. cool little cab. thanks

RemE said:
From a previous thread on this, I thought that the cab version had the delay but the direct reg edit method was virtually instantaneous, but I haven't verifed this.
Click to expand...
Click to collapse
i did it with the reg edit method, and there is no delay...
it took me about 5 minutes then, so whats that comparing to a lifetime?

Sorry but dont quite understd the registry method.
You mean :
1. Rename Standard DWORD parameter "Sound" to "Sound1"
2. Create new String Parameter "Sound"
3. Assign value *vibrate* to this new parameter.
HKEY_CURRENT_USER\ControlPanel\Sound1\Dtmf#
HKEY_CURRENT_USER\ControlPanel\Sound1\Dtmf*
HKEY_CURRENT_USER\ControlPanel\Sound1\Dtmf0
HKEY_CURRENT_USER\ControlPanel\Sound1\Dtmf1
HKEY_CURRENT_USER\ControlPanel\Sound1\Dtmf2
HKEY_CURRENT_USER\ControlPanel\Sound1\Dtmf3
HKEY_CURRENT_USER\ControlPanel\Sound1\Dtmf4
HKEY_CURRENT_USER\ControlPanel\Sound1\Dtmf5
HKEY_CURRENT_USER\ControlPanel\Sound1\Dtmf6
HKEY_CURRENT_USER\ControlPanel\Sound1\Dtmf7
HKEY_CURRENT_USER\ControlPanel\Sound1\Dtmf8
HKEY_CURRENT_USER\ControlPanel\Sound1\Dtmf9
Notes A softboot is required

open touch 2.4 and bluetooth profile problem (resolved)

I installed open touch 2.4 and LOVE IT.. it makes windows mobile so much useful..
one thing i found problamatic was the bluetooth profile. The problem is when I press the call button on my bluetooth headset it doesn't trigger the voice speed dial. It just launches the dialler which shows the keypad.
That kind of defeats the purpose of 'hands free' if I need to press the voice speed dial on the phone and then use the headset.
Any solution ? Or any other package I can install to get the full functionality of voice speed dial with bluetooth.

I have the same problem, and it effects the ability for me to use MS Voice Command. I wish someone would help, but I made a post about this and got no replies.

beowolf said:
I have the same problem, and it effects the ability for me to use MS Voice Command. I wish someone would help, but I made a post about this and got no replies.
Click to expand...
Click to collapse
guys,
I'm working on v2.5 and will try to resolve this issue if possible.
I need more details as to what is happening.
Also,
I did not see any of this nature posted in the original v2.2 post.
Who else is having this issue?

hoolahoous said:
I installed open touch 2.4 and LOVE IT.. it makes windows mobile so much useful..
one thing i found problamatic was the bluetooth profile. The problem is when I press the call button on my bluetooth headset it doesn't trigger the voice speed dial. It just launches the dialler which shows the keypad.
That kind of defeats the purpose of 'hands free' if I need to press the voice speed dial on the phone and then use the headset.
Any solution ? Or any other package I can install to get the full functionality of voice speed dial with bluetooth.
Click to expand...
Click to collapse
Just to cover all basis, did you setup the button 5 options?
Remember that I left the 5th button free for people to choose either voice record or voice speed dial.
Going forward, please do not create new post, instead post your issues in the original thread.
Thanks,

I'm pretty sure that what your dealing with is a registry problem. When i switched to touchit 2.3 i had to reconfig to the following:
1 Use registry editor to edit the following entries on your Wing:
Under: \HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\A udioGateway\, Modify Value data: OEMAGEX.dll to BTAGExtModule.dll
Under: \HKEY_LOCAL_MACHINE\SOFTWARE\OEM\VoiceCommand\, Add DWord Value: LaunchAPEnable, Value Data: 1
Under: \HKEY_LOCAL_MACHINE\SOFTWARE\OEM\VoiceCommand\, Add DWord Value: VoiceCmdEnable",Value Data: 0
2. Wait about 30 sec, then soft-reset
Try it and let me know how it goes. I dont get credit for this it is from a previous post. This did work for me tho. I can prompt the voice speed dial from the bluetooth.

ttran001 said:
guys,
I'm working on v2.5 and will try to resolve this issue if possible.
I need more details as to what is happening.
Also,
I did not see any of this nature posted in the original v2.2 post.
Who else is having this issue?
Click to expand...
Click to collapse
Thanks ttran for responding. I have great respect for you for putting together this great ROM.
The issue is..
I am pairing my bluetooth headset (motorola h850) with the phone. After paring, if I press the call button on my bluetooth, it is supposed to invoke the voice dial app in the phone and call the voice tag I spoke. However it just brings the phone dialler screen and does nothing.
My diagnosis
For an incoming call (when paired), I can pickup the call using bluetooth headphone's button. So I know bluetooth instrument is working.
Secondly when I directly invoke voice speed dial from phone (i mapped a hardware button to voice speed dial) it works fine too.
Only problem is I can not invoke voice speed dial from bluetooth headset.
Do not confuse this issue with the hardware button mapping since I am trying to invoke voice speed dial from bluetooth headset (not from hardware button on phone. that works fine)
Please let me know if you need any futher information. I will happy to provide any additional details.
BTW thanks again for putting together such a great ROM.

Hi,
Thanks for clearing that up.
Please try what mrmikemcguire posted:
1 Use registry editor to edit the following entries on your Wing:
Under: \HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\A udioGateway\, Modify Value data: OEMAGEX.dll to BTAGExtModule.dll
Under: \HKEY_LOCAL_MACHINE\SOFTWARE\OEM\VoiceCommand\, Add DWord Value: LaunchAPEnable, Value Data: 1
Under: \HKEY_LOCAL_MACHINE\SOFTWARE\OEM\VoiceCommand\, Add DWord Value: VoiceCmdEnable",Value Data: 0
2. Wait about 30 sec, then soft-reset
And let us know if it works for you, I don't use blue tooth so I can not test it for you.
Also,
Let me know if it fixes your issue so that I can add it to the next release.
Thanks folks,

sorry didn't work for me..

Ok.... First, thank you mrmikemiguire . Now hoolahoous .. did we make progress? The Audio gateway should be opening now... Verify that the registry modifications are correct in your device, then power cycle..... there may be another piece to the puzzle but those changes should work.
Edit: Final piece... Verify HKLM,"SOFTWARE\OEM\VoiceCommand "Path" = \Windows\SDDialer.exe

Okay.. thanks for everyone's help.. I finally got it to work... One thing incorrect in above settings was
\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\A udioGateway\, Modify Value data: OEMAGEX.dll to BTAGExtModule.dll
the default entry was VCBTHAG.DLL not OEMAGEX.dll , I missed that..
however when I changed VCBTHAG.DLL to BTAGExtModule.dll , it started working..
ttran001, maybe you can include these entries in 2.5.
I know you are not planning to include voice speed dial or voice command in 2.5, I personally feel that you should include atleast one of them. My vote would be voice speed dial since it works for everyone but voice command works only for subset of people. When I say work, I mean software being able to recognize what a person is saying.
but thanks to everyone including mrmikemcguire to get it to work for me.

hoolahoous said:
Okay.. thanks for everyone's help.. I finally got it to work... One thing incorrect in above settings was
\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\A udioGateway\, Modify Value data: OEMAGEX.dll to BTAGExtModule.dll
the default entry was VCBTHAG.DLL not OEMAGEX.dll , I missed that..
however when I changed VCBTHAG.DLL to BTAGExtModule.dll , it started working..
ttran001, maybe you can include these entries in 2.5.
I know you are not planning to include voice speed dial or voice command in 2.5, I personally feel that you should include atleast one of them. My vote would be voice speed dial since it works for everyone but voice command works only for subset of people. When I say work, I mean software being able to recognize what a person is saying.
but thanks to everyone including mrmikemcguire to get it to work for me.
Click to expand...
Click to collapse
Hi,
That reg fix has been added to v2.5 and yes Voice speed dial is included but not voice command since it takes about 4mb of space.

hoolahoous said:
Okay.. thanks for everyone's help.. I finally got it to work... One thing incorrect in above settings was
\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\A udioGateway\, Modify Value data: OEMAGEX.dll to BTAGExtModule.dll
the default entry was VCBTHAG.DLL not OEMAGEX.dll , I missed that..
however when I changed VCBTHAG.DLL to BTAGExtModule.dll , it started working..
ttran001, maybe you can include these entries in 2.5.
I know you are not planning to include voice speed dial or voice command in 2.5, I personally feel that you should include atleast one of them. My vote would be voice speed dial since it works for everyone but voice command works only for subset of people. When I say work, I mean software being able to recognize what a person is saying.
but thanks to everyone including mrmikemcguire to get it to work for me.
Click to expand...
Click to collapse
Yep sorry about that.. I realized that when i did it, same occurance, but forgot to mention it! Sorry about that, but at least you got it squared away. Glad I could at least point you in the right direction.

mrmikemcguire said:
Yep sorry about that.. I realized that when i did it, same occurance, but forgot to mention it! Sorry about that, but at least you got it squared away. Glad I could at least point you in the right direction.
Click to expand...
Click to collapse
Either way thanks for providing feed back so to help resolve this issue.

I am using 2.5 slim and cannot get audio from realplayer, skype, etc.
I push the button and all I get is some wrong application, try again later errors....
Please help.
It all worked perfectly with the Clean ROM so may be someone with know-how can look at the registry differences between them and tell me if this is fixable, or i have to install the clean again...
Thank You!

#13 said:
I am using 2.5 slim and cannot get audio from realplayer, skype, etc.
I push the button and all I get is some wrong application, try again later errors....
Please help.
It all worked perfectly with the Clean ROM so may be someone with know-how can look at the registry differences between them and tell me if this is fixable, or i have to install the clean again...
Thank You!
Click to expand...
Click to collapse
Is this with bluetooth or the actual headset, or headphones?
And is anybody else having this issue?

Yes, BT.
Sorry i didn't mention this important detail.

SMS when ignoring calls

when someone calls me I have the option to send a message which says " Im busy, ill call you back later ". is it possible to change that text through a registry edit?

did you try going into Setting --> Phone ---> Advanced
the first option there, i'm pretty sure you can change the message

no i did not, thank you

Is there a registry edit to bring this back up?I think after tinkering around the phone with Advance Configuration or S2U2 - that option isnt in my settings>phone>advance section and I would really like to have it back
Even in S2U2 I have the option "send busy text message" set to on

xNitr0us said:
when someone calls me I have the option to send a message which says " Im busy, ill call you back later ". is it possible to change that text through a registry edit?
Click to expand...
Click to collapse
use the registry editor to change following:--
[HKEY_LOCAL_MACHINE\SOFTWARE\HTC\PHONE\PhoneExtendSetting]
"Message"="I am busy right now. I'll call you back later."
change this to have any message....

Thank-you soo much
I will admit, I got lazy and didnt bother searching the forums, which im pretty sure it is.
Cheers!

c_shekhar said:
use the registry editor to change following:--
[HKEY_LOCAL_MACHINE\SOFTWARE\HTC\PHONE\PhoneExtendSetting]
"Message"="I am busy right now. I'll call you back later."
change this to have any message....
Click to expand...
Click to collapse
Hello,
I use S2U2 v2.04 and HTC P3400
I need to change auto SMS text. I did not find the KEY HKEY_LOCAL_MACHINE\SOFTWARE\HTC\PHONE\PhoneExtendS etting
I could only find
HKEY_LOCAL_MACHINE\SOFTWARE\HTC\PHONE
Please help.

shailesh.devasthali said:
Hello,
I use S2U2 v2.04 and HTC P3400
I need to change auto SMS text. I did not find the KEY HKEY_LOCAL_MACHINE\SOFTWARE\HTC\PHONE\PhoneExtendS etting
I could only find
HKEY_LOCAL_MACHINE\SOFTWARE\HTC\PHONE
Please help.
Click to expand...
Click to collapse
use any registry editor and you shold be finding it..

c_shekhar said:
use any registry editor and you shold be finding it..
Click to expand...
Click to collapse
I am using "S2U2 2.04" on "Samsung Omnia 910" (verizon) with registery editor "PHM Registry Editor" ver 0.70. I do not find the "HTC" part of the registry. Is this because I am using a Samsung Omnia? I have even looked under the "Samsung" key and still have not found the "Phone" key.
Any help will be much appreciated.

Arcangl123 said:
I am using "S2U2 2.04" on "Samsung Omnia 910" (verizon) with registery editor "PHM Registry Editor" ver 0.70. I do not find the "HTC" part of the registry. Is this because I am using a Samsung Omnia? I have even looked under the "Samsung" key and still have not found the "Phone" key.
Any help will be much appreciated.
Click to expand...
Click to collapse
Sorry bro! I suggested for the HTC devices..

TOUCHFLO3D Caller ID screen

Hello,
Can anyone help me with the following situation:
I have a TD2 with the TF3D. Recently I installed the beta 5 version of Inesoft Phone 5.0 software.
It seems to be working everything ok, but I don’t like the Caller ID Skins that come with it, so I disable that program extension. The original one, that I think it’s from TF3D, is better.
My problem is that by disabling that option on Inesoft Phone, the Caller ID screen of TF3D doesn’t appear any more. When I receive an incoming caller it only appears that small balloon from WM6, with the picture and the name of the caller!
Does anyone know how can I restore Caller ID screen of TF3D?
Best regards
PS: sorry my poor English

In registry go to:
"HKLM\Security\Phone\Skin" and there:
key "Enabled" must be "1"
delete key "Ext"
delete key "PrevExt"
key "PrevEnabled" must be "0"

Thank you for your help.
I did like you said but the problem persists: when someone calls me, it only appears that ugly (in my opinion) WM balloon! The original TF3D caller ID screen doesn’t appear any more!
Any other idea?
Thanks

After Hard Reset, the registry for this was:
"HKLM\Security\Phone\Skin"
key "Enabled" is "1"
key "Ext" is"\windows\phcanhtc.dll"
"PrevExt" doesn't exist
"PrevEnabled" doesn't exist

Had the same problem; also found that the TF3D Favourites couldn't be called. Anyway, I installed the following which is the same as the original dialer & for the past week it's worked fine -
http://forum.xda-developers.com/showthread.php?t=499076
Steve.
(there are also diff colour skins available for this.)