I've been using iDialer and iContacts but recently ran into a kind of a timing issue where iDialer was either dialing the number too early or too late (I can't really tell) so I gave gVo a try, but it has some hurdles to overcome.
Namely, there is no way that I have found to force it to launch and dial numbers instead of the existing dialer. With iDialer and iContacts, iContacts would always supercede the Outlook contacts that launch by default, and all outgoing calls made from iContacts were routed through iDialer.
So I looked into changing 6.5's soft keys, tried doing it with a reg editor, this did not work. Also tried using an application I found here, two different versions of SoftKey Manager. I saved my changes, soft-resetted and the soft key actions were not changed.
I understand there is added complexity with 6.5 because scrolling through the different options on the Home screen changes the functions of the soft keys.
I'm using an HTC Touch Pro, and a MightyRom... uh... ROM...
If all else fails, I can simply try tweaking my config for iDialer, adding or subtracting some pauses... I believe my string currently looks like
<google voice><p><PIN><p><target area code and phone number>
Moved as not software release.
Related
Flashed to AustinSync's big ROM, like it a lot, but I've got a Tilt and can't stand the video dialer - not that it doesn't look nice, but the AT&T version is so much handier... As soon as I bring up the keypad, it shows the last 3 calls AND I can scroll up and down the ENTIRE list of call history right there on that screen. Even better, I can also flip thru their Mobile, Home, TXT, etc by pressing left and right!
Only problem is I'm not sure if I need to install an actual dialer or it can be accomplished via a registry edit...
WM6 Default Dialer
Reg Key change.
'HKEY_LOCAL_MACHINE / Security / Phone / Skin' and change the value of 'Enabled' from 1 to 0.
That will change the Dialer to the Default Windows Mobile 6 dialer. I like it better than the At&t and HTC dialers.
Sigh - the world is normal again! Thanks!
I am having an absolute FIT with the damn keyboard light on my 750! It gos off after about 5 seconds, and THAT is ridiculous! I was told by a source at Palm there IS a registry entry to fix this, but he could not divulge the info (I did tell him I was open to receiving an anonymous email, but haven't seen it yet!)
Anyone have any ideas? He said it was the same one that worked on the TyTn/Hermes/8525 but I have not found it yet....
Help??
HKEY_CURRENT_USER\ControlPanel\Backlight and key is QKeyLedTimeout. The number of seconds is usually set to default at 10. you can make it any number you like. Mine is set at 20.
I wonder if this also relates to my current issue too - can anyone comment?
The backlight on my Treo 750's keyboard refuses to come on IN USE - however I'm fairly convinced it's not a hardware issue; when performing a soft reset the keypad lights up fine during the boot cycle.
It's as if there's a registry entry that sets the "turn off keypad light after" value to 0 (i.e; always off).
Thoughts?
Cheers,
Steve
Found It in WM5
I traded in my WM6 phone for a Treo 750 with WM5 - wow, everything is where it should be, and the phone works the way it should!
As far as the On-Off issue, Steve, I see that in line in my phone - the key is set to 1, so I would try changing that:
HKEY_CURRENT_USER\ControlPanel\Backlight and key is QKeyOnOff change it from 0 to 1
Let me know - this could be my first crack at helping someone else out!!
I have a question. I can not seem to find the registry edit area for the Treo 750 running WM6. Can you help me in giving me some instructions on getting to this so I can edit the file to keep the keyboard lights on for longer than a few seconds?
on my kaiser it's set to 30 by default.
[email protected] said:
I have a question. I can not seem to find the registry edit area for the Treo 750 running WM6. Can you help me in giving me some instructions on getting to this so I can edit the file to keep the keyboard lights on for longer than a few seconds?
Click to expand...
Click to collapse
Hi there,
There is no default registry editor on WM devices, so you will have to install one if you want to make any changes. You will find a few built into well known commercial apps such as MemMaid and Resco Explorer (I've used both and they work fine on WM6). There may also be some free ones around.
Every time I type sms, my TP auto corrects and forces me to use words from its dictionary, instead of my intended word. Then it won't let me change its word. I have tried to turn off auto-correct and set suggested words to 0, but no luck. Please someone tell me how to stop this.
are u sure T9 is not selected?
I have same problem. With sms messages the word correction screws up my messages. I turned off the suggest words option under advanced config...but doesn't help the sms/mms messaging helper. Haven't tried registry hacks...might have to explore the registry a bit...
Manoli
Yes I am sure it is not selected. I am using slide-out keyboard anyway, but am sure T9 is not selected. Please someone must have come up with some way to stop this [email protected]@@@ing thing from changing all my words.
There should be T9 as a secondary function on one of the buttons on the slide out keyboard. For the FUZE it is Fn+right arrow. It brings up a menu to choose ABC or T9.
turning off word completion in either t9 or keyboard mode doesn't matter. The word completion still comes up. Doesn't seem to be a way to turn it off!
Try This. this should do the trick... hopefully!
http://forum.xda-developers.com/showpost.php?p=3241772&postcount=1668
I have disable word correction using the Advanced confing App 3.3
The Advanced Config. 3.3 application has been a great tool for me so far and allows for many customizations. I am using a Touch Pro and it was able to stop word correction on my device. If you are going to install Advanced Config tool, you will need to install Microsoft .Net compact framework 3.5 first. Hope this is helpful.
Anyone using the NATF fix? A few questions:
1. Does it solve the forced changing of words?
2. Does it stop all corrections such as auto capitalizing of 1st word in sentence? - (which I like)
3. Any side effects of using this program?
I like people like NATF that solve problems. Kind of a hero.
Krizza, I also use AC3.3. Under INPUT I changed suggested words to 0 (default). This didn't seem to do anything for sms. Is there another setting somewhere?
maybe it isn't Advanced Config......
Joe_PDA said:
Krizza, I also use AC3.3. Under INPUT I changed suggested words to 0 (default). This didn't seem to do anything for sms. Is there another setting somewhere?
Click to expand...
Click to collapse
I just assumed that it was AC3.3 that was stopping the "suggest words" function. I have mine set to 0 (default) as well. My Touch Pro no longer suggests words when I'm texting, but I just checked out ,my phone and I have also adjusted START > SETTINGS > INPUT > WORD COMPLETION then I have unchecked the box that says "suggest words when entering text"......maybe that is what has been working for me all along.....hehehe
Krizza, I've had that un-checked all along. However the problem seems to have fixed itself when I reselected 0 (default) in AC3.3 then soft reset. It wasn't instant though, it seemed to correct after a few days. odd.
Using EnergyROM Genesis, no manila, on my Raphael, I've now installed the new Rhodium dialer with slide to answer. When getting a call, the WM dialer and the Rhodium seem to conflict. Sometimes, the slider will work and sometimes the soft keys that I recognize from WM will work.
Being worn out from previous experiences with S2U2, I installed Chobit Smartlock, which has its own slide to answer. Wouldn't you know, now there are three apps in conflict when I have an incoming call, with each only partially functioning.
How can I preserve the functionality of one of the non-WM slide to answers and mitigate this conflict? I'd really like to keep the Rhodium dialer and Smartlock is working for me otherwise, as well.
I know this is somewhat a combination of known issues, but my searches couldn't find this exact topic.
My screen goes crazy. During a call up to my ear it flips to horizontal, changes out of key pad view and not always to mute/speakerphone... keys view, sometimes to contact info, and can be a nightmare to get back to "end call." I've found times when the caller hung up but the TP2 put them on hold and kept my time going.
Any programs and or reg hacks to:
1) stop the horizontal flip when placed to an ear, and
2) keep it in keypad mode or general call mode?
Real pain when dialing into a system that requires keypad responses. Everytime I put it back to my ear I have to go through a crazy sequence to get back to the key pad.
This is my only complaint wth this phone, it's not easy to use as a phone!
Thanks.
I have the same problem when dialing into VM, or into any call queue. I looked through the registry a bit. Didn't see anything obviously labeled.
yeah me too. Only thing I could find was using Gyrators' exception list to not rotate the phone, but it wasnt 100% reliable. I would *LOVE* to find a way to stay in keypad mode too.
Hi All - I guess I'm just jumping on the bandwagon but I have the same issue and find it annoying. I loaded the 'incall screen tweak' but that didn't work. Any help more seasoned members than I could offer would be greatly appreciated.
Cheers!!!
I had the same issue too, whenever I put my phone up to my ear (left handed) it would go into landscape. The fix is simple but you have to edit a registry setting. I'm going by memory here, so please forgive the vague info
1) make sure to backup your reg info
2) using your favorite reg edit program, goto
HKCU\Software\HTC\HTCSENSOR\GSensor\Whitelist
3) now this is the part I kind of forgot, you need to find a string with the DATA value that includes "phone" or "dailer"
4) delete that string
5)soft reset and give it a try, the phone shouldn't go into landscape whenever you turn it during a call.
AstarteSV said:
I had the same issue too, whenever I put my phone up to my ear (left handed) it would go into landscape. The fix is simple but you have to edit a registry setting. I'm going by memory here, so please forgive the vague info
1) make sure to backup your reg info
2) using your favorite reg edit program, goto
HKCU\Software\HTC\HTCSENSOR\GSensor\Whitelist
3) now this is the part I kind of forgot, you need to find a string with the DATA value that includes "phone" or "dailer"
4) delete that string
5)soft reset and give it a try, the phone shouldn't go into landscape whenever you turn it during a call.
Click to expand...
Click to collapse
OK, I went where you said, but no dialer, and only phone entry is:
Phone/Lock/Compose/Picture
String= Dialog
And deleting this stopped "lefty" in call flipping? Doesn't make sense to me. Doesn't seem to only control dialer or phone.
Please confirm or anyone out there please help. I don't want to delete something don't understand.
Can I simple change Dialog to something like "Zero" or "0"?
MLT2004 said:
OK, I went where you said, but no dialer, and only phone entry is:
Phone/Lock/Compose/Picture
String= Dialog
And deleting this stopped "lefty" in call flipping? Doesn't make sense to me. Doesn't seem to only control dialer or phone.
Please confirm or anyone out there please help. I don't want to delete something don't understand.
Can I simple change Dialog to something like "Zero" or "0"?
Click to expand...
Click to collapse
That's it! forgot what the process name was, but yeah, deleting that stopped the phone from trying to change to landscape during a phone call. Deleting that will tell the G-Sensor not to change the orientation of the phone's screen during a phone call, however it also tells it not to change the orientation during a picture (which wasn't a big deal for me cuz I can change it when I view them in windows). You can always look up the process in google or even the forum search tool if you're still scared.
If anyone else is interested I tried a "partial" delete of the suggestion above. I created a new string leaving out the Phone.
Lock/Compose/Picture
String= Dialog
deleted old string with phone/....
So far no more "lefty" crazy problems, and pictures seem to appear in landscape.
Here's hoping all is OK!
MLT2004 said:
If anyone else is interested I tried a "partial" delete of the suggestion above. I created a new string leaving out the Phone.
Lock/Compose/Picture
String= Dialog
deleted old string with phone/....
So far no more "lefty" crazy problems, and pictures seem to appear in landscape.
Here's hoping all is OK!
Click to expand...
Click to collapse
Awesome, good job!
I installed Gyrator 2. Just create a new event with the phone as the application. Nothing for orientation, nothing on stylus, and rotate screen for actions. Then promote the event to the top. Highlight your new phone event and select orientation, it will have a check mark and a number one next to the event. It hasn't failed on me yet and I use the key pad all day long with my job!
I just upgraded to the Verizon official WinMo 6.5 and the registry hack doesn't seem to work anymore, and I'm having issues getting Gyrator to work, has anyone resolved this issue for WinMo 6.5?
AstarteSV said:
I just upgraded to the Verizon official WinMo 6.5 and the registry hack doesn't seem to work anymore, and I'm having issues getting Gyrator to work, has anyone resolved this issue for WinMo 6.5?
Click to expand...
Click to collapse
I haven't had any of the issues with the 6.5 upgrade that were mentioned with 6.1. Haven't needed to add S2U2 since the screen lock is built in and the phone is much more responsive when placed to the ear and then moved away to access the keypad. It's not perfect but vastly improved over 6.1...
I guess my point is try it the way it is with 6.5 and see if you thinks its better. leave gyrator and reg hacks aside for a few.