[UPDATES] TouchLockPro version 227 [Updated 2-8-2009]

[Updated 2-8-2009]
TouchLockPro version 2.2.7


Summary
There are already a lot of applications to disable touchpanel and/or hardware keys for the Touch Diamond and Pro. I added the next step of improvements:
* lock using the Power button, BattClock and/or Stylus Sensor
* auto-unlock by the Light Sensor
* unlock using a sequence of GSENSOR orientation changes
* unlock using triple touch of the Capacitive Sensor
* unlock using Stylus Sensor
* unlock using Keyboard Slider Sensor
* unlock when on AC/USB power
* auto-unlock at incoming call (you have a "Slide to Answer" on your phone): commandCallIncoming: "TouchLockAction.exe" unlock
* unlock by hardware key coupled to command "TouchLockAction.exe" unlock

Supported phones (known)
Touch Diamond
Touch Pro
Sprint CDMA Diamond
Touch HD (only triple touch capacitive sensor for unlock does not work)

Some people have problems with version 2.2.7, they do not have problems with version 2.1. Others have no problem at all (like me).

Version 2.2.7

• solved the stylus toggle time 99999999 .NET 2.0 bug and added extra logging in TouchLockAction (again)
• Reverted change: suspend when incoming call is ended (so it was a missed call) and setting SuspendOnBacklightOff = 1 or SuspendTimeOutPowerOn > 0, saves some extra battery

Version 2.2.6

• solved the stylus toggle time 99999999 .NET 2.0 bug and added extra logging in TouchLockAction
• solve the reported problem for some people, because of subclassing the foreground window, that sometimes the hardware buttons did not work anymore
• solved a small problem, when a call was connected, it was locked when ended (side effect of solving autolockonpoweron=0)
• suspend when incoming call is ended (so it was a missed call) and setting SuspendOnBacklightOff = 1 or SuspendTimeOutPowerOn > 0, saves some extra battery

Version 2.2.5

• Test version (on XDA forum)
• tried to solve the stylus toggle time 99999999 and added extra logging in case it is not solved
• solved a small problem, when a call was connected, it was locked when ended (side effect of solving autolockonpoweron=0)
• tried to solve the reported problem because of subclassing the foreground window

Version 2.2.4

• Changed default UnlockOrientationSequence into 343 (please reset to defaults (middle bottom icon in the first settings screen) if you want the default settings)
• No longer vibrate/beep when lock/unlock when there is an incoming call, to avoid stopping vibrate from call coming in
• solved a bug with autlockonpoweron=0 in combination with outgoing call and screen off/on
• I do no longer make a popup child window of the foreground window but just subclass it (own wndproc in front of it). This should solve the following problems:
• reported problem of the password screen disappearing after some time not used (black screen)
• waking up the device by pressing the power button the TF3D clock does not update until the device is unlocked
• PhoneAlarm running on SecondToday today screen, TLP is freezing repeating alarms.

Version 2.2.3

• Solved the problem with x taskbar button, which could crash TF3D

Version 2.2.2

• Solved the problem with the latest roms (Dutty v4, AZTOR X, 2.0.3) have issues with capacitive touches if TF3D is enabled on the Today screen.

Version 2.2.1

• Because the GESTURES where too sensitive, introduced UnlockOrientationSequence instead of UnlockOrientationChanges.. You can define your own sequence you like!
• The default orientation sequence is 8888 (so the sequence Portrait-UpsideDown-Portrait-UpsideDown-Portrait will unlock).
• Lowered the UnlockOrientationTime into 5 seconds (but if you used 2.2, that default will be in the registry and used)

Version 2.2

• Added GSENSOR orientation changes for unlock, see UnlockOrientationTime and UnlockOrientationChanges
• Reset call status for setting combinationautolockonpoweron=0 and lockwhenincoming=1
• Fixed problem that configured 1 touch for CapacitiveTouchesSequence unlocking did not work
• Added exit button in the Settings screens
  I am searching for a solution for the capacitive touches but right now the choices are:
  * Use light sensor to unlock
  * Use stylus or keyboard slider to unlock
  * Use GSENSOR orientation changes to unlock
  * Disable TF3D from Today screen (many Today clock plugins etc to use instead)
  * Don't use newer rom (e.g. Dutty v4 has the problem but v3.6b does not)
  
  Dennis van de Sande, alias MR_Q has sponsored/donated a website and domain.
  All the details and downloads of TouchLockPro you can now find here:

Code

http://www.zuinigerijder.com

[CajunReefer]

Thanks, but I find PocketShield v2.1 to be a little better. I'm still looking for the right one though!

https://www.wckediden.com/showthread...=pocket+shield


-Dennis

[scott8813]

new 2.2.3 update added!

[scott8813]

Just came in!!!!!! Try version 2.2.7!!!!!