[Windows Mobile Apps and Games] ZuinigeRijder:
TouchLockPro is not exactly new (currently at version 1.9), but it was posted in the Diamond thread, because there things started. But because other phones are also supported, maybe the TouchLockPro thread could move to here. If this cross posting is not wanted, I hope the moderators let me know how to continue. At the Diamond thread or in this one?

But Windows Mobile has an OEM screen locker!

Yes, Windows Mobile locks the screen, but unlocks the Answer and Ignore buttons as soon as a call rings, so it is useless. The same happens when any notification pops up, the Snooze and Dismiss buttons are enabled even when screen is locked, leaving them vulnerable to any accidental touch.

Supported phones (known)

Touch Diamond

Touch Pro

Sprint CDMA Diamond

Touch HD (only triple touch capacitive sensor for unlock does not work)

Summary

There are already a lot of applications to disable touchpanel and/or hardware keys for the Touch Diamond and Pro. I added yet another one:

* lock using the Power button, BattClock and/or Stylus Sensor

* auto-unlock by the Light Sensor

* unlock using triple touch of the Capacitive Sensor

* unlock using Stylus Sensor

* unlock when on AC/USB power

Why is TouchLockPro better than other locking solutions

TouchLockPro is designed not to interfere with running applications and is a multipurpose locking application. Other locking solutions are often specific for locking only incoming calls/SMS. A lot of locking solutions also place a (transparant looking) Window on top of the running application (e.g. slide 2 unlock), so the information of the background application is no longer visible. This is not the case for TouchLockPro, so it can be kept lean and mean. Also the used resources is very very low.

Does TouchLockPro use much battery, RAM, CPU

Not at all, TouchLockPro is designed to be lean and mean!

TouchLockPro does not have noticeable effect on battery life. It only uses 33 Kb RAM in memory, whereas other solutions often use much more. For example S2U2 uses 4 Mb (125 times more) and PocketShield 1.7Mb (50 times more) memory. TouchLockPro uses 0% CPU (check it with a task manager!) and is totally event driven. Polling is kept to a minimum (currently only for polling once per second the light sensor when LOCKED and the screen is on). Requested features which would violate the "lean and mean" principle are rejected. Note that larger UI related stuff is done in a separate TouchLockAction.exe (e.g. editing settings), so the memory is only used when that program is active for a small moment.

Which other solutions exist

This is a list of other solutions, which may suit you better:

* Built in locking of Windows Mobile

* Stylus(BattC)lock

* Get A Reward! Create A "answer Only With Hw Buttons" Option!

* S2U2

* PDAVIET's dialer

* CSDEVCTRL

* SensorLock

* Answerkeys Disabler

* PocketShield

* ThrottleLock

Interested in *FREE* TouchLockPro?

I just posted TouchLockPro version 1.8.

I also posted the source code belonging to version 1.8. Hope you will learn something from it and you are inspired to make great programs too. At the end programming Windows Mobile is not so difficult if you have programming experience. Prerequisites for programming:

* Visual Studio, Express editions are free!

* Windows Mobile 6 Professional SDK (also free)

Note that others pointed out, that Express editions are not suitable for Windows Mobile development. See Smart Development for what is supported by which version. I used myself Visual Studio 2008 Professional SP1.

Note that TouchLockPro is written in C++ and TouchLockAction in C# (and deployed using .NET Framework 2.0).

Enjoy the software and source code :rolleyes: