yashsingh1/xdaforums huggingface dataset:
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I only knew the Home and Back buttons could not be blocked completely, I did not know of the RED button. Is it hard to press the RED button? What is the difference with the Answer reject (End) button? Is it only available while there is a connected call?

The TouchPanel can only be locked, when other programs do not enable/hook the TouchPanel too. So it is possible this is not working for all programs.unfortunately. I am working on a simple foreground screen (to keep the memory low), so this would be the way to go for this situation. Maybe also there I can better block the keys, because I have a foreground window......
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I assume you did set HTCLockAPI = 1, because otherwise the send keys would be intercepted by the keyboard hook. You can try to set HTCLockAPI = 0, enable debug logging and see which codes are blocked by the keyboard hook.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Strange. Did you get this immediately after the first startup, or after the first lock, or when TouchLockAction is started? Which ROM do you use?

Is it possible that during download the CAB file got corrupted? Or during copy?

I assume you copied the CAB file to your phone and then installed it by running the CAB file on your phone? Did you install it on your phone memory or on the memory card? Did it give problems during installation?
[Touch Diamond, MDA Compact IV Themes and Apps] o.k.:
It is indeed answer reject button. In my scenario it remains obviously unlocked while not in a call (there are no explicitly unlocked buttons set).

More precisely: I assigned a long press of the call reject button to run the action screen. While the phone is locked, the action screen comes up after long press. The touch panel is locked, so it is not possible to tap on any icon on the action screen.
[Touch Diamond, MDA Compact IV Themes and Apps] hugr:
I have downloaded the CAB file from your site (again); copied it to my SD card and reinstalled it in main memory. I get the same result. Phone does not lock and I get the Error report. Everytime the phone comes out of standby it generate such an error. In spite of the error the program seems to continu running but doe not lock.
[Touch Diamond, MDA Compact IV Themes and Apps] o.k.:
one apparent difference is that it uses broadcomm BT stack, not MS one.

ZuinigeRijder, maybe there are some BT init actions that cause this? Do you have any reports on successful run on touch pro2?
[Touch Diamond, MDA Compact IV Themes and Apps] hugr:
The Microsoft Error log indicates:

EvntType: WinCE501bExeptio

AppName: TouchLockPro.exe

AppVer: 5.2.0.0

AppStamp: 4a7e9bd3

ModName: touch.dll

ModVer: 5.2.0.0

etc.

I can give the rest if this helps.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Touch Pro 2 and Bluetooth problem?

Previously I used a API for detecting bluetooth active.

However, I switched into querying a registry key:

HKLM\\System\\State\\Hardware\\Bluetooth

So I think it is not related to bluetooth.

But you can check, by disabling bluetooth (which is default) in the TAPI settings screen:

DetectBluetooth = 0

Another problem can be the double touchpanel lock, you can try disabling this one in the keysboard settings screen:

DoubleTouchPanelLock = 0

Can people having this problem, enable debug logging and post the debug logging TouchLockPro.log.txt as zipped attachment. Maybe that gives me a clue :confused:
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Apparently something to do with the Touch dll:

ModName: touch.dll

You can try setting DoubleTouchPanelLock = 0, because for more people the default setting 1 is not working.
[Touch Diamond, MDA Compact IV Themes and Apps] wrecklesswun:
great app! just donated but the link above doesn;t work to well...sent to your email.
[Touch Diamond, MDA Compact IV Themes and Apps] JoeSchmoe22:
Detailed Debug Log

Attached is a detailed debug file. I took two incoming calls and was able to answer both calls while still locked using the soft answer key on the caller ID pop-up.

First call was at 17:41 while the device was on but locked.

Second call was at 17:42 while the device was turned off and locked.

Also, while still locked [from 17:43 - 17:44], I was able to repeatedly tap the start menu, navigate to the device root folder and make a copy of the log file. I did this to help you evaluate the screen not being 100% locked.

Let me know if I can help more.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
many thanks for the first donation!

I just configured my PayPal account and for me it is the first time I added a Donate possibility.

I did receive your donation via PayPal.

What was not working so well during your donation?

Thanks,

Zuinige Rijder Rick
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I tested with the following settings overruled (the rest default):

lockindicator = 0 // So no pixel is seen when unlocked, but a pixel is seen when locked

clockheight = 1

clockwidth = 1 // 1 pixel BattClock

unlockonlightsensortime = 0 // no unlock on light seen

vibrate = 1 // vibrate twice when locked, once when unlocked

With these settings I could unlock by capacitive touches :)

I am now confused why this is not working at your side :confused:

I tried also with setting locktouchpanelonly = 1.

Also with this setting I could unlock via the triple tap :cool:

Anyway, I think I will officially release 1.5, after I have looked at the problem in post #242.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Help with "locktouchpanelonly = 1", is it working for others??

Thanks for the testing effort.

Hmmm, I looked into the log file and I do not see anything strange. TouchLockPro tried to disable the TouchPanel regularly.

I tested myself with the following overruled settings (rest default):

clockx = 185

lockindicator = 0

locktouchpanelonly = 1

unlockonlightsensortime = 0

vibrate = 1

It is working with my TD :) So I think this has to do with the CDMA device you have :mad:

Is the caller ID popup different than on a Touch Diamond?

Are the soft keys different on a CDMA device?

I have no clue, why it is not working on your phone.

Do others use "locktouchpanelonly = 1" and do not have problems with incoming calls?

Hope that others can help in getting things clear :eek:
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Uploaded version 1.5

I promoted 1.5 WIP version to an official version 1.5.

Please help each other to make TouchLockPro better. I am glad to hear feedback (positive and negative). What works for you, what does not work for you.

Special request:

are people using "touchlockpanelonly = 1" and have problems with the locking of only the TouchPanel? See also post #245
[Touch Diamond, MDA Compact IV Themes and Apps] jodeltje:
I have a gsm based diamond with 1.5 running and it seems when the phone goes in suspend mode and I push the power button, it shows locked but isn't... But when I push the power button to turn my phone off and push it again to turn it on (within 3 seconds or so) it does lock the touchpanel.

I think it has something to do with suspend mode (or whatever it's called)...

UPDATE: I messed around with the powersaving options in advanced config a bit:

I enabled all powersaving options...but also "battery resuming from suspend timeout" from 1 to 90 seconds... maybe there's something? because I can't recreate a locked indication and a nonlocked screen??? IT WORKS!?! HUH?

I'll check back when I'm from work to see if I've fixed it somehow.
[Touch Diamond, MDA Compact IV Themes and Apps] fireweed:
First of all, excellent work! This is a very creative use of the available hardware to solve a very important problem.

One thing that's kind of weird to me is that I want my device to be locked when I put it in my pocket but when I lock it by clicking the icon it does not suspend the device, just locks it. Even worse it locks the power button so I cannot turn it off that way. I have to wait for it to time out and shut off on its own. It would be nice to have an easy off mechanism the way there is an easy unlock (triple tap). Perhaps having an option to lock on power off the way there is a lock on power on?

The other thing I noticed is that when it is locked and suspended you cannot turn it back on for about 30 seconds. Is it tied to the backlight in some way?
[Touch Diamond, MDA Compact IV Themes and Apps] GriFolle:
Same jodeltje'issue here...when the device wake up (not ever, but very often) batclock is showing that it's locked, but it's not..I'm totally able to use my touchscreen...
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Thanks for the good thinking. That is the spirit we need :D

I also enabled with advanced config a lot of powersaving options. The setting "Battery resuming from suspend timeout" is set to 10 seconds at my phone. And my TD does seem to work with "locktouchpanelonly = 1" during testing.

Maybe you solved the mystery :eek:

Would be great if this *IS* the solution for the problem.

What do you mean by "gsm based diamond". Is that just a regular Touch Diamond or a special branded one? Or a variant of a CDMA one?
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
The 30 seconds is not tied to the backlight. Normally, when the phone goes the suspend, applications have 20 seconds to react on the suspend, before it goes really to suspend. I use this also in TouchLockPro to trap power off/power on events. So this is the behaviour of Windows Mobile and not specific to the phone.

Instead of pressing the battClock, you can just Power Off the device, because the default setting AutoLockOnPowerOn = 1, will make sure the phone will be locked at power on. There is a little inconvenience with this setting. When you have an incoming call and the screen goes off, and the incoming call is ended or you want to end the call the phone is locked too. So you need to unlock first :mad: Till now I do not have a solution for this, I am thinking hard about this problem :cool:

Anyway, I am working on a separate action screen program with different options to power off the device (see post #2 for a screenshot). You can couple this to a hard or soft key, so you do not need to press the power button always.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Thanks for sharing this.

Did you also have those powersaving options set as described in post #247?

Is it working Ok with default setting "LockTouchPanelOnly = 1" :confused:
[Touch Diamond, MDA Compact IV Themes and Apps] jodeltje:
I ment NOT the cdma one but the regular one, because the post you were referring to was about a cdma one...

I really hope this fixes it too, and I'm pretty confident it has (for me)... It works flawlessly now on my phone. :D
[Touch Diamond, MDA Compact IV Themes and Apps] JoeSchmoe22:
CDMA help

Here are some links to threads that could possibly help explain the CDMA version difference:

http://code.google.com/p/answerkeysdisabler/issues/detail?id=4

http://xdaforums.com/showpost.php?p=2781974&postcount=486

http://xdaforums.com/showpost.php?p=2809117&postcount=501

Hope this helps in some small way. ;)
[Touch Diamond, MDA Compact IV Themes and Apps] 4D3:
I have same issue too
[Touch Diamond, MDA Compact IV Themes and Apps] GriFolle:
Yes, I've enabled theese power management settings (because of I'm using a Swto's rom wich enbles theese "by default") but don't think they are so important...anyhow, following your words, I've set the "resume battery" to 10 sec as you.

The problem is still here...

:(
[Touch Diamond, MDA Compact IV Themes and Apps] GriFolle:
A small update:

I've unistalled 1.5, erased all reg. keys, installed back 1.4...

the problem seems to stay always there!!!
[Touch Diamond, MDA Compact IV Themes and Apps] ericsson68:
OK can any body help?

I've sat in complete darkness to test I'm not going mad, called myself and the phone still unlocks after 5 seconds no matter what I do - rendering this software a bit useless for my requirements i.e. not answering calls while in my pocket.

What am I doing wrong as no one else seems to be experiencing this or has noticed?
[Touch Diamond, MDA Compact IV Themes and Apps] jodeltje:
maybe an annoying/dumb questio, bit do you have 'unlockonlightsensortime' =0? that would disable the auto unlocking after 5sec by the lightsensor.

maybe you overlooked this... (probably not)
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Hmmm, according to the links it has probably to do with another locking mechansim for (some) CDMA phones. Actually, the LockTouchPanelOnly method is the same for answerkeydisabler as for TouchLockPro.

That means for people having problems with the locking of the touchpanel only there is till now no solution. And the only thing they can do, is just lock hardware keys and touchpanel.

Actually, that is safer too, you never press accidently hardware keys too.

However, with that approach there are some inconveniences. I will summarize in another post.
[Touch Diamond, MDA Compact IV Themes and Apps] o.k.:
Hi ZuinigeRijder,

kinda consulting question, asked in a different forum:

- is it possible to implement the following scenario: all the time the phone is unlocked and only during incoming call hardware keys get locked?

With hardware keys it is simple (TAPI->KeysOnly), I answered this, but is it possible to avoid locking all other time??
[Touch Diamond, MDA Compact IV Themes and Apps] hugr:
After setting DoubleTouchPanelLock to 0 I do not get the problem reports anymore. Thanx.

Some other remarks (i have a dutch user if):

1-in the Batterij Klok screen "uu-dd" is displayed, this must be "dd-mm".

2-in the Software Invoer Paneel the options are English and different from the options in the manual (which are Dutch!).

3-on my Pro2 the penin/penout function is not working
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Yes, this is possible by setting the settings:

AutoLockOnPowerOn = 0

LockWhenIncoming = 1

LockWhenIncomingKeyOnly = 1
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Ok, I will check the dutch translations.

For point 3, this means that TouchLockPro does not show correctly if it is out or in? There is a known issue that if you reset the phone, without putting in the stylus during boot, HTC reports the wrong registry value.

Another problem can be that the Stylus Sensor is nor working correctly (dust?). You can try to gently blow away dust, after removing the battery. I assume it has a stylus sensor, because the Pro had.
[Touch Diamond, MDA Compact IV Themes and Apps] rickd26:
TouchLockAction Load Time

I use mostly the SUSPEND button as I want to minimize the use of the power button.

If it will not consume too much memory, I think it maybe worth considering to keep TouchLockAction in memory also. Or, can you suggest other way(s) to quickly access and execute LOCKSUSPEND command aside from using stylus or GSENSOR? I'm thinking something like a a shorcut or program icon on the Today screen.
[Touch Diamond, MDA Compact IV Themes and Apps] Mandragore:
You can set CapacitiveCommandsWhenUnlocked = 1 and bind one of TLP's Capacitive Swipes to !LOCKSUSPEND. And yes, you can create a shortcut with this command: "TouchLockAction.exe" !LOCKSUSPEND

Once you have created the shortcut, not only can you add it to your Start Menu folder(s) and other launchers. You can also quickly launch shortcuts with applications like AE Button Plus and GScroll.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Hmmm, TouchLockAction is written in C#, known that it starts slow.

However, I have made a small exe, TLPSuspend.exe, which does only one thing: Inform TouchLockPro to !LOCKSUSPEND. So you can put that e.g. in your programs menu. And yes, this one is bloody fast ;)

Just unzip the attachment and put the exe somewhere on your phone. It does not have parameters, so by just starting, it will locksuspend.

Hope you like it :D Probably I will add this in a next release, part of the installation.
[Touch Diamond, MDA Compact IV Themes and Apps] Cobaltikus:
I have used HTCLockAPI = 0 ever since it was an option because I use buttons to unlock.

THAT IS AWESOME!!!! Thanks - I will enable debugging and that will tell me which codes I need to unlock.

Problem Solved!

Thanks again!
[Touch Diamond, MDA Compact IV Themes and Apps] Cobaltikus:
What should I look for in the log to determine which button was blocked?

EDIT: Found it "LLKeyboardHookCallbackFunction hooked: 233"

For some reason on this rom I just flashed "EnergyROM", the Home key is 233.

Another thing about this rom is that the Stylus Sensor doesn't work - but that is not because of TLP - just a ROM issue.
[Touch Diamond, MDA Compact IV Themes and Apps] Cobaltikus:
Unlock Volume Issue

I can't seem to unlock the volume keys completely.

From the log file it appears to be codes 117 and 118, but it also shows 38 and 40.

So I unlocked all 4 (38,40,117,118).

But when the phone is locked, and I press volume up a few times, the volume screen comes up but the volume does not change. I do however notice that the stripe flashes every time I press vol up or vol down and so does the screen. Maybe that is interfering somehow?

I am using "EnergyROM" but I have had this problem consistently with many different ROMs.

It seems to only affect roms with the full screen volume control (as opposed to the default Windows Mobile volume that drops from the taskbar.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
38 and 40 are the decimal values, so these are:

# 38 = Up: VK_TUP = 0x26

# 40 = Down: VK_TDOWN = 0x28

Maybe the volume down/up do generate a up/down too :confused:

What I think is that the keyboard hook procedure takes too much time (although I highly optimized it), so the repeat Volume Up/Down is too slow for the Volume control and as such does not react. I have the same issue on my Touch Diamond. I do not think it is related to the BattClock redraw. But you can try stealth mode, because that will not redraw....

maybe that gives some insight?
[Touch Diamond, MDA Compact IV Themes and Apps] Cobaltikus:
Problem still exists in stealth mode... not a big deal though I guess.
[Touch Diamond, MDA Compact IV Themes and Apps] Hambonedk:
Suspend, but no lock on Touch Pro

Hi

I've tried installing TouchLockPro on my Touch Pro phone in several different versions, both before and after upgrading the phones' firmware (it is now at 5.05, I think), but my problem is always the same. The phone reacts to the different inputs exactly as decribed except for one thing: It never actually locks or unlocks the phone!

It blanks the screen when it should do a suspend, but the keys are not locked.

It clearly detects the stylus out/in gesture, but doesn't lock.

The slide in or out are also detected, but again, the phone doesn't lock/unlock.

What could be the problem, you think?

Hambone
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
More people have problems with the double touchpanel lock, so you can try:

DoubleTouchPanelLock = 0

Make sure to do a soft-reset after applying this setting.

If that does not work, you can try setting:

HTCLockAPI = 1.

If that still does not work, you can enable debug logging (LogDebug = 1), reproduce the problem and post the log file \TouchLockPro.log.txt as zipped attachment.
[Touch Diamond, MDA Compact IV Themes and Apps] bjorn78:
Tried this app on my touch pro2. When the device is locked I cannot use the volume buttons to control the volume. Pressing once will bring up the htc volume (full screen) control and pressing again will bring back the home screen.

However, if I first turn off the screen (without locking the device), then the volume buttons are working fine (while listening to music in my headset). Then turning on the screen it is still possible to control the volume! So the current state the device is locked and volume control working. But now it is not possible to unlock the screen with the unlock key I specified (114). So I then need to pull out the keyboard or stylus to unlock...

So the issues are:

1. From an unlocked state, turning the screen off and then using the volume control buttons while the screen is still off will affect the locking/unlocking as when the screen in powered on the device is locked but cannot be unlocked with the a key.

2. From screen state on, locking the device and then trying to use the volume buttons will just bring up/down the htcl volume control, so the volume cannot be changed.

When I say screen off or on I mean by pressing the power button.
[Touch Diamond, MDA Compact IV Themes and Apps] Alkerion:
Hi !

Just installed V2.7.2 on my Touch DH, and the volume down/up to unlock doesn't work.

The vol down is not working when phone locked.

Is it due to my rom ?

BR
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Issue 2 is a known issue and is described in this post

Issue 1 seems that TouchLockPro cannot apply the Keyboard hook, because some other program uses the same keyboard hook procedure. It is also possible that the DoubleTouchPanelLock gives this issue, so you can try DoubleTouchPanelLock = 0.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Keyboard unlocking is only possible with setting HTCLockAPI = 0. Do you have this setting?

Can you check that the answer/reject keys are really locked :confused:

If not, TouchLockPro could not get the keyboard hook.

Can you enable debug logging, reproduce the scenario and post the log file \TouchLockPro.log.txt as zipped attachment.
[Touch Diamond, MDA Compact IV Themes and Apps] Alkerion:
Okay,

It works now, more or less.

Phone react to vol down, but only one time, I cannot reduce the volume when locked.

When I press vol dw then vol up the phone unlock but stay on volume control panel for a few seconds.

BR
[Touch Diamond, MDA Compact IV Themes and Apps] cichy3000:
Hi :) could You write an additional thing for this ? program ? if touchlock IS locked then program sends to TouchLockPro !Unlock otherwise when IS UNlocked it sends !LOCKSUSPEND - sort of program toggler (On if Off, Off if On)
[Touch Diamond, MDA Compact IV Themes and Apps] cichy3000:
Hihihiih, I wrote sort of that program, it looks at registry.txt, gets path to registry, then to subkey then to default value,

Software\\ZuinigeRijder\\Status

IsLockedStatus

0

if value is true (is default) then program runs program from: executeiftrue.txt

path:

\Program Files\TouchLockPro\TouchLockAction.exe

argument:

Lock

else it runs program from: executeiffalse.txt

path:

\Program Files\TouchLockPro\TouchLockAction.exe

argument:

ScreenOn

but here i have problem with addition arguments of touchlockaction ... what arguments shopuld i use to Lock / Unlock (unlock with screen and backlight and keys in ON state...)

so ... now with link to power button (for ex. short click) we can toggle lock / unlock status...