Version 2.12.4 (7-3-2010) for all Windows Mobile touchscreen phones, *NEW* Proximity sensor support for Samsung and HTC having proximity sensor
Updated Russian (thanks to Vadim Bogaiskov) and Dutch translations (thanks to myself ;-) for BattConfig and TouchLockAction.
Visual feedback if a button is pressed
Do not do !SCREENON at end call when lock(suspend) command or bluetooth is active
Some commands are now also executed when not power on/screen on (lockscreen, locksuspend, suspend) to achieve the previous point
When multiple commands are specified, make sure to execute them via a request,so events related to a previous command are effected already (e.g. screen off).
Fixed problem that multiple commands where only executed the first time (e.g. Proximity disable/ignore problems)
Fixed possible problem that multiple commands could mean that an earlier one was not executed/overwritten
Version 2.12.3 (25-2-2010) for all Windows Mobile touchscreen phones, *NEW* Proximity sensor support for Samsung and HTC having proximity sensor
Added command !PROXIMITYIGNORE, so the Proximity sensor keeps in the state it was, for other applications. TouchLockPro wil not react anymore, till !PROXIMITYACCEPT command is used.
Added command !PROXIMITYACCEPT, so Proximity commands are accepted from then on.
Changed the defaults for better use of Proximity (note that those will only be overruled if not already set or by reset to defaults):
Proximity Sensor Time (ProximitySensorTime = 700)
Near (CmdProximityNear = "!SUSPEND")
Not Near (CmdProximityNotNear = "!UNLOCK")
New settings:
Lock (CmdLock = "!PROXIMITYACCEPT")
Unlock Call (CmdUnlockCall = "!PROXIMITYIGNORE")
Unlock No Call (CmdUnlockNoCall = "!PROXIMITYDISABLE")
Incorporated BattClock 1.9 improvements:
Possibly to show the info in columns instead of rows (option Divide Horizontally)
Added option to show Battery Temperature (updated once per minute)
Added option to show Battery Current in mA (updated once per second), great to see power consumption
Version 2.10 (1-1-2010) for all Windows Mobile touchscreen phones, *NEW* with Samsung SDK compatible Light Sensor and GSensor support
Added support for Samsung SDK compatible phones, G-Sensor and Light Sensor. Samsung Windows Mobile SDK 1.2.1 or 2.1.0 are now supported! Just install also the appropriate Samsung SDK (see downloads)
Samsung SDK compatible (SGH-i900 Omnia, SCH-i910 Omnia, GT-I8000 Omnia 2, SCH-m490/m495 T*Omnia, Omnia Pro, GT-B7620 Armani, GT-I8000 Omnia II, SCH-i920 Omnia II), Sensors: Light Sensor, GSensor
TouchLockPro tries to identify your phone type now automatically and disables not available sensors
I discovered that the HTCSmartTouchDll window is also available on Diamond and Touch Pro, so now I only subclass for ZoomBar when PhoneType is Diamond2 or Touch Pro2
Added PhoneType configuration possibility in Index Settings screen, best is to first select your PhoneType before changing other settings and soft reset after changing your phone type and settings.
Lock already at power off when AutoLockOnPowerOn = 1 and HTCLOCKAPI = 0 is used
Reintroduce and fixed Screen Off to Screen On, which was disabled in 2.8.1
Delayed Power On to Screen On when possible, so when the phone awakes without screen on (e.g. checking mail), no extra CPU is used by TouchLockPro which saves a bit power
Made it possible to use HTCLOCKAPI = 1 in general and only at incoming call lock keys only with the general keyboard hook
Improved HTCLockAPIWhenBluetoothActive
Made Bluetooth status detection event driven instead of polling on need and added debug logging for state changes
Version 2.8.1 (28-10-2009) now with improved GSENSOR and for all Windows Mobile touchscreen phones
Added setting KeepAliveAlways in Keyboard Settings screen, for people wanting the awakening for key sequence always. Note this will drain battery by 8% per hour on my phone!
Note that if another program uses the same hook mechanism as TouchLockPro, TouchLockPro cannot hook the keyboard (only 1 hook may be active in Windows Mobile).
PocketMusic is one of the programs having the same hook.
Possibility to control the LED's when the phone is locked (e.g. flashing LED's) for better visual indication the phone is locked
What possibilities does this give:
Power button is no longer locked, when locked, so you can just power off again (e.g. quickly checking the clock)
Unlock certain keys
Unlock the device via a key sequence (e.g. Volume Down/Up or middle button)
Unlock the TouchPanel only and keep the keys locked at incoming call (Slide 2 Answer)
TouchLockPro will also work on other brands (although the sensors will not work). Because TouchLockAction is designed for VGA, configuration is easier on those phones having VGA.
I will describe the settings.
HTCLockAPI (HTCLockAPI = 0) There are 2 methods for locking the hardware keys in TouchLockPro. The HTC Lock API, locks all the keys (including the power button) and the TouchPanel. This HTC Lock API is only available on the newer HTC phones.
The other (new) key lock method is a general locking method, using a low level keyboard hook, which also works on other types of phones.
This keyboard hook keeps the power button unlocked and the press is not detected.
The TouchPanel is not locked (TouchLockPro has a separate TouchPanel hook)
This makes it possible also to lock only the hardware keys (e.g. in combination with Slide 2 Answer at incoming call)
The Home and Back keys are blocked, but still they are detected by the phone, so when pressed, the phone will still go to the Home screen.
The general keyboard hook, makes it possible to unlock more keys or detect keys pressed, so also an unlock key sequence can be specified.
On my Touch Diamond, unlocking the VolumeUp and VolumeDown does not work correctly. Although unlocked, the change is detected, but the volume will not change, while the volume screen is shown. Therefore the keyboard hook is only applied when locked, to avoid side effects like just mentioned.
Default it will use the general lock method. If you want the HTC Lock method, overrule this registry key with "HTCLockAPI = 1"
EnableInputAtSuspend (EnableInputAtSuspend = 1) The HTC Lock API also locks the power button. To avoid power on button problems for some people/phones in combination with HTC Lock API (you enabled this one), this one is enabled by default. When using the general keyboard lock method, this setting does not have an effect. Overrule this registry key with "EnableInputAtSuspend = 0", if you do not want the power button unlocked at power off.
UnlockedKeys (UnlockedKeys = ) This setting does only have effect, with setting "HTCLockAPI = 0". Default no keys are unlocked. You can specify which keys you want to be unlocked. You must specify the decimal key values, separated by a space, comma or semicolon. For a list of virtual key codes, see here
A list of the most important keys:
8 = Back: VK_TBACK/VK_ESCAPE = 0x08
37 = Left: VK_TLEFT = 0x25
38 = Up: VK_TUP = 0x26
39 = Right: VK_TRIGHT = 0x27
40 = Down: VK_TDOWN = 0x28
91 = Home: VK_THOME = 0x5B
114 = Talk: VK_TTALK = 0x72
115 = End: VK_TEND = 0x73
117 = VolumeUp: VK_TVOLUMEUP, 0x75
118 = VolumeDown: VK_TVOLUMEDOWN, 0x76
129 = Power: VK_TPOWER = 0x81 (cannot be detected)
130 = Red Key: VK_REDKEY = 0x82
134 = Middle button: VK_ACTION 0x86 (at least on my Touch Diamond)
UnlockKeySequence (UnlockedKeySequence = )
This setting does only have effect, with setting "HTCLockAPI = 0", Default you cannot unlock with a key sequence. You can specify a key sequence (one or more keys) to unlock the phone. You must specify the decimal key values, separated by a space, comma or semicolon. See previous setting for the possibilities for the keys.
KeysOnly (LockWhenIncomingKeyOnly = 0) Default it will default lock (so including TouchPanel). If you only want the keys locked at incoming call (e.g. you have a Slide 2 Answer and want to take the phone via the slider), you can enable this setting.
DetectBluetooth (DetectBluetooth = 0) With this setting enabled, you can keep the phone locked when Bluetooth radio is on, do not unlock by light sensor and do not execute TAPI commands. By default this setting is disabled, if you want the bluetooth detection, enable this setting.
Light (DetectBluetoothLightUnlock = 1) This setting only has effect when DetectBluetooth is set. With this setting enabled, it will unlock on light sensor, when the Bluetooth radio is on. If you do not want this behaviour with DetectBluetooth, overrule this setting with "DetectBluetoothLightUnlock = 0".
LED number (LEDNumber = -1) You can configure which LED (beneath the hardware buttons) to be on, when the phone is locked AND on. Note that the LED will not be on, when locked after 30 seconds of power on.
Default no LED's is configured to be on. Some values for the Touch Diamond:
1 all button LEDs
2 Home
4 Call answer
8 Back
16 End call
32 Center
128 Pulse center once
256 Pulse center repeatedly
512 Home/Call answer/Back/End call
1024 Pulse center once/Home/Call answer/Back/End call
2048 Pulse center led anticlockwise spiral twice, pause and repeat
4096 all on
8192 all off, backlight off
Especially, 2048 is nice: Pulse center led anticlockwise spiral twice, pause and repeat. On other types of phone you must try which values work.
Changed the Settings screen to not maximized, so the start row is seen again
Added Light Sensor current value in Settings screen
Added GSensor current value in Settings screen
Added NavSensor current value in Settings screen
Added Stylus Sensor current value in Settings screen
Added Keyboard Sensor current value in Settings screen
Added Color picker in BattClock Settings screen
Realtime move of BattClock position via change of values
Added possibility of translations of the Settings screens
Store TouchLockAction in the same directory as TouchLockPro (no longer \Windows\TouchLockAction.exe)
prefix Capacitive NavSensor touches by T and GSensor Orientation by G in the BattClock
Added HKCU\Software\ZuinigeRijder\Status for IsLockedStatus, LightSensor, GSensor, NavSensor so other programs and TouchLockAction can listen to those keys
Added Portrait/Landscape for SIP (2 extra SIP possibilities for those which do not have a keyboard)
Lock TouchPanel always at "suspend/screen off" and unlock TouchPanel at "power on/screen on" when not locked
No longer close GSensor and NavSensor at suspend (does not save battery and better response)
Removed LogDebugDetailed setting, just use LogDebug
Version 2.4.1 (18-03-2009)
Fixed SIP bug: special characters in SIP name (e.g. German umlaut) was not working
Fixed SIP bug: when the same SIP name was chosen for different settings, only the first one was working
Version 2.4 (14-03-2009)
Added SIP (Software Input Panel) Changer: dependent of Stylus and/or Keyboard position choose automatically other SIP
Added possibility to disable the TF3D workaround (tab right - tab left) for the HTC bug of capacitive sensor not always working when on home screen of TF3D
Totally reorganised the TouchLockAction settings screens
Regrouped all the settings to the more functional/logical groups
Better navigation (index screen)
Optimized for VGA, so that each setting screen can be operated in portrait and landscape, without having scroll bars
In portrait there is more room for the SIP (Software Input Panel)
Black Theme
Hope these changes are appreciated.
Version 2.3.5 (25-02-2009)
sets the registry key HKCU\ControlPanel\GScroll\Disabled
sets the registry key HKCU\Software\ZuinigeRijder\ActionSettings\IsLockedStatus (so other programs can also see the lock status of TLP and can react on that)
in my debug log I saw an error orientation 7, an unknown orientation, so I ignore that now
I had a disappearing BattClock, looked into the log file and now show the BattClock in DestroyLockedWindow (I am not sure this will help)
Version 2.3.4 (24-02-2009)
Fixed bug, that a command with double quotes without parameters was not executed
Added internal command to TouchLockPro and coupled to capacitive swipe LeftUp: !BACKLIGHTON
Added internal command to TouchLockPro and coupled to capacitive swipe LeftDown: !BACKLIGHTOFF
Note that if you had an earlier version of TouchLockPro installed, with capacitive swipes, you can reset the settings in the first action screen (middle bottom button).
Fix/workaround the problem with TF3D Today Home screen, that sometimes capacitive touches are not sensed:
simulate a right key press followed by a left key press (after 2 seconds). Note this will only be done when the following conditions are met:
when at power on
when no incoming call
when capacitive is enabled (CapacitiveToggleTime > 0)
when TF3D is the foreground window
This is a kind of hack, till I find a better solution.
Version 2.3.1 (19-02-2009)
Fixed bug that changing the GSensor orientation changes were not picked up
Removed autolock when switching from USB/AC power to battery power
Removed unnecessary/redundant logging, so the log files will not grow too fast when debugging enabled
Only InvalidateClock when really necessary
Added GSENSOR option to only execute commands when locked (CmdOrientationWhenUnlocked=1)
Added Capacitive Sensor option to only execute commands when locked (CapacitiveCommandsWhenUnlocked=1)
Only poll for the GSENSOR and CapacitiveSensor when needed (e.g. all empty GSENSOR commands, or only commands when locked)
Close GSENSOR and CapacitiveSensor when going into a deep sleep and open them at awake (maybe that solves some of the reported problems?)
Added logging to pinpoint possible problems with the GSENSOR and capacitive sensor
CPU usage is back to 0.0% CPU when unlocked, even when logging is enabled
Version 2.3 (15-02-2009)
To fix/avoid the reported problems people had with version 2.2.7:
Removed the foreground subclassing method
Poll the capacitive sensor directly outside the Window thread (more responsive now and under control of TLP)
Poll the GSensor directly outside the Window thread (more responsive now and under control of TLP)
Now you can suspend the phone without pressing the power button, using the Capacitive Swipes and GSensor orientation changes!
Green capacitive swipes up for UNLOCK
Green capacitive swipes down for LOCKSCREEN
Blue capacitive swipes left or right for LOCKSUSPEND
But of course you can configure other (external) commands
Version 2.2.7 (08-02-2009)
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.
Added Exception handling in TouchLockAction for initializing a form and saving the settings and show this to the user if it occurs
Made it possible to configure larger max values for Time values via TouchLockAction, e.g. StylusOutInToggleTime
Changed the recreation of the BattClock to default 5 seconds instead of 8 seconds.
Fixed the commandCallIncoming, commandCallConnected and commandCallEnded configuration, so they can be executed. Example: "TouchLockAction.exe" unlock
Fixed the setting change of Background/Foreground color is picked up immediately by TouchLockPro.
Fixed that in TouchLockAction.exe action command an explicit Exit command was needed
Version 1.9.2
Bug fix release:
When UseTAPI = 0 was selected, the device became slow
Version 1.9.1
Bug fix release:
Fixed problem that after an outgoing call the device would not lock anymore
Clock12 no longer shows 0 for hours, but 12
Added support for touching any area (4) and made CapacitiveTouchesSequence = 444 the default (old behaviour)
Made center button touches more sensitive
When you choose stripe in TouchLockAction, then the width will be set to 640 (actually the height), so the stripe is also shown nicely ion landscape mode
Changed the default setting into LockWhenIncoming = 0, because the default setting is already to lock at power on
TouchLockPro will wait 30 seconds after startup, to let the device initialize after boot, before loading the different dll's
Only write the time and battery, when the ClockHeight is greather than 8, so this is no longer done in stealth mode and stripe mode
Version 1.9
added TAPI support
added AppToDate support
show -1 when battery gives BATTERY_FLAG_UNKNOWN (so no 100% is shown)
fixed TouchLockAction Screen ClockBackground and ClockForeground
reset to default settings button added in Setting screen 1
added About Box with hyperlinks (so you can donate if you did not already ;-)
now in all occasions the input is enabled at power off/screen off, so all power on problems should be solved by this now (EnableInputAtSuspend setting)
LockWhenIncoming = 1; // lock when there is an incoming call
UnlockWhenConnected = 1; // unlock when call is connected
ScreenOffWhenConnected = 1; // screen off when call gets connected, to avoid presses with your ear
EnableInputAtSuspend = 1; // enable input at power off/screen off to avoid power on problems
UseStylus = 1; // when false, it will not react on stylus changes
UseTAPI = 1; // when false, TAPI will not be loaded
DateDDMM = 0; // show date in DD-MM instead of battery percentage
DateMMDD = 0; // show date in MM-DD instead of battery percentage
StylusOutDisablesLockMode = 1; // stylus out disables lock mode, yes or no
SuspendOnStylusIn = 1; // stylus in suspends the phone, when locked
SuspendTimeOutPowerOn = 30000; // suspend when the phone is locked and the suspend time has expired
CommandCallIncoming // command to execute at incoming call
CommandCallConnected // command to execute at connected call
CommandCallEnded // command to execute at ended call
CapacitiveTouchesSequence = 222 // now you can configure the sequence order of area 1, 2 and 3 to unlock. More/less than 3 touches is possible. So you can also use this as a security unlock, if you disable the other unlock possibilities, including the UseStylus.
Version 1.8
Fixed the "Power On" button problems
Completed the Configuration settings in TouchLockAction program (Second row, first icon)
Changed settings via TouchLockAction are automatically picked up by TouchLockPro
When Soft Reset icon in TouchLockAction is pressed, a confirmation is asked to avoid accidently soft resets
Unlock at suspend, when "AutoLockOnPowerOn=1" is set
Taking the Stylus out now disables the LockMode, so putting the Stylus in will not lock anymore
Note that StylusOut/In within (configurable) 1 second still locks the device.
When locking via TouchLockAction screen (LockScreen, row 1, first icon) or via Stylus Out/In method, the light sensor unlocking and suspend on backlight is temporarily disabled, till the next lock.
Added source code, so others can also learn and use ideas (please share your source code too, so we get wonderful programs for our phones and learn from each other).
Version 1.7 WIP2
Not for all the problems were gone. So this is my next attempt for solving the problems.
Several measures/improvements have been done:
Revisited the state changes for Power Off/On/Suspend
WIP version of settings screens (second row, first icon) in TouchLockProAction. Press the accept button on a setting screen to save them. TouchLockPro will automatically pick up the changes settings.
Added settings VibratesLock and VibratesUnlock
No longer set PowerPolicyNotify PPN_UNATTENDEDMODE, to catch power off events
Suspend via simulation Power off button instead of SetSystemPowerState POWER_STATE_SUSPEND
Different locking mechanism for "LockTouchPanelOnly = 1". With this mechanism I do no longer need to reapply the lock regularly.
I do not know if this works for all phone variants (e.g. CDMA), so please TEST!
Only disable input immediately at resume
Nice TouchLockAction icons, provided by MysticGenius (the settings are not available yet, so this button is disabled)
The default settings are written in the registry, when they are not there (used by Settings screens in TouchLockAction)
Because I did not have those Power button problems, I would be glad to hear if the problems are solved (or less frequently). Be careful, I did not extensively test, but I am sure you will.
Version 1.7 WIP
I have tried to solve the problems some people encounter with the fact that pressing the power button not always wakes up the device.
Several measures/improvements have been done:
No longer set PowerPolicyNotify PPN_UNATTENDEDMODE, to catch power off events
Suspend via simulation Power off button instead of SetSystemPowerState POWER_STATE_SUSPEND
Different locking mechanism for "LockTouchPanelOnly = 1". With this mechanism I do no longer need to reapply the lock regularly.
I do not know if this works for all phone variants (e.g. CDMA), so please TEST!
Only disable input immediately at resume
Nice TouchLockAction icons, provided by MysticGenius (the settings are not available yet, so this button is disabled)
The light sensor is closed when the phone gets unlocked
The default settings are written in the registry, when they are not there (as part of the upcoming Settings screens in TouchLockAction)
Because I did not have those Power button problems, I would be glad to hear if the problems are solved (or less frequently). Be careful, I did not extensively test, but I am sure you will.
Version 1.6
Added TouchLockAction screen
Fixed BattClock position with negative ClockX value and switching to landscape/portrait (ScreenWidth can be configured too now)
Added configuration item for 12 hours clock
Made it possible to configure the number of touches for unlock to be 2 (CapacativeTouchesToUnlock)
Disable hardware keys too on power off, when AutoLockOnPowerOn is enabled
Make it possible to unlock using the capacitive sensor when the backlight is off
Version 1.5
Open/Close capacitive sensor back on main thread (suspect problems with LockTouchPanelOnly = 1)
Vibrate on a background thread (so the main thread is not blocked)
Removed the flashing behaviour when using LockIndicator = 0
Now the locked window is also recreated when the backlight is off (people reported that it took some time to get the capacitive touches, and it seems to be related with their Windows Mobile setting for the backlight)
Removed listening to PBT_POWERSTATUSCHANGE (no action behind that one in TouchLockPro)
Show the version in the debug logging
Tried to better support LockTouchPanelOnly = 1
But the same applies as to what I already said in version 1.2:
Please be careful with the non-default setting LockTouchPanelOnly = 1. I tested with Opera and Home screen, and did a lock after it has been started. When Opera gets FullScreen, I constantly pressed the non-full screen button on the right-bottom corner. And sometimes, it reacted on my presses on the TouchPanel. The CALL-COMING-IN screen is not a FullScreen application, so I do not know if this small accidently press problem also occurs there, although on CDMA devices it does not seem to work. Please let me/others know your experiences, when you use this setting. I keep myself on the safe side, with the default LockTouchPanelOnly = 0.
Version 1.4
Easier capacitive unlock, because touching another area does not reset to 0
Close the light sensor when the screen is off, so it does not consume extra battery/CPU
Reverted back to SuspendOnBackLightOff = 1, so if it awakes in you pocket, it will go to Suspend earlier
Open the capacitive sensor and light sensor not on the main thread, to keep responsive UI
Improved LockTouchPanelOnly locking behaviour (BUT people are reporting this no longer works, so use a previous version if you want to overrule LockTouchPanleOnly = 1) In the mean time I will try to find a solution.
When the capacitive sensor and/or light sensor cannot be loaded, then continue with the appropriate feature disabled (maybe it works now on Touch HD)
Added possibility to have debug logging in case of problems (LogDebug and LogDebugDetailed setting, see post #3)
Total internal redesign to avoid race conditions
Version 1.3
Introduced auto-unlock by the Light Sensor in not too dark conditions
UnlockOnLightSensorTime = 5000 ms is the default time before the Light Sensor will unlock when it senses light
So that is the (default) time you have, when taking the phone out of your pocket/Pouch, before you may accidently press hardware keys and/or TouchPanel.
UnlockOnLightMinimumValue = 1 is the default minimum light level it will react on.
Made SuspendOnBackLightOff = 0 the default behaviour, because the light sensor will mostly unlock the phone anyway
Added settings ClockLockActiveTime = 8000 ms, so you can control how often it is recreated
Made the capacitive touches react quicker at Power On (previously it could take 5 seconds)
Fixed the BattClock showing weird with setting "LockIndicator = 0"
Removed StylusAlwaysControl settings, because it is not useful anymore
Version 1.2
renamed setting AutoLockOnPowerOff into AutoLockOnPowerOn
With this setting the hardware keys and touchpanel are locked immediately after PBT_RESUME message
When going to suspend the hardware keys and touchpanel are unlocked, to avoid the problem with the Power On button
Made Vibration = 0 the default, because this saves battery and we trust the phone will be locked at PowerOn
Changed the recreation of the lock clock from once per 4 seconds into once per 8 seconds (less CPU, more time to triple touch)
Made available setting LockTouchPanelOnly.
Please be careful with the non-default setting LockTouchPanelOnly = 1. I tested with Opera, and did a lock after it has been started. When Opera gets FullScreen, I constantly pressed the non-full screen button on the right-bottom corner. And sometimes, it reacted on my presses on the TouchPanel. The CALL-COMING-IN screen is not a FullScreen application, so I do not know if this small accidently press problem also occurs there. Please let me/others know your experiences, when you use this setting. I keep myself on the safe side, with the default LockTouchPanelOnly = 0.
Version 1.1
Added AutoLockOnPowerOff
Removed the flashing of the BattClock, when locked (although I still need to switch/recreate the 2 clocks)
Version 1.0
First version integrated with Stylus(BattC)lock 1.6
triple touch capacitive hardware area to unlock
Made the clock accurate within 1 second (compared to StylusLock)
