yashsingh1/xdaforums huggingface dataset:
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Version 1.9.2 also had the area around the middle button as area 2. I will make a setting in the next version, so also the area around the middle button can be configured, for the ones who want easier capacitive unlock.

I assume you did use 2.0 and not the test version 2.0.3 (somewhere in these post above)? Because in version 2.0.3 I did some improvements on sometimes disappearing stripe/BattClock when LockIndicator=0 was set.
[Touch Diamond, MDA Compact IV Themes and Apps] fourcc:
definitively i will. thanks for your support!
[Touch Diamond, MDA Compact IV Themes and Apps] NLS:
CHECK? not clear?

sure I get it right?
[Touch Diamond, MDA Compact IV Themes and Apps] NLS:
BTW, ahem...

http://xdaforums.com/showthread.php?p=3133995#post3133995
[Touch Diamond, MDA Compact IV Themes and Apps] amnya:
Bug found when using TouchLock Pro

Dear ZuinigeRijder,

Lets start with a huge thanks you message from all the users of your BRILLIANT application. Your program is one of the MUST HAVE applications when using a touch screen mobile phone. (My case, HTC Touch Pro).

I noticed that you mentioned on the website donated from "MR_Q" that you did not test your application on slide out keyboard phones. I am glad to assure you that your program works perfectly on it. Some bugs are found ,but nevertheless, its one of the best programs ever.

Now, down to business. The bug occurs ONLY when you play with the settings of the ClockY and and the ClockHeight.

The bug is. When i set the ClockY to 5. To make the icon on the top menu go 5px down (to go below the battery bar). and change the ClockHeight to 5px lower as well. What happens is:

1. If for example you open the Start>Settings in normal mode, and then you open the keyboard. The Tabs at the bottom disappear, and the whole settings menu would look wrong, hand and uncontrollable. Its a weird activity.

2. If the keyboard is slided out, any comboBox controls, would become unusable, why? The text of the combobox selections would appear to write over itself.

For example: Instead of showing "This is my example" the combobox would show something like: " # " (the # is just the whole line of "This is my example" is being overwritten in the same block. The photo will explain MUCH more.

Once i change back those parameters back to the defaults. Everything is back to normal again. Weird.

Again, you have the best program EVER!

PS: If i need to ENABLE the answer buttons when a phone call is incoming! How can i configure that? Its annoying to touch the phone 3 times till it unlocks and then answer. The screen is disabled, GREAT, but why are the buttons disabled as well. Is this configurable? If so, how.

THANK YOU :)
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Sorry for the confusion. In the TouchLockAction settings you need to check/enable the CheckBox or uncheck/disable the CheckBox SuspendOnBacklightOff to change the setting.

SuspendOnBacklightOff = 0

Default it will NOT try to go to suspend, when the backlight switches from ON to OFF, because another setting is added to go to suspend after a timeout has expired after power on. If you do want to suspend, overrule this registry key with "SuspendOnBacklightOff = 1".
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Thanks for the kind words.

You can configure that only the TouchPanel is locked and not the hardware keys,, via the setting "LockTouchPanelOnly":

LockTouchPanelOnly = 0

Default it will lock the hardware buttons AND touchpanel. If you only want to lock the touchpanel, overrule this registry key with "LockTouchPanelOnly = 1" Please be careful with the non-default setting LockTouchPanelOnly = 1, because hardware keys can also be pressed in your pocket!

But probably, you only want this in when there is an incoming call. That is unfortunately not available. But people are using the TouchLockPro in combination with Slide to Answer PhoneCanvas. So they are protected by a locked phone (by accidently pressing the power button and hardware keys) when in the pocket and can use the Slide to Answer PhoneCanvas when there is an incoming call.

Then they configure commandCallIncoming (Incoming in the TouchLockAction Settings screen) for auto unlock when there is an incoming call:

"TouchLockAction.exe" unlock

Note that the double quotes are necessary to separate the command from the parameters.

The other problem, if i read correctly, has to do with the landscape mode (automatically when the keyboard is out). So the TouchLockAction screen is not prepared for this. Indeed I did not make the settings screens, so they look ok in Landscape mode. If I was a good programmer (yes, I was lazy), I would have make sure that it was also easy to configure in landscape mode. I will set it in the TODO/Wish list, but has not a high priority, because you can also operate with the Stylus.

And the other problem is about the position of the BattClock, when going outside the TaskBar area. Probably I cannot do anything on that, because it is an overlay and gives this effect when positioning this outside the taskbar area. And then Windows Mobile gets weird.
[Touch Diamond, MDA Compact IV Themes and Apps] NLS:
erm sorry but still not clear:

default WM behavior is to have it 0 (unticked) or 1 (ticked)?
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
SuspendOnBacklightOff = 1 (ticked)
[Touch Diamond, MDA Compact IV Themes and Apps] quicksite:
Just checking: Based on all research to date on SENSORS...

ZuinigeRijder, I know that by this time you have learned all factors of control with sensors in some of these phones. I know the T-mobile WING (HTC Herald) is not supported by your app. But are you able to say now, sort of definitively, whether those devices have *anything* that could possibly be used to accomplish at least part of your functionality -- to keep the touchscreen from accidentally getting activated by one's ear during a call?

I just am asking as a rule-out, because I have been subscribed to this thread trying to see what's possible. But before I unsubscribe (since my phone is not supported), I wanted to see if anyone here had any ideas about how any of this fucntionality might be approached for Wing/Herald type devices.

I am not an engineer or hacker. I'm an end user only. Thank you.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Actually, locking the TouchPanel (by power button) and screen off when in a call, is possible, because it uses standard Windows API's. However, then the unlocking should be done without the sensors. This is possible, by coupling a command to one of the hardware buttons:

"TouchLockAction.exe" unlock

So you miss the unlock features by the sensors, but you unlock by a hardware key coupled to the described command.

So in principle this should work (hope your phone will not be ruined by trying out, so be prepared for a hard reset).

I can give you also the 2 executables TouchLockPro.exe and TouchLockAction.exe (so without installation), so you do not need to install it on your phone, but you can try it out by copying it on your phone and just execute them. That is less harmfull. Probably you would run into the problem that the TouchLockAction is made for VGA resolution, but you can also configure via the registry.

What for features this would give you:

* touchpanel lock using the Power button, BattClock

* unlock via hardware key coupled to command: "TouchLockAction.exe" unlock

* BattClock or Stripe or Stealth mode

* Vibration possibilities when locked/unlocked

* Separate TouchLockAction program for Lock Screen, Lock Suspend, soft-reset and power off

* Unlocked when on AC or USB power

* TAPI support (call incoming, call connected and call ended)

* AppToDate support

And the relevant settings:

* SuspendOnBacklightOff

* AutoLockOnPowerOn

* LockTouchPanelOnly

* UnlockOnACPower

* Beep

* Vibrate

* VibratesLock

* VibratesUnLock

* UnlockWhenConnected

* UseTAPI

* UnlockWhenConnected

* ScreenOffWhenConnected

* LockWhenIncoming

* CommandCallIncoming

* CommandCallConnected

* CommandCallEnded

* BattClock, Stripe or Stealth

* ShowTime

* ShowBattery

* Clock12

* DateDDMM

* DATEMMDD

* ClockClickable

* ClockLockActiveTime

* ClockX

* ClockY

* ClockWidth

* ClockHeight

* ClockBackground

* ClockForeground

* LogDebug

* LogDebugDetailed

* SuspendTimeOutPowerOn

* FontSize

But of course, you have to figure out how to couple a command to a hardware key on your phone.

Let me know if you want to experiment with the 2 executables, because using that approach the only risk is you need to do a soft reset.
[Touch Diamond, MDA Compact IV Themes and Apps] amnya:
Dear ZuinigeRijder,

Again and again, THANK YOU for this great product. As for the topics above.

Thank you for clearing things out regarding the Panel Lock. And yes, you understood me correclty, I needed it to UNLOCK only on incoming calls. In other words, if you ever tried the program called AnswerKeyDisabler. This program disables the softkey Answer Reject when an incoming call arrives, allowing me to press the physical button to answer or reject. This is perfect.

My question is, wouldn't this solve my issue? I mean, to set the TouckLockPro somewhere to UNLOCK on incoming call, and then the AnswerKeyDisabler would take over. Shouldn't this do the trick? (Of course it would be perfect if its done from within your great program).

Regarding the other issue with windows, the problem is that i am not overlaying anything. I first downsize the height of the Icon on the Bar above and then i play with its Y axis accordingly.So its not overlaying any other sections except for the top bar.

Any ideas?

And again, congrats for this great achievement. You have successfully been a great helping hand in changing the universe to a better place and helping millions of people with this great tool of yours. Brilliant work. Bravo

Cheers :)
[Touch Diamond, MDA Compact IV Themes and Apps] 4D3:
hey all,

i have just installed this on Duttys v4 rom and it doesnt seem to work.

capacitative touch doesnt work at all, i have it set to unlock with 2 touches of area 1, i can press it as many times as i was but no unlock.

also, the stylus locking doesnt seem to be functioning properly, it unlocks when you take the stylus out, and locks when you put the stylus in, but when you cycle the stylus (i.e. remove it to unlock and replace it with in 1 second) to keep the device unlocked with the stylus in place, the device just unlocks, then relocks no matter how fast i do it.

i also changes it to have a time of 8000 (8 seconds) to replace the stylus, but no joy.

any ideas?

thanks
[Touch Diamond, MDA Compact IV Themes and Apps] quicksite:
ZuinigeRijder, thanks very much for prompt & thorough reply! Yes, I would really like to try the two executables -- and experiment. The timing is good because I am about ready to upgrade from Open Touch 6.5 to v 7.7, so I am prepared for reinstalling everything.

I will have to go back to top to re-read this whole thread to see how your app-suite integrate with A_C's s2u2. It's crazy but even after about 6 months with WING, 9 times out of 10 when my phone is in my pocket and it rings, by the time I have gotten it out the call has gone to voicemail! In the few times when I manage to get it out in time, when I've depressed the green answer graphic on S2U2's full-screen incoming-call display, the call fails to connect. I am sure this is prob mostly human error. I only mention this here because ultimately the baseline interest I have, as silly as it sounds, is to be able to answer a call -- then not have it hit hold or disconnect etc due to accidental touch-screen actions. I really do have 90% of my incoming calls screwed up or complete failures ever since my first touchscreen (t-Mobile MDA) 3 years ago.

... I will PM you with my email address, or you can reply here and tell me how to obtain the executables, thank you!
[Touch Diamond, MDA Compact IV Themes and Apps] nitroblu:
ZuinigeRijder

Thanks so much for this program! I don't know how I missed this! I was looking for sometihng like this for like 2 days straight on xda and Google before I left for a trip, in which this program would have really come in handy. I think it's because I used the wrong search words. I was afraid the only thing available was S2U2 (no offense meant to A_C, it's just battery drain is terrible on S2U2 lol).

Again, thanks!
[Touch Diamond, MDA Compact IV Themes and Apps] djkasmic:
@ zuinigeRijder: i want the programm to unlock automatically on incoming call but it doesn't work. i set the command "touchlockaction.exe" unlock but it doesn't work for me. have i done anything wrong??
[Touch Diamond, MDA Compact IV Themes and Apps] e.gammieri:
I've tried the 2.0.3 version on my htc diamon with Aztor.X rom and it work fine... also the capacitive sensors...

Great app!
[Touch Diamond, MDA Compact IV Themes and Apps] e.gammieri:
Wrong consideration... the capacitive sensors are reactives only on the first use of unloking mechanism, after that the sensors are no more reactives to unlock sequence :(
[Touch Diamond, MDA Compact IV Themes and Apps] yawpk:
zuinigeRijder,

when i press on the touch screen while pressing the poweron, phone wakes up and TLP activates. But before TLP activates, the phone also responds to the area i press on the screen and launch the program behind TLP.

this explained the few occassions that applications was launched in my pouch. As the phone wakes up in the pouch by accident and if the touch surface sensed the pressure at touch screen area, it launches the application under the touch screen but remain lock by TLP.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Actually, I have 2 different locking mechanisms:

1) locking the hardware keys AND TouchPanel (HTC API)

2) locking the TouchPanel only (standard Windows Mobile)

I can try if I can use the 2 mechanisms together, because now I enable input when suspended, because otherwise we get problems with the power button. In the new approach, I can still enable input, but I have then still locked the TouchPanel. I will give it a try.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
More people have problems with the capacitive areas, dependent on the ROM. I do not have a clue why that is. I never have this with the Touch Diamond with the official 1.93 ROM.

With respect to the stylus operation, these are the configuration options:

StylusOutDisablesLockMode = 1

Default it will disable lockmode when you take out the stylus. Earlier versions did not have this behaviour. If you do not want this (new) behaviour, overrule this registry key with "StylusOutDisablesLockMode = 0"

SuspendOnStylusIn = 1

Default it will suspend when you put the stylus in when in lockmode. If you do not want this behaviour, overrule this registry key with "SuspendOnStylusIn = 0"

StylusOutInToggleTime = 1000 decimal or 3E8 hexadecimal

By default, taking the Stylus OUT and putting back IN within the specified milliseconds, toggles the "lock mode". Overrule this registry key with another milliseconds value, if you need more or less time. If you specify 0, you cannot toggle "lock mode" anymore via the Stylus OUT/IN approach.

I think, you should set StylusOutDisablesLockMode = 0, because you want it to be unlocked when you take it out/in in the specified time, otherwise you want to lock it again, when putting the Stylus in.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Others are also having problems with the Aztor X ROM.

e.g. post #884
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Ok, I added the 2 separate executables in the attached zip file.

TouchLockPro.exe you can put anywhere on your phone.

TouchLockAction.exe should be stored in \Windows\TouchLockAction.exe, so they can work together.

How would I approach it:

1) start TouchLockPro.exe and wait till the BattClock appears after 30 seconds (or crashes ;-)

2) make sure to stop TouchLockPro.exe (kill via TaskManager, or start it again to disable the other instance or soft-reset)

3) change with a registry setting (e.g. PHM Registry editor) the created settings underneath HKCU\Software\ZuinigeRijder\LockSettings

4) TouchLockPro ignores functionality when it cannot be loaded, except I think when the Stylus registry key is not available. So make sure you create the registry key HKCU\ControlPanel\Keybd\StylusOutStatus = 0 if it does not exist (if it exists, probably the Stylus will be detected on the Wing :))

You can disable the sensors you are sure are not available, e.g.:

* UnlockOnLightSensor = 0

* LockTouchPanelOnly = 1

* UseStylus = 0

* UseSlider = 0

* UnlockOnLightSensorTime = 0

* CapacitiveToggleTime = 0

Thereafter power button to suspend the phone and put it on via the power button and see if the TouchPanel is locked.

If so, you can not unlock anymore, so do a soft-reset.

Couple a command to the hardware key: "TouchLockAction.exe" unlock

If something is not working as expected, enable debug logging (logdebug=1 and logdebugdetailed=1) and post the log file \TouchLockPro.log.txt (after stopping TouchLockPro) as zipped attachment.

Try if it works. If everything is working fine, you can make a link so TouchLockPro is automatically starting, but in the beginning I would go for starting it manually, till you are confident it works as expected.

Suc6.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I do not know if it is case sensitive, otherwise it must be:

"TouchLockAction.exe" unlock

Are you sure you have the correct double quotes, because someone else used the wrong double quotes from the SIP (Software Input Panel), probably you can try searching for SIP in this thread.

If still a problem, post a debug log file (logdebug=1 and logdebugdetailed=1) and post the debug log file \TouchLockPro.log.txt as zipped attachment.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Yes, this would work. They configure commandCallIncoming (Incoming in the TouchLockAction Settings screen) for auto unlock when there is an incoming call:

"TouchLockAction.exe" unlock

Others do this with Phone Canvas too.

I will try it myself, although I do not have a keyboard slider. So I can only set it to landscape.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I contacted http://www.ageye.de/ and Jörg will add support for automatic unlocking of TouchLockPro in combination with G-Alarm:

Hi Rick,

thank you very much! You’re great

I will implement this in the next version.

Jörg
[Touch Diamond, MDA Compact IV Themes and Apps] quicksite:
ZR, I must be blind. I have looked all over for that zip file, here, on your site. I just can't seem to find the specific zip you are referring to. Was it uploaded to your post above?
[Touch Diamond, MDA Compact IV Themes and Apps] fourcc:
my logs with some problems i find in TLP.

The most repeated problems i have are:

1.- can't turn on Device until i take stylus out (From time to time, once per day maybe - Very annoying)

2.- no lock but i can make a call or do some clicks until getting locked (several times per day - aprox 3-6 seconds - Annoying)

3.- tlp.log in use (Sometimes, newer versions has reduced this problem a lot - if killing TLA, problems goes away - i can live with it)

Chronology of some of the problems in the last 24H:

7-1-09

styluslockpro1.log.txt

22:25 no lock but i can make a call

22:28 tlp.log in use

8-1-09

styluslockpro2.log.txt

00:19 can't turn on until i take stylus out

styluslockpro3.log.txt

9:35 no lock at first & i can do some clicks until it gets locked

styluslockpro4.log.txt

10:43 no lock at first & i can do some clicks until it gets locked

styluslockpro5.log.txt

12.34 no lock at first & i can do some clicks until it gets locked

styluslockpro6.log.txt

2:22 can't turn on until i take stylus out

hope the logs helps you, ZuinigeRijder
[Touch Diamond, MDA Compact IV Themes and Apps] drjim:
neat but overwhleming

Very sophisticated, but so many options, I'm a bit overwhelmed.

Is there a way to set it so that the only unlocking mechanism is the light sensor? If everything else is turned off, will the small icon in the taskbar disappear?

Thanks.
[Touch Diamond, MDA Compact IV Themes and Apps] bill48105:
This works for me: Go into configuration (open TouchLockPro & click on 4 diamond icon on lower left of 5 icon screen) uncheck the unlock options you don't want leaving just UnlockOnLight sensor. Use right arrow to go to next screens. Check Stealth mode to hide icon. Keep in mind it will be very tough to answer a call in the dark or dim room. :D Heck could be dangerous if you can't call 911 or such!! :eek: You would likely want to at least leave the stylus option for emergencies or check the 'Lock Touch Panel Only' box so you can answer with the call button but consider the consequences of not being able to use the phone in the dark.. Play with the settings, you might find a combination you prefer over light sensor only.
[Touch Diamond, MDA Compact IV Themes and Apps] bill48105:
I can duplicate the exact same thing. Look for an area to touch that will show you it is reacting like the Start button area. Press the power button to put it to sleep. Place your finger where you know the Start button is & press the power button with your finger still touching that area. The Start menu will popup before TLP can catch it! I've also found that if you touch the upper right corner where task manager or the X to close a program is at it will register the touch too but I think that is unrelated.
[Touch Diamond, MDA Compact IV Themes and Apps] bill48105:
I have the same issue with TLP capacitive touch not working with Dutty's v4 rom but it worked fine with 3.6b. It works sometimes depending on what program is up but never when the Home screen is up. Later I found if I disable TouchFLO 3D from the Today screen it always works so I assume it must be a TF3D thing.

Perhaps Dutty used the rom from his new Touch HD as the base for this v4 Diamond rom & this problem is related to why TLP doesn't work with HD's?? Anyone out there with an HD try disabling TF3D from the Today screen to see? (Heck I could be completely off here, just a thought..)

Rather than going back to 3.6b, for now I turned off TF3D and installed Pocket Digital Clock. It is WAY lighter than TF3D and I prefer simple over flashy anyway. ;)
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
My fault, you are not blind :D

I did add it, but I had it more often, if you press the wrong save changes, it will not always save the attachments.

You should find it in post #916
[Touch Diamond, MDA Compact IV Themes and Apps] quicksite:
now we're talkin'! thank you.
[Touch Diamond, MDA Compact IV Themes and Apps] Kraize:
[REQUEST]

Please add an exceptions list or something of that sort. So if a specific app is running, and I suspend my device screen, so it doesn't lock at all. Suppose when I'm listening to music on S2P, It would lock it when I turn off my screen and decide to turn it on to switch a track, press play/pause, etc. I don't want to use the d-pad for those of you who will give me that answer :| So I kindly reqest that you add an exceptions to TouchLockPro so it doesn't lock in these exceptions.
[Touch Diamond, MDA Compact IV Themes and Apps] quicksite:
Well that's just plain kraize.

:D
[Touch Diamond, MDA Compact IV Themes and Apps] mspingeld:
Will this be reverted in the next version? It's happening multiple times per day. Thanks.