does anyone know of a responsive dialer? I am looking for an original looking(bigger buttons would be nice) dialer that doesnt have a delay between pressing and recognition/drawing/tone. The lag time on all the dialers i have used seems excessive. I wonder why, as response to screen presses are quite snappy otherwise.
sorry I am no help here..............I would like to see a dialer that is more responsive too. I imagine it has something to do with how fast the processor can process the little app's requests...........not too fast it appears.
i dont know about wm6, but i'm using wm5 and turning off smartdialing helps A LOT, well not much help if you do use smartdialing...
mthomas said:
does anyone know of a responsive dialer? I am looking for an original looking(bigger buttons would be nice) dialer that doesnt have a delay between pressing and recognition/drawing/tone. The lag time on all the dialers i have used seems excessive. I wonder why, as response to screen presses are quite snappy otherwise.
Click to expand...
Click to collapse
I gained some speed by deactivating the sound of the keys when you press them
I did global search on the forum and found this one, so I'll just add comment on this one rather than creating a new thread
pfmboidi said:
I gained some speed by deactivating the sound of the keys when you press them
Click to expand...
Click to collapse
i only got a tiny bit improvement, my cheap nokia 3210 that came with T-mobile pre-paid card was MUCH MUCH MORE responsive!!!
I'm totally frustrated, it took up to 3 seconds to dial 1 number, consider the following:
- in order to improve the performance I need to turn the key sound off, so I have to keep looking at my screen
- pressing a button can fail altogether or can work with delay
- if i don't see the number you pressed immediately on the screen I have 2 options:
-- press again, but this can work OR create DOUBLE PRESSES
-- wait and see if it's just a delay, sometimes i wait only to see that I NEED TO PRESS AGAIN
this is OK when i don't badly need the phone "feature" and all the other bells and whistles distract me from thinking I'm supposed to have a dependable phone in this stupid device.
let me know if there's any smarter way around this and how do you guys deal with this? is iphone much more responsive when it comes to phone?
I think the real problem is that MS really doesn't care. If iphone (my wife has one) could do decent secure exchange I would dump this turkey of a phone and go that route. It is excellent as aphone except for the lack of voice commander and most of the pda functions are great as well. I n fact ifyou eliminate the ability to add a bunch of beta aps that are trying to imitate the user interface of a competing product, and screw up you r phone after a couple of days, what is the advantage of a wm platform?
My new HTC S740 is excellent except for one thing - the keypad backlight goes out after only 15 seconds. Very irritating in the dark.
I've looked for kb_light_timeout in hklm/software/htc/keypad but this does not exist.
I've found keylight timeout and qkeyledtimeout in hkcu/control panel/backlight which looks like the right place but altering values and rebooting makes no difference.
I've also looked in hklm/drivers/builtin/keylight and keypad.
I feel I'm very close. Can anyone help?
Yes Its most annoying as well as fact that only numbers or keys round circular button light seperately. Look forward to someone cracking it. Otherwise an excellent phone.
I agree, this is very annoying.
So theres no fix for this issue? To bad no ACT for this phone. An awesome phone, just wm standard gets so little love it seems.
I did some research today and he're the results:
1. This is far of to be a new issue. First complaints about the keyboard backlight timeout you can find under Qtek models...
2. Apparently, they were just few (2-3?) HTC models supporting a registry entry included in WM hkcu/control panel/backlight/QKeyLedTimeout - Rose definitely doesn't
3. The issue could be a case of WM 6.1 limitation - Rose has in fact three keyboard backlight arrays with separate light managements (soft keys, numeric, QWERTY - try to use them simultaneusly and you will see - their timing is independent on each other) and I've found some extra HTC registry entries concerning power management confirming a bit non-standard settings. Unluckily, nothing useful there for the kb backlights.
Sorry, based on my experiments, I can advice you only one very strange way how to overcome it for now: Limit the display timeout to the same 10 seconds as the keyboard has. At least, first press of any key will become inactive and just light-up both display and keyboard. Until display works, all keys are still active even the keybord backlight is off.
Nevertheless, any opposite finding will be appreciated...
Thank you for your investigation
I have a new s743 and this is the exact problem I came searching for fix for!
Too bad - it really is a sweet phone.
-John
To me this is a winmo thing. I don't understand why this option isn't included from the factory. It is a plain "NO BRAINER"! It's been this way on all my previous devices whether pro or standard. The diff being the pro os has wonderful tweaks and various cabs one can install to set the time out. What we need is to get some tweaking guru to set up something like ACT for standard. Problem is so little love for the standard os. The screens are to small anyway for my taste. I'll just stick to pro, the tweaks are better.
Well, i set the display timeout on my device to 5 seconds. Backlight of the qwerty and numeric keypads went off after 5 seconds.
The softkeys remained lit till 10 seconds was up.
TouchLockPro is not exactly new (currently at version 1.9), but it was posted in the Diamond thread, because there things started. But because other phones are also supported, maybe the TouchLockPro thread could move to here. If this cross posting is not wanted, I hope the moderators let me know how to continue. At the Diamond thread or in this one?
But Windows Mobile has an OEM screen locker!
Yes, Windows Mobile locks the screen, but unlocks the Answer and Ignore buttons as soon as a call rings, so it is useless. The same happens when any notification pops up, the Snooze and Dismiss buttons are enabled even when screen is locked, leaving them vulnerable to any accidental touch.
Supported phones (known)
Touch Diamond
Touch Pro
Sprint CDMA Diamond
Touch HD (only triple touch capacitive sensor for unlock does not work)
Summary
There are already a lot of applications to disable touchpanel and/or hardware keys for the Touch Diamond and Pro. I added yet another one:
* lock using the Power button, BattClock and/or Stylus Sensor
* auto-unlock by the Light Sensor
* unlock using triple touch of the Capacitive Sensor
* unlock using Stylus Sensor
* unlock when on AC/USB power
Why is TouchLockPro better than other locking solutions
TouchLockPro is designed not to interfere with running applications and is a multipurpose locking application. Other locking solutions are often specific for locking only incoming calls/SMS. A lot of locking solutions also place a (transparant looking) Window on top of the running application (e.g. slide 2 unlock), so the information of the background application is no longer visible. This is not the case for TouchLockPro, so it can be kept lean and mean. Also the used resources is very very low.
Does TouchLockPro use much battery, RAM, CPU
Not at all, TouchLockPro is designed to be lean and mean!
TouchLockPro does not have noticeable effect on battery life. It only uses 33 Kb RAM in memory, whereas other solutions often use much more. For example S2U2 uses 4 Mb (125 times more) and PocketShield 1.7Mb (50 times more) memory. TouchLockPro uses 0% CPU (check it with a task manager!) and is totally event driven. Polling is kept to a minimum (currently only for polling once per second the light sensor when LOCKED and the screen is on). Requested features which would violate the "lean and mean" principle are rejected. Note that larger UI related stuff is done in a separate TouchLockAction.exe (e.g. editing settings), so the memory is only used when that program is active for a small moment.
Which other solutions exist
This is a list of other solutions, which may suit you better:
* Built in locking of Windows Mobile
* Stylus(BattC)lock
* Get A Reward! Create A "answer Only With Hw Buttons" Option!
* S2U2
* PDAVIET's dialer
* CSDEVCTRL
* SensorLock
* Answerkeys Disabler
* PocketShield
* ThrottleLock
Interested in *FREE* TouchLockPro?
I just posted TouchLockPro version 1.8.
I also posted the source code belonging to version 1.8. Hope you will learn something from it and you are inspired to make great programs too. At the end programming Windows Mobile is not so difficult if you have programming experience. Prerequisites for programming:
* Visual Studio, Express editions are free!
* Windows Mobile 6 Professional SDK (also free)
Note that others pointed out, that Express editions are not suitable for Windows Mobile development. See Smart Development for what is supported by which version. I used myself Visual Studio 2008 Professional SP1.
Note that TouchLockPro is written in C++ and TouchLockAction in C# (and deployed using .NET Framework 2.0).
Enjoy the software and source code
you can lock specific programs? waaahhh? this is what I've been waiting for for a very long time. downloading right now.
lennie said:
you can lock specific programs? waaahhh? this is what I've been waiting for for a very long time. downloading right now.
Click to expand...
Click to collapse
I do not know if HTC x7501 has the same sensor like capabilities. Does it work for you? Or do you have another phone too?
anybody tried with tytan II ?
shuren said:
anybody tried with tytan II ?
Click to expand...
Click to collapse
TouchLockPro uses the unique sensors since Touch Diamond was brought out:
* auto-unlock by the Light Sensor
* unlock using triple touch of the Capacitive Sensor
So probably those functions will not work on your phone. BUT I continue without those functions when the loading of the needed HTC libraries fails.
There is also a stylus sensor, but TouchLockPro just observes a registry key for detecting if the stylus is in or out. So you can check if that registry key also exists on your phone, before you try to install:
HKCU\ControlPanel\Keybd\StylusOutStatus
1 = out
0 = in
If this registry key does not exists, probably TouchLockPro will not work for your phone.
For the rest it is standard Windows Mobile programming, although the locking of the hardware keys may also not work. But the locking of only the TouchPanel should work (setting "LockTouchPanelOnly = 1". TouchLockAction is written in C# and needs .NET Compact Framework 2.0.
Note that controlling the locking only with the stylus is also doable, actually my first version only supported this:
StylusLock
So you could use TouchLockPro with only the Stylus (if that registry key is written) and/or LockTouchPanelOnly, you miss only some of the unlocking features. Actually if you only lock the touchpanel, you can assign the command "\Windows\TouchLockAction.exe unlock" to a hardware key for unlocking.
Hope this helps......
So you say it won't lock some hardware buttons...this won't get around the problem with Samsung i730 and the power off key?
No program I have found yet can lock that hardware key to prevent it from powering off while in my pocket
EDIT: Nevermind...it isn't supported on the i730 anyway
First of all:
Congratulations for your post. Didn't see a long time an informative post like this - your own program is introduced, the reason for doing it AND other existing solutions!!! Hat off to you.
ZuinigeRijder said:
I also posted the source code belonging to version 1.8. Hope you will learn something from it and you are inspired to make great programs too. At the end programming Windows Mobile is not so difficult if you have programming experience.
Click to expand...
Click to collapse
Thank you very much for sharing the source code. It is for sure helpful in both ways - to learn and to get inspired. I already took my hat off otherwise I would do it again.
StrykerC3 said:
So you say it won't lock some hardware buttons...this won't get around the problem with Samsung i730 and the power off key?
No program I have found yet can lock that hardware key to prevent it from powering off while in my pocket
EDIT: Nevermind...it isn't supported on the i730 anyway
Click to expand...
Click to collapse
Actually it does lock ALL hardware keys, even "Power Off" key.
But maybe you meant the "Power On" key (actually, the same key).
That is why TouchLockPro does also lock immediately at Power On or Screen On (due to an external event, incoming call, or via pressing the power on key).
Code:
// --------------------------------------------------------------------------
// HTC Touch Panel
//
// Reverse engineered from HTC's TPEnable.exe and TPDisable.exe
// --------------------------------------------------------------------------
#define IOCTL_HTC_HAL_ENABLE_TOUCHPANEL CTL_CODE(FILE_DEVICE_HAL, 2698, METHOD_BUFFERED, FILE_ANY_ACCESS)
struct STouchPanel {
BYTE n1;
BOOL bEnable;
};
DWORD nBytesReturned;
STouchPanel s = { 0, !disable };
KernelIoControl(IOCTL_HTC_HAL_ENABLE_TOUCHPANEL, &s, sizeof(s), NULL, 0, &nBytesReturned);
But indeed, it will not work on your phone
ZuinigeRijder said:
Actually it does lock ALL hardware keys, even "Power Off" key.
But maybe you meant the "Power On" key (actually, the same key).
That is why TouchLockPro does also lock immediately at Power On or Screen On (due to an external event, incoming call, or via pressing the power on key).
Code:
// --------------------------------------------------------------------------
// HTC Touch Panel
//
// Reverse engineered from HTC's TPEnable.exe and TPDisable.exe
// --------------------------------------------------------------------------
#define IOCTL_HTC_HAL_ENABLE_TOUCHPANEL CTL_CODE(FILE_DEVICE_HAL, 2698, METHOD_BUFFERED, FILE_ANY_ACCESS)
struct STouchPanel {
BYTE n1;
BOOL bEnable;
};
DWORD nBytesReturned;
STouchPanel s = { 0, !disable };
KernelIoControl(IOCTL_HTC_HAL_ENABLE_TOUCHPANEL, &s, sizeof(s), NULL, 0, &nBytesReturned);
But indeed, it will not work on your phone
Click to expand...
Click to collapse
Well right, power off/power on, but when the phone is powered off, I am not worried about it being power on by accident, only the other way around
Why can't any one make a program for WM5 that can disable the Power On/Off key?!?! Ugh!
Finally!
So far, this seems to be the best solution to accidentally pressing hardware buttons or screen buttons while the phone is in my pocket. When using bluetooth I was constantly hanging up on people. Also, I would accidentally call people with the phone in my pocket when an SMS or e-mail would "wake up" the phone and then 2 unknown presses of the hardware "answer" button would first bring up call history and then call the first person on the list. I'll wait a few more days and, if all is well, I'll make a donation. Thank you so much for your effort. (tried Sensorlock, S2U2 and Answerkeydisabler but none did the trick)
mspingeld said:
So far, this seems to be the best solution to accidentally pressing hardware buttons or screen buttons while the phone is in my pocket. When using bluetooth I was constantly hanging up on people. Also, I would accidentally call people with the phone in my pocket when an SMS or e-mail would "wake up" the phone and then 2 unknown presses of the hardware "answer" button would first bring up call history and then call the first person on the list. I'll wait a few more days and, if all is well, I'll make a donation. Thank you so much for your effort. (tried Sensorlock, S2U2 and Answerkeydisabler but none did the trick)
Click to expand...
Click to collapse
I am a bit surprised the other locking solutions do not work well together with bluetooth. Others reported indeed that TouchLockPro does not interfere with bluetooth and you can pick up the phone with bluetooth, although the keys are locked.
Enjoy the software
The other solutions worked with bluetooth but the bluetooth call connection would wake up the phone and activate either the screen, the hardware buttons, or both causing the accidental hang ups or calls. TouchLockPro locks both the screen and the hardware buttons. btw I have the touches set to 2 and the light sensor set to 500. Very convenient!
mspingeld said:
The other solutions worked with bluetooth but the bluetooth call connection would wake up the phone and activate either the screen, the hardware buttons, or both causing the accidental hang ups or calls. TouchLockPro locks both the screen and the hardware buttons. btw I have the touches set to 2 and the light sensor set to 500. Very convenient!
Click to expand...
Click to collapse
Good to know.
In the upcoming version TouchLockPro 1.9 I will introduce the ScreenOffWhenCallConnected option, so you cannot accidently press stuff with your ears. Also I will introduce the option UnlockWhenCallConnected, so you can still use the hardware keys, when the screen is off (e.g. for ending the call) and it is not locked when the call is ended from the other side.
Dependent of the bluetooth usage, if you have the phone in your pocket, you may want to disable these settings.
TouchLockPro version 1.9
I just uploaded version 1.9.2 on my new website.
See TouchLockPro thread for more details.
Many thanks to Dennis van de Sande, alias Mr_Q from XDA-Developers, for sponsoring/donating the website and domain.
I wish you a merry christmas and a happy new year!
Version 2.0
I uploaded version 2.0, which fixes some (small) issues and added some features, like unlocking when sliding the keyboard out (if available). See Version 2.0
[APP][Updated 11-01-2009] TouchLockPro version 2.1
I just uploaded TouchLockPro version 2.1. Hope this version is again more perfect.
TouchLockPro 2.2.1 with GSENSOR support for unlocking
I just uploaded TouchLockPro 2.2.1 with GSENSOR support for unlocking.
TouchLockPro version 2.3
TouchLockPro version 2.3 is available.
How to unlock using touchprolock?
Im using xperia (no gsensor, no light, etc) ??
royalbloodvi said:
How to unlock using touchprolock?
Im using xperia (no gsensor, no light, etc) ??
Click to expand...
Click to collapse
Then you must unlock with a key sequence, using TouchLockPro 2.8.2.
See http://www.zuinigerijder.com
Hi,
I wish I had the knowledge to create such an application, but I don't so I'll try to explain this idea as clearly as I can see if someone finds it interesting enough.
As you know some phones already have the built-in feature to turn OFF the screen when a call is established. This prevents accidental actions with your cheek and ear on the touchscreen.
Some phones have fancy sensors like light sensor and proximity sensor.
But many other phones don't have, so this tiny app would be very useful to all of them:
How should it work?
Very simple:
1. Detect when a call is established
2. Call the "Turn OFF screen" command (same as pressing the power button)
That's it.
This would be exactly like pressing the power button after call is connected, so there wouldn't be incompatibilities with other apps. Plus the phone behavior when call is finished would be the same as always, since it only called the same command as power button.
This tiny app then could be cooked inside many ROM's.
Well, it's very easy explained like this, but as I said, I don't have the knowledge to do it myself
If you feel like programming the app I will gladly be your tester (or should I say guinea pig? )
+1
Having the problem with accidental touching the buttons and so fort pausing or hanging up a established Call.
+1
Add the functionality of turning the screen back on after the call is dis-connected and I'm sold
A software like this would be manufacturer dependant. For HTC devices, check out Touch InCall Screen Tweak. This app works on all HTC devices, and is a great app.
You can also use DiamondTweak or Advanced Config and setup the device to suspend quickly when in call (but these apps might only work on Diamond).
longice said:
A software like this would be manufacturer dependant. For HTC devices, check out Touch InCall Screen Tweak. This app works on all HTC devices, and is a great app.
You can also use DiamondTweak or Advanced Config and setup the device to suspend quickly when in call (but these apps might only work on Diamond).
Click to expand...
Click to collapse
Thank you!
Although I have an Elf, and it's got no G-sensor and no light sensor, so it won't work on my device
But it's pretty close to what I'm looking for! Thanks!
Is there really no way to disable the "Green" "Home" "Left arrow" and "Red" button when I'm in a call.
Ive tried to disable the buttons with AEB-plus, but it still doesn't work while Im in a Call.
Is it just me that have the problem with time and time Pausing or Hanging up established calls, "thanks" to the "Hardware" buttons.
PS
Using Touch HD