Attend XDA's Second Annual Developer Conference, XDA:DevCon 2014!
5,809,924 Members 45,005 Now Online
XDA Developers Android and Mobile Development Forum

Development stopped: [APP][15-7-2011] TouchLockPro 2.12.9 Final release

Tip us?
 
ZuinigeRijder
Old
(Last edited by ZuinigeRijder; 21st January 2012 at 09:41 PM.) Reason: Development stopped
#1  
ZuinigeRijder's Avatar
Retired Recognized Developer - OP
Thanks Meter 205
Posts: 2,854
Join Date: Jun 2008
Unhappy Development stopped: [APP][15-7-2011] TouchLockPro 2.12.9 Final release

PayPal > USD / EUR
All the details and downloads of TouchLockPro you can find here: http://touchlockpro.sourceforge.net





Youtube video


Changelog

Version 2.12.9 (15-7-2011) for all Windows Mobile touchscreen phones
- Added Czech translations, thanks to oldasuk
- Updated translations provided by BattClock users, including Greek, Hebrew and Polish

Version 2.12.8 (1-4-2010) for all Windows Mobile touchscreen phones, *NEW* Proximity sensor support for Samsung and HTC having proximity sensor
- Updated Russian translations, thanks to Vadim Bogaiskov

Version 2.12.7 (30-3-2010) for all Windows Mobile touchscreen phones, *NEW* Proximity sensor support for Samsung and HTC having proximity sensor
- Fixed problem that the Proximity Lock command was not always executed due to screen off

Version 2.12.6 (25-3-2010) Updated translations
- Translations updated with new Excel spreadsheet containing all translations Russian translations, thanks to Vadim Bogaiskov
- Chinese Simplified translations, thanks to zhongzw
- Chinese Traditional translations, thanks to victorchen101
- Spanish translation, thanks to animalote
- French translations, thanks to YoLoLo
- Italian translations, thanks to tigro11 and ephestione
- Norwegian translations, thanks to longice
- Dutch translation, thanks to myself ;)

Version 2.12.5 (15-3-2010) for all Windows Mobile touchscreen phones, *NEW* Proximity sensor support for Samsung and HTC having proximity sensor
- Updated Chinese Traditional (thanks to victorchen101)
- Updated Chinese Simplified (thanks to zhongzw)
- Do not use HTCLockAPIWhenBluetoothActive when no call
- Added option to disable Zoombar

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:

Show Battery percentage, temperature and Current above the top bar.
- 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
- Show CPU also if it getidletime is greater than 100

Version 2.12.2 (20-2-2010) for all Windows Mobile touchscreen phones, *NEW* Proximity sensor support for Samsung and HTC having proximity sensor
  • Do not do !SCREENON at end call, when (lock)suspend is configured as command at end call
  • InCallTweak: do also for landscape, for right handed people

    Proximity changes:
  • CmdProximityNear, default !IDLE
  • CmdProximityNotNear, default !UNLOCK
  • CmdProximityOnBluetooth, default empty
  • Time proximity change configurable (ProximitySensorTime)
  • Added !PROXIMITYDISABLE command
  • Added !PROXIMITYENABLE command

    Taken over BattClock 1.8.1 improvements:
  • Added option to show CPU usage percentage
  • Color of CPU info configurable
  • CPU indicator configurable (default %)
  • Thresholds for Battery and Free memory separate configurable

    Extra commands:
  • Added !HOME command: add option to automatically go to the home screen when locked (Security)
  • Added !SOFTRESET command
  • Added !POWEROFF command
  • Added !UP command
  • Added !DOWN command
  • Added !LEFT command
  • Added !RIGHT command

Version 2.12.1 (14-2-2010) for all Windows Mobile touchscreen phones, *NEW* Proximity sensor support for Samsung and HTC having proximity sensor
Note that I could only test myself by simulating the Proximity Sensor via Stylus Sensor and Capacitive NavSensor. Please report if it is working!
  • Add support for proximity sensor
  • Proximity sensor Unlock when no object is nearby for approximate a second.
  • Proximity sensor option to do ScreenOff when detecting an object nearby for approximate one second
  • Proximity sensor option to disable proximity sensor when not locked
  • Proximity sensor option to disable proximity sensor when bluetooth is active

Version 2.11 (7-2-2010) for all Windows Mobile touchscreen phones
  • Fix: Do not do InCallTweak when not on battery or Bluetooth is active
  • Take over BattClock 1.6 and 1.7 standalone features in TouchLockPro
  • Added option to show info divided into 3 lines
  • Added option to see free memory
  • Date and Time color separate configurable
  • Option font color to be dependent on the battery/memory status
  • Add icon possibility as background and draw info on top of it, good for people having not a solid color or nicer looking icon alike
  • Added settings BattClockInfo1, BattClockInfo2, BattClockInfo3, BattClockVersion, MemoryIndicator, LowThreshold, MediumThreshold, LowColor, MediumColor, HighColor
  • Fontsize per info line configurable, text room is divided dependent on fontsize settings.
  • Option to show free memory in MB instead of %
  • Make BattConfig more finger friendly

Version 2.10.5 (2-2-2010) for all Windows Mobile touchscreen phones, *NEW* with Samsung SDK compatible Light Sensor and GSensor support
Version 2.10.4 (29-1-2010) for all Windows Mobile touchscreen phones, *NEW* with Samsung SDK compatible Light Sensor and GSensor support
Version 2.10.3 (10-1-2010) for all Windows Mobile touchscreen phones, *NEW* with Samsung SDK compatible Light Sensor and GSensor support
Version 2.10.2 (4-1-2010) for all Windows Mobile touchscreen phones, *NEW* with Samsung SDK compatible Light Sensor and GSensor support
Version 2.10.1 (3-1-2010) for all Windows Mobile touchscreen phones, *NEW* with Samsung SDK compatible Light Sensor and GSensor support
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.
  • Added BootDelay registry key, if you want to change it, you need to do that via the registry, but be sure to know what you are doing. Default it is 60000 (60 seconds)

Version 2.9 (17-12-2009) for all Windows Mobile touchscreen phones, *NEW* ZoomBar unlock
Thanks to Cobaltikus for providing the solution!
  • Added ZoomBar unlock for Touch Diamond 2 and Touch Pro 2
  • Slide the Zoombar left or right to unlock
  • Triple touch the Zoombar to unlock, if you want different behaviour, change CapacitiveTouchesSequence (CapacitiveTouchesSequence = 222)

Version 2.8.2 (09-11-2009) for all Windows Mobile touchscreen phones
Version 2.8.1 (28-10-2009) now with improved GSENSOR and for all Windows Mobile touchscreen phones
Version 2.8 (27-10-2009) now with improved GSENSOR and for all Windows Mobile touchscreen phones

Version 2.7.6 (06-10-2009) now with InCallTweak and for all Windows Mobile touchscreen phones
More detailed info of the changes can be found here.


See here for QuickStart and Features

Number of AppToDate Users:


Many thanks to Dennis van de Sande, alias MR_Q, who has sponsored/donated for more than a year zuinigerijder.com website and domain. New location: touchlockpro.sourceforge.net
PayPal > USD / EUR
 
ZuinigeRijder
Old
(Last edited by ZuinigeRijder; 21st December 2008 at 04:48 PM.) Reason: Refer to new website
#2  
ZuinigeRijder's Avatar
Retired Recognized Developer - OP
Thanks Meter 205
Posts: 2,854
Join Date: Jun 2008
Default Screenshots

See my new website for the screenshots
 
ZuinigeRijder
Old
(Last edited by ZuinigeRijder; 21st December 2008 at 04:49 PM.) Reason: Refer to new website
#3  
ZuinigeRijder's Avatar
Retired Recognized Developer - OP
Thanks Meter 205
Posts: 2,854
Join Date: Jun 2008
Cool Overrule Settings

See my new website for the settings
 
ZuinigeRijder
Old
(Last edited by ZuinigeRijder; 21st December 2008 at 04:52 PM.) Reason: new website
#4  
ZuinigeRijder's Avatar
Retired Recognized Developer - OP
Thanks Meter 205
Posts: 2,854
Join Date: Jun 2008
For future use
 
ZuinigeRijder
Old
(Last edited by ZuinigeRijder; 21st December 2008 at 04:52 PM.) Reason: new website
#5  
ZuinigeRijder's Avatar
Retired Recognized Developer - OP
Thanks Meter 205
Posts: 2,854
Join Date: Jun 2008
another one for future use.
 
ZuinigeRijder
Old
(Last edited by ZuinigeRijder; 21st December 2008 at 04:51 PM.) Reason: Refer to new website
#6  
ZuinigeRijder's Avatar
Retired Recognized Developer - OP
Thanks Meter 205
Posts: 2,854
Join Date: Jun 2008
Default Version History

See new website for the version history
 
NLS
Old
#7  
NLS's Avatar
Senior Member
Thanks Meter 45
Posts: 2,381
Join Date: May 2005
Location: Piraeus
Great job!

My only (stupid?) concern is that by using your (otherwise nice) "BattClock" we miss custom battery indicators.

You will say that, then we should disable this. But then (a) you still get it when device is locked (why we HAVE to see the valid taps after we get used to them?) and (b) you have one less method to lock the device from the very few: just two - i.e. one left.

This comes to the second thing. Why not also lock it with other method?
I can think of: (a) Touching the capacitive area one right, one middle (action button), one left.... in fact you could even UNLOCK by doing the opposite. (b) Using some program shortcut (for some of us is enough to lock the device by running a shortcut in TF3D or some today manager like SPB Pocket Plus or even changing a default action in TF3D via SSMaPa)...

The best way would be to still use the area of the battclock but WITHOUT changing whatever the user has there (is there such a thing like a transparent window?)...

Another way would be to auto-lock after some timeout (which in fact is also the most common method among smartphones too) or configurable if the power button is pressed.

For example in my case pressing the power button to sleep the device exactly means I don't want the screen functioning (so lock it if something else turns it on - like a call), while if I leave the device to sleep by timeout, I probably mean I have it on my desk and don't care or need to lock it.

Sorry for the brainstorm, I hope it gives you some ideas.
NLS
*** I WANT YOUR SERVICE initiative ***
My Blog

Devices: (many in the past, still in possesion the following) HTC Touch Pro 6.5.3 NRG, HTC HD2 (RULEZ) 6.5.3 Artemis, Samsung Galaxy Note (magic).

USE FORUM SEARCH! USE GOOGLE SEARCH!

Also: THIS guy is unbelievable! (in a bad way)
 
fl4r3
Old
#8  
Senior Member
Thanks Meter 27
Posts: 294
Join Date: Feb 2008
Seems to be working fine so far....but I have one problem;
I'm using wisbar so your battery indicator does not show on the screen when the phone is unlocked. This means I have to lock the phone by using the stylus. The indicator does however appear when the phone is locked.

Is there no way to correct this, or make a shortcut for locking instead?
 
at10ti0n
Old
#9  
Senior Member
Thanks Meter 1
Posts: 144
Join Date: Jan 2007
can i set this app to only lock the screen on incomming phone call and unlock it by tapping 3 times on the capacitive area?

something like the answerkeys disabler did before uninstalling...
 
ZuinigeRijder
Old
#10  
ZuinigeRijder's Avatar
Retired Recognized Developer - OP
Thanks Meter 205
Posts: 2,854
Join Date: Jun 2008
Quote:
Originally Posted by NLS View Post
Great job!

My only (stupid?) concern is that by using your (otherwise nice) "BattClock" we miss custom battery indicators.
You can position the BattClock over the Windows Start logo, at the left side of the Start bar. You can still go to Programs, just by pressing the Start text then.

Quote:
Originally Posted by NLS View Post
You will say that, then we should disable this. But then (a) you still get it when device is locked (why we HAVE to see the valid taps after we get used to them?) and (b) you have one less method to lock the device from the very few: just two - i.e. one left.
Yes, the BattClock must be visible AND have focus to get the capacitive touches. So moving to another position is the only option, if you want to use the triple touches approach to unlock.

Quote:
Originally Posted by NLS View Post
This comes to the second thing. Why not also lock it with other method?
I can think of: (a) Touching the capacitive area one right, one middle (action button), one left.... in fact you could even UNLOCK by doing the opposite. (b) Using some program shortcut (for some of us is enough to lock the device by running a shortcut in TF3D or some today manager like SPB Pocket Plus or even changing a default action in TF3D via SSMaPa)...
I can only get keyboard/sensitive touches when my battClock has focus. And when there is another program in front, I cannot get them.

I am working on an Action screen addin for TouchLockPro. It will be activated by pressing the BattClock OR you can start the program by a shortcut, because it is a separate program. But be patient, working on that......I even want it possible by other programs to lock the device, just by writing some registry key.

Quote:
Originally Posted by NLS View Post
The best way would be to still use the area of the battclock but WITHOUT changing whatever the user has there (is there such a thing like a transparent window?)...
To my knowledge, there is no real transparant window possible, you can just not draw the background. But the underlying windows will not update. Or does someone know this is possible?

Quote:
Originally Posted by NLS View Post
Another way would be to auto-lock after some timeout (which in fact is also the most common method among smartphones too) or configurable if the power button is pressed.

For example in my case pressing the power button to sleep the device exactly means I don't want the screen functioning (so lock it if something else turns it on - like a call), while if I leave the device to sleep by timeout, I probably mean I have it on my desk and don't care or need to lock it.

Sorry for the brainstorm, I hope it gives you some ideas.
That would be something for my new Action screen program. I will think about your suggestions. Thansk for the ideas and comments.

Tags
capacitive, lock, pocketshield, sensor, stylus, touch
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes